Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

BSOD!


  • Please log in to reply
1 reply to this topic

#1 some1uknown

some1uknown

  • Members
  • 19 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:LA
  • Local time:06:13 AM

Posted 13 March 2009 - 12:34 AM

Currently i have a BSOD that comes about every few hours, not sure why it happens, can someone help me?
Here is the crash dump log.

Microsoft ® Windows Debugger Version 6.11.0001.404 X86
Copyright © Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Documents and Settings\some1uknown\Desktop\Mini031209-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Thu Mar 12 00:48:24.569 2009 (GMT-8)
System Uptime: 0 days 2:34:17.867
Loading Kernel Symbols
...............................................................
.............................................
Loading User Symbols
Loading unloaded module list
.......................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {5, 8a2910e0, 10de056a, 897f1700}

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

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

0: 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: 8a2910e0, Device extension pointer of the host controller
Arg3: 10de056a, PCI Vendor,Product id for the controller
Arg4: 897f1700, Pointer to Endpoint data structure

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


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xFE

PROCESS_NAME: Idle

LAST_CONTROL_TRANSFER: from ba5b7cc3 to 804f9c37

STACK_TEXT:
8055026c ba5b7cc3 000000fe 00000005 8a2910e0 nt!KeBugCheckEx+0x1b
8055028c ba5c4516 8a291028 0000dfd0 89771000 USBPORT!USBPORT_BugCheck+0x2d
805502c8 baba33dd 00ece9c0 8a2919dc 897f1700 USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x126
805502ec baba38a6 8a2919dc 897f1700 897f1700 usbehci!EHCI_PollActiveAsyncEndpoint+0x37
80550348 baba53d3 8a2919dc 897f1700 80550378 usbehci!EHCI_PollAsyncEndpoint+0x98
80550358 ba5b12ba 8a2919dc 897f1700 80545aac usbehci!EHCI_PollEndpoint+0x1f
80550378 ba5b2578 026c6f50 8a2910e0 897f1588 USBPORT!USBPORT_PollEndpoint+0xe8
805503a0 ba5b5ed0 8a291028 50457270 80545aac USBPORT!USBPORT_CoreEndpointWorker+0x2be
805503d0 ba5c3fb0 8a291028 80545aac 8a291028 USBPORT!USBPORT_DpcWorker+0x18a
8055040c ba5c4128 8a291028 00000001 8055b0a0 USBPORT!USBPORT_IsrDpcWorker+0x37e
80550428 80544e5f 8a29164c 6b755044 00000000 USBPORT!USBPORT_IsrDpc+0x166
80550440 8055ae40 ffdffc50 00000000 8055ae40 nt!KiRetireDpcList+0x61
80550450 80544d44 00000000 0000000e 00000000 nt!KiIdleThread0
80550454 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x28


STACK_COMMAND: kb

FOLLOWUP_IP:
usbehci!EHCI_PollActiveAsyncEndpoint+37
baba33dd 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: 41107d62

FAILURE_BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37

BUCKET_ID: 0xFE_usbehci!EHCI_PollActiveAsyncEndpoint+37

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

BC AdBot (Login to Remove)

 


#2 Elise

Elise

    Bleepin' Blonde


  • Malware Study Hall Admin
  • 61,088 posts
  • ONLINE
  •  
  • Gender:Female
  • Location:Romania
  • Local time:04:13 PM

Posted 13 March 2009 - 02:37 AM

Maybe your usb-driver is corrupt (usbehci.sys). You can try to download a fresh copy, after that uninstall the old driver, restart windows, and when it says new hardware found, just locate the downloaded file and install from there.

regards, Elise


"Now faith is the substance of things hoped for, the evidence of things not seen."

 

Follow BleepingComputer on: Facebook | Twitter | Google+ | lockerdome

 

Malware analyst @ Emsisoft





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users