Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\030111-15756-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\windbgsymbols*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.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02e07000 PsLoadedModuleList = 0xfffff800`03044e50
Debug session time: Wed Mar 2 00:29:49.730 2011 (UTC - 5:00)
System Uptime: 0 days 0:01:11.041
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000096, fffff8800408af17, fffff880031cb818, fffff880031cb080}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : memory_corruption
Followup: memory_corruption
---------
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: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8800408af17, The address that the exception occurred at
Arg3: fffff880031cb818, Exception Record Address
Arg4: fffff880031cb080, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000096 - {
FAULTING_IP:
USBPORT!USBPORTSVC_EtwWrite+7
fffff880`0408af17 6c ins byte ptr [rdi],dx
EXCEPTION_RECORD: fffff880031cb818 -- (.exr 0xfffff880031cb818)
ExceptionAddress: fffff8800408af17 (USBPORT!USBPORTSVC_EtwWrite+0x0000000000000007)
ExceptionCode: c0000096
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff880031cb080 -- (.cxr 0xfffff880031cb080)
rax=fffff880031cba90 rbx=fffffa800585a6a0 rcx=fffffa800585a6a0
rdx=ffffffffffffffff rsi=fffffa80058591a0 rdi=000000000000000d
rip=fffff8800408af17 rsp=fffff880031cba58 rbp=fffffa8005859050
r8=0000000000000000 r9=0000000000000001 r10=0000000000000000
r11=fffff880031cbaa8 r12=fffffa800604a001 r13=0000000000000000
r14=00000000ffffffff r15=0000000000000001
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
USBPORT!USBPORTSVC_EtwWrite+0x7:
fffff880`0408af17 6c ins byte ptr [rdi],dx ds:002b:00000000`0000000d=??
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000096 - {
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: CODE_CORRUPTION
LAST_CONTROL_TRANSFER: from fffff8800405b1d7 to fffff8800408af17
STACK_TEXT:
fffff880`031cba58 fffff880`0405b1d7 : fffffa80`0585a6a0 00000000`00000001 00000000`ffffffff 00000000`00000000 : USBPORT!USBPORTSVC_EtwWrite+0x7
fffff880`031cba60 fffff880`04062399 : fffffa80`0604c050 fffffa80`058591a0 fffffa80`05859000 fffffa80`0604c000 : usbohci!OHCI_SuspendController+0x3b
fffff880`031cbab0 fffff880`0406c0f8 : fffffa80`0604c050 fffffa80`058591a0 fffffa80`0604a1a0 00000000`00000000 : USBPORT!MPf_SuspendController+0x1a5
fffff880`031cbb00 fffff880`0443d724 : fffffa80`0604c050 fffffa80`0604cec8 fffffa80`0604c9c8 00000000`00000000 : USBPORT!USBPORTBUSIF_SuspendRootHub+0xc0
fffff880`031cbb50 fffff880`0443c52f : 00000000`00000000 00000000`00000001 fffff880`00000003 fffffa80`0604c050 : usbhub!UsbhSshSuspendHub+0x14c
fffff880`031cbbb0 fffff880`0443c3cb : 00000000`00000001 00000000`00000001 fffffa80`0604c050 fffff800`02e822a1 : usbhub!Usbh_SSH_HubActive+0x13f
fffff880`031cbbe0 fffff880`0443d27d : fffffa80`0604c1a0 fffff800`0301c5f8 fffffa80`0604c050 fffffa80`0604c9c8 : usbhub!Usbh_SSH_Event+0x147
fffff880`031cbc10 fffff880`0440973f : fffffa80`0604c1a0 fffffa80`0604c050 00000000`00000001 fffffa80`0724e7c0 : usbhub!UsbhHubSSH_Worker+0x2d
fffff880`031cbc40 fffff800`03171943 : fffffa80`0604c050 fffffa80`039e3b60 fffffa80`0724e7c0 fffffa80`039e3b60 : usbhub!UsbhHubWorker+0x63
fffff880`031cbc80 fffff800`02e84961 : fffff800`0301c500 fffff800`03171920 fffffa80`039e3b60 00000000`00000000 : nt!IopProcessWorkItem+0x23
fffff880`031cbcb0 fffff800`0311a7c6 : 0000056e`00000000 fffffa80`039e3b60 00000000`00000080 fffffa80`039739e0 : nt!ExpWorkerThread+0x111
fffff880`031cbd40 fffff800`02e55c26 : fffff880`02f63180 fffffa80`039e3b60 fffff880`02f6dfc0 0000056e`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd80 00000000`00000000 : fffff880`031cc000 fffff880`031c6000 fffff880`031cb800 00000000`00000000 : nt!KxStartSystemThread+0x16
CHKIMG_EXTENSION: !chkimg -lo 50 -d !USBPORT
fffff8800408af16 - USBPORT!USBPORTSVC_EtwWrite+6
[ 89:99 ]
1 error : !USBPORT (fffff8800408af16)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
STACK_COMMAND: .cxr 0xfffff880031cb080 ; kb
FAILURE_BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: X64_MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
---------
