BSOD playing Skyrim, error 0x0000007A

Page 1 of 2 12 LastLast

  1. Posts : 9
    Windows 7 Home Premium 64bit
       #1

    BSOD playing Skyrim, error 0x0000007A


    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.
    Attachment 194972
    Last edited by Zeybrin; 25 Jan 2012 at 14:07. Reason: attach zip
      My Computer


  2. Posts : 28,845
    Win 8 Release candidate 8400
       #2

    Zeybrin said:
    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.
      My Computer


  3. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #3

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

    Attached to original post.
      My Computer


  4. Posts : 28,845
    Win 8 Release candidate 8400
       #4

    Zeybrin said:
    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.

    RAM - Test with Memtest86+



    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:
    Code:
    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
      My Computer


  5. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #5

    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.

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

    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.
    Last edited by Zeybrin; 26 Jan 2012 at 03:58.
      My Computer


  6. Posts : 28,845
    Win 8 Release candidate 8400
       #6

    Zeybrin said:
    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.

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

    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 [URL]https://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
      My Computer


  7. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #7

    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.
      My Computer


  8. Posts : 28,845
    Win 8 Release candidate 8400
       #8

    Zeybrin said:
    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
      My Computer


  9. Posts : 9
    Windows 7 Home Premium 64bit
    Thread Starter
       #9

    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!
      My Computer


  10. Posts : 28,845
    Win 8 Release candidate 8400
       #10

    Zeybrin said:
    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}
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:27.
Find Us