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???
Attachment 259272
Dump Files - Configure Windows to Create on BSOD
Make your it has been configured for a Minidump, and you may want to check this directory to:
Code:C:\Windows\Minidump
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!
Your welcome.
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!
That's good to know, seems the RAM may have been causing some issues, please keep us informed.
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.
Thanks for the feedback, and glad to help!
Quote