Code:
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jcaswell\Windows_NT6_BSOD_jcgriff2\010412-45365-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a64000 PsLoadedModuleList = 0xfffff800`02ca9670
Debug session time: Wed Jan 4 12:19:33.855 2012 (UTC - 7:00)
System Uptime: 0 days 0:56:50.806
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002b123a2, fffff880031821d8, fffff88003181a30}
Probably caused by : usbccgp.sys ( usbccgp!UsbcReleaseRemoveLock+35 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002b123a2, The address that the exception occurred at
Arg3: fffff880031821d8, Exception Record Address
Arg4: fffff88003181a30, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02b123a2 48890a mov qword ptr [rdx],rcx
EXCEPTION_RECORD: fffff880031821d8 -- (.exr 0xfffff880031821d8)
ExceptionAddress: fffff80002b123a2 (nt!KxWaitForLockOwnerShip+0x0000000000000012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003181a30 -- (.cxr 0xfffff88003181a30)
rax=0000000000000000 rbx=fffffa8000410300 rcx=fffff880031824b0
rdx=04c0000000000542 rsi=fffff88002f63180 rdi=fffff880031824b0
rip=fffff80002b123a2 rsp=fffff88003182410 rbp=fffffa8005b36220
r8=fffff880031824b0 r9=fffff88002f63180 r10=fffffa80036e2750
r11=fffff880031824d8 r12=0000000005b36220 r13=fffffa8003e59828
r14=fffffa8003e596d0 r15=0000000000000013
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02b123a2 48890a mov qword ptr [rdx],rcx ds:002b:04c00000`00000542=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d13100
ffffffffffffffff
FOLLOWUP_IP:
usbccgp!UsbcReleaseRemoveLock+35
fffff880`06a06e41 4881c3e8000000 add rbx,0E8h
BUGCHECK_STR: 0x7E
LOCK_ADDRESS: fffff80002cdfb80 -- (!locks fffff80002cdfb80)
Resource @ nt!PiEngineLock (0xfffff80002cdfb80) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff80002cdfb80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002aeac4d to fffff80002b123a2
STACK_TEXT:
fffff880`03182410 fffff800`02aeac4d : fffffa80`00410300 fffff880`06a03290 00000000`00000013 00000000`00000001 : nt!KxWaitForLockOwnerShip+0x12
fffff880`03182440 fffff880`06a06e41 : fffffa80`05b36220 fffffa80`00410322 fffffa80`055e1010 fffffa80`03e59828 : nt!KeAcquireInStackQueuedSpinLock+0x8d
fffff880`03182490 fffff880`06a06fca : fffffa80`00410322 fffffa80`00410322 fffffa80`03e59828 00000000`00000000 : usbccgp!UsbcReleaseRemoveLock+0x35
fffff880`031824e0 fffff880`06a044a1 : fffffa80`055e1290 fffffa80`05d0ab58 fffffa80`055e1290 fffffa80`05ce7cb0 : usbccgp!UsbcCompleteIrp+0x2a
fffff880`03182510 fffff880`06a15b30 : fffffa80`055e1010 fffffa80`03e59820 fffffa80`03e59828 fffffa80`03e59828 : usbccgp!DispatchPdoPnp+0x339
fffff880`03182560 fffff880`06a01683 : 00000000`0000001b fffffa80`03e59820 fffffa80`0003131b fffffa80`055e1010 : usbccgp!USBC_PnP+0xd8
fffff880`031825a0 fffff800`02d4baf9 : fffffa80`03e596d0 00000000`c0000001 fffff880`03182600 fffffa80`055e1010 : usbccgp!USBC_Dispatch+0x233
fffff880`03182620 fffff800`02e9a708 : 00000000`c00000bb fffff880`03182860 fffff880`031827d8 fffffa80`03e596d0 : nt!IopSynchronousCall+0xc5
fffff880`03182690 fffff800`02e9d150 : 00000000`00000000 fffffa80`056ab790 00000000`00000000 fffffa80`056ab790 : nt!PnpIrpQueryID+0x68
fffff880`03182720 fffff800`02ecb89e : fffffa80`056ab790 00000000`00000000 00000000`00000001 00000000`00000001 : nt!PnpQueryID+0x30
fffff880`03182780 fffff800`02eccad8 : fffffa80`073cb6d0 fffffa80`056ab790 fffffa80`036eed90 00000000`00000001 : nt!PiProcessNewDeviceNode+0x12e
fffff880`03182950 fffff800`02ecd018 : fffff800`02cdd500 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PipProcessDevNodeTree+0x2e8
fffff880`03182bc0 fffff800`02bdd8e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000084 : nt!PiProcessReenumeration+0x98
fffff880`03182c10 fffff800`02aeb001 : fffff800`02bdd5c0 fffff800`02dd7901 fffffa80`037c0b00 fffffa80`056834f0 : nt!PnpDeviceActionWorker+0x327
fffff880`03182cb0 fffff800`02d7bfee : 00000000`00000000 fffffa80`037c0b60 00000000`00000080 fffffa80`03670890 : nt!ExpWorkerThread+0x111
fffff880`03182d40 fffff800`02ad25e6 : fffff880`03087180 fffffa80`037c0b60 fffff880`03092040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03182d80 00000000`00000000 : fffff880`03183000 fffff880`0317d000 fffff880`03182060 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbccgp!UsbcReleaseRemoveLock+35
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbccgp
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c0a
STACK_COMMAND: .cxr 0xfffff88003181a30 ; kb
FAILURE_BUCKET_ID: X64_0x7E_usbccgp!UsbcReleaseRemoveLock+35
BUCKET_ID: X64_0x7E_usbccgp!UsbcReleaseRemoveLock+35
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jcaswell\Windows_NT6_BSOD_jcgriff2\010912-44319-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a06000 PsLoadedModuleList = 0xfffff800`02c4b670
Debug session time: Mon Jan 9 12:49:07.736 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:29.686
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002ab43a2, fffff880031741d8, fffff88003173a30}
Probably caused by : usbccgp.sys ( usbccgp!UsbcReleaseRemoveLock+35 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ab43a2, The address that the exception occurred at
Arg3: fffff880031741d8, Exception Record Address
Arg4: fffff88003173a30, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02ab43a2 48890a mov qword ptr [rdx],rcx
EXCEPTION_RECORD: fffff880031741d8 -- (.exr 0xfffff880031741d8)
ExceptionAddress: fffff80002ab43a2 (nt!KxWaitForLockOwnerShip+0x0000000000000012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003173a30 -- (.cxr 0xfffff88003173a30)
rax=0000000000000000 rbx=fffffa8000410300 rcx=fffff880031744b0
rdx=0080000000000040 rsi=fffff88002f63180 rdi=fffff880031744b0
rip=fffff80002ab43a2 rsp=fffff88003174410 rbp=fffffa8005b55220
r8=fffff880031744b0 r9=fffff88002f63180 r10=fffffa80036e2790
r11=fffff880031744d8 r12=0000000005b55220 r13=fffffa8006051b58
r14=fffffa8006051a00 r15=0000000000000013
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02ab43a2 48890a mov qword ptr [rdx],rcx ds:002b:00800000`00000040=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb5100
ffffffffffffffff
FOLLOWUP_IP:
usbccgp!UsbcReleaseRemoveLock+35
fffff880`06d57e41 4881c3e8000000 add rbx,0E8h
BUGCHECK_STR: 0x7E
LOCK_ADDRESS: fffff80002c81b80 -- (!locks fffff80002c81b80)
Resource @ nt!PiEngineLock (0xfffff80002c81b80) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff80002c81b80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002a8cc4d to fffff80002ab43a2
STACK_TEXT:
fffff880`03174410 fffff800`02a8cc4d : fffffa80`00410300 fffff880`06d54290 00000000`00000013 00000000`00000001 : nt!KxWaitForLockOwnerShip+0x12
fffff880`03174440 fffff880`06d57e41 : fffffa80`05b55220 fffffa80`00410322 fffffa80`06016c60 fffffa80`06051b58 : nt!KeAcquireInStackQueuedSpinLock+0x8d
fffff880`03174490 fffff880`06d57fca : fffffa80`00410322 fffffa80`00410322 fffffa80`06051b58 00000000`00000000 : usbccgp!UsbcReleaseRemoveLock+0x35
fffff880`031744e0 fffff880`06d554a1 : fffffa80`06016ee0 fffffa80`0604ab58 fffffa80`06016ee0 fffffa80`036d64e0 : usbccgp!UsbcCompleteIrp+0x2a
fffff880`03174510 fffff880`06d66b30 : fffffa80`06016c60 fffffa80`06051b50 fffffa80`06051b58 fffffa80`06051b58 : usbccgp!DispatchPdoPnp+0x339
fffff880`03174560 fffff880`06d52683 : 00000000`0000001b fffffa80`06051b50 fffffa80`0003131b fffffa80`06016c60 : usbccgp!USBC_PnP+0xd8
fffff880`031745a0 fffff800`02cedaf9 : fffffa80`06051a00 00000000`c0000001 fffff880`03174600 fffffa80`06016c60 : usbccgp!USBC_Dispatch+0x233
fffff880`03174620 fffff800`02e3c708 : 00000000`c00000bb fffff880`03174860 fffff880`031747d8 fffffa80`06051a00 : nt!IopSynchronousCall+0xc5
fffff880`03174690 fffff800`02e3f150 : 00000000`00000000 fffffa80`06058c00 00000000`00000000 fffffa80`06058c00 : nt!PnpIrpQueryID+0x68
fffff880`03174720 fffff800`02e6d89e : fffffa80`06058c00 00000000`00000000 00000000`00000001 00000000`00000001 : nt!PnpQueryID+0x30
fffff880`03174780 fffff800`02e6ead8 : fffffa80`0605c980 fffffa80`06058c00 fffffa80`05fdea70 00000000`00000001 : nt!PiProcessNewDeviceNode+0x12e
fffff880`03174950 fffff800`02e6f018 : fffff800`02c7f500 00000000`00000000 00000000`00000001 fffff800`02cec814 : nt!PipProcessDevNodeTree+0x2e8
fffff880`03174bc0 fffff800`02b7f8e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`03174c10 fffff800`02a8d001 : fffff800`02b7f5c0 fffff800`02c23201 fffffa80`036d7000 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`03174cb0 fffff800`02d1dfee : 00000000`00000000 fffffa80`036d7040 00000000`00000080 fffffa80`03670890 : nt!ExpWorkerThread+0x111
fffff880`03174d40 fffff800`02a745e6 : fffff880`03087180 fffffa80`036d7040 fffff880`03092040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03174d80 00000000`00000000 : fffff880`03175000 fffff880`0316f000 fffff880`03174060 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbccgp!UsbcReleaseRemoveLock+35
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbccgp
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c0a
STACK_COMMAND: .cxr 0xfffff88003173a30 ; kb
FAILURE_BUCKET_ID: X64_0x7E_usbccgp!UsbcReleaseRemoveLock+35
BUCKET_ID: X64_0x7E_usbccgp!UsbcReleaseRemoveLock+35
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jcaswell\Windows_NT6_BSOD_jcgriff2\011012-44959-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a56000 PsLoadedModuleList = 0xfffff800`02c9b670
Debug session time: Tue Jan 10 14:40:45.314 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:29.265
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff80000410322, 8, fffff80000410322, 2}
Could not read faulting driver name
Probably caused by : usbccgp.sys ( usbccgp!DispatchPdoPnp+339 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80000410322, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80000410322, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d05100
fffff80000410322
FAULTING_IP:
+6436353063633837
fffff800`00410322 ?? ???
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88003182360 -- (.trap 0xfffff88003182360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000000017cf
rdx=fffff88002f70000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000410322 rsp=fffff880031824f0 rbp=fffff88003182570
r8=000000000000be78 r9=00000000000000a0 r10=fffff80002a56000
r11=fffff88003182470 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff800`00410322 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a7d3f0 to fffff80002ad2c40
STACK_TEXT:
fffff880`031821f8 fffff800`02a7d3f0 : 00000000`00000050 fffff800`00410322 00000000`00000008 fffff880`03182360 : nt!KeBugCheckEx
fffff880`03182200 fffff800`02ad0d6e : 00000000`00000008 fffff800`00410322 fffff8a0`00001900 fffffa80`037c0b60 : nt! ?? ::FNODOBFM::`string'+0x447c6
fffff880`03182360 fffff800`00410322 : fffffa80`037c0b60 fffff880`03182570 fffff8a0`00d53a60 fffff880`06a6b4a1 : nt!KiPageFault+0x16e
fffff880`031824f0 fffffa80`037c0b60 : fffff880`03182570 fffff8a0`00d53a60 fffff880`06a6b4a1 fffffa80`06044aa0 : 0xfffff800`00410322
fffff880`031824f8 fffff880`03182570 : fffff8a0`00d53a60 fffff880`06a6b4a1 fffffa80`06044aa0 fffffa80`06044a00 : 0xfffffa80`037c0b60
fffff880`03182500 fffff8a0`00d53a60 : fffff880`06a6b4a1 fffffa80`06044aa0 fffffa80`06044a00 ffffe0f9`185cf7dd : 0xfffff880`03182570
fffff880`03182508 fffff880`06a6b4a1 : fffffa80`06044aa0 fffffa80`06044a00 ffffe0f9`185cf7dd fffffa80`05f58850 : 0xfffff8a0`00d53a60
fffff880`03182510 fffff8a0`008922e0 : fffff8a0`00da3790 fffff800`02ab9231 fffffa80`06062b58 fffffa80`06062b58 : usbccgp!DispatchPdoPnp+0x339
fffff880`03182560 fffff8a0`00da3790 : fffff800`02ab9231 fffffa80`06062b58 fffffa80`06062b58 fffff8a0`008922e0 : 0xfffff8a0`008922e0
fffff880`03182568 fffff800`02ab9231 : fffffa80`06062b58 fffffa80`06062b58 fffff8a0`008922e0 fffffa80`06044820 : 0xfffff8a0`00da3790
fffff880`03182570 fffff800`02ab92a5 : 00000000`00000000 00000000`00000801 fffff880`00000001 6e657050`02ace470 : nt!vsnwprintf_l+0xd1
fffff880`031825e0 fffff800`02b5f4b8 : 00000000`c00000bb 00000000`00000000 00000000`00000000 00000000`00000000 : nt!vsnwprintf+0x11
fffff880`03182620 fffff8a0`00da3790 : 00000000`00000000 fffff800`02ace470 00000000`00000010 00000000`00000086 : nt!IopExceptionFilter+0x68
fffff880`03182650 00000000`00000000 : fffff800`02ace470 00000000`00000010 00000000`00000086 fffff880`03182688 : 0xfffff8a0`00da3790
STACK_COMMAND: kb
FOLLOWUP_IP:
usbccgp!DispatchPdoPnp+339
fffff880`06a6b4a1 488b5c2450 mov rbx,qword ptr [rsp+50h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: usbccgp!DispatchPdoPnp+339
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbccgp
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c0a
FAILURE_BUCKET_ID: X64_0x50_usbccgp!DispatchPdoPnp+339
BUCKET_ID: X64_0x50_usbccgp!DispatchPdoPnp+339
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jcaswell\Windows_NT6_BSOD_jcgriff2\011112-49483-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a02000 PsLoadedModuleList = 0xfffff800`02c47670
Debug session time: Wed Jan 11 11:40:22.940 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:29.236
Loading Kernel Symbols
...............................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002ab03a2, fffff8800317b1d8, fffff8800317aa30}
Probably caused by : usbccgp.sys ( usbccgp!UsbcReleaseRemoveLock+35 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002ab03a2, The address that the exception occurred at
Arg3: fffff8800317b1d8, Exception Record Address
Arg4: fffff8800317aa30, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02ab03a2 48890a mov qword ptr [rdx],rcx
EXCEPTION_RECORD: fffff8800317b1d8 -- (.exr 0xfffff8800317b1d8)
ExceptionAddress: fffff80002ab03a2 (nt!KxWaitForLockOwnerShip+0x0000000000000012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800317aa30 -- (.cxr 0xfffff8800317aa30)
rax=0000000000000000 rbx=fffffa8000410300 rcx=fffff8800317b4b0
rdx=0080000000000040 rsi=fffff88002f63180 rdi=fffff8800317b4b0
rip=fffff80002ab03a2 rsp=fffff8800317b410 rbp=fffffa8005421010
r8=fffff8800317b4b0 r9=fffff88002f63180 r10=fffffa80036e28e0
r11=fffff8800317b4d8 r12=0000000005421010 r13=fffffa8005fd79c8
r14=fffffa8005fd7870 r15=0000000000000013
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02ab03a2 48890a mov qword ptr [rdx],rcx ds:002b:00800000`00000040=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cb1100
ffffffffffffffff
FOLLOWUP_IP:
usbccgp!UsbcReleaseRemoveLock+35
fffff880`053afe41 4881c3e8000000 add rbx,0E8h
BUGCHECK_STR: 0x7E
LOCK_ADDRESS: fffff80002c7db80 -- (!locks fffff80002c7db80)
Resource @ nt!PiEngineLock (0xfffff80002c7db80) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff80002c7db80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002a88c4d to fffff80002ab03a2
STACK_TEXT:
fffff880`0317b410 fffff800`02a88c4d : fffffa80`00410300 00000000`00000000 005f0049`004d0000 00000000`00000001 : nt!KxWaitForLockOwnerShip+0x12
fffff880`0317b440 fffff880`053afe41 : fffffa80`05421010 fffffa80`00410322 fffffa80`05f0ac60 fffffa80`05fd79c8 : nt!KeAcquireInStackQueuedSpinLock+0x8d
fffff880`0317b490 fffff880`053affca : fffffa80`00410322 fffffa80`00410322 fffffa80`05fd79c8 00000000`00000000 : usbccgp!UsbcReleaseRemoveLock+0x35
fffff880`0317b4e0 fffff880`053ad4a1 : fffffa80`05f0aee0 fffffa80`05fedb58 fffffa80`05f0aee0 fffffa80`057c9660 : usbccgp!UsbcCompleteIrp+0x2a
fffff880`0317b510 fffff880`053beb30 : fffffa80`05f0ac60 fffffa80`05fd79c0 fffffa80`05fd79c8 fffffa80`05fd79c8 : usbccgp!DispatchPdoPnp+0x339
fffff880`0317b560 fffff880`053aa683 : 00000000`0000001b fffffa80`05fd79c0 fffffa80`0001131b fffffa80`05f0ac60 : usbccgp!USBC_PnP+0xd8
fffff880`0317b5a0 fffff800`02ce9af9 : fffffa80`05fd7870 00000000`c0000001 fffff880`0317b600 fffffa80`05f0ac60 : usbccgp!USBC_Dispatch+0x233
fffff880`0317b620 fffff800`02e38708 : 00000000`c00000bb fffff880`0317b830 fffff880`0317b808 00000000`00000000 : nt!IopSynchronousCall+0xc5
fffff880`0317b690 fffff800`02e3b150 : 00000000`000f003f fffffa80`05feed90 fffff8a0`00000001 fffffa80`05feed90 : nt!PnpIrpQueryID+0x68
fffff880`0317b720 fffff800`02e6a0bf : fffffa80`05feed90 ffffffff`80000278 00000000`00000000 fffffa80`05fd7870 : nt!PnpQueryID+0x30
fffff880`0317b780 fffff800`02e6aad8 : fffffa80`05fef980 fffffa80`05feed90 fffffa80`05f69d90 00000000`00000001 : nt!PiProcessNewDeviceNode+0x94f
fffff880`0317b950 fffff800`02e6b018 : fffff800`02c7b500 00000000`00000000 00000000`00000001 fffff800`02ce8814 : nt!PipProcessDevNodeTree+0x2e8
fffff880`0317bbc0 fffff800`02b7b8e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`0317bc10 fffff800`02a89001 : fffff800`02b7b5c0 fffff800`02c1f201 fffffa80`037abb00 00000000`00000000 : nt!PnpDeviceActionWorker+0x327
fffff880`0317bcb0 fffff800`02d19fee : 00000000`00000000 fffffa80`037abb60 00000000`00000080 fffffa80`03670890 : nt!ExpWorkerThread+0x111
fffff880`0317bd40 fffff800`02a705e6 : fffff880`03087180 fffffa80`037abb60 fffff880`03092040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0317bd80 00000000`00000000 : fffff880`0317c000 fffff880`03176000 fffff880`0317b060 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbccgp!UsbcReleaseRemoveLock+35
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbccgp
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c0a
STACK_COMMAND: .cxr 0xfffff8800317aa30 ; kb
FAILURE_BUCKET_ID: X64_0x7E_usbccgp!UsbcReleaseRemoveLock+35
BUCKET_ID: X64_0x7E_usbccgp!UsbcReleaseRemoveLock+35
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jcaswell\Windows_NT6_BSOD_jcgriff2\011112-44335-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a1d000 PsLoadedModuleList = 0xfffff800`02c62670
Debug session time: Wed Jan 11 16:00:03.548 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:29.499
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {fffff80000410322, 8, fffff80000410322, 2}
Could not read faulting driver name
Probably caused by : usbccgp.sys ( usbccgp!DispatchPdoPnp+339 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff80000410322, memory referenced.
Arg2: 0000000000000008, value 0 = read operation, 1 = write operation.
Arg3: fffff80000410322, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)
Debugging Details:
------------------
Could not read faulting driver name
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ccc100
fffff80000410322
FAULTING_IP:
+6436353063633837
fffff800`00410322 ?? ???
MM_INTERNAL_CODE: 2
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x50
PROCESS_NAME: System
CURRENT_IRQL: 0
TRAP_FRAME: fffff88003166360 -- (.trap 0xfffff88003166360)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=00000000000017cf
rdx=fffff88002f70000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80000410322 rsp=fffff880031664f0 rbp=fffff88003166570
r8=000000000000be78 r9=00000000000000a0 r10=fffff80002a1d000
r11=fffff88003166470 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
fffff800`00410322 ?? ???
Resetting default scope
LAST_CONTROL_TRANSFER: from fffff80002a443f0 to fffff80002a99c40
STACK_TEXT:
fffff880`031661f8 fffff800`02a443f0 : 00000000`00000050 fffff800`00410322 00000000`00000008 fffff880`03166360 : nt!KeBugCheckEx
fffff880`03166200 fffff800`02a97d6e : 00000000`00000008 fffff800`00410322 fffff8a0`00001900 fffffa80`0377a040 : nt! ?? ::FNODOBFM::`string'+0x447c6
fffff880`03166360 fffff800`00410322 : fffffa80`0377a040 fffff880`03166570 fffff8a0`00a35f20 fffff880`052694a1 : nt!KiPageFault+0x16e
fffff880`031664f0 fffffa80`0377a040 : fffff880`03166570 fffff8a0`00a35f20 fffff880`052694a1 fffffa80`05f1bb30 : 0xfffff800`00410322
fffff880`031664f8 fffff880`03166570 : fffff8a0`00a35f20 fffff880`052694a1 fffffa80`05f1bb30 fffffa80`05f1bb00 : 0xfffffa80`0377a040
fffff880`03166500 fffff8a0`00a35f20 : fffff880`052694a1 fffffa80`05f1bb30 fffffa80`05f1bb00 ffffe0fb`217f458e : 0xfffff880`03166570
fffff880`03166508 fffff880`052694a1 : fffffa80`05f1bb30 fffffa80`05f1bb00 ffffe0fb`217f458e fffffa80`05f2c820 : 0xfffff8a0`00a35f20
fffff880`03166510 fffff8a0`00a5bea0 : fffff8a0`00116ea0 fffff800`02a80231 fffffa80`05f47b58 fffffa80`05f47b58 : usbccgp!DispatchPdoPnp+0x339
fffff880`03166560 fffff8a0`00116ea0 : fffff800`02a80231 fffffa80`05f47b58 fffffa80`05f47b58 fffff8a0`00a5bea0 : 0xfffff8a0`00a5bea0
fffff880`03166568 fffff800`02a80231 : fffffa80`05f47b58 fffffa80`05f47b58 fffff8a0`00a5bea0 fffffa80`05f1b8b0 : 0xfffff8a0`00116ea0
fffff880`03166570 fffff800`02a802a5 : 00000000`00000000 00000000`00000801 fffff880`00000001 6e657050`02a95470 : nt!vsnwprintf_l+0xd1
fffff880`031665e0 fffff800`02b264b8 : 00000000`c00000bb 00000000`00000000 00000000`00000000 00000000`00000000 : nt!vsnwprintf+0x11
fffff880`03166620 fffff8a0`00116ea0 : 00000000`00000000 fffff800`02a95470 00000000`00000010 00000000`00000086 : nt!IopExceptionFilter+0x68
fffff880`03166650 00000000`00000000 : fffff800`02a95470 00000000`00000010 00000000`00000086 fffff880`03166688 : 0xfffff8a0`00116ea0
STACK_COMMAND: kb
FOLLOWUP_IP:
usbccgp!DispatchPdoPnp+339
fffff880`052694a1 488b5c2450 mov rbx,qword ptr [rsp+50h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: usbccgp!DispatchPdoPnp+339
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbccgp
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c0a
FAILURE_BUCKET_ID: X64_0x50_usbccgp!DispatchPdoPnp+339
BUCKET_ID: X64_0x50_usbccgp!DispatchPdoPnp+339
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\jcaswell\Windows_NT6_BSOD_jcgriff2\011112-47190-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a68000 PsLoadedModuleList = 0xfffff800`02cad670
Debug session time: Wed Jan 11 16:44:31.724 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:36.675
Loading Kernel Symbols
...............................................................
................................................................
....
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002b163a2, fffff880031891d8, fffff88003188a30}
Probably caused by : usbccgp.sys ( usbccgp!UsbcReleaseRemoveLock+35 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002b163a2, The address that the exception occurred at
Arg3: fffff880031891d8, Exception Record Address
Arg4: fffff88003188a30, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
nt!KxWaitForLockOwnerShip+12
fffff800`02b163a2 48890a mov qword ptr [rdx],rcx
EXCEPTION_RECORD: fffff880031891d8 -- (.exr 0xfffff880031891d8)
ExceptionAddress: fffff80002b163a2 (nt!KxWaitForLockOwnerShip+0x0000000000000012)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88003188a30 -- (.cxr 0xfffff88003188a30)
rax=0000000000000000 rbx=fffffa8000410300 rcx=fffff880031894b0
rdx=0080000000000040 rsi=fffff88002f63180 rdi=fffff880031894b0
rip=fffff80002b163a2 rsp=fffff88003189410 rbp=fffffa8005b02220
r8=fffff880031894b0 r9=fffff88002f63180 r10=fffffa8003749e00
r11=fffff880031894d8 r12=0000000005b02220 r13=fffffa800605cb58
r14=fffffa800605ca00 r15=0000000000000013
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!KxWaitForLockOwnerShip+0x12:
fffff800`02b163a2 48890a mov qword ptr [rdx],rcx ds:002b:00800000`00000040=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d17100
ffffffffffffffff
FOLLOWUP_IP:
usbccgp!UsbcReleaseRemoveLock+35
fffff880`0539ee41 4881c3e8000000 add rbx,0E8h
BUGCHECK_STR: 0x7E
LOCK_ADDRESS: fffff80002ce3b80 -- (!locks fffff80002ce3b80)
Resource @ nt!PiEngineLock (0xfffff80002ce3b80) Available
WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.
WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.
1 total locks
PNP_TRIAGE:
Lock address : 0xfffff80002ce3b80
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0
LAST_CONTROL_TRANSFER: from fffff80002aeec4d to fffff80002b163a2
STACK_TEXT:
fffff880`03189410 fffff800`02aeec4d : fffffa80`00410300 fffff880`0539b290 00000000`00000013 00000000`00000001 : nt!KxWaitForLockOwnerShip+0x12
fffff880`03189440 fffff880`0539ee41 : fffffa80`05b02220 fffffa80`00410322 fffffa80`06062c60 fffffa80`0605cb58 : nt!KeAcquireInStackQueuedSpinLock+0x8d
fffff880`03189490 fffff880`0539efca : fffffa80`00410322 fffffa80`00410322 fffffa80`0605cb58 00000000`00000000 : usbccgp!UsbcReleaseRemoveLock+0x35
fffff880`031894e0 fffff880`0539c4a1 : fffffa80`06062ee0 fffffa80`0602cb58 fffffa80`06062ee0 fffffa80`05ff0c70 : usbccgp!UsbcCompleteIrp+0x2a
fffff880`03189510 fffff880`053adb30 : fffffa80`06062c60 fffffa80`0605cb50 fffffa80`0605cb58 fffffa80`0605cb58 : usbccgp!DispatchPdoPnp+0x339
fffff880`03189560 fffff880`05399683 : 00000000`0000001b fffffa80`0605cb50 fffffa80`0003131b fffffa80`06062c60 : usbccgp!USBC_PnP+0xd8
fffff880`031895a0 fffff800`02d4faf9 : fffffa80`0605ca00 00000000`c0000001 fffff880`03189600 fffffa80`06062c60 : usbccgp!USBC_Dispatch+0x233
fffff880`03189620 fffff800`02e9e708 : 00000000`c00000bb fffff880`03189860 fffff880`031897d8 fffffa80`0605ca00 : nt!IopSynchronousCall+0xc5
fffff880`03189690 fffff800`02ea1150 : 00000000`00000000 fffffa80`05781900 00000000`00000000 fffffa80`05781900 : nt!PnpIrpQueryID+0x68
fffff880`03189720 fffff800`02ecf89e : fffffa80`05781900 00000000`00000000 00000000`00000001 00000000`00000001 : nt!PnpQueryID+0x30
fffff880`03189780 fffff800`02ed0ad8 : fffffa80`056ae2b0 fffffa80`05781900 fffffa80`0605f5b0 00000000`00000001 : nt!PiProcessNewDeviceNode+0x12e
fffff880`03189950 fffff800`02ed1018 : fffff800`02ce1500 00000000`00000000 00000000`00000001 fffff800`02d4e814 : nt!PipProcessDevNodeTree+0x2e8
fffff880`03189bc0 fffff800`02be18e7 : 00000001`00000003 00000000`00000000 00000000`00000001 00000000`00000000 : nt!PiProcessReenumeration+0x98
fffff880`03189c10 fffff800`02aef001 : fffff800`02be15c0 fffffa80`03726b01 00000000`00000000 fffffa80`03726b60 : nt!PnpDeviceActionWorker+0x327
fffff880`03189cb0 fffff800`02d7ffee : 00000000`00000000 fffffa80`03726b60 00000000`00000080 fffffa80`03670890 : nt!ExpWorkerThread+0x111
fffff880`03189d40 fffff800`02ad65e6 : fffff880`03087180 fffffa80`03726b60 fffff880`03092040 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`03189d80 00000000`00000000 : fffff880`0318a000 fffff880`03184000 fffff880`03189060 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbccgp!UsbcReleaseRemoveLock+35
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbccgp
IMAGE_NAME: usbccgp.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c0a
STACK_COMMAND: .cxr 0xfffff88003188a30 ; kb
FAILURE_BUCKET_ID: X64_0x7E_usbccgp!UsbcReleaseRemoveLock+35
BUCKET_ID: X64_0x7E_usbccgp!UsbcReleaseRemoveLock+35
Followup: MachineOwner
---------
These all point to the USB Common Class Generic Parent Driver, which is a system driver for your USB devices. Run through the steps in 
Quote