Gets BSOD when playing games, BCCode: 1000007e

Hey.

I played BF3 earlier today, and suddenly my system closed down, and i've got a BCCode: 1000007e.
Meanwhile i was playin, i talk to some friends over Skype.

I've got the same BSOD a couple of times, the last two months, I built the computer in January 2012.
I had tried to reinstall Windows one time.
The other times when i got the BSOD, I was playing different games.

I ran a System Health Report, a couple hours ago. There i've got three device errors.
Win32_PnPEntity.DeviceID="ROOT\\SIDESHOW\\0000"
Win32_PnPEntity.DeviceID="ROOT\\SIDESHOW\\0001"
Win32_PnPEntity.DeviceID="ACPI\\NTN0530\\4&36293D96&0"
Doesn't have any drivers.

Where can i see which devices these are?


I've added:
Windows_NT6_BSOD_jcgriff2
and a screen picture of the error.

System specifications:

Windows 7 Enterprise Edition (64-bit) Service Pack 1 (Build 7601)
Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
Gigabyte GV-R695OC-1GD
Asrock z68 Extreme 3 Gen 3
Corsair Enthusiast Series TX650 V2
16GB Corsair Vengeance 1866MHz DDR3
Fractal Design Define R3
ASUS DRW 24B3ST
Edimax EW-7728In
Corsair H60
120GB OCZ Agility 3 Series
2 TB WD Caviar Black WD2002FAEX
Logitech G19
Samsung S23A700D
Logitech G500

Best reagards
zytex3

We do need the DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.

If you are overclocking STOP

You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.

To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.

The procedure:

* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.
* Zip up the copy.
* Attach the ZIP archive to your post using the "paperclip" (file attachments) button.
*If the files are too large please upload them to a file sharing service like "Rapidshare" and put a link to them in your reply.

To ensure minidumps are enabled:

* Go to Start, in the Search Box type: sysdm.cpl, press Enter.
* Under the Advanced tab, click on the Startup and Recovery Settings... button.
* Ensure that Automatically restart is unchecked.
* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).
* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.
* OK your way out.
* Reboot if changes have been made.

Here are the links:

https://rapidshare.com/files/4008519...3-2012__1_.png

https://rapidshare.com/files/3099723...D_jcgriff2.zip

Several issues



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

Other things that can cause BSOD'S

AsrAppCharger.sys
AsrVDrive.sy
Avast
FNETURPX.SYS (3+ years old)