Custom PC, Working several weeks, Sudden BSOD on any game

[v3rdict]

"STOP: 0X0000007E"

Just built a new PC only a couple weeks ago. I don't have much on it, simply because I wish to use it as a gaming rig. The two programs I use most often is FF14 and SWTOR.

Initial problem (which may be the root):

When I got my disc for the OS, I got it through a discount program with my University. I installed Windows and the key wouldn't work. It was late, so I continued. I downloaded SP1, THEN called tech support. They said run the installer again to 'upgrade' Windows. I did, only to find out that with the SP on it, it was past the 'version of Windows' than was on the disk. Knowing that this would cause...'some' problems, I removed SP1, then was able to validate Windows. This caused a few minor problems, with drivers being the main issue, and one error at shut down (BtvStack.exe- exception unknown software exception (0x000070a) occurred the application at location 0x7751d009). But I fixed the driver issues (just not that uncommon shut down error).

When it started:

The BSoD memory dump screen first started when I downloaded Everquest 2. I played it for years, then stopped. Thought it would be a good benchmark to see where my computer was at. This was, of course, after playing Final Fantasy 14 and SW:TOR after only a few weeks without issue. Played for only 15 minutes, then on switching to character, BSOD. Tried another game, and after character select, it gave me two minutes before it gave another BSOD. I uninstalled EQ2 and of course the error is still around.

That day, I also added two old, smaller fans to experiment on an air flow theory.

System Specs:

Windows 7 Pro 64bit SP1
Intel i7 2600 (Sandy Beach) - Coolmaster Hyper 212 EVO Heatsink and fan
ASUS p8Z68 motherboard
16GB Corsair Vengeance DDR3
2 EVGA Geforce GTX560Ti in SLI
Patriot SSD 120GB. I ran a code to see if garbage collection was working, and it said yes (learned it from Newegg)


MISC.:

Nothing else of note. Using my 42" TV as a monitor...

CPU only ran to 70oC once (for less than five seconds), then put a new heat-sink and never runs above 50oC, if that. Not sure on Graphics, Motherboard might be a bit warm.

System Health Report says I don't have Anti-Virus...but I'm running AVG Free.

 

[JMH]

View attachment 199765


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


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

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



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.

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

 

[v3rdict]

Removed AVG, replaced with Windows Security Essentials, another BSoD.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF880055AB708
BCP3: FFFFF8802446A790
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

New file uploaded. I...don't have a blank CD anywhere, so I'm going to try booting it with a USB drive, starting with one stick. Assuming those tests pass, I'll try the Driver test.

 

[zigzag3143]

Removed AVG, replaced with Windows Security Essentials, another BSoD.

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033

Additional information about the problem:
BCCode: 3b
BCP1: 00000000C0000005
BCP2: FFFFF880055AB708
BCP3: FFFFF8802446A790
BCP4: 0000000000000000
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

New file uploaded. I...don't have a blank CD anywhere, so I'm going to try booting it with a USB drive, starting with one stick. Assuming those tests pass, I'll try the Driver test.

Related to VirtuWDDM.sys LucidInterop WDDM Driver from Lucidlogix Inc. I would at least to test

Dont forget verifier & memtest!!