BSOD - usbccgp.sys (after waking up from sleep)

[hanchas]

Hello!
I know there have been quite a lot of posts dealing with BSOD, but if I searched well, none of these problems is the same as mine.
My laptop: Lenovo Flex 2-14, OS: Windows 8.1
Sometimes when it wakes up from sleep it says there is a problem with a microphone, but reinstalling the drivers did not help.

Here is my dump file:


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


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*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 Personal
Built by: 9600.17668.amd64fre.winblue_r8.150127-1500
Machine Name:
Kernel base = 0xfffff802`bb80d000 PsLoadedModuleList = 0xfffff802`bbae6250
Debug session time: Fri Mar 13 08:36:27.542 2015 (UTC + 1:00)
System Uptime: 0 days 15:37:26.567
Loading Kernel Symbols
...............................................................
................................................................
.........................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00007ff7`e361e018). Type ".hh dbgerr001" for details
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe0017c4058c0, ffffd00020393cb0, ffffe001805f8010}

Probably caused by : usbccgp.sys

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

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

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


DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffe0017b389060

IMAGE_NAME: usbccgp.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 53d0f1b3

MODULE_NAME: usbccgp

FAULTING_MODULE: fffff800d9b25000 usbccgp

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: chrome.exe

CURRENT_IRQL: 2

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

DPC_STACK_BASE: FFFFD00020393FB0

STACK_TEXT:
ffffd000`20393c78 fffff802`bba15e3e : 00000000`0000009f 00000000`00000003 ffffe001`7c4058c0 ffffd000`20393cb0 : nt!KeBugCheckEx
ffffd000`20393c80 fffff802`bba15d5e : ffffe001`80d031d0 00000000`00000000 ffffe001`80d03208 fffff802`bb8c0515 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`20393ce0 fffff802`bb8c1428 : 00000000`00000000 ffffd000`20393e30 00000000`00000001 ffffd000`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`20393d30 fffff802`bb960ad5 : 00000000`00000000 ffffd000`245e7180 fffff802`bbff5e00 000003ff`a826dd99 : nt!KiRetireDpcList+0x4f8
ffffd000`20393fb0 fffff802`bb9608d9 : 0000007d`be2faaf0 0000007d`be2fac78 0000007d`be2b1500 0000007d`ba1cc598 : nt!KxRetireDpcList+0x5
ffffd000`21a82c00 fffff802`bb962b45 : ffffd000`21a82cc0 fffff802`bb95f287 00000000`00000001 00000000`9133b001 : nt!KiDispatchInterruptContinue
ffffd000`21a82c30 fffff802`bb95f287 : 00000000`00000001 00000000`9133b001 0000007d`ba1cbb01 ffffe001`7edea601 : nt!KiDpcInterruptBypass+0x25
ffffd000`21a82c40 00007ff8`8e70ac55 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x197
0000007d`ba1cba00 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`8e70ac55


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

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
---------
Can you please help me how to solve it?

 

[johnbl]

basically, a USB device attached to your system refused to wake up.

- update the driver for the actual failing USB device.
- update BIOS to get any USB fixes
- update CPU chipset drivers to get USB 2.x chipset fixes
- update any special USB 3.0 chip driver for your motherboard.

or go to windows control panel device manager, find the device and disable its sleep (low power) functions. This will not fix the problem but will prevent the bugcheck.