DRIVER_POWER_STATE_FAILURE 0x0000009f - after hibernation,shutdown


  1. Posts : 4
    Windows 7 Ultimate x64
       #1

    DRIVER_POWER_STATE_FAILURE 0x0000009f - after hibernation,shutdown


    Hello guys,
    would you please analyze uploaded files from SF Diagnostic Tool ?
    After every shutdown or hibernation(monitor is going to sleep,but pc is runing ) desktop PC is regulary going to BSOD(it takes cca 20min from execute shutdown/hibernation to BSOD) . Next windows start I can see dmp bellow.
    Hardware manager is without any allerts.
    ==================================================
    Dump File : 121614-13681-01.dmp
    Crash Time : 15.12.2014 22:31:16
    Bug Check String : DRIVER_POWER_STATE_FAILURE
    Bug Check Code : 0x0000009f
    Parameter 1 : 00000000`00000003
    Parameter 2 : fffffa80`04d04050
    Parameter 3 : fffff800`00b9c518
    Parameter 4 : fffffa80`069b0d30
    Caused By Driver : ntoskrnl.exe
    Caused By Address : ntoskrnl.exe+75bc0
    File Description : NT Kernel & System
    Product Name : Microsoft® Windows® Operating System
    Company : Microsoft Corporation
    File Version : 6.1.7601.18409 (win7sp1_gdr.140303-2144)
    Processor : x64
    Crash Address : ntoskrnl.exe+75bc0
    Stack Address 1 :
    Stack Address 2 :
    Stack Address 3 :
    Computer Name :
    Full Path : C:\Windows\Minidump\121614-13681-01.dmp
    Processors Count : 4
    Major Version : 15
    Minor Version : 7601
    Dump File Size : 1 666 936
    Dump File Time : 16.12.2014 7:07:31
    ==================================================

    Thank you
    Petr
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Welcome to the forum.

    Please uninstall Daemon Tools. It uses a driver called sptd.sys which is known to cause BSODs in Windows 7.

     SPTD Removal:

    • Uninstall the software using Add/Remove Programs.
    • Reboot the system.
    • Once the program is uninstalled, run sptd.sys uninstaller to remove the driver from your system.
    • DuplexSecure - Downloads
    As an alternative, many people recommend the use of Total Mounter or Magic ISO

    Code:
    
    Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.
    
    
    Loading Dump File [C:\Users\USER\Downloads\Compressed\SF_16-12-2014\121614-13681-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available
    
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`024ccc32?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff8a0`00214022?
    DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`02c4d000 PsLoadedModuleList = 0xfffff800`02e90890
    Debug session time: Tue Dec 16 03:31:16.569 2014 (UTC + 6:00)
    System Uptime: 0 days 14:29:52.084
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .....................................
    Loading User Symbols
    Loading unloaded module list
    .....
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8004d04050, fffff80000b9c518, fffffa80069b0d30}
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: USBPORT!_DEVICE_EXTENSION                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : usbohci.sys
    
    Followup: MachineOwner
    ---------
    
    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: fffffa8004d04050, Physical Device Object of the stack
    Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
    Arg4: fffffa80069b0d30, The blocked IRP
    
    Debugging Details:
    ------------------
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands to work properly, your symbol path           ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: USBPORT!_DEVICE_EXTENSION                     ***
    ***                                                                   ***
    *************************************************************************
    
    DRVPOWERSTATE_SUBCODE:  3
    
    DRIVER_OBJECT: fffffa800485fbb0
    
    IMAGE_NAME:  usbohci.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52954db5
    
    MODULE_NAME: usbohci
    
    FAULTING_MODULE: fffff880043ed000 usbohci
    
    CUSTOMER_CRASH_COUNT:  1
    
    DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
    
    BUGCHECK_STR:  0x9F
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  2
    
    TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0
    
    STACK_TEXT:  
    fffff800`00b9c4c8 fffff800`02d328d2 : 00000000`0000009f 00000000`00000003 fffffa80`04d04050 fffff800`00b9c518 : nt!KeBugCheckEx
    fffff800`00b9c4d0 fffff800`02ccd85c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
    fffff800`00b9c570 fffff800`02ccd6f6 : fffffa80`06b5a438 fffffa80`06b5a438 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
    fffff800`00b9c5e0 fffff800`02ccd5de : 00000079`84e806de fffff800`00b9cc58 00000000`00330cd8 fffff800`02e41d88 : nt!KiProcessExpiredTimerList+0xc6
    fffff800`00b9cc30 fffff800`02ccd3c7 : 000000ad`fe8758c2 000000ad`00330cd8 000000ad`fe87589c 00000000`000000d8 : nt!KiTimerExpiration+0x1be
    fffff800`00b9ccd0 fffff800`02cba8ca : fffff800`02e3de80 fffff800`02e4bcc0 00000000`00000000 fffff800`02cc904c : nt!KiRetireDpcList+0x277
    fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_NAME:  MachineOwner
    
    FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_usbohci.sys
    
    BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_usbohci.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa80069b0d30
    Irp is active with 5 stacks 4 is current (= 0xfffffa80069b0ed8)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         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
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 fffffa8004d04050 00000000 00000000-00000000    pending
    	      Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
     \Driver\usbohci
    			Args: 00015500 00000001 00000003 00000003
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8006f75310    
    
    			Args: 00000000 00000000 00000000 00000000
    0: kd> lmvm sptd
    start             end                 module name
    fffff880`0105c000 fffff880`01182000   sptd     T (no symbols)           
        Loaded symbol image file: sptd.sys
        Image path: \SystemRoot\System32\Drivers\sptd.sys
        Image name: sptd.sys
        Timestamp:        Mon Oct 12 02:55:14 2009 (4AD24632)
        CheckSum:         000D6B26
        ImageSize:        00126000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
     Clean boot


    Reduce items at start-up. No software except anti-virus is required plus doing this improves the time for logging into windows:
      My Computer


  3. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Hi koolkat77,

    thank you for quick analyze, but issue is still persisting.
    Action performed :
    -deinstall daemon tools
    -deinstall sptd.sys
    -reduced all items at start up except ms services

    Also I've installed windbg and performed my investigate. Would you please a look on results how this can be fixed?

    Petr
    Last edited by Pieohpah; 17 Dec 2014 at 16:07.
      My Computer


  4. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #4

    Code:
    ******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 9F, {3, fffffa8003fab060, fffff80000b9c518, fffffa800660d9a0}
    
    Probably caused by : pci.sys
    
    Followup: MachineOwner
    ---------
    
    0: kd> !irp fffffa800660d9a0
    Irp is active with 8 stacks 6 is current (= 0xfffffa800660dbd8)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         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
     [  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
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
    
    			Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0  0 fffffa8004720060 00000000 00000000-00000000    
    	      Unable to load image \SystemRoot\system32\drivers\ctaud2k.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ctaud2k.sys
    *** ERROR: Module load completed but symbols could not be loaded for ctaud2k.sys
     \Driver\ctaud2k
    			Args: 00016600 00000001 00000004 00000000
     [ 16, 2]   0 e1 fffffa8004726e30 00000000 00000000-00000000    pending
    	       \Driver\ksthunk
    			Args: 00016600 00000001 00000004 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa8007118c40    
    
    			Args: 00000000 00000000 00000000 00000000
    Try Updating the Creative Audio driver here:
    Creative Worldwide Support
      My Computer


  5. Posts : 4
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Hi Golden,

    I've deinstalled customized PAX Creative drivers and installed original Creative drivers.
    And that worked, issue is gone.
    You guys rock !
    Thank you very much.
      My Computer


  6. Posts : 19,383
    Windows 10 Pro x64 ; Xubuntu x64
       #6

    Its a pleasure - Merry ChristFSMas
      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 04:16.
Find Us