Bugcode_USB_Driver BSOD

TwoFooted Lunge said:

Been going on a month now, any help appreciated, even if it's just to tell me it's knackered

Load of dump files

MiniDump.rar

Hello !! Welcome to SF !!

I guess there are lot of issues going on. Please the steps mentioned..!!

Run the Memory Diagnostic & HD Diagnostic

Also i would recommend to run System Integrity Checker
Start > Run > CMD >Right Click and Run as administrator > SFC/ SCANNOW

Old Drivers that needs to be updated

Code:

ASACPI.sys   Mon Mar 28 08:00:36 2005
MarvinBus64.sys Sat Sep 24 02:47:03 2005

ASACPI.sys driver is from Asus its a utility which is well known problems. I'm attaching the file so download it and update it

MB_WIN7_ATK.ZIP

Uninstall all the Asus Utilities Like PC Probe etc. then see whether it makes any diference

MarvinBus64.sys is most likely related to Pinnacle so i would recommend to update those drivers are well Pinnacle Systems - Product Support

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa80053eb1a0, Device extension pointer of the host controller
Arg3: 0000000010330035, PCI Vendor,Product id for the controller
Arg4: fffffa8007f96250, 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 fffff88010b9fe4e to fffff80002c71f00

STACK_TEXT:  
fffff800`00b9cad8 fffff880`10b9fe4e : 00000000`000000fe 00000000`00000005 fffffa80`053eb1a0 00000000`10330035 : nt!KeBugCheckEx
fffff800`00b9cae0 fffff880`04411a45 : 00000000`fffffff3 fffffa80`07f96010 00000000`00000000 fffff880`03c74000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff800`00b9cb20 fffff880`04413737 : fffffa80`07f96250 fffffa80`07f96010 00000000`00000000 fffffa80`053eb1a0 : usbohci!OHCI_PollAsyncEndpoint+0x99
fffff800`00b9cb80 fffff880`10b73e8b : 00000000`00000002 fffffa80`07f96010 fffffa80`053eb1a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x3f
fffff800`00b9cbb0 fffff880`10b789b1 : 00000000`00000050 00000000`00000004 fffffa80`07f96010 00000000`00000282 : USBPORT!MPf_PollEndpoint+0x9b
fffff800`00b9cbe0 fffff880`10b84043 : fffffa80`053eb1a0 00000000`00000050 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff800`00b9cc40 fffff880`10b74f89 : fffffa80`053eb050 00000000`00000000 fffffa80`053eba02 fffffa80`053eba10 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1af
fffff800`00b9cca0 fffff800`02c7d5dc : fffff800`02deae80 fffffa80`053eba10 fffffa80`053eba28 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff800`00b9ccd0 fffff800`02c7a6fa : fffff800`02deae80 fffff800`02df8c40 00000000`00000000 fffff880`10b74db0 : nt!KiRetireDpcList+0x1bc
fffff800`00b9cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbohci!OHCI_PollAsyncEndpoint+99
fffff880`04411a45 8bd3            mov     edx,ebx

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  usbohci!OHCI_PollAsyncEndpoint+99

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: usbohci

IMAGE_NAME:  usbohci.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bcc06

FAILURE_BUCKET_ID:  X64_0xFE_usbohci!OHCI_PollAsyncEndpoint+99

BUCKET_ID:  X64_0xFE_usbohci!OHCI_PollAsyncEndpoint+99

Followup: MachineOwner

Hope this helps,
Captain

TwoFooted Lunge said:

Thanks for the quick reply Captain Jack, sfc /scannow found corrupt files but was unable to repair them, can't find anything "not repair" in the CBS.log

Updated drivers as advised

CBS & CBS.persist are about 50mb, I could upload them if needed

Try this article SFC /SCANNOW Command - System File Checker and How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7 for details on how to Repair them

Hope this helps,
Captain

TwoFooted Lunge said:

Cheers Jack, lost the head with it & wiped it, redone it, so far so good

This can be closed

Glad that you got it working !! Thank You for posting back !!

- Captain