0x0000001e error

Hi all,

I've gotten a few BSOD's lately and can't seem to figure it out.

I have attached 2 of the minidumps.

Any help you can give is much appreciated. I am to the point of formatting soon.

Thanks
Scott

smanuel said:

Hi all,

I've gotten a few BSOD's lately and can't seem to figure it out.

I have attached 2 of the minidumps.

Any help you can give is much appreciated. I am to the point of formatting soon.

Thanks
Scott

Scott Hi and welcome

These are Related to usbohci.sys related to OHCI USB Miniport Driver from Microsoft.

I would run a system file check toverify and repair it and read here USB Driver - General Fix for Problems

Code:

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


Loading Dump File [C:\Users\K\Desktop\052511-26660-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 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`03054000 PsLoadedModuleList = 0xfffff800`03299650
Debug session time: Wed May 25 00:28:11.368 2011 (GMT-4)
System Uptime: 0 days 11:15:21.508
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
.............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, fffffa8007a951a0, 10024397, fffffa80085c3f68}

Probably caused by : usbohci.sys ( usbohci!OHCI_PollAsyncEndpoint+99 )

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

5: 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: fffffa8007a951a0, Device extension pointer of the host controller
Arg3: 0000000010024397, PCI Vendor,Product id for the controller
Arg4: fffffa80085c3f68, 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 fffff88005164f7e to fffff800030d3d00

STACK_TEXT:  
fffff880`030b0ad8 fffff880`05164f7e : 00000000`000000fe 00000000`00000005 fffffa80`07a951a0 00000000`10024397 : nt!KeBugCheckEx
fffff880`030b0ae0 fffff880`041c1a45 : 00000000`cf180180 fffffa80`085c3d20 00000000`00000000 fffff880`05b0c000 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`030b0b20 fffff880`041c3737 : fffffa80`085c3f68 fffffa80`085c3d20 00000000`00000000 fffffa80`07a951a0 : usbohci!OHCI_PollAsyncEndpoint+0x99
fffff880`030b0b80 fffff880`05138e8b : 00000000`00000002 fffffa80`085c3d20 fffffa80`07a951a0 00000000`00000000 : usbohci!OHCI_PollEndpoint+0x3f
fffff880`030b0bb0 fffff880`0513d9d1 : 00000000`00000000 00000000`00000004 fffffa80`085c3d20 fffffa80`07a95050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`030b0be0 fffff880`05149077 : fffffa80`07a951a0 00000000`00000000 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`030b0c40 fffff880`05139f89 : fffffa80`07a95050 00000000`00000000 fffffa80`07a95a02 fffffa80`07a95a18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`030b0ca0 fffff800`030df10c : fffff880`03088180 fffffa80`07a95a18 fffffa80`07a95a30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`030b0cd0 fffff800`030cba2a : fffff880`03088180 fffff880`03093040 00000000`00000000 fffff880`05139db0 : nt!KiRetireDpcList+0x1bc
fffff880`030b0d80 00000000`00000000 : fffff880`030b1000 fffff880`030ab000 fffff880`030b0d40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
usbohci!OHCI_PollAsyncEndpoint+99
fffff880`041c1a45 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:  4d8c0bff

FAILURE_BUCKET_ID:  X64_0xFE_usbohci!OHCI_PollAsyncEndpoint+99

BUCKET_ID:  X64_0xFE_usbohci!OHCI_PollAsyncEndpoint+99

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

Other things that could be causing it are your AVG, and VM software.

I performed the steps above and was still getting BSODs. I have since replaced the harddrive (needed an upgrade anyway) and am still getting errors.

I have attached the zip of the BSOD tool results