BSOD when trying to sleep or hibernate, bugcheck code 0x9F


  1. Posts : 3
    Windows 7 Professional x64 SP1
       #1

    BSOD when trying to sleep or hibernate, bugcheck code 0x9F


    I have had intermittent problems with getting my HP laptop to successfully enter sleep or hibernate mode. Recently the BSODs are happening much more frequently, and I can't determine what changes may have precipitated any of this.

    When trying to sleep, the screen goes black, but the HDD and fans spin until a BSOD appears (many minutes later).

    WhoCrashed analysis of the latest minidump

    On Thu 6/14/2012 12:53:36 AM GMT your computer crashed
    crash dump file: C:\Windows\Minidump\061412-45271-01.dmp
    This was probably caused by the following module: ntoskrnl.exe (nt+0x7CC40)
    Bugcheck code: 0x9F (0x3, 0xFFFFFA8007B4D060, 0xFFFFF80004778748, 0xFFFFFA8007FD3B80)
    Error: DRIVER_POWER_STATE_FAILURE
    file path: C:\Windows\system32\ntoskrnl.exe
    product: Microsoft® Windows® Operating System
    company: Microsoft Corporation
    description: NT Kernel & System
    Bug check description: This bug check indicates that the driver is in an inconsistent or invalid power state.
    This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
    The crash took place in the Windows kernel. Possibly this problem is caused by another driver which cannot be identified at this time
    Analyisis in WinDBG gives the same results.

    I have read about this being often caused by video or network drivers, so I have tried to update all of those. I have also tried a CHKDSK.

    My machine (full system specs in my profile)

    Windows 7 Professional x64 SP1 Retail
    1 year old laptop
    6 months since OS install - it seems like the problem has always occurred in some form, since the initial OS setup

    P.S. I would love to learn more about debugging my crashes, so I appreciate any guidance on the steps I missed.

    Thanks very much for your help!
    Last edited by inarius; 14 Jun 2012 at 12:20. Reason: added details
      My Computer


  2. Posts : 1,314
    Windows 7 64-bit
       #2

    Your Intel LAN drivers look to be responsible. This is only a partial analysis, however. I cannot dig further without a kernel dump (MEMORY.DMP in Windows directory).

    Code:
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time (usually 10 minutes).
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: fffffa8007b4d060, Physical Device Object of the stack
    Arg3: fffff80004778748, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa8007fd3b80, The blocked IRP
    
    Debugging Details:
    ------------------
    
    TRIAGER: Could not open triage file : C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64\triage\modclass.ini, error 2
    
    DRVPOWERSTATE_SUBCODE:  3
    
    IMAGE_NAME:  pci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7928f
    
    MODULE_NAME: pci
    
    FAULTING_MODULE: fffff88000f1c000 pci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  mscorsvw.exe
    
    CURRENT_IRQL:  2
    
    STACK_TEXT:  
    fffff800`047786f8 fffff800`02eeccd2 : 00000000`0000009f 00000000`00000003 fffffa80`07b4d060 fffff800`04778748 : nt!KeBugCheckEx
    fffff800`04778700 fffff800`02e8a5fc : fffff800`04778830 fffff800`04778830 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34a90
    fffff800`047787a0 fffff800`02e8a496 : fffff800`03029f00 00000000`005e2857 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`04778810 fffff800`02e8a37e : 000000e0`21a4e56b fffff800`04778e88 00000000`005e2857 fffff800`02ff7d68 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`04778e60 fffff800`02e8a167 : fffff800`02ff4ec1 fffffa80`005e2857 00000000`00000000 00000000`00000057 : nt!KiTimerExpiration+0x1be
    fffff800`04778f00 fffff800`02e81765 : 00000000`00000000 fffffa80`126e7b60 00000000`00000000 fffff800`02f30760 : nt!KiRetireDpcList+0x277
    fffff800`04778fb0 fffff800`02e8157c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
    fffff880`0afe7aa0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_e1c62x64_IMAGE_pci.sys
    
    BUCKET_ID:  X64_0x9F_3_e1c62x64_IMAGE_pci.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa8007fd3b80 1
    Irp is active with 4 stacks 3 is current (= 0xfffffa8007fd3ce0)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
    Flags = 00000000
    ThreadListEntry.Flink = fffffa8007fd3ba0
    ThreadListEntry.Blink = fffffa8007fd3ba0
    IoStatus.Status = c00000bb
    IoStatus.Information = 00000000
    RequestorMode = 00000000
    Cancel = 00
    CancelIrql = 0
    ApcEnvironment = 00
    UserIosb = 00000000
    UserEvent = 00000000
    Overlay.AsynchronousParameters.UserApcRoutine = 00000000
    Overlay.AsynchronousParameters.UserApcContext = 00000000
    Overlay.AllocationSize = 00000000 - 00000000
    CancelRoutine = 00000000   
    UserBuffer = 00000000
    &Tail.Overlay.DeviceQueueEntry = fffffa8007fd3bf8
    Tail.Overlay.Thread = 00000000
    Tail.Overlay.AuxiliaryBuffer = 00000000
    Tail.Overlay.ListEntry.Flink = fffffa80125b20b8
    Tail.Overlay.ListEntry.Blink = fffff80003029ae0
    Tail.Overlay.CurrentStackLocation = fffffa8007fd3ce0
    Tail.Overlay.OriginalFileObject = 00000000
    Tail.Apc = 00000000
    Tail.CompletionKey = 00000000
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
                Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa8008232050 00000000 fffff800030c61b0-fffffa800a6e75c0 Success Error Cancel pending
              Unable to load image \SystemRoot\system32\DRIVERS\e1c62x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for e1c62x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
     \Driver\e1cexpress    nt!PopSystemIrpCompletion
                Args: 00014400 00000000 00000004 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa800a6e75c0    
    
                Args: 00000000 00000000 00000000 00000000
    
    
    0: kd> !error c00000bb
    Error code: (NTSTATUS) 0xc00000bb (3221225659) - The request is not supported.
    
    0: kd> lmvm e1c62x64
    start             end                 module name
    fffff880`05000000 fffff880`0505b000   e1c62x64 T (no symbols)           
        Loaded symbol image file: e1c62x64.sys
        Image path: \SystemRoot\system32\DRIVERS\e1c62x64.sys
        Image name: e1c62x64.sys
        Timestamp:        Wed Nov 30 18:09:31 2011 (4ED6B7AB)
        CheckSum:         0006396D
        ImageSize:        0005B000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    I may be reading the IoStatus incorrectly, but it looks like the problem is with a bad request by the driver. The driver is not that old - Nov 2011, but still, look for an update if possible. Again, this is a partial diagnosis.
      My Computer


  3. Posts : 3
    Windows 7 Professional x64 SP1
    Thread Starter
       #3

    Thanks, I will check that out. I think that is one that I updated but I will see what other version are available.

    Is there a way that I should supply the kernel dump (~900MB) or better yet, are there resources I can use to learn to examine it myself?

    Thanks very much!!
      My Computer


  4. Posts : 3
    Windows 7 Professional x64 SP1
    Thread Starter
       #4

    I did find a newer driver using Intel's own Driver Update Utility. I am installing it and will try to report back on what I find.
      My Computer


  5. Posts : 1,314
    Windows 7 64-bit
       #5

    Aside from buying the book Windows Internals and reading and studying up on it as well as the various facets of debugging, I can't find any other way to offer you assistance on how to analyze this kinda stuff. I have debugging articles you can review, and there's plenty other resources out there. If you're gonna start with it though, expect to be in it for the long haul. :)

    Also, yes, a kernel dump would be greatly beneficial. If you end up crashing again, it's best to provide me the new minidump first, then if need be I'll request the kernel dump. In addition, turning on Driver Verifier and sending us any new crashes from it would be great. When setting it up, do not select the following checks: Low Resource Sim, IRP Logging, and Force Pending I/O Requests. Anything else is ok. Remember to restart the PC after you set it all up.
      My Computer


 

  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 16:13.
Find Us