BSOD playing Skyrim, error 0x0000007A

[Zeybrin]

Is Windows 7 . . . - x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes
- an OEM or full retail version? OEM
- What is the age of system (hardware)? Less than a month (Time i've had it anyway)
- What is the age of OS installation? have not reinstalled

Sometimes I will get BSOD's and other times I will get unexpected I/O errors from any program
That is running (wmplayer.exe, explorer.exe, various system EXE's) and then the system will just
auto restart and not actually crash.
View attachment 194972

 

[zigzag3143]

Is Windows 7 . . . - x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Yes
- an OEM or full retail version? OEM
- What is the age of system (hardware)? Less than a month (Time i've had it anyway)
- What is the age of OS installation? have not reinstalled

Sometimes I will get BSOD's and other times I will get unexpected I/O errors from any program
That is running (wmplayer.exe, explorer.exe, various system EXE's) and then the system will just
auto restart and not actually crash.

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.

 

[Zeybrin]

Forgot to actually click the attach button, kept clicking the arrow and wondering why the attachment wasn't showing up.

Attached to original post.

 

[zigzag3143]

Forgot to actually click the attach button, kept clicking the arrow and wondering why the attachment wasn't showing up.

Attached to original post.

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.

These crashes were caused by memory corruption (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!!!


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.

If that doesn't work, post back and we'll have to see about fixing the registry entry off-line:

Delete these registry keys to stop Driver Verifier from loading (works in XP, Vista, Win7):
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDrivers
        HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\VerifyDriverLevel

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

 

[Zeybrin]

Okay! I have run the Driver verifier and here is the dump file I have procured form its use.

Thank you deeply for the help thus far.

View attachment 195086

Edit: Also I did run the Memtest and my RAM passed it with 0 errors.

Edit 2: Here is another BSOD dump that I got, I think it had the same STOP code also. (yay consistent error!)

View attachment 195091

Also I got this BSOD in about the same amount of time without the Driver Verifier running, if that is anything of note.

 

[zigzag3143]

Okay! I have run the Driver verifier and here is the dump file I have procured form its use.

Thank you deeply for the help thus far.

View attachment 195086

Edit: Also I did run the Memtest and my RAM passed it with 0 errors.

Edit 2: Here is another BSOD dump that I got, I think it had the same STOP code also. (yay consistent error!)

View attachment 195091

Also I got this BSOD in about the same amount of time without the Driver Verifier running, if that is anything of note.

One verified one not and both related to wininit.exe (probably not the true cause) Lets run a system file check to verifiy the OS


I would also run a system file check to verify and repair the OS files


Run a system file check to verify and repair your system files.

To do this type cmd in search, then right click to run as administrator, then
SFC /SCANNOW

It may need to be run up to three times before successful
Let us know the results from the report at the end

Read here for more information http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Zeybrin]

Well I ran the scan 4 times just to be sure but, no integrity violations here Boss. Unless the SFC is a dirty liar.

I also ran the Memtest again last night whilst I was asleep.. ran 8 passes and 0 errors. Just to update.

 

[zigzag3143]

Well I ran the scan 4 times just to be sure but, no integrity violations here Boss. Unless the SFC is a dirty liar.

I also ran the Memtest again last night whilst I was asleep.. ran 8 passes and 0 errors. Just to update.

Good news. SO the OS and the ram is good. Now we wait for more bsod's

 

[Zeybrin]

Okay Boss, I'll get on that tonight after work... should have a whole slew of em for you by the morrow. Lol.

Thanks again!

 

[zigzag3143]

Okay Boss, I'll get on that tonight after work... should have a whole slew of em for you by the morrow. Lol.

Thanks again!

No worries. I am on for the next 18 hours {grin}

 

[Zeybrin]

So far I haven't had any luck, every time it has been crashing I haven't been getting a BSOD.. just an IO error and then the computer restarts. The computer must have crashed at least 8-10 times already. The couple of times I did get a BSOD, it froze and didnt give me a dump. I have even reactivated the Verifier to see if it would make it crash harder and give me a BSOD... but no luck.

Could it be my HDD Driver? Sometimes I also get very quick runtime errors before they disappear.

I mean it would have to be something that is specifically strained by high end gaming because that is the only time my computer crashes... I have the Verifier on right now... Not so much as a snag... Then again I guess high end gaming kinda puts more of a strain on everything...

any tips would be appreciated. This is getting disheartening.

Thanks in advance.

 

[zigzag3143]

So far I haven't had any luck, every time it has been crashing I haven't been getting a BSOD.. just an IO error and then the computer restarts. The computer must have crashed at least 8-10 times already. The couple of times I did get a BSOD, it froze and didnt give me a dump. I have even reactivated the Verifier to see if it would make it crash harder and give me a BSOD... but no luck.

Could it be my HDD Driver? Sometimes I also get very quick runtime errors before they disappear.

I mean it would have to be something that is specifically strained by high end gaming because that is the only time my computer crashes... I have the Verifier on right now... Not so much as a snag... Then again I guess high end gaming kinda puts more of a strain on everything...

any tips would be appreciated. This is getting disheartening.

Thanks in advance.

{Probably not the Hd driver (if there is one), more likely either an HD issue, or perhaps your malware app. One way to find out if it is software or hardware is a clean install. If the problem persists it is hardware if it goes it was software. At some point you may want to start thinking about it.

 

[Zeybrin]

Oh trust me.. it has crossed my mind. How should I go about a full clean install? reformat the drive and all that? Seeing as the computer is so new it really wouldnt be much of a loss if at all.. just back up a few save files and I am good to go.

Would the fact I have an SDD Intel rapid storage (currently set to a spare drive/inactive) make things more complicated?

 

[Zeybrin]

Update time!

Okay so I decided to do some thinking and I decided... the BSOD's are just a possible result of the actual problem.. not always the end result.. Most of the time the computer restarts after a I/O error... What would cause this? Well the thing that usually causes an I/O error cause it is the thing that is most used when it comes to Memory and I/O (Besides RAM) and that is the HDD.

After doing a clean install the error's were still happening. So like you said it must be the hardware. My HDD is a seagate.. and it just so happens that Seagate has some awesome tools for diagnosing your HDD. Upon the execution of said tools they failed my HDD. So now I am going to run the Bootable version of the software and hope that the tool can repair my poor HDD.

Only time will tell! I will keep ya posted.

 

[Zeybrin]

Weeell... Seatools didn't do anything for me. The program fails me in windows mode and passes me in DOS mode.. So I dunno...

View attachment 195987

Here is a dump file.. I will upload more as I get them. If I get them.. maybe I will be luckily unlucky tonight. -sigh-

 

[writhziden]

Try the following steps to fix hard disk or Windows file errors.

• Run Disk Check with both boxes checked for all HDDs and with Automatically fix file system errors checked for all SSDs. Post back your logs for the checks after finding them using http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
  
  
  
• Run http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html up to three times to fix all errors. Post back if it continues to show errors after the third run or if the first run comes back with no integrity violations.