goombawaho
MIS
Here is the output of my crash dump analysis using the windows debugging tool. The memory tests out fine, so does that mean the USB controller on the motherboard is toast (a hardware issue)?? I are confused as to what to conclude.
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\Mini051311-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\symbols*Executable search path is: c:\i386
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805540c0
Debug session time: Fri May 13 11:33:48.234 2011 (GMT-4)
System Uptime: 0 days 0:32:22.781
Loading Kernel Symbols
...............................................................
........................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, 8427f0e0, 11063104, 8426b930}
Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveAsyncEndpoint+37 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: 8427f0e0, Device extension pointer of the host controller
Arg3: 11063104, PCI Vendor,Product id for the controller
Arg4: 8426b930, Pointer to Endpoint data structure
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from f724fe7b to 804f8cc5
STACK_TEXT:
f79d5e1c f724fe7b 000000fe 00000005 8427f0e0 nt!KeBugCheckEx+0x1b
f79d5e3c f725c7b9 8427f028 0000dfd0 83d25000 USBPORT!USBPORT_BugCheck+0x2d
f79d5e70 f7871c69 5650706d 8427f9dc 8426b930 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x11d
f79d5e94 f7872192 8427f9dc 8426b930 8426b930 usbehci!EHCI_PollActiveAsyncEndpoint+0x37
f79d5ef0 f7873f1d 8427f9dc 8426b930 f79d5f20 usbehci!EHCI_PollAsyncEndpoint+0x98
f79d5f00 f72494aa 8427f9dc 8426b930 80542788 usbehci!EHCI_PollEndpoint+0x1f
f79d5f20 f724a768 026c6f50 8427f0e0 8426b7b8 USBPORT!USBPORT_PollEndpoint+0xe8
f79d5f48 f724e0a0 8427f028 50457270 80542788 USBPORT!USBPORT_CoreEndpointWorker+0x2be
f79d5f78 f725c24b 8427f028 80542788 8427f028 USBPORT!USBPORT_DpcWorker+0x18a
f79d5fb4 f725c3c2 8427f028 00000001 8417c910 USBPORT!USBPORT_IsrDpcWorker+0x38f
f79d5fd0 80541c3d 8427f64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
f79d5ff4 8054190a ed1ed884 00000000 00000000 nt!KiRetireDpcList+0x46
f79d5ff8 ed1ed884 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
8054190a 00000000 00000009 bb835675 00000128 0xed1ed884
STACK_COMMAND: kb
FOLLOWUP_IP:
usbehci!EHCI_PollActiveAsyncEndpoint+37
f7871c69 50 push eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: usbehci!EHCI_PollActiveAsyncEndpoint+37
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbehci
IMAGE_NAME: usbehci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce
FAILURE_BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37
BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [c:\Mini051311-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*C:\symbols*Executable search path is: c:\i386
Windows XP Kernel Version 2600 (Service Pack 3) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp3_gdr.101209-1647
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805540c0
Debug session time: Fri May 13 11:33:48.234 2011 (GMT-4)
System Uptime: 0 days 0:32:22.781
Loading Kernel Symbols
...............................................................
........................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, 8427f0e0, 11063104, 8426b930}
Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveAsyncEndpoint+37 )
Followup: MachineOwner
---------
kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 00000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: 8427f0e0, Device extension pointer of the host controller
Arg3: 11063104, PCI Vendor,Product id for the controller
Arg4: 8426b930, Pointer to Endpoint data structure
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: explorer.exe
LAST_CONTROL_TRANSFER: from f724fe7b to 804f8cc5
STACK_TEXT:
f79d5e1c f724fe7b 000000fe 00000005 8427f0e0 nt!KeBugCheckEx+0x1b
f79d5e3c f725c7b9 8427f028 0000dfd0 83d25000 USBPORT!USBPORT_BugCheck+0x2d
f79d5e70 f7871c69 5650706d 8427f9dc 8426b930 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x11d
f79d5e94 f7872192 8427f9dc 8426b930 8426b930 usbehci!EHCI_PollActiveAsyncEndpoint+0x37
f79d5ef0 f7873f1d 8427f9dc 8426b930 f79d5f20 usbehci!EHCI_PollAsyncEndpoint+0x98
f79d5f00 f72494aa 8427f9dc 8426b930 80542788 usbehci!EHCI_PollEndpoint+0x1f
f79d5f20 f724a768 026c6f50 8427f0e0 8426b7b8 USBPORT!USBPORT_PollEndpoint+0xe8
f79d5f48 f724e0a0 8427f028 50457270 80542788 USBPORT!USBPORT_CoreEndpointWorker+0x2be
f79d5f78 f725c24b 8427f028 80542788 8427f028 USBPORT!USBPORT_DpcWorker+0x18a
f79d5fb4 f725c3c2 8427f028 00000001 8417c910 USBPORT!USBPORT_IsrDpcWorker+0x38f
f79d5fd0 80541c3d 8427f64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
f79d5ff4 8054190a ed1ed884 00000000 00000000 nt!KiRetireDpcList+0x46
f79d5ff8 ed1ed884 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2a
WARNING: Frame IP not in any known module. Following frames may be wrong.
8054190a 00000000 00000009 bb835675 00000128 0xed1ed884
STACK_COMMAND: kb
FOLLOWUP_IP:
usbehci!EHCI_PollActiveAsyncEndpoint+37
f7871c69 50 push eax
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: usbehci!EHCI_PollActiveAsyncEndpoint+37
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbehci
IMAGE_NAME: usbehci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 480254ce
FAILURE_BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37
BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37
Followup: MachineOwner
---------