BSOD While Playing Skyrim, BCC code 1000007e

[Shazbot]

Hey all, long time reader/browser, first time register and poster.

I had a BSOD playing Skyrim, I have a feeling it has to do with my software but I'd like a little direction in debugging. Crash report is as follows:

Additional information about the problem:
BCCode: 1000007e
BCP1: FFFFFFFFC0000005
BCP2: FFFFF880010249D5
BCP3: FFFFF88005DE5178
BCP4: FFFFF88005DE49D0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\050612-26457-01.dmp
C:\Users\User\AppData\Local\Temp\WER-31090-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Attached necessary files,

Running Windows 7 x64 on SSD (OEM)
8gb ram
gtx 570
AMD phenom 2 x6 1100t overclocked to 3.8hz - stable
Been running on above specs for about a year, purchased the PC a year ago. SSD added in later on, used Paragon Migrate to SSD software to copy over my OS



Thanks for the help,
Shazbot

 

[JMH]

Hello there Shazbot,

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

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

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"
NOTE: You can use Low Resource Simulation if you'd like.
From my limited experimentation it makes the BSOD's come faster.
- 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.

If you are using win 8 add these
- Concurrency Stress Test
- DDI compliance checking

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.

Thanks to JGriff2 & Usasma.

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

Driver Verifier

Using Driver Verifier (Windows Drivers)

 

[Shazbot]

Thanks JMH,

Currently burning Memtest86 to a disk, will run test 1 on stick 1 overnight, will follow up when I encounter errors/complete

And will then run Driver Verifier... although this makes me a little weary:
"If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier."
not sure how I'd do this.

Also, I cannot creat a system repair disk, I get "System repair disk could not be created. The parameter is incorrect. (0x80070057). Although I have my OEM installation, that'd do the trick as well no?

Anyways, that'll be my step after memtest so I'll proceed with the memtest for now.

Cheers

 

[JMH]

Shazbot one step at a time....
Do Memtest & let us know the results.

Then someone will be here to help you with Verifier.

 

[Shazbot]

Sounds good,

quick question, I have 4 ram slots, and 2 sticks of ram. For the sake of time, is it adequate to only test the slots I am using? I don't forsee myself using the other 2 slots for a long while anyways.

Done slot 1 stick 1 test 7 pass no errors, onto slot 2 stick 1.

Cheers

 

[Shazbot]

Alright, Memtest+ tests done, No problems with sticks or slots. Will do driver verifier after I do a backup to my new backup disk.

Now with regards to my question above regarding:

If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

How would this be done if I cannot get into windows?
Further, to access my backup on the internal disk would I need to have my windows installation disk handy?

I just want to be ready in case things don't go A-ok

Thanks

 

[zigzag3143]

Sounds good,

quick question, I have 4 ram slots, and 2 sticks of ram. For the sake of time, is it adequate to only test the slots I am using? I don't forsee myself using the other 2 slots for a long while anyways.

Done slot 1 stick 1 test 7 pass no errors, onto slot 2 stick 1.

Cheers

Just do the occupied slots.

Good news on memtest.

In hundreds (more likely thousands) of verifier runs maybe 10 have been problematic and we were able to get them working.

Be sure to have a restore point and a backup .

Ken