Windows 10: 37 Crashes from Wide Range of Error Codes (0x0d1, 0x00a, 0x0109)

So, should I mark it as solved for now, or wait a week, and then mark it?

 

Wait and see what happens.

 

Yea, glad I didn't close this thread. Got another crash, playing Call of Duty, World at War Zombies custom map from this page Cheese Cube Unlimited: Cube of Circles Page 1 - Releases - UGX-Mods.
However, it was a 0x07e bugcheck. Want me to upload the crash data on this thread, or start a new one? And by the way, I did not have the USB Network Adapter even attached at the time, so I know it didn't cause the crash.

 

I'll post them (There have been two more crashes. One when the PC was idle, and I wasn't there to see it, and the other when I shut down the PC. Almost thought the PC was going to crash EVERY time I shut it down, but it doesn't)
None of these crashes are constant, and I can't always cause them. They seem to occur as randomly as they want.

 

Neither dump had any useful info in it. Time to give Driver Verifier a try.

Driver Verifier is a diagnostic tool built into Windows 10, it is designed to verify both native Microsoft drivers and third party drivers. Driver Verifier's verification process involves putting heavy stress on drivers with the intention of making bad, outdated, incompatible or misbehaving drivers fail. The required result is a BSOD (Blue Screen of Death) which will generate a crash dump for debugging purposes.
Machines exposed to Driver Verifier will run very sluggishly due to the stress being applied to the drivers.

Driver Verifier - Enable and Disable in Windows 10

Warning:
It is not advised to run Driver Verifier for more than 48 hours at a time. Disable Driver Verifier after 48 hours or after receiving a BSOD, whichever happens soonest.

Always create a Restore Point prior to enabling Driver Verifier.

What we're looking for is a BSOD with a mini dump that will tell us what driver caused it.

 

Okay, Driver Verifier is running, pc didn't instantly crash, and I created a restore point ahead of time. All in all, everything seems to be going well

 

Hopefully you followed the directions, especially Part Two and set it up as directed.

 

I have a crash report. Bug Code 0x0A

 

Driver Verifier was setup correctly but the dump was not DV induced. It's another memory_corruption.

Did you ever validate the memory DIMM in slot 3 (you have slots 0 to 3 with 1 and 3 populated with identical nodules).

 

...I only have 2 slots. It says I have 4?

 

Also, I validated both DIMM, and both slots

 

Yes, the dump indicates 4 memory slots. Obviously wrong, I wonder why?

Code: [Memory Device (Type 17) - Length 34 - Handle 0025h] Physical Memory Array Handle 0023h Memory Error Info Handle [Not Provided] Total Width [Unknown] Data Width 64 bits Size [Not Populated] Form Factor 02h - Unknown Device Set [None] Device Locator Node0_Dimm0 Bank Locator Node0_Bank0 Memory Type 02h - Unknown Type Detail 0000h - Speed 0MHz Manufacturer Dimm0_Manufacturer Serial Number Asset Tag Number Part Number Dimm0_PartNum [Memory Device (Type 17) - Length 34 - Handle 0027h] Physical Memory Array Handle 0023h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 8192MB Form Factor 09h - DIMM Device Set [None] Device Locator Node0_Dimm1 Bank Locator Node0_Bank0 Memory Type 18h - Specification Reserved Type Detail 4080h - Synchronous Speed 1600MHz Manufacturer Undefined Serial Number Asset Tag Number Part Number 8GBH2X04E9992 [Memory Device (Type 17) - Length 34 - Handle 0029h] Physical Memory Array Handle 0023h Memory Error Info Handle [Not Provided] Total Width [Unknown] Data Width 64 bits Size [Not Populated] Form Factor 02h - Unknown Device Set [None] Device Locator Node0_Dimm2 Bank Locator Node0_Bank0 Memory Type 02h - Unknown Type Detail 0000h - Speed 0MHz Manufacturer Dimm2_Manufacturer Serial Number Asset Tag Number Part Number Dimm2_PartNum [Memory Device (Type 17) - Length 34 - Handle 002bh] Physical Memory Array Handle 0023h Memory Error Info Handle [Not Provided] Total Width 64 bits Data Width 64 bits Size 8192MB Form Factor 09h - DIMM Device Set [None] Device Locator Node0_Dimm3 Bank Locator Node0_Bank0 Memory Type 18h - Specification Reserved Type Detail 4080h - Synchronous Speed 1600MHz Manufacturer Undefined Serial Number Asset Tag Number Part Number 8GBH2X04E9992[/quote] Try running again with Driver Verifier enabled. See if anything shows this time.

Looked at one of the older dumps from Thu Jun 23 16:37:36. It indicates a problem with your video card/driver:
Code: ffffd001`639f7518 fffff800`9656c676Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys atikmdag+0x14c676[/quote] Looks like you have a AMD Radeon(TM) R7 Graphics. The driver is version 16.150.2211.0 dated 21-Mar-16 12:00:00 AM. 16.15.2211 is the latest version available. Do you know when you updated to that version?
You can try rolling back the driver from Device Manager, see if that makes a difference.

You can also try to stress test your GPU:

FurMark - GPU Stress Test - Windows 10 Forums

 

Okay, I will try to wipe AMD Graphics, because I can't get CCC to open up. Also, I have an APU, so not sure how I would stress-test something that I don't have. Or is the process the same?

 

FurMark doesn't mention APU at all so I don't know. You can try it, just monitor the temps and stop if they get to high. You would normally do this anyway.

You could try UNIGINE 3D Benchmark. I just downloaded and ran their Heaven Benchmark. My GPU temp stabilized at 69C:

Attachment 88550

Only ran for 4 minutes or so.

 

Got a recommendation for you to do the following from Arc, one of the BSOD Gurus here:

• Disable XMP, run the RAM at 1333 MHz.
• Remove a RAM stick from one slot, let the computer run with single channel memory.
• Make it sure that PNY XLR8 is listed in the Memory Support List.