New
#1
BSOD
Well, for the first time in 8 or 9-odd months, I had a BSOD pop up randomly. So I installed and ran the debugger, and this is what I got. Unfortunately I have no clue how to interpret the results, so any assistance here would be greatly appreciated. Thanks!
By the way, my Laptop's an HP G60 64-bit, and has been running Windows 7 for nearly 6 months now, with no major problems until today.
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\053110-40841-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c4c0?
Symbol search path is: srv*DownstreamStore*Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e19000 PsLoadedModuleList = 0xfffff800`03056e50
Debug session time: Mon May 31 15:24:10.057 2010 (UTC - 4:00)
System Uptime: 0 days 6:47:45.085
Loading Kernel Symbols
...............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9F, {3, fffffa80064d3060, fffff80000b9c4d8, fffffa8007bbb0e0}
Probably caused by : usbccgp.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80064d3060, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa8007bbb0e0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc15
MODULE_NAME: usbccgp
FAULTING_MODULE: fffff8800606d000 usbccgp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`00b9c488 fffff800`02ef81b3 : 00000000`0000009f 00000000`00000003 fffffa80`064d3060 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`02e956a6 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c530 fffff800`02e94a26 : fffff800`03039700 00000000`0017ee08 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`02e9557e : 00000038`f653d82e fffff800`00b9cc18 00000000`0017ee08 fffff800`03006388 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`02e94d97 : 0000000b`365a68c1 0000000b`0017ee08 0000000b`365a680e 00000000`00000008 : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`02e91dfa : fffff800`03003e80 fffff800`03011c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys
BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80064d3060, Physical Device Object of the stack
Arg3: fffff80000b9c4d8, Functional Device Object of the stack
Arg4: fffffa8007bbb0e0, The blocked IRP
Debugging Details:
------------------
DRVPOWERSTATE_SUBCODE: 3
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bcc15
MODULE_NAME: usbccgp
FAULTING_MODULE: fffff8800606d000 usbccgp
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
STACK_TEXT:
fffff800`00b9c488 fffff800`02ef81b3 : 00000000`0000009f 00000000`00000003 fffffa80`064d3060 fffff800`00b9c4d8 : nt!KeBugCheckEx
fffff800`00b9c490 fffff800`02e956a6 : fffff800`00b9c5c0 fffff800`00b9c5c0 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x292f0
fffff800`00b9c530 fffff800`02e94a26 : fffff800`03039700 00000000`0017ee08 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5a0 fffff800`02e9557e : 00000038`f653d82e fffff800`00b9cc18 00000000`0017ee08 fffff800`03006388 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cbf0 fffff800`02e94d97 : 0000000b`365a68c1 0000000b`0017ee08 0000000b`365a680e 00000000`00000008 : nt!KiTimerExpiration+0x1be
fffff800`00b9cc90 fffff800`02e91dfa : fffff800`03003e80 fffff800`03011c40 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
FAILURE_BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys
BUCKET_ID: X64_0x9F_3_usbvideo_IMAGE_usbccgp.sys
Followup: MachineOwner