Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: DRIVER_POWER_STATE_FAILURE 0x0000009f - after hibernation,shutdown

16 Dec 2014   #1
Pieohpah

Windows 7 Ultimate x64
 
 
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 System SpecsSystem Spec
.
17 Dec 2014   #2
koolkat77

Microsoft Community Contributor Award Recipient

Windows 10 Home 64Bit
 
 

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 System SpecsSystem Spec
17 Dec 2014   #3
Pieohpah

Windows 7 Ultimate x64
 
 

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
My System SpecsSystem Spec
.

17 Dec 2014   #4
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

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 System SpecsSystem Spec
19 Dec 2014   #5
Pieohpah

Windows 7 Ultimate x64
 
 

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 System SpecsSystem Spec
19 Dec 2014   #6
Golden
Microsoft MVP

Windows 7 Ult. x64
 
 

Its a pleasure - Merry ChristFSMas
My System SpecsSystem Spec
Reply

 DRIVER_POWER_STATE_FAILURE 0x0000009f - after hibernation,shutdown




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
DRIVER_POWER_STATE_FAILURE 0x0000009f ntkrnlpa.exe
Have been getting these BSOD since the time I bought my laptop 7 months ago. Can't say that there's any particular reason or condition for them to appear. Most cases are when I use the internet ( skype,torrents,just browsing) or leave my computer still, never while playing games. Had Win7 x64 at...
BSOD Help and Support
Help with BSOD DRIVER_POWER_STATE_FAILURE 0X0000009F
Hello all, Could anyone please help? I am getting some BSOD on my (almost brand new in terms of usage) laptop and would like to know what can be done to avoid this worrying recurrence. The first time it happened a couple of days ago while browsing the net, the second time today while I was...
BSOD Help and Support
DRIVER_POWER_STATE_FAILURE 0x0000009f on Shutdown
Hi, I've been getting this BSOD DRIVER_POWER_STATE_FAILURE whenever I'm in the process of shutting down my computer. Help to fix this would be most appreciated!
BSOD Help and Support
Unexpected Shutdown DRIVER_POWER_STATE_FAILURE 0x0000009f
New system Win7 x64. swapped out the Asus Z77 motherboard with an Intel DH77EB board BIOS 0100, reinstalled windows clean, all current Intel drivers RST 12.5.0.1066. Intel 335 SSD. Same thing, shuts down when in sleep mode. 051513-6193-01.dmp 5/15/2013 11:26:00 PM ...
BSOD Help and Support
Driver_Power_State_Failure on entering Hibernation BSOD 0x0000009f
I did look at some other similar threads to this but each had its own unique differences from the issue I'm having, so I started a new thread, I apologize if I missed something in another thread that would have helped me I hope to not be causing anyone to repeat their efforts here. While the...
BSOD Help and Support
DRIVER_POWER_STATE_FAILURE 0x0000009f
Random blue screen and reboots. Have run all type of hadware tests and everything is ok. Dell XPS 435 MTIntel i7 920 8GB ram see attached files
BSOD Help and Support


Our Sites

Site Links

About Us

Find 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 09:04.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App