BSOD DRIVER POWER STATE FAILURE 0x0000009f

kiki714 · 29 Dec 2014

Hello Win 7 experts,

I have a Lenovo T520, running Win 7 Pro SP1 on a clean install on a Crucial M500 mSATA SSD. It always crashes when I close the laptop and it sleeps. It did this before as well when I was running a Samsung 830 SSD previously, so I'm hoping I have an outdated driver somewhere that is causing this issue. Thankfully this is not a major problem, but it is annoying and I'd like to get it solved once and for all.

DM Log Collector results are attached to this post.

Thanks in advance for your help.

Ed

koolkat77 · 29 Dec 2014

Welcome to the forum.

Do you have anything connected to USB ports?

Code:

Microsoft (R) Windows Debugger Version 6.2.9200.20512 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\admin\Downloads\New folder\ELOUIE-T520-PC-12_28_14_211908_84\122814-8923-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

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.18526.amd64fre.win7sp1_gdr.140706-1506
Machine Name:
Kernel base = 0xfffff800`02e54000 PsLoadedModuleList = 0xfffff800`03097890
Debug session time: Mon Dec 29 06:10:57.975 2014 (UTC + 6:00)
System Uptime: 0 days 2:02:18.818
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800c9c1a00, fffff80004fdd3d8, fffffa800e1f2410}

Probably caused by : usbscan.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: fffffa800c9c1a00, Physical Device Object of the stack
Arg3: fffff80004fdd3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800e1f2410, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

DEVICE_OBJECT: fffffa800a4856e0

DRIVER_OBJECT: fffffa800ba19d10

IMAGE_NAME:  usbscan.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  51d3ab2c

MODULE_NAME: usbscan

FAULTING_MODULE: fffff8800816d000 usbscan

IRP_ADDRESS:  fffffa800e1f2410

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80004FE3FB0

STACK_TEXT:  
fffff800`04fdd388 fffff800`02f398d2 : 00000000`0000009f 00000000`00000003 fffffa80`0c9c1a00 fffff800`04fdd3d8 : nt!KeBugCheckEx
fffff800`04fdd390 fffff800`02ed485c : fffff800`04fdd4d8 fffff800`04fdd4d8 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`04fdd430 fffff800`02ed46f6 : fffffa80`0689e798 fffffa80`0689e798 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`04fdd4a0 fffff800`02ed45de : 00000011`1646caa8 fffff800`04fddb18 00000000`00072da2 fffff800`030486c8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04fddaf0 fffff800`02ed43c7 : 00000004`28899fc5 00000004`00072da2 00000004`28899fe4 00000000`000000a2 : nt!KiTimerExpiration+0x1be
fffff800`04fddb90 fffff800`02ec18ca : fffff800`03044e80 fffff800`03052cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04fddc40 00000000`00000000 : fffff800`04fde000 fffff800`04fd8000 fffff800`04fddc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_usbscan.sys

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_usbscan.sys

Followup: MachineOwner
---------

0: kd> !irp fffffa800e1f2410
Irp is active with 8 stacks 6 is current (= 0xfffffa800e1f2648)
 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 fffffa800a4856e0 00000000 00000000-00000000    
	       \Driver\usbscan
			Args: 00014400 00000001 00000004 00000002
 [ 16, 2]   0 e1 fffffa800a484e30 00000000 00000000-00000000    pending
	       \Driver\ksthunk
			Args: 00014400 00000001 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800afbf9c0    

			Args: 00000000 00000000 00000000 00000000

Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

Click on the
Type CMD on Search
Left click and Run as Administrator
Type SFC /scannow

Full tutorial here:

SFC /SCANNOW Command - System File Checker

Clean boot

Troubleshoot Application Conflicts by Performing a Clean Startup

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

How to Change, Add, or Remove Startup Programs in Windows 7

Run Disk Check on your Hard Drive for file system errors and bad sectors on it.

Hard Drive Diagnostics

Double click and open my computer.
Right click on desired drive and hit properties.
Click on tools tab and Check now.

Read complete instructions on the tutorial: Disk Check

Other Tests:

kiki714 · 29 Dec 2014

Thanks for the reply! When I ran the diagnostics there was nothing connected to the USB ports. The only things I occasionally plug into USB are a Garmin ANT stick for downloading fitness activity data, and a CF card reader. The laptop also has a hard drive bay installed where the DVD used to be (but no drive installed at the moment - just used for backups) and a built-in SD card reader.

I'll run SFC, Clean Boot and diagnostics and report back.

Thanks!

kiki714 · 01 Jan 2015

SFC returned no errors.
Clean Startup fixed the problem. I haven't gone through the entire troubleshooting problem but is there any downside to keeping some of the service and startup items disabled? The disabled items don't seem to cause any issues with my daily usage of this machine.

kiki714 · 01 Jan 2015

SFC returned no errors.
Clean Startup fixed the problem. I haven't gone through the entire troubleshooting tutorial (turning on and off services/startup items) but is there any downside to keeping some of the service and startup items disabled? The disabled items don't seem to cause any issues with my daily usage of this machine. Kapersky AV is on.