BSOD with 0x9F driver_power_state_failure

I have a client site with one HP 15 Notebook PC running Windows 8.1 that has been having a problem for the last 2-3 weeks when accessing their own in-house websites. After a minute or two of navigating throughout the websites, the laptop has a BSOD with the stop code 0x9F DRIVER_POWER_STATE_FAILURE. No other websites are known to cause this BSOD and as I said it started 2-3 weeks ago.

This laptop is the only computer at the client site with this problem. All other computers (laptops and desktops both HP and Dell) are running either Windows 8.1 or Windows 7. The only difference we are able to discern between this laptop and the other computers is that this one has an AMD CPU, all others have Intel.

I and a co-worker have put in some time trying to determine the cause and correct it. We have installed all pending Windows updates (it was a fair amount behind), updated all drivers, reset IE and Chrome, and have looked at the dmp files with BlueScreenView which indicates the problem is in ntoskrnl.exe though I am not convinced that is the actual cause of the problem.

We are wondering if the website developers made a change 3 weeks ago which is now causing this BSOD though why it would affect only this one computer is a mystery. I can't think of why something in a website would crash a specific brand of CPU.

Does anyone have any ideas on how else to proceed with determining the cause of the BSOD?

February 24th, 2015 5:20pm

 We do need the actual log files (called a DMP files) as they contain the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.  

Please follow our instructions for finding and uploading the files we need to help you fix your computer. They can be found here If you have any questions about the procedure please ask
Free Windows Admin Tool Kit Click here and download it now
February 24th, 2015 5:26pm

I read through the procedure and while I knew about the .dmp file and how to access and process it, I'm stopped at sharing it. I have a OneDrive for Business folder from my company and I am unable to determine how to share the .dmp file I've uploaded there or a link to it.

Or can I only use a personal OneDrive folder?

February 24th, 2015 5:41pm

Jonathan

You can use either.  Go to the files/folder and "get a link".  Post that link in your next post.  If you cannot for some reason you can email them to zigzag3143@gmail.com.

Free Windows Admin Tool Kit Click here and download it now
February 24th, 2015 6:02pm

See if you can access this link. I didn't see any option as you indicated but when clicking the more (...) next to the filename it did pop up a box with this link. If you can't access it then I'll email it to you.

https://micronetkc-my.sharepoint.com/personal/jonathan_leslie_micronetkc_com/Documents/Shared%20with%20Everyone/022415-20906-01.zip

February 24th, 2015 6:26pm

Jonathan

Nope.  Assumes I have an office365 subscription.  Try onedrive or ANY file sharing ser vice like (reapidshare)

Free Windows Admin Tool Kit Click here and download it now
February 24th, 2015 7:07pm

Try this one.

http://1drv.ms/1ze1Zit

February 24th, 2015 9:24pm

SBA

This single DMP was not conclusive but does point to the USBVIDEO.SYS driver.  I would remoeve the current driver and install the newest driver available.  Win 8.1 is NOT fond fo USB video.  Install the newest driver even if it is the same date because driver often do become corrupt.  If you/they continue to crash upload the DMPS.  If you want to get more definitive proof you can also run driver verifier

These crashes were related to memory corruption (probably caused by a driver). 

Please run these two tests to verify your memory and find which driver is causing the problem.  Please run verifier first.  You do not need to run memtest yet unless you want to.

If you are over-clocking anything reset to default before running these tests.
In other words STOP!!! 
 

If you do not know what this means you probably are not


1-Driver verifier (for complete directions see our wiki here)

2-Memtest. (You can read more about running memtest here)


Microsoft (R) Windows Debugger Version 6.3.9600.17298 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Ken\Desktop\022415-20906-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

WARNING: Whitespace at start of path element
WARNING: Whitespace at end of path element
Error: Empty Path.
Symbol search path is: 
SRV*e:\symbols*http://msdl.microsoft.com/download/symbols 
Executable search path is: 
Windows 8 Kernel Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
Machine Name:
Kernel base = 0xfffff800`75c7c000 PsLoadedModuleList = 0xfffff800`75f462d0
Debug session time: Tue Feb 24 14:51:46.453 2015 (UTC - 5:00)
System Uptime: 0 days 0:06:50.334
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe001d4e82240, fffff8007768f930, ffffe001d2875010}

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: ffffe001d4e82240, Physical Device Object of the stack
Arg3: fffff8007768f930, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001d2875010, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

DRIVER_OBJECT: ffffe001d434ad30

IMAGE_NAME:  usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  52678625

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff801a68de000 usbccgp

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE:  FFFFF80077696FB0

STACK_TEXT:  
fffff800`7768f8f8 fffff800`75e78c1e : 00000000`0000009f 00000000`00000003 ffffe001`d4e82240 fffff800`7768f930 : nt!KeBugCheckEx
fffff800`7768f900 fffff800`75e78b3e : ffffe001`d53bb150 00001f00`ffffffff ffffe001`d53bb190 ffffe001`d53bb1c8 : nt!PopIrpWatchdogBugcheck+0xde
fffff800`7768f960 fffff800`75cd5810 : 00000000`00000000 fffff800`00000001 ffffd000`793acb70 fffff800`00000002 : nt!PopIrpWatchdog+0x32
fffff800`7768f9b0 fffff800`75dd3aea : fffff800`75f62180 fffff800`75f62180 fffff800`75fc9a00 ffffe001`d67ed880 : nt!KiRetireDpcList+0x4f0
fffff800`7768fc60 00000000`00000000 : fffff800`77690000 fffff800`7768a000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  6.3.9600.16442

FAILURE_BUCKET_ID:  0x9F_3_IMAGE_usbccgp.sys

BUCKET_ID:  0x9F_3_IMAGE_usbccgp.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_image_usbccgp.sys

FAILURE_ID_HASH:  {2240478d-2a07-44ce-f277-d13120a9d2d6}

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

0: kd> !irp ffffe001d2875010
Irp is active with 19 stacks 16 is current (= 0xffffe001d2875518)
 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
 [  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
 [  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 e1 ffffe001d4e82240 00000000 fffff801a3c98ec0-ffffe001d4df0bc0 Success Error Cancel pending
	       \Driver\usbccgp	ks!CKsDevice::CompleteDevicePowerIrp
			Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0  1 ffffe001d4df0040 00000000 00000000-00000000    pending
	       \Driver\usbvideo
			Args: 00000000 00000001 00000001 00000000
 [ 16, 2]   0 e1 ffffe001d4b98e40 00000000 fffff80075d9a2d8-ffffe001d53bb150 Success Error Cancel pending
	       \Driver\ksthunk	nt!PopRequestCompletion
			Args: 00000000 00000001 00000001 00000000
 [  0, 0]   0  0 00000000 00000000 00000000-ffffe001d53bb150    



Free Windows Admin Tool Kit Click here and download it now
February 25th, 2015 8:21am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics