Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\Mini020613-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*c:symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Personal Built by: 2600.xpsp_sp3_gdr.130107-0416 Machine Name: Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720 Debug session time: Wed Feb 6 07:29:26.000 2013 (GMT+1) System Uptime: 0 days 0:51:32.750 Loading Kernel Symbols ............................................................... ................................................................ Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 1000007F, {d, 0, 0, 0} Probably caused by : hardware ( USBPORT!USBPORT_FlushCancelList+f9 ) Followup: MachineOwner --------- 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP_M (1000007f) 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: 0000000d, EXCEPTION_GP_FAULT Arg2: 00000000 Arg3: 00000000 Arg4: 00000000 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_d CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT PROCESS_NAME: plugin-containe MISALIGNED_IP: USBPORT!USBPORT_FlushCancelList+f9 f5e7a2af 00837814000f add byte ptr [ebx+0F001478h],al LAST_CONTROL_TRANSFER: from f5e777c3 to f5e7a2af STACK_TEXT: f79faef4 f5e777c3 02504b90 80546b8c 86504b90 USBPORT!USBPORT_FlushCancelList+0xf9 f79faf1c f5e79b7c 86737028 867370e0 86504b90 USBPORT!USBPORT_DmaEndpointWorker+0x1b9 f79faf44 f5e7d0a0 86737028 00000003 80546b8c USBPORT!USBPORT_CoreEndpointWorker+0x6d2 f79faf74 f5e8b24b 86737028 80546b8c 86737028 USBPORT!USBPORT_DpcWorker+0x18a f79fafb0 f5e8b3c2 86737028 00000001 864fe308 USBPORT!USBPORT_IsrDpcWorker+0x38f f79fafcc 80545f3f 8673764c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166 f79faff4 80545aab b7e19d44 00000000 00000000 nt!KiRetireDpcList+0x61 f79faff8 b7e19d44 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2b WARNING: Frame IP not in any known module. Following frames may be wrong. 80545aab 00000000 00000009 0081850f bb830000 0xb7e19d44 STACK_COMMAND: kb FOLLOWUP_IP: USBPORT!USBPORT_FlushCancelList+f9 f5e7a2af 00837814000f add byte ptr [ebx+0F001478h],al SYMBOL_STACK_INDEX: 0 SYMBOL_NAME: USBPORT!USBPORT_FlushCancelList+f9 FOLLOWUP_NAME: MachineOwner IMAGE_NAME: hardware DEBUG_FLR_IMAGE_TIMESTAMP: 0 MODULE_NAME: hardware FAILURE_BUCKET_ID: IP_MISALIGNED BUCKET_ID: IP_MISALIGNED Followup: MachineOwner ---------