BSOD, error 0x0000009F


  1. Posts : 2
    Windows 7 Pro x64
       #1

    BSOD, error 0x0000009F


    - Windows 7 Pro x64
    - Fresh system. Installed and updated yesterday.
    - BSOD occurred while downloading files from Origin and Adobe Download Assistant

    I have never seen this BSOD before the only difference is that now I have new SSD for OS.
    Could someone please tell me what caused this error: driver_power_state_failure 0x0000009F?

    In zip there is also screen and WinDbg file.

    Thanks
      My Computer


  2. Posts : 4,161
    Windows 7 Pro-x64
       #2

    Your system stopped at a driver named amm9h5at.sys because of a pending I/O in sptd.sys. Sptd.sys may be a faulty CD ROM emulation driver from Daemon Tools. I couldn't find anything on amm9h5at.sys but I suspect it's a Daemon Tools driver also.

    Update or Un-install the Daemon Tools.

    Edit: SPTD is used by Daemon Tools and Alcohol 120%. It is also utilized in PowerArchiver Pro 2010 (v11.60+);


    Code:
     
    0: kd> lmvm amm9h5at
    start             end                 module name
    fffff880`0721d000 fffff880`0726e000   amm9h5at T (no symbols)           
        Loaded symbol image file: amm9h5at.SYS
        Image path: \SystemRoot\System32\Drivers\amm9h5at.SYS
        Image name: amm9h5at.SYS
        Timestamp:        Tue Dec 27 16:30:45 2011 (4EFA4715)
        CheckSum:         00057531
        ImageSize:        00051000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    0: kd> !irp fffffa8005cc7e10
    Irp is active with 4 stacks 2 is current (= 0xfffffa8005cc7f28)
     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
    >[ 16, 2]   0  1 fffffa800c7fd050 00000000 00000000-00000000   pending
           *** WARNING: Unable to verify timestamp for sptd.sys
    *** ERROR: Module load completed but symbols could not be loaded for sptd.sys
     \Driver\amm9h5at
       Args: 00014400 00000000 00000004 00000002
     [ 16, 2]   0 e1 fffffa800c7fb060 00000000 fffff80003acc200-fffffa800ea250a0 Success Error Cancel pending
            \Driver\cdrom nt!PopSystemIrpCompletion
       Args: 00014400 00000000 00000004 00000002
     [  0, 0]   0  0 00000000 00000000 00000000-fffffa800ea250a0    
       Args: 00000000 00000000 00000000 00000000
    Last edited by carwiz; 05 May 2012 at 15:17. Reason: Additional Info
      My Computer


  3. Posts : 338
    win7 home premium-64bit-SP1-IE10
       #3

    Welcome to the forum
    Try to visit the following site to understand what's the meaning of driver power state failure 0x9f and act accordingly

    HELP - DRIVER_POWER_STATE_FAILURE - 0x0000009f - - Microsoft Answers
    Good luck
      My Computer


  4. Posts : 11,269
    Windows 7 Home Premium 64 Bit
       #4

    If you remove the software that carwiz suggests, also use the sptd.sys uninstaller to remove sptd.sys from the system. Select uninstall to uninstall the sptd.sys driver.
      My Computer


  5. Posts : 2
    Windows 7 Pro x64
    Thread Starter
       #5

    Uninstalled Daemon Tools and sptd.sys and we will see.
    Thanks.
      My Computer


  6. Posts : 4,161
    Windows 7 Pro-x64
       #6

    Hanna 1 said:
    Welcome to the forum
    Try to visit the following site to understand what's the meaning of driver power state failure 0x9f and act accordingly

    HELP - DRIVER_POWER_STATE_FAILURE - 0x0000009f - - Microsoft Answers
    Good luck
    That's a good start but reflects only one occurrence. I copied the description below because it better relates what is happening when a Driver Power State Failure occurs. As noted, a PC can crash even if not transitioning between power states--A simple driver query about the power state can cause a failure too if the driver doesn't handle it correctly. Which is most likely the cause treated by the MS patch in your example.

    I ran across this while looking for something else and can't remember the source but a quoted search would most likely turn it up. I have the process and procedure in a Word Document for reference.

    0x0000009F (and 0x1000009F) is a fairly common bug check that occurs when a device driver does not complete processing on an I/O Request Packet (IRP) in a timely fashion (often 10 minutes). This can occur for a variety of reasons, but the main reasons are due to kernel-mode drivers not properly handling changes in power states (commonly to standby/hibernation and back to a full system working state).

    The system has 6 main power states that are usable, S0 - S5. S0 is a fully awake processing state and S5 is the shutdown state. S1-S3 are standby states and S4 is the hibernating state. To transition between states, the system must return to state S0 (ex. Standby -> Hibernate is actually Standby - > Awake -> Hibernate). If devices and drivers do not correctly handle state transitions (or even queries about the current power state), it is possible for the system to crash with the DRIVER_POWER_STATE_FAILURE
      My Computer


  7. Posts : 338
    win7 home premium-64bit-SP1-IE10
       #7

    carwiz
    Thank you for the info.
      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:23.
Find Us