Solved Continuous BSODs

[TheShining]

I need some help with my constant BSODs. My computer seems to crash every hour.

Specs:
OS: Windows 7 Professional x64
CPU: AMD Phenom II x6 1090t
Motherboard: Gigabyte 990XA-UD3
Memory: G.Skill DDR3-1600 4gb x 2
GPU: PNY GeForce GTX 560 Ti OC1 SLI
HDD: 2 Tb WD Caviar Black
SSD: Kingston SSDNow V+100 2.5" 96GB
PSU: Antec HCG-750 watt

 

[zigzag3143]

I need some help with my constant BSODs. My computer seems to crash every hour.

Specs:
OS: Windows 7 Professional x64
CPU: AMD Phenom II x6 1090t
Motherboard: Gigabyte 990XA-UD3
Memory: G.Skill DDR3-1600 4gb x 2
GPU: PNY GeForce GTX 560 Ti OC1 SLI
HDD: 2 Tb WD Caviar Black
SSD: Kingston SSDNow V+100 2.5" 96GB
PSU: Antec HCG-750 watt

All of these were memory exceptions caused by a driver and my bet is your Avast.

I would remove and replace it with Microsoft security essentials at least to test.


http://files.avast.com/files/eng/aswclear5.exe

Virus, Spyware & Malware Protection | Microsoft Security Essentials




If you want to confirm first you can run these two tests but they take substantially longer to test.



1-Memtest. 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.



2-Driver verifier

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/Win7 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.

 

[TheShining]

Thanks. I'll try Memtest and get rid of avast after seeing the results.

 

[TheShining]

I didn't remove avast but when I tried to use memtest I ended up with 500k+ errors with each ram in every slot.

 

[zigzag3143]

I didn't remove avast but when I tried to use memtest I ended up with 500k+ errors with each ram in every slot.

Guess that might be the problem. Are you overclocking?

Could be the ram or the mobo.

 

[TheShining]

I just tried putting another ram that passed the test on another computer. It failed in every slot in my motherboard. I'm guessing that means my motherboard is the problem. Also, I'm not overclocking anything but I am underclocking my GPU using easy tuner 6 to conserve energy since I'm not sure if my power supply could handle two 560 Ti

 

[TheShining]

I am not currently overclocking and I just recently changed my motherboard and still have the same problems here is a link to a new thread with new info and new dmp
http://www.sevenforums.com/crashes-debugging/181704-still-more-bsods.html