BleepingComputer.com: BSOD USBEHCI.SYS

If anyone can help, I am a new member here and this is the first time I post something. I keep getting BSOD on a 6 month old Dell Precision Mobile Workstation M6500, running WindowsXP SP3 64-bit. Below is the dump file analysis report:


Microsoft ® Windows Debugger Version 6.12.0002.633 AMD64
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Desktop\Mini012511-02.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 (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100427-1636
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Tue Jan 25 16:44:03.726 2011 (UTC - 5:00)
System Uptime: 0 days 2:08:03.468
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, 88e6e0e0, 80863b3c, 88e23998}

Probably caused by : usbehci.sys ( usbehci!EHCI_PollActiveAsyncEndpoint+37 )

Followup: MachineOwner
---------

2: 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: 88e6e0e0, Device extension pointer of the host controller
Arg3: 80863b3c, PCI Vendor,Product id for the controller
Arg4: 88e23998, Pointer to Endpoint data structure

Debugging Details:
------------------


CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from b599fe7b to 804f9f43

STACK_TEXT:
b84e7b74 b599fe7b 000000fe 00000005 88e6e0e0 nt!KeBugCheckEx+0x1b
b84e7b94 b59ac7b9 88e6e028 00000fd0 8856c000 USBPORT!USBPORT_BugCheck+0x2d
b84e7bc8 b842bc69 5650706d 88e6e9dc 88e23998 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x11d
b84e7bec b842c192 88e6e9dc 88e23998 88e23998 usbehci!EHCI_PollActiveAsyncEndpoint+0x37
b84e7c48 b842df1d 88e6e9dc 88e23998 b84e7c78 usbehci!EHCI_PollAsyncEndpoint+0x98
b84e7c58 b59994aa 88e6e9dc 88e23998 80546b0c usbehci!EHCI_PollEndpoint+0x1f
b84e7c78 b599a768 026c6f50 88e6e0e0 88e23820 USBPORT!USBPORT_PollEndpoint+0xe8
b84e7ca0 b599e0a0 88e6e028 50457270 80546b0c USBPORT!USBPORT_CoreEndpointWorker+0x2be
b84e7cd0 b59ac24b 88e6e028 80546b0c 88e6e028 USBPORT!USBPORT_DpcWorker+0x18a
b84e7d0c b59ac3c2 88e6e028 00000001 8055c0c0 USBPORT!USBPORT_IsrDpcWorker+0x38f
b84e7d28 80545ebf 88e6e64c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
b84e7d50 80545da4 00000000 0000000e 00000000 nt!KiRetireDpcList+0x61
b84e7d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
usbehci!EHCI_PollActiveAsyncEndpoint+37
b842bc69 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
---------

2: kd> lmvm usbehci
start end module name
b8428000 b842f600 usbehci (pdb symbols) c:\symbols\usbehci.pdb\EFB2A9AC22FC4AB18588464EE6D6826B1\usbehci.pdb
Loaded symbol image file: usbehci.sys
Mapped memory image file: c:\symbols\usbehci.sys\480254CE7600\usbehci.sys
Image path: usbehci.sys
Image name: usbehci.sys
Timestamp: Sun Apr 13 14:45:34 2008 (480254CE)
CheckSum: 000099D5
ImageSize: 00007600
File version: 5.1.2600.5512
Product version: 5.1.2600.5512
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 2.0 Dll
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: USBEHCI.sys
OriginalFilename: USBEHCI.sys
ProductVersion: 5.1.2600.5512
FileVersion: 5.1.2600.5512 (xpsp.080413-2108)
FileDescription: EHCI eUSB Miniport Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.

This post has been edited by Sh@rky: 31 January 2011 - 11:36 AM

Look in the Device Manager to see if there are any error in the Universal Serial Bus controllers. If there is, uninstall the driver. The driver will be reinstalled at the next start up.

No errors found in the Universal Serial Bus Controllers.

Please do the following as it will provide us with more information than the mini dump.

Please download BlueScreenView
No installation required.
Double click on BlueScreenView.exe file to run the program.
When scanning is done, go Edit>Select All.
Go File>Save Selected Items, and save the report as BSOD.txt.
Open BSOD.txt in Notepad, copy all content, and paste it into your next reply.

Here is the result of the instructions provided:

==================================================
Dump File : Mini012511-02.dmp
Crash Time : 1/25/2011 4:44:34 PM
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000005
Parameter 2 : 0x88e6e0e0
Parameter 3 : 0x80863b3c
Parameter 4 : 0x88e23998
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+ee7b
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\Users\Desktop\Mini012511-02.dmp
Processors Count : 8
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

==================================================
Dump File : Mini012511-01.dmp
Crash Time : 1/25/2011 2:36:08 PM
Bug Check String : BUGCODE_USB_DRIVER
Bug Check Code : 0x000000fe
Parameter 1 : 0x00000005
Parameter 2 : 0x88e5e0e0
Parameter 3 : 0x80863b34
Parameter 4 : 0x88c27f28
Caused By Driver : USBPORT.SYS
Caused By Address : USBPORT.SYS+ee7b
File Description :
Product Name :
Company :
File Version :
Processor : 32-bit
Computer Name :
Full Path : C:\Users\Desktop\Mini012511-01.dmp
Processors Count : 8
Major Version : 15
Minor Version : 2600
Dump File Size : 98,304
==================================================

Go to the Universal Serial Bus contollers and uninstall all of the drivers and then restart your computer. The drivers will be reinstalled with the restart.

Thank you for your prompt reply BC3, I won't be able to try it until tomorrow morning, I will let you know then.

I'll be here.

I have not been able to continue on this since the user has not been able to let me work on the laptop, hopefully sometime next week.

Hello DC3, the user finally contacted me and informed me that she received 2 BSOD and one freeze up this morning while she had the laptop docked. She's been working for a couple of weeks without the docking station and she does not get the BSODs. Is the docking port conisdered a USB device?

A docking station is a device into which you can plug your laptop in order to gain extra functionality, such as access to printers, mice, scanners, full-sized monitors and keyboards, and external hard drives. It basically is an extension for the USB or Firewire ports.

If the problem is only occurring with this docking station then I would suggest that it has a problem. This is assuming that she has no problems with her USB devices when not using the docking station.