Solved Clevo P170EM random BSOD ntoskrnl.exe

[timduke985]

Ok, I got a BSOD after driver verifier had been running for 11 hours. It wouldn't create a dump file, so I just powered off and rebooted. I took a picture of the bluescreen before I powered off. Is it possible that driver verifier could cause a BSOD on an otherwise stable system???

View attachment 259272

 

[x BlueRobot]

http://www.sevenforums.com/tutorials/174459-dump-files-configure-windows-create-bsod.html

Make your it has been configured for a Minidump, and you may want to check this directory to:

C:\Windows\Minidump

 

[timduke985]

I give up! I keep getting the same memory corruption bsod. Gonna send it in for warranty repairs. I'm probably gonna end up getting a divorce if I spend much more time trying to fix this thing, (LOL). I really appreciate all the help, time, and effort the two of you have given me!

 

[x BlueRobot]

Your welcome.

 

[timduke985]

Hey guys, I decided to follow the procedure for singling out bad sticks of ram, and the first one I checked had numerous errors on Memtest86+! Removed the bad stick of ram, and have had driver verifier running since 11 pm last night (16 hours so far) , no problems at all. Gonna wait the full 24 hours with driver verifier running, I really think the stick of ram was the problem!

 

[x BlueRobot]

That's good to know, seems the RAM may have been causing some issues, please keep us informed.

 

[timduke985]

Well folks, my computer has been running driver verifier for 37 hours now with no blue screens or other errors. I have a replacement ram stick on the way. I'm gonna disable verifier, reboot, and consider this case CLOSED!!! Again, thanks for the help! I learned an awful lot about diagnosing errors from you guys.

 

[x BlueRobot]

Thanks for the feedback, and glad to help!