BSOD when shutting down PC - Driver Power State Failure

Natvander · 09 Mar 2014

Hi

I really hope someone can help me. I've been getting frequent BSODs of late, but currently I get one which stops the shutdown process - screen displays Windows Shutting Down for a considerable amount of time and then I get a BSOD - Driver Power State Failure. This basically prevents me from running checkdisk and other such utilities.

I've used BlueScreenView which highlights ntoskrnl.exe, which was involved in my previous BSODs.

I've uploaded 3 dump files as per directions (the only 3 I have after performing a clean up to try and fix the issue with CCleaner).

Help...please

Arc · 10 Mar 2014

What are the USB devices you are having?

Try removing them all other than the keyboard/mouse?

Also Upload the list of all the third party drivers Using NirSoft DriverView :

Download and execute Driverview
View > Hide Microsoft Drivers
Edit > Select all
File > Save Selected Items
In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
Zip the .txt file and upload it.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8014cdb3f0, fffff80003c073d8, fffffa800f02dc10}

Probably caused by : usbccgp.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.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8014cdb3f0, Physical Device Object of the stack
Arg3: fffff80003c073d8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800f02dc10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52954dbb

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff88005dba000 usbccgp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

DPC_STACK_BASE:  FFFFF80003C0DFB0

STACK_TEXT:  
fffff800`03c07388 fffff800`035048d2 : 00000000`0000009f 00000000`00000003 fffffa80`14cdb3f0 fffff800`03c073d8 : nt!KeBugCheckEx
fffff800`03c07390 fffff800`0349f85c : fffff800`03c074c0 fffff800`03c074c0 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`03c07430 fffff800`0349f6f6 : fffff800`03636f70 00000000`0001bc70 00000000`00000000 fffff880`0f6ae149 : nt!KiProcessTimerDpcTable+0x6c
fffff800`03c074a0 fffff800`0349f5de : 00000004`21efcf25 fffff800`03c07b18 00000000`0001bc70 fffff800`03613088 : nt!KiProcessExpiredTimerList+0xc6
fffff800`03c07af0 fffff800`0349f3c7 : 00000001`68dd97c2 00000001`0001bc70 00000001`68dd97f2 00000000`00000070 : nt!KiTimerExpiration+0x1be
fffff800`03c07b90 fffff800`0348c8ca : fffff800`0360fe80 fffff800`0361dcc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`03c07c40 00000000`00000000 : fffff800`03c08000 fffff800`03c02000 fffff800`03c07c00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.1.7601.18328

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_usbscan_IMAGE_usbccgp.sys

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_usbscan_IMAGE_usbccgp.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_usbscan_image_usbccgp.sys

FAILURE_ID_HASH:  {825ad414-c565-cd24-7367-3c1e18f75976}

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

0: kd> !irp fffffa800f02dc10
Irp is active with 8 stacks 6 is current (= 0xfffffa800f02de48)
 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 fffffa8014c9d190 00000000 00000000-00000000    
           \Driver\usbscan
            Args: 00016600 00000001 00000004 00000005
 [ 16, 2]   0 e1 fffffa8014b03a60 00000000 00000000-00000000    pending
           \Driver\ksthunk
            Args: 00016600 00000001 00000004 00000005
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8013727130    

            Args: 00000000 00000000 00000000 00000000
0: kd> lmvm iusb3xhc
start             end                 module name
fffff880`0568e000 fffff880`05751000   iusb3xhc   (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Fri Mar 29 18:06:19 2013 (51558AC3)
    CheckSum:         000C59AC
    ImageSize:        000C3000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Natvander · 10 Mar 2014

Thanks for the reply.

I'll try unplugging all the USB devices, in the meantime here's the list of drivers.

Cheers

Natvander · 10 Mar 2014

Attached are the BSOD dump files after unplugging all USB devices apart from mouse and keyboard.

Arc · 11 Mar 2014

Code:

BugCheck 9F, {3, fffffa80148b1060, fffff80003c073d8, fffffa80159c1600}

Probably caused by : usbccgp.sys

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

Same BSOD continues.
Here is Spyder3 that I am suspecting, the one USB thing having too old driver.

Code:

==================================================
Driver Name       : Spyder3.sys
Address           : 00000000`065F6000
End Address       : 00000000`06600000
Size              : 0x0000a000
Load Count        : 1
Index             : 138
File Type         : System Driver
Description       : Spyder3 USB Driver 1.0-1
Version           : 1.0.0.1
Company           : 
Product Name      : 
Modified Date     : 6/11/2007 13:08:30
Created Date      : 6/11/2007 13:08:30
Filename          : C:\Windows\system32\DRIVERS\Spyder3.sys
File Attributes   : A
Service Name      : Spyder3
Service Display Name: Datacolor Spyder3
Digital Signature : 
==================================================

And Virtual Usb Hub.

Code:

==================================================
Driver Name       : vuhub.sys
Address           : 00000000`05243000
End Address       : 00000000`05252000
Size              : 0x0000f000
Load Count        : 1
Index             : 113
File Type         : Unknown
Description       : 
Version           : 
Company           : 
Product Name      : 
Modified Date     : 17/12/2007 11:25:14
Created Date      : 4/10/2013 12:02:51
Filename          : C:\Windows\system32\DRIVERS\vuhub.sys
File Attributes   : A
Service Name      : vuhub
Service Display Name: Virtual Usb Hub
Digital Signature : 
==================================================

Either update those or uninstall those.

And, Disable USB Selective Suspend too.
USB Selective Suspend - Turn On or Off

Let us know the results.

Natvander · 11 Mar 2014

The Spyder3Pro driver I'm using is the latest driver (4.0.2 I believe) but for testing's sake I have uninstalled all Spyder3 software.

I can't find the device that uses the driver for the virtual USB hub. Is it ok to just delete that file? Device manager is showing a warning for the USB mass storage device (This device cannot start. (Code 10)) but it's a different driver to the one you mentioned. I've tried disabling the device but that makes no difference.

I've also disabled USB Selective Suspend

I have recently (i.e. last night) updated the video drivers to the latest from NVidia. I attempted to restart the PC but on shutting down it froze. I waited 20 mins ended up manually restarting the computer.

At this stage the only devices I have plugged in are the Corsair K60 keyboard and modem via ethernet.

Arc · 12 Mar 2014

A few of the latest versions of nvidia display drivers are problematic at themselves.

I dont have enough idea about spyder3, but the data says that the driver is too old. If a device has that old driver as the latest version, I would not have used that one.

Anyway, your issue is a driver issue only, and a clean install is supposed to solve the issue.

Natvander · 15 Mar 2014

Sorry about the late reply - life gets in the way sometimes.

That seemed to have resolved the issue - no BSODs for a few days. Much thanks.

Arc · 15 Mar 2014

You are welcome. :)