BSOD bugcode_usb_driver on new laptop!

[nicchen]

Hi Everyone, this is my first post here, so please be patient

I ordered a new Alienware m17x Windows 7 Ultimate x64 laptop from Dell in Septmeber this year (2010) and have had the machine at my house since first week of October. I had a few issues with it which was resulting in BSODs of all different natures and Dell came to my house about a week ago to replace BOTH Graphics cards and all 8GB of RAM.

Since then i have only had 1 BSOD which seems to be linked to the power settings on the laptop? Just a guess, but everytime i leave the laptop on for a period of time and try and 'wake' it up from hibernation by moving the mouse, touching the mouse pad or hitting keys on the keyboard, the USB mouse (Alienware's TACTX Mouse), touchpad and keyboard are ALL unresponsive, then the laptop dumps the system with the BSOD BUGCODE_USB_DRIVER. If i unplug the mouse whilst it is unresponsive and replug into the same USB port or a different one, no lights on the mouse come up, like there is no power being sent to it??

I have changed the power settings to never turn off HDDS & never turn off selective USB ports, but apart from that i am at loss as to how to fix this. It is the last hurdle towards a stable system. The only USB items i have had on the laptop so far are the Alienware TactX mouse which comes with its own DVD for software and drivers, and a small 4GB USB stick which has no drivers or software on it.

System Specs
- Windows 7 Ultimate x64 i7 940 - system installed by Dell, OEM version.
- laptop shipped to me first week October 2010.
- restored the system to the recovery environment about 2 weeks ago while on the phone to dell tech support.
- 8GB RAM 1333
- DUAL ATI Radeon HD 5870 1GB Graphics Cards in CrossFire.
- Alienware TactX Mouse.
- 2x 500GB HDDs in RAID 1


BSOD .dmp files are attached to this post as per forum instructions.

Any help is greatly appreciated! :shock:

 

[zigzag3143]

Hi Everyone, this is my first post here, so please be patient

I ordered a new Alienware m17x Windows 7 Ultimate x64 laptop from Dell in Septmeber this year (2010) and have had the machine at my house since first week of October. I had a few issues with it which was resulting in BSODs of all different natures and Dell came to my house about a week ago to replace BOTH Graphics cards and all 8GB of RAM.

Since then i have only had 1 BSOD which seems to be linked to the power settings on the laptop? Just a guess, but everytime i leave the laptop on for a period of time and try and 'wake' it up from hibernation by moving the mouse, touching the mouse pad or hitting keys on the keyboard, the USB mouse (Alienware's TACTX Mouse), touchpad and keyboard are ALL unresponsive, then the laptop dumps the system with the BSOD BUGCODE_USB_DRIVER. If i unplug the mouse whilst it is unresponsive and replug into the same USB port or a different one, no lights on the mouse come up, like there is no power being sent to it??

I have changed the power settings to never turn off HDDS & never turn off selective USB ports, but apart from that i am at loss as to how to fix this. It is the last hurdle towards a stable system. The only USB items i have had on the laptop so far are the Alienware TactX mouse which comes with its own DVD for software and drivers, and a small 4GB USB stick which has no drivers or software on it.

System Specs
- Windows 7 Ultimate x64 i7 940 - system installed by Dell, OEM version.
- laptop shipped to me first week October 2010.
- restored the system to the recovery environment about 2 weeks ago while on the phone to dell tech support.
- 8GB RAM 1333
- DUAL ATI Radeon HD 5870 1GB Graphics Cards in CrossFire.
- Alienware TactX Mouse.
- 2x 500GB HDDs in RAID 1


BSOD .dmp files are attached to this post as per forum instructions.

Any help is greatly appreciated! :shock:

These are all virtually identical. All caused by usbehci.sys. The process EHCI eUSB Miniport Driver belongs to the software Microsoft USB 2.0 Enhanced Host Controller Miniport Driver by Microsoft Corporation (Microsoft Corporation).

Ok either you have bunch of unpowered external USB devices (3 or more) or there is a corrupt file.

Lets assume you dont and first I would run a system file check
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S

Also just to be safe I would run a memory test
Download a copy of Memtest86 and burn the ISO to a CD using Iso Recorder or another ISO burning program. Boot from the CD, and leave it running for at least 5 or 6 passes.


Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots.

Let us know if you need help

Ken J

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\110910-26301-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c4c000 PsLoadedModuleList = 0xfffff800`02e89e50
Debug session time: Mon Nov  8 20:39:20.778 2010 (GMT-5)
System Uptime: 0 days 3:09:30.777
Loading Kernel Symbols
...............................................................
................................................................
.................................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, fffffa800a8c51a0, 80863b34, fffffa800af45250}

*** WARNING: Unable to verify timestamp for usbehci.sys
*** ERROR: Module load completed but symbols could not be loaded for usbehci.sys
Probably caused by : usbehci.sys ( usbehci+5fdf )

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

7: kd> !anallyze -v
No export anallyze found
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
    using a physical memory address that was not allocated by
    the USBport driver.
Arg2: fffffa800a8c51a0, Device extension pointer of the host controller
Arg3: 0000000080863b34, PCI Vendor,Product id for the controller
Arg4: fffffa800af45250, Pointer to Endpoint data structure

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


CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xFE

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8800466ae4e to fffff80002cbc740

STACK_TEXT:  
fffff880`03392a18 fffff880`0466ae4e : 00000000`000000fe 00000000`00000005 fffffa80`0a8c51a0 00000000`80863b34 : nt!KeBugCheckEx
fffff880`03392a20 fffff880`04631fdf : 00000000`ac1447c0 fffffa80`0a8c66a0 fffffa80`0af453c0 00000000`00000000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`03392a60 00000000`ac1447c0 : fffffa80`0a8c66a0 fffffa80`0af453c0 00000000`00000000 fffffa80`0af453c0 : usbehci+0x5fdf
fffff880`03392a68 fffffa80`0a8c66a0 : fffffa80`0af453c0 00000000`00000000 fffffa80`0af453c0 00000000`ac1447c0 : 0xac1447c0
fffff880`03392a70 fffffa80`0af453c0 : 00000000`00000000 fffffa80`0af453c0 00000000`ac1447c0 fffffa80`0aa1bbb0 : 0xfffffa80`0a8c66a0
fffff880`03392a78 00000000`00000000 : fffffa80`0af453c0 00000000`ac1447c0 fffffa80`0aa1bbb0 fffffa80`07496d30 : 0xfffffa80`0af453c0


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbehci+5fdf
fffff880`04631fdf ??              ???

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  usbehci+5fdf

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbehci

IMAGE_NAME:  usbehci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b18b98a

FAILURE_BUCKET_ID:  X64_0xFE_usbehci+5fdf

BUCKET_ID:  X64_0xFE_usbehci+5fdf

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

 

[cybercore]

Please follow all suggested in the previous post.

If crashes persist:


1. Remove Avira, install MSE:

Avira AntiVir Removal Tool - Download

http://www.microsoft.com/security_essentials/



2. Update drivers for all your USB devices such as Logitech SetPoint:


LMouFilt.Sys Wed Apr 22 20:05:26 2009
LHidFilt.Sys Wed Apr 22 20:05:22 2009