Windows 10: 37 Crashes from Wide Range of Error Codes (0x0d1, 0x00a, 0x0109)
Well, it has been a full day, and no crashes. Even doing the normal things to cause a crash. So, it looks like it was just a driver issue
That has to be a bug with memtest86+. 360Mhz instead of 1796Mhz is enormous so unlikely to be accurate.
Also agree your ram and system board look good.
Sure hope so. If it runs clean for a week I'll feel a lot better about it.
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
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 did a teardown of my Windows 10 machine to clean all the parts and do some cable management and when I reassembled and restarted I had some issues. It started with a corrupted RAM BSOD, so I cleaned the connector pins on the RAM sticks with...
FYI - The list of error codes for Windows 10 setup
Read more: http://winaero.com/blog/the-list-of-error-codes-for-windows-10-setup/#Error0x0000005C
Hopefully this is the correct subforum to post this in. If it is not could somebody point me to the correct one?
I am using THIS guide here on tenforums.
When I try to dump the stack I input the command dps ffffd00026876000...
I updated my 8.1 Pro laptop to 10 Pro a couple of weeks ago, and so far I really like what I see.
The only nasty bit about W10 so far has been these BSODs happening every once in a while. After the first few I decided I might need...
I updated from windows 7 the day that 10 launched and for a few days everything worked perfectly, then I crashed a few times, and today I crashed three times, all for different reasons.
The first crash was a kernell_data_inpage_error. I did...