Crash Dump Analysis - What does it mean?? 2

[goombawaho]

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*

http://msdl.microsoft.com/download/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
---------

 

[satrow]

The stack_text is full of USB references so it looks like the problem is somewhere along the USB route. Is this a laptop or desktop? What USB devices are connected?

 

[goombawaho]

This is a desktop PC. At the time of these crashes ABSOLUTELY NO USB devices were connected. Only PS2 keyboard, PS2 mouse, and monitor cable.

I reloaded Windows TWICE (once was a repair install and the other was a full FORMAT and reload), so it's nothing I did wrong. FULLY patches after XP SP3 as well. The dates of the driver files (.SYS) are the same as on my XP machine, so it's not the driver files themselves.

That's why I suspect hardware.

 

[papadba]

"At the time of these crashes ABSOLUTELY NO USB devices were connected."
Which does not eliminate the ports from reference?

As there are many indications there is something bent/broken with USB, i'd determine why these diagnostics are generated.

"so it's nothing I did wrong."
I'll stand a bit off to the side, so if there is a lightning strike, i'll be out of range. . .<g>

 

[goombawaho]

so it's nothing I did wrong." Loaded XP a ton of times, I stand by my loads.

One time the system DID spontaneously shut down when I put a USB memory stick in one of the rear ports, which would further blame the actual USB system hardware, I guess.

 

[stduc]

Maybe a bad mobo but I would triple check I had the right drivers and check the cables were connected to the mobo firmly & correctly and then maybe replace the USB ports and cabling to the mobo?

 

[satrow]

One time the system DID spontaneously shut down when I put a USB memory stick in one of the rear ports, which would further blame the actual USB system hardware, I guess." That could suggest there's a bad connection/short in that port that's causing it.

 

[BadBigBen]

If the USB ports are not in use, then see if turning them off in the BIOS will alleviate the problem...

but I am with most here, in that there is an underlying hardware problem with the USB ports on the mainboard...

Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[goombawaho]

Yeah, I don't want to troubleshoot this to death, I was going to call it bad motherboard and be done with it.

I mean, you can't use a PC with disable USB ports and it can't be used like it is, so...............

".... I would triple check I had the right drivers and check the cables were connected to the mobo firmly & correctly and then maybe replace the USB ports and cabling to the mobo?"

USB port that caused reboot is ON the motherboard so it's not a cabling issue there.

Drivers are 100% up to date (though no usb drivers - I even installed the VIA 4 in 1 and a ViaPatch for the heck of it.

I guess I can see if I can disable all USB in the BIOS and see if it behaves. Thanks for the advice. The real problem with this whole thing is that I've done about $200 worth of work on a PC that is worth $80.

PCs are becoming throw away devices like paper towels.

 

[stduc]

PCs are becoming throw away devices like paper towels.

Never a truer word. It is rarely worth even upgrading a PC anymore, certainly not if it is older than a year or so. As for software issues it is best IMHO to keep regular image backups and just image restore rather than troubleshooting. Or reload from scratch if you don't backup. (your silly if you don't backup though)

Typical time to restore from an image on USB drive - 12 mins
Typical time to rebuild from scratch re-install software and re-customise - 1 working day

Just my 2p worth

 

[goombawaho]

1 working day" Wow - that would cripple me if it took that long. I usually "budget" about 2 - 2.5 hours for a full reload with a small amount of data backup, windows install, windows updates and program installs.

But anyway, I'm calling this a bad motherboard.

 

[stduc]

"1 working day" Wow - that would cripple me if it took that long.

You are quite right if that's all you do - about 5 minutes of your time and the rest being elapsed time. But I was talking about if it was your PC. So I am including customisation. I don't just mean picking your desktop either. I am talking about all the little things that make it look and feel as you like it. Personally I prefer the 12 minute restore, which is why I take weekly images. LOL

 

[goombawaho]

Details - oh that could take weeks to get everything nailed down if your retentive like me.

I had a customer one time that wanted everything back like it was on two PCs that they replaced. Took me about 7 hours to "get it back the way it was".

But the guy was wealthy, so no big deal.

Anyway, I called this motherboard bad, so closing this thread.