KERNEL_DATA_INPAGE_ERROR BSOD 0x0000007a on Resume from sleep

Page 1 of 3 123 LastLast

  1. Posts : 260
    Windows 7 Ultimate 64bit
       #1

    KERNEL_DATA_INPAGE_ERROR BSOD 0x0000007a on Resume from sleep


    Hi all.

    This intermittent issue continues to cause system failure, on resume from (long) sleep.


    Hibernation is disabled.


    Details attached.


    SPEC: Win 7 Ultimate 64-bit, Dell XPS L502x


      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Code:
    ERROR_CODE: (NTSTATUS) 0xc000009d - STATUS_DEVICE_NOT_CONNECTED
    
    DISK_HARDWARE_ERROR: There was error with disk hardware
    Test your HDD using Seatools. SeaTools for DOS and Windows - How to Use

    Let us know the result.

    Also, free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

    1. Click on the Start button
    2. Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
    3. Select the “Startup” tab.
    4. Deselect all items other than the antivirus and teh touchpad driver, SynTPenh
    5. Apply > OK
    6. Accept then restart.

    Daemon Tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known BSOD causer. Uninstall Daemon Tools at first. Then download SPTD standalone installer from Disk-Tools.com, and execute the downloaded file as guided below :

    • Double click to open it.
    • Click this button only:
    • If it is grayed out, as in the picture, there is no more SPTD in your system, and you just close the window.
      My Computer


  3. Posts : 260
    Windows 7 Ultimate 64bit
    Thread Starter
       #3

    Thanks for the tips.

    I'm using the native virtualisation offered by Windows 7. I have several builds. Typically(!!), it's my fossil-build that DOESN'T exhibit this issue (ever).


    All builds use Daemon and the same 750G internal HD, making me think it's an OS config / device driver cause...


    Having said that, I wonder if this hotfix could resolve - You receive various Stop error messages in Windows 7 or in Windows Server 2008 R2 when you try to resume a computer that has a large SATA hard disk


    Will check my (old, working) build to see if that update's on there... brb!
      My Computer


  4. Posts : 260
    Windows 7 Ultimate 64bit
    Thread Starter
       #4

    tried to run the hotfix, it obtained the Windows6.1-KB977178-v2-x86 edition (not sure why x64 wasn't detected on download) spotted the all platforms link and just installed the hotfix...

    Now, interestingly, whilst glancing at the dm log collector report on the working OS, the installed hotfixes report doesn't mention that the other OS (that doesn't have this problem) has this hotfix installed.

    I'm very skeptical that this will resolve (my HD is only 750G for a start), but will try...


    Another report I found online identified a bad msahci.sys driver, fixed by installing newer intel rapid drivers or something... this sounds familiar. Prior to this, however, I think an SP(1) update will have to be tried...

    Status: Resolution #1 (hotfix Windows6.1-KB977178-v2-x64) being monitored....

    Thanks again!
      My Computer


  5. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #5

    I would say you again to take the suggestions and report accordingly.

    Dont find fixes abruptly.
      My Computer


  6. Posts : 260
    Windows 7 Ultimate 64bit
    Thread Starter
       #6

    That's very good advice. I wish I'd followed it.

    Currently unable to login, following restart. Stuck "preparing desktop" after installing kb977178.

    suspect a corrupted profile. I Mounted the volume, is it possible to sfc an offline volume, and will it detect user profile corruption?

    the ntuser.dat doesn't appear to have a .bak. not sure how to proceed.

    Only able to load windows in safe mode.
      My Computer


  7. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #7

    Sometimes it takes time to install an update.

    suspect a corrupted profile.
    It is not a profile, but something related to the HDD.

    You should have paid attention to my suggestions at first; before searching for online solutions. Every single BSOD is different from another one; there is no unique fix, mostly.

    If needed, uninstall the update in safe mode and continue from seatools test. Both the short and long test.
      My Computer


  8. Posts : 260
    Windows 7 Ultimate 64bit
    Thread Starter
       #8

    cannot login with existing or new account


    You're right again. The update took a long time, but it did complete. I closed all applications and restarted... and haven't been able to get in since (exc. using safe mode).

    Removed the hotfix, restarted, still unable to login. Created a new user account in safe mode using cmd (as the "user accounts" applet stops responding once you click "create new account"...) but I was unable to log into the new account or the old account. I'm talking > 30 minutes "preparing a desktop" (I think, with the new account, it didn't even get there... stuck @ "wait for User Profile Service..."

    Considering retiring that particular volume (new DAW with Reaper et al), I can quickly mount and collect any downloads/dox etc, and restart trying the fix the original, occasional annoyance that is the BSOD on resume from sleep. It's pretty goosed.
      My Computer


  9. Posts : 260
    Windows 7 Ultimate 64bit
    Thread Starter
       #9

    Ok, after breaking the new build by installing the hotfix, and attempting (to no avail) to system restore from safe mode / w. cmd prompt (the only way I could login to ANY account after restarting to complete the updates) I found some reg backups (default/sam/software/security/system) in a regbackup in windows\config...

    I noticed that I didn't have Service Pack 1 installed.
    Since installing, I've gone to standby, and resumed successfully, on several occasions.
    Just now, I opened my lid to resume from sleep. I noticed the laptop wasn't plugged in (the battery is highly degraded).


    The moment it connected to power, it blue-screened - this time 0x000000f4 (CRITICAL TERMINATION again).


    Just installed SeaTools for windows.


    Assuming I should run on the physical drive?





    Thanks again...
      My Computer


  10. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #10

    Yes, test the physical drive. Take both the short generic test and the long generic test.
      My Computer


 
Page 1 of 3 123 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 05:20.
Find Us