Random BSODs with new build, unable to pinpoint cause

I've switched the gpu to a different port. Will keep you updated as to what happens.

For post #34 step #8.
If the BIOS was not yet reset please reset the BIOS.

See if you can post images of the voltages.

zbook said:

For post #34 step #8.
If the BIOS was not yet reset please reset the BIOS.

Yes the bios was reset and has since been reset again when I installed the latest bios update.

See step #9 in post #34.
When available please post an image into the thread.

zbook said:

See step #9 in post #34.
When available please post an image into the thread.

Those images are attached in post #35

Okay.
The voltages are within 5%.

Well, I had another crash today. I've attached the logs and linked the memory dump. So again this crash is only occurring after the pc goes idle for some time. The gpu is in a different slot and it is a different gpu from before. At this point I'm really not sure if this is a software issue, or if I need to look at replacing the motherboard or possibly the power supply...

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.


Edit: To add a little more context that might help troubleshoot.... For about the past two days I had no crashes, even when I left the PC on all night. However, the monitor wasn't going off even though it was set to turn off after 20 minutes. I believe some background program may have been keeping the pc awake. I had no crashes during this time. I went and closed a few of the programs I had left opened and changed the monitor to shut off after 1 minute. The monitor shut off maybe 2 times and resumed ok, but then the pc locked up again the 3rd time. It appears that this crash only occurs when the pc is idle and the monitor shuts off. Then it can't resume properly. I've tried disabling the HDD timeout and the PCIe Link State Power Management in the power settings to troubleshoot. I will see if it still crashes now, although I'm pretty stumped as to the cause...

1) The memory dump displayed two drivers in the crash with bugcheck EA.

2) The AMD GPU drivers were in the stack and appeared in the running command.

3) Uninstall CPU-Z software during the troubleshooting process.
The software can be reinstalled after the completion of the troubleshooting.

4) Temporarily turn off Windows updates of non-Microsoft drivers:
Enable or Disable Driver Updates in Windows Update in Windows 10 | Tutorials

5) Uninstall everything AMD using Display driver uninstaller and install new drivers from the AMD website.

6) On the AMD web site be sure the "clean install" box is checked and only install the graphics driver.

7) Install a driver older than: 25.20.15021.1007

Official Display Driver Uninstaller DDU Download

Display Driver Uninstaller Download version 18.0.0.8 (or newer version if available)

Display Driver Uninstaller: How to use - Windows 7 Help Forums

AMD Drivers and Support for Radeon, Radeon Pro, FirePro, APU, CPU, Ryzen, desktops, laptops

How to Install Radeon™ Software on a Windows® Based System | AMD

8) There is a tool that can be used to find misbehaving drivers.

9) The computer already has Macrium in use

10) Make sure that the Macrium image is up to date and that the image is on a different disk drive (not another partition on the same disk drive)

11) Make a brand new restore point:
Create System Restore Point in Windows 10 | Tutorials

12) Read this link on Windows driver verifier:
Enable and Disable Driver Verifier in Windows 10 | Tutorials

13) Make sure that you understand the methods to turn off and recover from using the tool after a BSOD.

14) The computer may become sluggish and the boots may become slow while using the tool.

15) Plan to use the tool for 48 hours and after the last BSOD for an additional 36 hours.

16) After any BSOD:
a) run the BETA log collector and post a new zip into the thread
b) open file explorer > this PC > C: > in the right upper corner search for C:\windows\memory.dmp > if the file size is < 1.5 GB then zip and post a separate share link into the thread using one drive, drop box, or google drive

Code:

STACK_TEXT:  
fffff109`b3e98ab8 fffff805`0e42a790 : 00000000`000000ea ffffcb08`8af09080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff109`b3e98ac0 fffff805`0e42a86a : fffff109`b3e98b98 fffff805`1555c934 fffff109`b3e98b98 00000000`00000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x40
fffff109`b3e98b30 fffff805`154cb764 : ffffcb08`7ea65000 00000000`00000000 fffff109`b3e98c80 fffff805`1555c920 : dxgkrnl!TdrTimedOperationDelay+0xca
fffff109`b3e98b70 fffff805`154c12f3 : fffff109`00000011 00000000`00000000 fffff805`15866370 fffff109`00000200 : atikmdag+0x6b764
fffff109`b3e98bf0 fffff805`1555c7c9 : fffff109`b3e98cd1 00000000`00000000 00000000`000007d0 00000000`00000063 : atikmdag+0x612f3
fffff109`b3e98c30 fffff805`1556487e : 00000000`000007d0 00000000`00000095 ffffcb08`80c4b004 00000000`00000200 : atikmdag+0xfc7c9
fffff109`b3e98d20 fffff805`15565397 : 00000000`00000200 ffffcb08`80c4b004 fffff109`b3e98ee9 fffff805`154be466 : atikmdag+0x10487e
fffff109`b3e98d70 fffff805`155608c6 : fffff109`b3e98e38 ffffcb08`80c4b004 00000000`00000000 00000000`00000000 : atikmdag+0x105397
fffff109`b3e98dd0 fffff805`1556071a : ffffcb08`80c4b004 ffffcb08`80c64004 ffffcb08`7fac0018 00000000`00000000 : atikmdag+0x1008c6
fffff109`b3e98e00 fffff805`16b21b4e : ffffcb08`7f98d134 fffff109`b3e98ee9 00000000`00000206 00000003`00000030 : atikmdag+0x10071a
fffff109`b3e98e30 fffff805`16ad8e8c : 00000000`00000001 ffffcb08`80c64004 ffffe100`00000001 00000000`00000000 : atikmdag+0x16c1b4e
fffff109`b3e98e90 fffff805`16aeb608 : ffffcb08`7fac0010 ffffcb08`80c64004 00000000`00000001 00000000`00000206 : atikmdag+0x1678e8c
fffff109`b3e98f50 fffff805`154dc7c3 : fffff109`b3e990b0 fffff109`b3e99160 00000000`00000000 ffffcb08`7faf78a0 : atikmdag+0x168b608
fffff109`b3e98ff0 fffff805`16515da4 : 00000000`00000001 00000000`00000000 ffff8980`0ffefcf0 fffff805`04df71ac : atikmdag+0x7c7c3
fffff109`b3e99060 fffff805`165159b9 : 00000000`00000001 00000000`00000000 fffff109`b3e995f0 00000000`00000004 : atikmdag+0x10b5da4
fffff109`b3e99230 fffff805`15512a39 : ffff643b`a527ce6a fffff805`15455063 00000000`00000000 fffff109`b3e995f0 : atikmdag+0x10b59b9
fffff109`b3e99400 fffff805`1548d23a : fffff109`b3e995f0 fffff109`b3e995f0 00000000`00000000 ffffcb08`786a5a80 : atikmdag+0xb2a39
fffff109`b3e99430 fffff805`0fb8a758 : ffffcb08`7ea64040 fffff109`b3e995f0 ffffcb08`8af09402 ffffcb08`7f81dd10 : atikmdag+0x2d23a
fffff109`b3e99480 fffff805`0fb7a413 : ffffcb08`88e88cc0 00000000`00000000 00000000`00000001 fffff805`0e3f9b3f : atikmpag+0x1a758
fffff109`b3e994b0 fffff805`0fbddd9a : ffff8980`27e0dd40 ffffcb08`80d70000 00000000`00000001 ffffcb08`80d70000 : atikmpag+0xa413
fffff109`b3e994e0 fffff805`0e50b8be : 00000000`00000001 ffff8980`27e0dd40 ffffcb08`80d70000 00000000`00000026 : atikmpag+0x6dd9a
fffff109`b3e99510 fffff805`0e5b2b30 : ffffcb08`8af09080 00000000`00989680 000000be`78d4bef3 ffff8980`0ffefcf0 : dxgkrnl!DXGADAPTER::DdiQueryAdapterInfo+0x15e
fffff109`b3e995d0 fffff805`0e5cbc2a : ffffcb08`8af09080 ffffcb08`00000000 00000000`00989680 00000000`20206f49 : dxgkrnl!DXGADAPTER::GetNodePerfData+0xec
fffff109`b3e99660 fffff805`0e5cb66b : 00000000`00000000 00000000`00000000 00000000`00000020 00000080`0143dff0 : dxgkrnl!DxgkQueryStatisticsInternal+0x5b2
fffff109`b3e99aa0 fffff4e9`1c3167b1 : 00000080`0143df70 00007ffa`00000004 00007ffa`00000038 00000000`00000000 : dxgkrnl!DxgkQueryStatistics+0xb
fffff109`b3e99ad0 fffff805`049dd685 : ffffcb08`8af09080 00000080`0143dfc8 fffff109`b3e99ad8 ffffcb08`8759b590 : win32kbase!NtGdiDdDDIQueryStatistics+0x11
fffff109`b3e99b00 00007ffa`b49a5544 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000080`0143dbf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`b49a5544

Code:

9: kd> !running -t

System Processors:  (000000000000ffff)
  Idle Processors:  (000000000000fdff)

       Prcbs             Current         (pri) Next            (pri) Idle
  9    ffffe100f3b08180  ffffcb088af09080 ( 9)                       ffffe100f3b18400  ................

 # Child-SP          RetAddr           Call Site
00 fffff109`b3e98ab8 fffff805`0e42a790 nt!KeBugCheckEx
01 fffff109`b3e98ac0 fffff805`0e42a86a dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x40
02 fffff109`b3e98b30 fffff805`154cb764 dxgkrnl!TdrTimedOperationDelay+0xca
03 fffff109`b3e98b70 fffff805`154c12f3 atikmdag+0x6b764
04 fffff109`b3e98bf0 fffff805`1555c7c9 atikmdag+0x612f3
05 fffff109`b3e98c30 fffff805`1556487e atikmdag+0xfc7c9
06 fffff109`b3e98d20 fffff805`15565397 atikmdag+0x10487e
07 fffff109`b3e98d70 fffff805`155608c6 atikmdag+0x105397
08 fffff109`b3e98dd0 fffff805`1556071a atikmdag+0x1008c6
09 fffff109`b3e98e00 fffff805`16b21b4e atikmdag+0x10071a
0a fffff109`b3e98e30 fffff805`16ad8e8c atikmdag+0x16c1b4e
0b fffff109`b3e98e90 fffff805`16aeb608 atikmdag+0x1678e8c
0c fffff109`b3e98f50 fffff805`154dc7c3 atikmdag+0x168b608
0d fffff109`b3e98ff0 fffff805`16515da4 atikmdag+0x7c7c3
0e fffff109`b3e99060 fffff805`165159b9 atikmdag+0x10b5da4
0f fffff109`b3e99230 fffff805`15512a39 atikmdag+0x10b59b9
10 fffff109`b3e99400 fffff805`1548d23a atikmdag+0xb2a39
11 fffff109`b3e99430 fffff805`0fb8a758 atikmdag+0x2d23a
12 fffff109`b3e99480 fffff805`0fb7a413 atikmpag+0x1a758
13 fffff109`b3e994b0 fffff805`0fbddd9a atikmpag+0xa413
14 fffff109`b3e994e0 fffff805`0e50b8be atikmpag+0x6dd9a
15 fffff109`b3e99510 fffff805`0e5b2b30 dxgkrnl!DXGADAPTER::DdiQueryAdapterInfo+0x15e
16 fffff109`b3e995d0 fffff805`0e5cbc2a dxgkrnl!DXGADAPTER::GetNodePerfData+0xec
17 fffff109`b3e99660 fffff805`0e5cb66b dxgkrnl!DxgkQueryStatisticsInternal+0x5b2
18 fffff109`b3e99aa0 fffff4e9`1c3167b1 dxgkrnl!DxgkQueryStatistics+0xb
19 fffff109`b3e99ad0 fffff805`049dd685 win32kbase!NtGdiDdDDIQueryStatistics+0x11
1a fffff109`b3e99b00 00007ffa`b49a5544 nt!KiSystemServiceCopyEnd+0x25
1b 00000080`0143dbf8 00000000`00000000 0x00007ffa`b49a5544

Code:

atikmdag.sys Tue Feb 12 18:05:12 2019 (5C635F38)
atikmpag.sys Tue Feb 12 17:55:45 2019 (5C635D01)

Code:

Name	AMD Radeon (TM) R7 360 Series
PNP Device ID	PCI\VEN_1002&DEV_665F&SUBSYS_E258174B&REV_81\6&33F1E177&0&0020020B
Adapter Type	AMD Radeon Graphics Processor (0x665F), Advanced Micro Devices, Inc. compatible
Adapter Description	AMD Radeon (TM) R7 360 Series
Adapter RAM	(2,147,483,648) bytes
Installed Drivers	C:\WINDOWS\System32\DriverStore\FileRepository\u0339148.inf_amd64_044b2a0aaee39cbb\B339146\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0339148.inf_amd64_044b2a0aaee39cbb\B339146\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0339148.inf_amd64_044b2a0aaee39cbb\B339146\aticfx64.dll,C:\WINDOWS\System32\DriverStore\FileRepository\u0339148.inf_amd64_044b2a0aaee39cbb\B339146\amdxc64.dll
Driver Version	25.20.15021.1007
INF File	oem6.inf (ati2mtag_R505 section)
Color Planes	Not Available
Color Table Entries	4294967296
Resolution	2560 x 1440 x 60 hertz
Bits/Pixel	32
Memory Address	0xE0000000-0xF07FFFFF
Memory Address	0xF0000000-0xF07FFFFF
I/O Port	0x0000EF00-0x0000EFFF
Memory Address	0xFE100000-0xFE4FFFFF
IRQ Channel	IRQ 4294967245
Driver	c:\windows\system32\driverstore\filerepository\u0339148.inf_amd64_044b2a0aaee39cbb\b339146\atikmpag.sys (25.20.15021.1007, 577.11 KB (590,960 bytes), 2/13/2019 11:19 AM)

Ok, I've uninstalled all the amd stuff and reinstalled only the gpu driver version 25.20.15003.5010 (no radeon settings, no chipset drivers etc.) Backups are current and driver verifier is running with the recommended settings. Let's see how this goes...

Edit: I also reverted the power setting changes I made earlier to eliminate some possible variables.

The settings for Windows driver verifier can be modified.
All non-Microsoft drivers should be tested simultaneously.

If there is no significant sluggishness with 3 simultaneous tests then increase the number of simultaneous tests by 4 - 5 each hour so that there are approximately 19 simultaneous tests:

Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community