Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\032811-18673-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0xfffff800`02e03000 PsLoadedModuleList = 0xfffff800`03048e90
Debug session time: Sun Mar 27 19:15:02.868 2011 (UTC - 4:00)
System Uptime: 13 days 11:37:49.398
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7F, {8, 80050031, 6f8, fffff80002e96519}
Probably caused by : NETIO.SYS ( NETIO!CompareSecurityContexts+6a )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
Arg2: 0000000080050031
Arg3: 00000000000006f8
Arg4: fffff80002e96519
Debugging Details:
------------------
BUGCHECK_STR: 0x7f_8
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from fffff80002e82be9 to fffff80002e83640
STACK_TEXT:
fffff880`009f0ce8 fffff800`02e82be9 : 00000000`0000007f 00000000`00000008 00000000`80050031 00000000`000006f8 : nt!KeBugCheckEx
fffff880`009f0cf0 fffff800`02e810b2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009f0e30 fffff800`02e96519 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2
fffff880`089bb000 fffff800`02e95844 : fffffa80`07d1c15c fffff880`089bb340 fffff880`089bb340 00000000`00000008 : nt!SepNormalAccessCheck+0x189
fffff880`089bb090 fffff800`02e95de8 : 00000000`00000001 00000000`00000000 fffff880`089bb340 fffff880`089bba50 : nt!SepAccessCheck+0x1d4
fffff880`089bb1c0 fffff800`02e5248e : fffffa80`08f5d7c8 00000000`00000001 fffffa80`07d1c148 00000000`00000000 : nt!SeAccessCheckWithHint+0x178
fffff880`089bb2c0 fffff880`01405a4a : fffff880`089bbb70 fffffa80`03fe6710 fffffa80`06ef69f0 00000000`00000000 : nt!SeAccessCheckFromState+0x102
fffff880`089bb9b0 fffff880`014052af : fffff880`00000000 fffff880`00000000 00020000`00020001 00020001`00020000 : NETIO!CompareSecurityContexts+0x6a
fffff880`089bba20 fffff880`01405444 : 00000000`00000000 00000000`00000000 00000000`00000003 fffff880`014d7999 : NETIO!MatchValues+0xef
fffff880`089bba70 fffff880`014057c1 : fffffa80`04d6d710 fffffa80`070c5350 fffff880`089bc2f0 fffff880`089bbcb0 : NETIO!FilterMatch+0x94
fffff880`089bbac0 fffff880`014066fc : 00000000`00000003 00000000`00000010 fffff880`089bc2f0 fffff880`089bbcb0 : NETIO!IndexHashClassify+0x151
fffff880`089bbb70 fffff880`01769819 : fffff880`089bc2f0 fffff880`089bc028 fffff880`089bce40 fffffa80`04cdb610 : NETIO!KfdClassify+0xa4e
fffff880`089bbee0 fffff880`017316f8 : fffffa80`04ca7bc0 fffff880`089bcd68 fffff880`0182f7a0 fffff880`089bce40 : tcpip!WfpAleClassify+0x49
fffff880`089bbf30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : tcpip!WfpAlepAuthorizeReceive+0x818
STACK_COMMAND: kb
FOLLOWUP_IP:
NETIO!CompareSecurityContexts+6a
fffff880`01405a4a 448b442470 mov r8d,dword ptr [rsp+70h]
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: NETIO!CompareSecurityContexts+6a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce79381
FAILURE_BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a
BUCKET_ID: X64_0x7f_8_NETIO!CompareSecurityContexts+6a
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\051611-26410-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02e13000 PsLoadedModuleList = 0xfffff800`03058650
Debug session time: Mon May 16 11:49:54.048 2011 (UTC - 4:00)
System Uptime: 3 days 10:10:39.188
Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
..................................................
Unable to load image \SystemRoot\system32\DRIVERS\usbhub.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for usbhub.sys
*** ERROR: Module load completed but symbols could not be loaded for usbhub.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {8, 6, 6, fffffa80060a8000}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Probably caused by : usbhub.sys ( usbhub+12a60 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 0000000000000006, TimeoutCode: Timeout_PCE_Disable_Action - PortData->PortChangeListDone - Timeout trying to set Disable bit
Arg4: fffffa80060a8000, TimeoutContext - PortData
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbport!_DEVICE_EXTENSION ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: usbhub!_DEVICE_EXTENSION_HUB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
Unable to open image file: E:\Program Files\Debugging Tools for Windows (x64)\sym\ntoskrnl.exe\4D9FDD5B5e9000\ntoskrnl.exe
The system cannot find the file specified.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: usbhub
FAULTING_MODULE: fffff80002e13000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d8c0c15
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0xFE
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff88007b0da60 to fffff80002e92d00
STACK_TEXT:
fffff880`031cbc18 fffff880`07b0da60 : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`00000006 : nt+0x7fd00
fffff880`031cbc20 00000000`000000fe : 00000000`00000008 00000000`00000006 00000000`00000006 fffffa80`060a8000 : usbhub+0x12a60
fffff880`031cbc28 00000000`00000008 : 00000000`00000006 00000000`00000006 fffffa80`060a8000 fffff880`00f1077d : 0xfe
fffff880`031cbc30 00000000`00000006 : 00000000`00000006 fffffa80`060a8000 fffff880`00f1077d 00000000`00000000 : 0x8
fffff880`031cbc38 00000000`00000006 : fffffa80`060a8000 fffff880`00f1077d 00000000`00000000 00000000`00000001 : 0x6
fffff880`031cbc40 fffffa80`060a8000 : fffff880`00f1077d 00000000`00000000 00000000`00000001 fffffa80`05ebc0f0 : 0x6
fffff880`031cbc48 fffff880`00f1077d : 00000000`00000000 00000000`00000001 fffffa80`05ebc0f0 fffffa80`05ebc0f0 : 0xfffffa80`060a8000
fffff880`031cbc50 fffff800`031890c3 : fffffa80`05b81050 00000000`00000001 ffffffff`dc3a58a0 fffff800`030302b8 : Wdf01000!FxWorkItem::WorkItemThunk+0x195
fffff880`031cbc80 fffffa80`05b81050 : 00000000`00000001 ffffffff`dc3a58a0 fffff800`030302b8 fffff800`031890a0 : nt+0x3760c3
fffff880`031cbc88 00000000`00000001 : ffffffff`dc3a58a0 fffff800`030302b8 fffff800`031890a0 fffff800`02e9d021 : 0xfffffa80`05b81050
fffff880`031cbc90 ffffffff`dc3a58a0 : fffff800`030302b8 fffff800`031890a0 fffff800`02e9d021 fffff800`03030200 : 0x1
fffff880`031cbc98 fffff800`030302b8 : fffff800`031890a0 fffff800`02e9d021 fffff800`03030200 fffff800`03189001 : 0xffffffff`dc3a58a0
fffff880`031cbca0 fffff800`031890a0 : fffff800`02e9d021 fffff800`03030200 fffff800`03189001 fffffa80`03a00b00 : nt+0x21d2b8
fffff880`031cbca8 fffff800`02e9d021 : fffff800`03030200 fffff800`03189001 fffffa80`03a00b00 00000000`00000000 : nt+0x3760a0
fffff880`031cbcb0 fffff800`03030200 : fffff800`03189001 fffffa80`03a00b00 00000000`00000000 fffff880`031cbce0 : nt+0x8a021
fffff880`031cbcb8 fffff800`03189001 : fffffa80`03a00b00 00000000`00000000 fffff880`031cbce0 00000000`00000001 : nt+0x21d200
fffff880`031cbcc0 fffffa80`03a00b00 : 00000000`00000000 fffff880`031cbce0 00000000`00000001 fffffa80`05ebc0f0 : nt+0x376001
fffff880`031cbcc8 00000000`00000000 : fffff880`031cbce0 00000000`00000001 fffffa80`05ebc0f0 00000000`00000000 : 0xfffffa80`03a00b00
STACK_COMMAND: kb
FOLLOWUP_IP:
usbhub+12a60
fffff880`07b0da60 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: usbhub+12a60
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: usbhub.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------