Windows 10: BSODs at random times atikmdag.sys THREAD STUCK IN DEVICE DRIVER

Unfortunately I do not have one

 

Could you tell us what the 3.3v, 5v and 12v values are according to the BIOS.

 

3.344v 5.040v 12.096v

Shall I buy a PSU tester such as this one:
Xinda Atx power supply tester lcd display screen computer case power supply diagnostic tester:Amazon.co.uk:Computers & Accessories

 

PSU tester finally arrived.
I have tested and everything seems fine.

Attachment 137103

 

About a week ago someone who had/has the same BSOD (but different situation). At first it looked like the AMD drivers were causing issues, maybe they did, but the user ran driver verifier which revealed different BSODs with an entirely different cause, Avast.
I haven't heard back from him/her, so I'm not 100% sure if Avast truly was the cause, but since it is almost a week ago..

I don't know if you ran driver verifier, but before blaming the motherboard I would suggest to run driver verifier. Chance exists that it may reveal another driver causing issues.

How to enable driver verifier
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials
I would recommend to run driver verifier with the settings specified in the tutorial, and with the below settings
Code: STANDARD FLAGS: [X] (0x00000000) Automatic Checks [X] (0x00000001) Special pool [X] (0x00000002) Force IRQL checking [X] (0x00000008) Pool tracking [ ] (0x00000010) I/O verification [X] (0x00000020) Deadlock detection [ ] (0x00000080) DMA checking [X] (0x00000100) Security checks [X] (0x00000800) Miscellaneous checks [X] (0x00020000) DDI compliance checking ADDITIONAL FLAGS: [ ] (0x00000004) Randomized low resources simulation [ ] (0x00000200) Force pending I/O requests [ ] (0x00000400) IRP logging [ ] (0x00002000) Invariant MDL checking for stack [ ] (0x00004000) Invariant MDL checking for driver [X] (0x00008000) Power framework delay fuzzing [ ] (0x00010000) Port/miniport interface checking [ ] (0x00040000) Systematic low resources simulation [ ] (0x00080000) DDI compliance checking (additional) [ ] (0x00200000) NDIS/WIFI verification [ ] (0x00800000) Kernel synchronization delay fuzzing [ ] (0x01000000) VM switch verification [ ] (0x02000000) Code integrity checks [X] Indicates flag is enabled[/quote] Link to thread I'm talking about
Thread Stuck in Device Driver BSOD (when DotA is opened) - Page 2 - Windows 10 Forums

 

Link to thread I'm talking about
Thread Stuck in Device Driver BSOD (when DotA is opened) - Page 2 - Windows 10 Forums[/quote] I enabled it and restarted, but it wouldn't turn back on so I forced restarted. It showed Bad Pool Caller and mfesapsn.sys. I uninstalled McAfee Web Advisor as it may have something to do with that?

I've uploaded a new dump, if that helps *Smile

 

Just got a THREAD STUCK IN DEVICE DRIVER BSOD again:

 

Please keep driver verifier running, if there are more different BSODs with different drivers then the motherboard can be blamed.

 

Ok, will do.

 

I got another thread stuck in device driver BSOD, but the dump file is a bit different?

Should I try refreshing my PC?

 

It looks like the data from the last dump is corrupted, the dump doesn't even know what driver caused the crash.
Code: ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*G:\Symbols*Symbol information Symbol search path is: SRV*G:\Symbols*Symbol information Executable search path is: Unable to load image Unknown_Module_98f07de5`66c38714, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_98f07de5`66c38714 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_98f07de5`66c38714 Debugger can not determine kernel base address Windows 10 Kernel Version 15063 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 15063.0.amd64fre.rs2_release.170317-1834 Machine Name: Kernel base = 0xfffff801`5a40f000 PsLoadedModuleList = 0xfffff801`5a75b5a0 Debug session time: Wed May 31 16:02:40.185 2017 (UTC + 2:00) System Uptime: 0 days 0:04:14.826 Unable to load image Unknown_Module_98f07de5`66c38714, Win32 error 0n2 *** WARNING: Unable to verify timestamp for Unknown_Module_98f07de5`66c38714 *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_98f07de5`66c38714 Debugger can not determine kernel base address Loading Kernel Symbols . Loading User Symbols ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck EA, {ffffd70d6f142080, 0, 0, 0} ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. Unable to read KTHREAD address ffffd70d6f142138 Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner[/quote]

 

Shall I reset my pc to see if that makes any difference?

 

I'd recommend a clean install instead

 

Is there a way to do that without affecting secondary drives?

 

You'll want to remove the drives you don't want to affect.