Excessive BSODs, different errors every crash

[Philosophy6]

System specs:
Windows 7 64-bit Home Premium OEM
AMD Phenom II X4 965 CPU 3.40 GHz
8 GB DDR3 RAM
EVGA GTX 570

The operating system I currently have is about 3 or 4 months old, and my motherboard, CPU, and graphics card are no more than 7 months old. My two 2 GB memory modules are a few years old, and just a week ago I added another 4 GB module and a bigger fan to my case. I haven't had a blue screen on this operation system until several days after I installed the new memory module, but I was experiencing them as much now as I was on my last install of Windows 7. Eventually it got to the point where I would get BSODs every time I would login, which is why I bought an OEM version of Windows and installed that. Now I'm getting blue screens randomly, usually when watching a video or playing a game but sometimes simply on websites. There isn't one STOP error either, they seem to be different every time.

 

[JMH]

These crashes were caused by memory corruption/exception (Cx05) probably a driver.
Please run these two tests to verify your memory and find which driver is causing the problem.

* If you are overclocking anything reset to default before running these tests.
In other words STOP!!!

* If you have a Raid update its Driver.



Memtest.

*Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Memtest86+ - Advanced Memory Diagnostic Tool

*Boot from the CD, and leave it running for at least 5-7 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.

Any errors are indicative of a memory problem.

If a known good stick fails in a motherboard slot it is probably the slot.

http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html






Driver Verifer

Using Driver Verifier is an iffy proposition.
Most times it'll crash and it'll tell you what the driver is.
But sometimes it'll crash and won't tell you the driver.
Other times it'll crash before you can log in to Windows.
If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable 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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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).

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.


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.

Thanks to JGriff2 & Usasma.

Using Driver Verifier to identify issues with Windows drivers for advanced users

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[zigzag3143]

These were related to memory corruption as JMH suggests. In addition to her suggestions you may want to remove AVG at loeast to test as it is known to cause BSOD's on some systems

I note you have AVG.
AVG can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Download tools and utilities | AVG Worldwide


Microsoft Security Essentials - Free Antivirus for Windows

 

[Philosophy6]

Yesterday I ran memtest86 and found a lot of errors with my memory. Just now I decided to remove the new memory module and run the test again. The test is almost finished and I have received no errors so far. I will try the driver verifier too, but it appears the RAM module is most likely the problem, I will come back if I still get BSODs but I don't think I will. Also I bought the module from BestBuy, is it likely that it was already bad or that I may have busted something when installing the module?

 

[zigzag3143]

Yesterday I ran memtest86 and found a lot of errors with my memory. Just now I decided to remove the new memory module and run the test again. The test is almost finished and I have received no errors so far. I will try the driver verifier too, but it appears the RAM module is most likely the problem, I will come back if I still get BSODs but I don't think I will. Also I bought the module from BestBuy, is it likely that it was already bad or that I may have busted something when installing the module?

No ways to tell, but I believe BB does warranty the ram. (call them to be sure)