Recurring BSOD

Hello,

I bought a new PC 2 months ago. On the 1st week, it started to do some BSOD. I then reinstalled my video card drivers and was able to be stable for ~1 week. Then the BSODs were back. I then ran memtest86+ for more than 32 hours on my 4x4GB sticks of RAM. I thought one stick was bad, but it seems I was wrong. I took off one stick and it looked better, but it was only an illusion again... one week later the BSOD were back. Now, I just had 5 BSOD in a row... and this thing is killing me... I can't find where it's coming from... (also need to mention, my PC was overclocked to 4.2ghz, I put it back to its regular clock speed and it didn't fix anything)

My computer specs:
Windows 7 Pro 64bit (legit MSDNAA)
Intel Core i7-2600K 3.4GHz CPU
ASUS P8Z68-V LE Motherboard
16GB (4x4G) Patriot DDR3 1600MHz
Crucial M4 256GB SATAIII 2.5" SSD (CT256M4SSD2)
Seagate Barracuda 1TB 7200.12 3.5" SATA III 6GB/S 32MB Cache 7200RPM
Sapphire Radeon HD6950 2G DDR5 DIRT3 EDITION

The BSOD seems to be happening when new stuff or old stuff is getting added/removed from the ram. Example: If I close a game that been running for a very long time on my system, it is likely to crash. Or..it often crash when I have a lot of tabs open on chrome, I get some memory errors and few seconds later it BSOD.

I attached the "Windows_NT6_BSOD_jcgriff2 folder" as mentioned in the recommended posting instructions. There are a good amount of crash dumps in there, I hope they can help to find the problem.

Thank you for your time and support.

Edit: I don't think it matters much, but the OS is installed on the SSD.

These crashes were caused by memory corruption/exception (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 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 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.

Any errors are indicative of a memory problem.

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

RAM - Test with Memtest86+



Driver verifier

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.

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

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 "Special Pool", "Force Pending I/O Requests" and "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.

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.

Avast can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST


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

Microsoft Security Essentials - Free Antivirus for Windows

zigzag3143 said:

[B]
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 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.

Any errors are indicative of a memory problem.

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

Like I mentioned in the OP, I previously ran memtest for more than 32 hours.

I first ran the test with 16gb for ~3 hours and obtained no errors.
Then I ran the test with 16gb again for 10hours and got those errors:


Then I ran a test for 7 hours again on 8gb, got no errors
And on the other 8gb for 7 hours and also got no errors.

Then..after I moved all the ram around, I ran the test on 16gb for ~10 hours again and got no errors.

Would that suggest that one of my motherboard slot is faulty ?

JHM said:

Avast can be a contributing cause of BSOD'S .
Please remove and replace with Microsoft Security Essentials AT LEAST TO TEST

Will do.


Thanks again.

To narrow it down to either ram or mobo take one known good stick and re-run memtest using it in each mobo slot.