In answer to the question "Still not solved. Will AMD ever respond?" Possibly if you ever ask them. Unfortunately if you think you are asking AMD in these forums that is not correct. These are USER to USER forums. You are not asking AMD, only other users like you for their input. In some rare cases one of the only 2 AMD mods, not driver development guys may get involved in a discussion. I'd say it's maybe a 1 in a 1oo chance. So if you need help from AMD you need to contact them the only way they allow us to and that is with a Support Ticket or Issue report. These are available in Radeon Settings, the contact page and or the driver download page.
Not sure how he gets 15 gb of ram unless you have miss matched modules. Seems like you would have to have a 1 gb module and I don't think that they even made a DDR 4 module that size. Maybe it is just that speccy is incorrect on the unknown thing it does this to me too. I don't doubt he would have issues if what speccy shows is accurate. Below is what speccy shows for mine and it shows unknown too and my ram is very common GSkill ram. Followed by what CPU-Z shows. Hope it helps clear things up.
It does clear things up a bit, but if you noticed, your SPECCY also indicates SPD and how many RAM Modules you have installed. The OPS doesn't indicated how many modules are installed and which DIMM socket like both of our does. The OPS SPECCY shows ZERO SPD Modules installed.
The only difference between your SPECCY and mine is the TYPE: in which in yours it shows Unknown but accurate amount of RAM MEMORY installed.
So, either the RAM MEMORY the OPS is bad in which one is showing less than the full amount or his motherboard is bad or his RAM MEMORY is incompatible with the Motherboard and Ryzen.
Thanks pokester for uploading your SPECCY showing your RAM.
The life of AMD. LOL. It's crashed less recently but still annoying.
As for the Speccy information.. I think it's just a bug in their software.
The system clearly recognizes 16 GB (https://i.imgur.com/21iYRyv.png )
I think it has possibly something to do with the RAM you choose honestly.
Here's microsoft's explanation: Bug Check 0x116 VIDEO_TDR_ERROR | Microsoft Docs
This is the RAM I've been using: CORSAIR Vengeance LPX 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 2666 (PC4 21300) Desktop Memory Model C...
I'm sure it's a microsoft + amd problem though.
The GPU is taking more time than permitted to display graphics to your monitor. This behavior can occur for one or more of the following reasons:
I got the same problem and I think I have it fixed
Few weeks ago I have overclocked my GPU portion to 1500 Mhz @ 1.168 V on GFX voltage, SOC + 0.0018 which means SOC is at
1.1698 V which is pretty safe
yesterday I wanted to go a liitle bit higher so I tried 1525 Mhz @ 1.181 GFX voltage, after 2 hours of playing Paladins I got TDR video failure so I dialed it back to 1500 Mhz @ 1.168.
I got my RAM to work Stable at 3200 Mhz 16 16 16 32 52 2T by using Ryzen DRAM calculator and put the timings manually, also DRAM voltage is @ 1.36 voltage.
What you want to try is: Set a fix voltage for the GPU portion of you don't wanna overclocked (btw getting the RAM to work on high frequency with tight timing is more important and beneficial for GPU performance.
my System is table now and this is how I confirmed it:
AIDA64: 11 Hours no problem
Memtest 86+: 10 Hours now problem
Resident evil 6 Benchmark tool: (Free download from Steam): let it run 10 times @ 1080p Max settings so I can stress the crap out of the GPU and those were the results:
5466, 5462, 5463, 5467, 5466, 5468, 5459, 5465, 5466, 5464 (those numbers are how many frames during the entire Benchmark.
CPU temp: Max 51c on AIDA64
VRM temp Max 47c on AIDA64
MOFset temp: During the heavy benchmark max 65c, During gaming like Paladins Max 58c
So try increasing the frequency on your GPU portion and pump a little bit of voltage there and you'll be fine.
Also give Ryzen DRAM calculator a shot, you'll be really happy more than you might think, I got 12-15% more performance by using the right and the tightest timing @ 3200 Mhz
Edit: one thing worth mentioning is the TDR delay in the registry key
once I had similar problem with another system and I found a way around it:
open AIDA64 and open the Stress test tool. uncheck all the options and then recheck CPU and GPU, if you got a message after checking GPU saying that the TDR delay is too low then click yes to let AIDA64 fix it and then reboot the system. Another option is to locate the key and set the value to 10 Decimal.
This Method worked for sure.
If you can't locate it please let me know I'll try to help you
Just an update: Bought ram on my motherboards QVL list and haven't blue screened for 3 weeks...
yap - Ryzen works well with good RAM
ps - Gigabytes Bios arent the best...
pps - try KETs BiosMods for Gigabyte X370 Boards - i use them on 3 different MoBos (GA-AX370-Gaming-5 + F4-3200C14D-16GVK DDR4-3200CL14 + 2600X 4.2GHz + RX580 4G && GA-AX370-Gaming-3 + F4-2400C15D-16GNT DDR4-2400CL15 + A6 9500 (will be replaced) + RX460 2G LP && GA-AB350N-Gaming-WiFi + F4-2400C15D-16GNT DDR4-2400CL15 + 2400G 4GHz)
I don't know if this has been covered but from personal experience with the problem, I concluded that it might be a problem with how much ram the system is taking or not taking. I own a 2200g and with intergrated graphics it only contains about 200mb of vram which is to be expected for intergrated graphics. Since it doesn't have very much vram typically it should take system memory which is way slower and may be why the error message video tdr failure pops up. I would run a game then open task manager to see that I had 4gb of available shared memory and my system was using none of it but this wasn't always the case when my game didn't crash the moment I opened it I would check task manager and it was in fact using the system memory fixing the problem for the couple hours I was on my pc but the next day the same issue would occur making it really unreliable. This may be a problem with system ram or a faulty apu if that is the case shame on amd. The only possible way I see this error being fixed is if you buy a dedicated graphics card with at least 2gb of vram. I suggest you take a look yourself and open task manager and decide for yourself if this is the problem I am not claiming this is the true explanation but it may be and hopefully this will help you.