Driver power state failure after resuming from sleep mode

[Lan1]

I'm having a BSOD problem. After walking computer from sleep mode, within 1-2 minutes it will get a BSOD with the "driver power state failure" error and restart, but interestingly I never get the error the moment I wake up the computer. I'm using a Lenovo IdeaPad Y510P with Windows 8.1 64-bit. I already tried uninstalling the Intel HD 4000 driver, restarting computer, and installing the one on Lenovo's site (as this was suggested on the Lenovo forum as a common fix) but it didn't help. The problem only started occurring after one of the following:
- Updating Malwarebytes to latest last week
- Installing a Windows update last week (there were 3 installed components, 1 of them was an Intel HD 4000 driver update, forgot what the other 2 were)
- Updating GeForce Experience and latest NVIDIA Graphics Driver (337.88), it included NVIDIA PhysX System Software 9.13.1220


Here is a log created by WinDbg tool: 'BSOD dump' | TextUploader.com
Here is a log created by BluescreenView:
==================================================
Dump File : 060514-96281-01.dmp
Crash Time : 6/5/2014 7:23:39 PM
Bug Check String : DRIVER_POWER_STATE_FAILURE
Bug Check Code : 0x0000009f
Parameter 1 : 00000000`00000003
Parameter 2 : ffffe001`218f88e0
Parameter 3 : ffffd000`bff2b930
Parameter 4 : ffffe001`2561d1c0
Caused By Driver : ntoskrnl.exe
Caused By Address : ntoskrnl.exe+153fa0
File Description :
Product Name :
Company :
File Version :
Processor : x64
Crash Address : ntoskrnl.exe+153fa0
Stack Address 1 :
Stack Address 2 :
Stack Address 3 :
Computer Name :
Full Path : C:\WINDOWS\Minidump\060514-96281-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 9600
Dump File Size : 1,271,704
Dump File Time : 6/5/2014 7:26:13 PM
==================================================


The full minidump .dmp file is attached. In case attachments don't work here is the full minidump .dmp file uploaded: https://www.mediafire.com/?uv33hc3ffzdg8xb




Thanks for any help.

 

[blueelvis]

Hi Lan1 and welcome to the forums ^_^,

I have analyzed your Dump file and below has been provided an analysis of your dump file for informative purposes :-

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


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




DRVPOWERSTATE_SUBCODE:  3


DRIVER_OBJECT: ffffe00135b70c30


IMAGE_NAME:  usbccgp.sys


DEBUG_FLR_IMAGE_TIMESTAMP:  52678625


MODULE_NAME: usbccgp


FAULTING_MODULE: fffff80157d82000 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.16384 (debuggers(dbg).130821-1623) amd64fre


STACK_TEXT:  
ffffd000`c3df98f8 fffff801`31803c1e : 00000000`0000009f 00000000`00000003 ffffe001`35b5c060 ffffd000`c3df9930 : nt!KeBugCheckEx
ffffd000`c3df9900 fffff801`31803b3e : ffffe001`32f70320 ffffe000`ffffffff 00000000`00000000 fffff801`31664240 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`c3df9960 fffff801`31660810 : 00000000`00000000 ffffd000`c3df9ab0 ffffe001`32f70358 fffff801`317e1e24 : nt!PopIrpWatchdog+0x32
ffffd000`c3df99b0 fffff801`3175eaea : ffffd000`c8800180 ffffd000`c8800180 ffffd000`c880c3c0 ffffe001`32b9c080 : nt!KiRetireDpcList+0x4f0
ffffd000`c3df9c60 00000000`00000000 : ffffd000`c3dfa000 ffffd000`c3df4000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a




STACK_COMMAND:  kb


FOLLOWUP_NAME:  MachineOwner


IMAGE_VERSION:  6.3.9600.16442


FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_usbccgp.sys


BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_usbccgp.sys


ANALYSIS_SOURCE:  KM


FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_image_usbccgp.sys


FAILURE_ID_HASH:  {447d6c25-e30e-cab7-b8c4-6eeb621d3df1}


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

If we run an !irp on the 4th parameter, we get the usbccgp.sys and a reference to KSTHUNK which is the Kernel Streaming WOW64 Thunk Service of Windows

I remember this same kind of case. This KSTHUNK is associated with your Lenovo Easy Camera Software. So, please uninstall Lenovo Easy Camera and this should resolve your issue. (Fingers Crossed ^_^ )

In case the issue is solved, please mark this thread as solved ^_^

 

[Lan1]

Thanks for the reply.
It actually stopped crashing for a few days, but today it gave the BSOD again, and since I didn't install anything over the last few days, the period of no crashes might have just been luck.
Attached is today's minidump.
Link: https://www.mediafire.com/?bf5ga8j7k90bpqt

Thanks.

 

[Lan1]

Up.

 

[blueelvis]

Thanks for the reply.
It actually stopped crashing for a few days, but today it gave the BSOD again, and since I didn't install anything over the last few days, the period of no crashes might have just been luck.
Attached is today's minidump.
Link: https://www.mediafire.com/?bf5ga8j7k90bpqt

Thanks.

Hi Lan1,

I have analyzed your latest Dump file and it is returning the same error that is, the Driver_Power_State_Failure and there is the presence of KSTHUNK as well. Did you remove the Lenovo Easy Camera from Control Panel's Add/Remove Programs?

Also, please follow this post in case the problem is still not solved as I would require the complete diagnostic info of your system :-
http://www.eightforums.com/bsod-cra...e-screen-death-bsod-posting-instructions.html

 

[Lan1]

I used RevoUninstaller to uninstall Lenovo Easy Cam to make sure it clears everything associated with the program, not sure why it's saying it's still installed...
I checked the program list there's another program called "Lenovo YouCam" that's still installed, is that relevant?
Attached are the logs from the SF Diagnostics.
Thank you very much.

 

[Lan1]

Up.

 

[blueelvis]

Hi Lan1,

Yeah please uninstall any lenovo software related to the webcam and see if the issue still persists or not. I guess that software is also using the same faulty module which is present in the lenovo easy camera. Please let me know if you still face problem.