BSOD after fresh install of Windows 7 (while playing Battlefield 3)

[adamxatomic]

I was getting random BSOD while playing Battlefield 3 and decided to try a fresh install of Windows 7. The BSOD happened after 2 hours after the fresh install and the I only have Battlefield 3 and a handful of other programs installed.

The BIOS and all drivers are up to date. At first I thought it was because I have unmatched RAM (all 4 sticks are DDR3 1600, but 2 are PC10700 and the other 2 are PC12800). I ran 6 passes of memtest and it passes. Ran Windows memory diagnostic and it passed.

I've ran furmark for 2 hours to stress the GPUs and everything was ok. I then ran Prime95 to stress the CPU overnight and no BSOD. It only happened that one time.

My system specs are-
OS- Windows 7 Ultimate x64 OEM
CPU- AMD Phenom II 955 BE @3.6GHz 1.475v
Motherboard- Asus Crosshair IV Formula (3027 BIOS)
RAM- 4x2GB (8GB total) G.Skill Ripjaws DDR3 1600 (2x2GB PC10700 2x2GB PC 12800)
Graphic Card(s)- 2x XFX HD 6850 Crossfire (12.1 drivers 11.10 CAP)
Sound- Onboard X-Fi
Storage- OCZ Solid 3 120GB SSD 6Gb/s (boot drive) / 2TB Samsung F4 5400 RPM (system storage)
PSU- Cougar SX850 850W

I'm attaching dump files, and the System Health Report.
(It says that I have no anti-virus, but I'm using Microsoft Security Essentials.

 

[zigzag3143]

I was getting random BSOD while playing Battlefield 3 and decided to try a fresh install of Windows 7. The BSOD happened after 2 hours after the fresh install and the I only have Battlefield 3 and a handful of other programs installed.

The BIOS and all drivers are up to date. At first I thought it was because I have unmatched RAM (all 4 sticks are DDR3 1600, but 2 are PC10700 and the other 2 are PC12800). I ran 6 passes of memtest and it passes. Ran Windows memory diagnostic and it passed.

I've ran furmark for 2 hours to stress the GPUs and everything was ok. I then ran Prime95 to stress the CPU overnight and no BSOD. It only happened that one time.

My system specs are-
OS- Windows 7 Ultimate x64 OEM
CPU- AMD Phenom II 955 BE @3.6GHz 1.475v
Motherboard- Asus Crosshair IV Formula (3027 BIOS)
RAM- 4x2GB (8GB total) G.Skill Ripjaws DDR3 1600 (2x2GB PC10700 2x2GB PC 12800)
Graphic Card(s)- 2x XFX HD 6850 Crossfire (12.1 drivers 11.10 CAP)
Sound- Onboard X-Fi
Storage- OCZ Solid 3 120GB SSD 6Gb/s (boot drive) / 2TB Samsung F4 5400 RPM (system storage)
PSU- Cougar SX850 850W

I'm attaching dump files, and the System Health Report.
(It says that I have no anti-virus, but I'm using Microsoft Security Essentials.

It is much easier to find patterns, etc, when there are more than one crash. We prefer you wait until you have at least two so that if one is corrupt the other probably wont be.


Windows memory diagnostics does not stress the memory enough so we recommend Memtest


This on DMP is inconclusive


I suggest the following



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


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

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



2-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 (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.

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