Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\082810-17971-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
WARNING: Whitespace at end of path element
Symbol search path is: SRV*C:\symbols;*http://msdl.microsoft.com/download/symbols ;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02e60000 PsLoadedModuleList = 0xfffff800`0309de50
Debug session time: Sat Aug 28 03:36:34.150 2010 (GMT-4)
System Uptime: 0 days 0:00:14.617
Loading Kernel Symbols
...............................................................
................................................................
.........
Loading User Symbols
Unable to load image \SystemRoot\system32\DRIVERS\nusb3xhc.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nusb3xhc.sys
*** ERROR: Module load completed but symbols could not be loaded for nusb3xhc.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff880047e4169, fffff880033bcdc8, fffff880033bc630}
Probably caused by : nusb3xhc.sys ( nusb3xhc+19169 )
Followup: MachineOwner
---------
0: 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: fffff880047e4169, The address that the exception occurred at
Arg3: fffff880033bcdc8, Exception Record Address
Arg4: fffff880033bc630, 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:
nusb3xhc+19169
fffff880`047e4169 488b4810 mov rcx,qword ptr [rax+10h]
EXCEPTION_RECORD: fffff880033bcdc8 -- (.exr 0xfffff880033bcdc8)
ExceptionAddress: fffff880047e4169 (nusb3xhc+0x0000000000019169)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000069
Attempt to read from address 0000000000000069
CONTEXT: fffff880033bc630 -- (.cxr 0xfffff880033bc630)
rax=0000000000000059 rbx=fffffa800739ad70 rcx=fffffa8006790680
rdx=fffffa80059d5910 rsi=fffffa80059d5910 rdi=fffffa8006790680
rip=fffff880047e4169 rsp=fffff880033bd000 rbp=fffffa8007351700
r8=fffffa800739ad70 r9=fffffa800739ad70 r10=fffffa8006790680
r11=0000000000000001 r12=0000000000000000 r13=fffff880033bd800
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
nusb3xhc+0x19169:
fffff880`047e4169 488b4810 mov rcx,qword ptr [rax+10h] ds:002b:00000000`00000069=????????????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
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: 0000000000000069
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800031080e0
0000000000000069
FOLLOWUP_IP:
nusb3xhc+19169
fffff880`047e4169 488b4810 mov rcx,qword ptr [rax+10h]
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffff8a001ecbd00 to fffff880047e4169
STACK_TEXT:
fffff880`033bd000 fffff8a0`01ecbd00 : fffff800`02ed2d26 fffff880`00000001 00000000`00000000 ffff0000`07457d9e : nusb3xhc+0x19169
fffff880`033bd008 fffff800`02ed2d26 : fffff880`00000001 00000000`00000000 ffff0000`07457d9e fffff800`0304ae00 : 0xfffff8a0`01ecbd00
fffff880`033bd010 00000000`00000000 : 00000000`00000000 fffff880`033bd800 fffffa80`059d5910 fffff880`047e25c3 : nt!IopfCompleteRequest+0x3a6
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nusb3xhc+19169
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nusb3xhc
IMAGE_NAME: nusb3xhc.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ae5b004
STACK_COMMAND: .cxr 0xfffff880033bc630 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nusb3xhc+19169
BUCKET_ID: X64_0x7E_nusb3xhc+19169
Followup: MachineOwner
---------
