BSOD 3 Time - Playing Bc2 with fraps

Hello, i just custom built a gaming computer specs:

Gigabyte GA-990FXA-U3H
AMD Phenom II X6 1090T - 6 Core 3.2 GHz
Patriot G2 8 GB 1333
WD Caviar Black 1.5 TB 7200 RPM
Windows 7 Ultimate 64-Bit (6.1, Build 7601
AMD Radeon 6970

Everything but the 6970 is new. The 6970 isn't the problem because on my old build i never got these BSODs.

First 1-3 Days I ran Bc2 fine VERY fine, with fraps recording 3.4.5 no BSOD.

Then on the 4th day i installed Fraps version 3.4.6 and I kept getting BSOD while running bc2! I uninstalled it and installed the old version 3.4.5 and i didn't crash at all. Now i went afk for a while, when i cam back i moved my mouse screen went from black to desktop then it crashed. (first it shows like lines at the top of screen horizontally and then it crashed to BSOD)
0x0000001e (2times)
0x0000003b (1 time)
Right now I disconnected my Remote Control Infrared Sensor and my computer randomly restarting, so maybe that will be the problem but just in case I'm still posting this. - Kevin

perphection said:

Hello, i just custom built a gaming computer specs:

Gigabyte GA-990FXA-U3H
AMD Phenom II X6 1090T - 6 Core 3.2 GHz
Patriot G2 8 GB 1333
WD Caviar Black 1.5 TB 7200 RPM
Windows 7 Ultimate 64-Bit (6.1, Build 7601
AMD Radeon 6970

Everything but the 6970 is new. The 6970 isn't the problem because on my old build i never got these BSODs.

First 1-3 Days I ran Bc2 fine VERY fine, with fraps recording 3.4.5 no BSOD.

Then on the 4th day i installed Fraps version 3.4.6 and I kept getting BSOD while running bc2! I uninstalled it and installed the old version 3.4.5 and i didn't crash at all. Now i went afk for a while, when i cam back i moved my mouse screen went from black to desktop then it crashed. (first it shows like lines at the top of screen horizontally and then it crashed to BSOD)
0x0000001e (2times)
0x0000003b (1 time)
Right now I disconnected my Remote Control Infrared Sensor and my computer randomly restarting, so maybe that will be the problem but just in case I'm still posting this. - Kevin

Hi Kevin and welcome

These were caused by a memory exception. Please run these two tests to verify your memory and find which driver is causing the problem.


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.

RAM - Test with Memtest86+



2-Driver verifier

I'd suggest that you first backup your data 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.

Driver Verifier - Enable and Disable

I just got 4 more bsods....
this time a new one 0x0000007(idk the letter)
basically said the same thing that it was dumping something off physical memory

perphection said:

I just got 4 more bsods....
this time a new one 0x0000007(idk the letter)
basically said the same thing that it was dumping something off physical memory

With that many errors its asfe to say it is a memory issue. If this is under warranty I would call the mfr.

Thank you for your help, as today my computer is working perfectly. I RMAd my ram and its all good now! thank u! #1 forums for help