|08 Jul 2011||#2|
| || |
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program.
Boot from the CD, and leave it running for at least 5 or 6 passes.
Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot.
Test the sticks individually, and if you find a good one, test it in all slots.
I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).
In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .
Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.
Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).
If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
|My System Specs|
|09 Jul 2011||#3|
| || |
I had run Memtest before posting with all 16Gb of Kingston HyperX coming out clean, so I jumped straight to Verifier. After setting it up, my PC was BSoD'ing right at the log in screen pointing to gdrv.sys, something I already knew was counter-productive to OC'ing.
During the original install, I was fairly certain I had chose to not install the Gigabyte Power Saving utility, while still installing ET6 and a few other of the utilities off the original MoBo CD. Somehow it still ended up there. After several attempts to remove it from my system with no luck, I blew out the install and did a fresh one without using the MoBo CD and used drivers from the manufacture websites. As of right now I am running clean and clear with no OC'ing.
I have set a new restore point with the fresh install, and I am about to begin installing my games. I will update as I get things reinstalled and stress test the GPU's. Thanks for all the help thus far.
*edit* After letting the system run over night, I had one error pop up. Windows System Assessment Tools had crashed.
|My System Specs|
|Similar help and support threads for2: Multiple BSoD's|
|Multiple BSOD's with multiple errors occuring randomly||BSOD Help and Support|
|Multiple BSOD's with multiple reasons||BSOD Help and Support|
|BSOD errors. multiple times during multiple programs||BSOD Help and Support|
|bsod constant errors, restarting ,multiple bsod||BSOD Help and Support|
|Multiple BSOD with multiple errors. Pls help me!||BSOD Help and Support|
|Multiple BSOD, Multiple STOP errors||BSOD Help and Support|
|Multiple BSOD at Random Times with Multiple Drivers Identified||BSOD Help and Support|
|Our Sites ||Site Links ||About Us ||Find Us |
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.
© Designer Media Ltd
All times are GMT -5. The time now is 12:36 AM.