Share via

USBSTOR.SYS BSOD errors

Anonymous
2011-04-23T01:26:33+00:00

I keep getting BSOD with the following error from my dump file.  It appears to be with my USBSTOR.sys file.  can someone please help me determine what I need to do next?

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\042211-20373-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

Executable search path is:

Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850

Machine Name:

Kernel base = 0xfffff8000341d000 PsLoadedModuleList = 0xfffff80003662e90

Debug session time: Fri Apr 22 02:38:11.001 2011 (UTC - 4:00)

System Uptime: 0 days 8:57:07.000

Loading Kernel Symbols

...............................................................

................................................................

.................................

Loading User Symbols

Loading unloaded module list

.....

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck FE, {6, fffffa800caa4d28, 63706458, 0}

Probably caused by : USBSTOR.SYS ( USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121 )

Followup: MachineOwner


0: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

BUGCODE_USB_DRIVER (fe)

USB Driver bugcheck, first parameter is USB bugcheck code.

Arguments:

Arg1: 0000000000000006, USBBUGCODE_BAD_SIGNATURE An Internal data structure (object)

 has been corrupted.

Arg2: fffffa800caa4d28, Object address

Arg3: 0000000063706458, Signature that was expected

Arg4: 0000000000000000

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 fffff8800537523d to fffff8000349d640

STACK_TEXT: 

fffff8000499ac18 fffff8800537523d : 00000000000000fe 0000000000000006 fffffa800caa4d28 0000000063706458 : nt!KeBugCheckEx

fffff8000499ac20 fffff8800535a8a5 : fffffa800caa4050 fffff880053579b9 fffffa800caa4d28 fffff8800534a5c2 : USBPORT!USBPORT_AssertSig+0x25

fffff8000499ac60 fffff8800535aae0 : fffffa801383dc00 fffffa800da97a00 fffffa800caa41a0 fffffa800caa4050 : USBPORT!USBPORT_Core_iInsertPriorityTransferDirect+0xd5

fffff8000499aca0 fffff88005357af4 : fffffa801383dc00 0000000000000000 fffffa800dcffc10 fffff8800534df99 : USBPORT!USBPORT_Core_iInsertPriorityTransfer+0x124

fffff8000499ace0 fffff80003547154 : fffffa800caa4480 fffffa801383de00 fffffa800caa41a0 fffff8800534f17a : USBPORT!USBPORT_TxCsqInsertIrpEx+0xb8

fffff8000499ad10 fffff8800535a77e : fffffa801383dc02 fffffa801383dc00 fffffa800da97a00 fffffa800da9fc48 : nt!IoCsqInsertIrpEx+0x64

fffff8000499ad50 fffff8800536a88e : fffffa800caa4050 fffffa800da9fc48 fffffa800caa4050 fffffa800ad35990 : USBPORT!USBPORT_Core_QueueTransferUrb+0x192

fffff8000499ad90 fffff8800536a478 : fffffa800ad35990 fffffa800dcffc10 fffffa800da9fc48 fffffa800caa4050 : USBPORT!USBPORT_BulkOrInterruptTransfer+0xca

fffff8000499ae10 fffff88005372e34 : fffffa800dcffc10 fffffa800ee20009 fffffa800dcffc10 fffffa800da9fc48 : USBPORT!USBPORT_ProcessURB+0xb44

fffff8000499aec0 fffff8800534caf4 : 0000000000000000 fffffa800ee23050 fffffa800c190ae0 fffffa800dcffc10 : USBPORT!USBPORT_PdoInternalDeviceControlIrp+0x138

fffff8000499af00 fffff88000f9e7a7 : fffffa800dcffc10 fffffa800cd218d0 fffffa800dcffc10 fffffa800dcffc10 : USBPORT!USBPORT_Dispatch+0x1dc

fffff8000499af40 fffff88000fa6789 : fffff88000fc4b50 0000000e00000028 fffffa800dcfff20 fffffa800dcfff20 : ACPI!ACPIDispatchForwardIrp+0x37

fffff8000499af70 fffff88000f9ea3f : fffff88000fc4b50 fffffa8009d32cc0 fffffa800dcffc10 fffffa800dcec050 : ACPI!ACPIIrpDispatchDeviceControl+0x75

fffff8000499afa0 fffff88001203566 : fffff88006140110 0000000000000004 fffffa800dcec050 fffffa800dcfb060 : ACPI!ACPIDispatchIrp+0x12b

fffff8000499b020 fffff88001233d8f : 0000000000000000 0000000000000000 fffffa800dcfb060 0000000000000000 : usbhub!UsbhFdoUrbPdoFilter+0xde

fffff8000499b050 fffff88001201fb7 : fffffa800dcffc10 fffffa800dc659e0 fffffa800dcffc10 fffffa800dcffc10 : usbhub!UsbhPdoInternalDeviceControl+0x373

fffff8000499b0a0 fffff88000f9e7a7 : fffffa800dcffc10 fffff88000f2d90b fffff8000499b3d0 fffff800034bd1e4 : usbhub!UsbhGenDispatch+0x57

fffff8000499b0d0 fffff88000fa6789 : fffff88000fc4b50 fffffa800ee22c20 0000000000000080 fffffa800dcfff20 : ACPI!ACPIDispatchForwardIrp+0x37

fffff8000499b100 fffff88000f9ea3f : fffff88000fc4b50 fffffa8009d322d0 fffffa800dcffc10 fffffa800da9fc48 : ACPI!ACPIIrpDispatchDeviceControl+0x75

fffff8000499b130 fffff88006138029 : fffff88002fb93c8 0000000000000000 fffffa800da9fc48 0000000000000000 : ACPI!ACPIDispatchIrp+0x12b

fffff8000499b1b0 fffff880061399f7 : fffffa800dcffc10 fffffa800dceb6b8 fffff88006140110 fffffa800da9fa10 : USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+0x121

fffff8000499b210 fffff88006137c37 : fffffa800dcffc10 fffffa800da9fb60 fffffa800dcffc10 fffffa800da9fb60 : USBSTOR!USBSTOR_CbwTransfer+0xf7

fffff8000499b270 fffff80003547285 : fffffa800dcffc02 fffffa800dcffc10 fffff880061378cc fffff800034a9e6a : USBSTOR!USBSTOR_StartIo+0x273

fffff8000499b2f0 fffff88006137532 : 0000000000000000 fffffa800d9b3b60 fffffa800d9b3b02 fffffa800d9b3cb0 : nt!IoStartPacket+0xa5

fffff8000499b330 fffff88001866139 : fffffa800dceb640 fffffa800dceb640 0000000000000000 fffffa800dceb8e0 : USBSTOR!USBSTOR_Scsi+0x312

fffff8000499b390 fffff88001866679 : fffffa800d981900 fffffa800dceb8e0 fffffa800dceb790 0000000000000002 : CLASSPNP!ClasspSendMediaStateIrp+0x329

fffff8000499b3f0 fffff8800185546a : fffff8000499b420 fffff8000499b420 0000000000000000 fffffa800da9fbe8 : CLASSPNP!ClassCheckMediaState+0x59

fffff8000499b420 fffff800034acd3f : 0000000000000000 0000000000000002 0000000000000001 fffffa800dc78bd8 : CLASSPNP! ?? ::FNODOBFM::`string'+0x4398

fffff8000499b460 fffff800034a9062 : 0000000000000002 fffff8000499b648 0000000000000000 0000000000000095 : nt!IopTimerDispatch+0x132

fffff8000499b570 fffff800034a8f06 : fffff880029d5710 00000000001f859c 0000000000000000 0000000000000000 : nt!KiProcessTimerDpcTable+0x66

fffff8000499b5e0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiProcessExpiredTimerList+0xc6

STACK_COMMAND:  kb

FOLLOWUP_IP:

USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121

fffff880`06138029 8bd8            mov     ebx,eax

SYMBOL_STACK_INDEX:  14

SYMBOL_NAME:  USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: USBSTOR

IMAGE_NAME:  USBSTOR.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce7a675

FAILURE_BUCKET_ID:  X64_0xFE_USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121

BUCKET_ID:  X64_0xFE_USBSTOR!USBSTOR_IssueBulkOrInterruptRequest+121

Followup: MachineOwner


0: kd> lmvm USBSTOR

start             end                 module name

fffff88006135000 fffff88006150000   USBSTOR    (pdb symbols)          c:\symbols\usbstor.pdb\25EB307048DD48ACABCDDB5450AC275E1\usbstor.pdb

    Loaded symbol image file: USBSTOR.SYS

    Mapped memory image file: c:\symbols\USBSTOR.SYS\4CE7A6751b000\USBSTOR.SYS

    Image path: \SystemRoot\system32\drivers\USBSTOR.SYS

    Image name: USBSTOR.SYS

    Timestamp:        Sat Nov 20 05:44:05 2010 (4CE7A675)

    CheckSum:         0002319D

    ImageSize:        0001B000

    File version:     6.1.7601.17514

    Product version:  6.1.7601.17514

    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:     usbstor.sys

    OriginalFilename: usbstor.sys

    ProductVersion:   6.1.7601.17514

    FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)

    FileDescription:  USB Mass Storage Class Driver

    LegalCopyright:   © Microsoft Corporation. All rights reserved.

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2011-04-23T17:58:27+00:00

    thank you, let me try that this weekend.

    0 comments No comments
  2. Anonymous
    2011-04-23T02:17:02+00:00

    Hi,

    Be sure to check the System Maker's Site (Motherboard Maker for custom systems) for updated

    BIOS, low level chipset drivers, and other major device drivers. (Consider the ones in BOLD

    as absolute requirements.) Also check their support and their forums (if any) for known issues.

    Check these KB Articles which "might" apply.

    Stop 0xFE Resuming from Sleep or Hibernate with USB Streaming Device

    http://support.microsoft.com/kb/974303

    "Stop 0x9F" or "Stop 0xFE" error on a Windows 7-based or Windows Vista-based computer that

    uses certain AMD USB EHCI host controllers

    http://support.microsoft.com/kb/982091

    "STOP 0x000000FE" error in Windows 7 or in Windows Server 2008 R2 when the computer enters

    or resumes from sleep (S3) or from hibernation (S4)

    http://support.microsoft.com/kb/974410

    Those and 2 other KB Articles are available (as of the date of this reply)

    http://support.microsoft.com/search/default.aspx?mode=a&query=0x000000FE&spid=14019&catalog=LCID%3D1033&res=10

    ===========================================================

    Although the Bug Check 0xFE: BUGCODE_USB_DRIVER does usually indicate hardware it could easily

    be a USB device attached and not System USB hardware. And you can never really rule out drivers.

    BCCode: FE    0x000000FE  <-- read thishttp://www.faultwire.com/solutions-fatal\_error/BUGCODE-USB-DRIVER-0x000000FE-\*1251.html?order=date


    Is this a Upgrade installation of Windows 7 or did Windows 7 come on the system from the factory?

    A possible cause could be Windows Updates, especially drivers. Even drivers not usually thought of as

    USB related, such as video/display, network (NIC & WiFI), and others, can be the cause.

    Norton especially, McAfee, Kaspersky, SpyBot, Adaware and others could be causing or have a role

    in this issue. Try uninstalling them to see if that helps. Use their maker's Removal Tools and/or

    special instructions. (Antivirus/antispyware/security programs.)


    Remove ALL USB devices from the computer. Be sure to check for updated drivers for ALL USB

    devices.

    References to Vista also apply to Windows 7.

    Do these to clear corruption and repair/replace damaged/missing system files.

    Start - type in Search box -  COMMAND   find at top of list -  RIGHT CLICK  -  RUN AS ADMIN

    sfc /scannow

    How to Repair Windows 7 System Files with System File Checker

    http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

    Then run checkdisk (chkdsk).

    How to Run Disk Check in Windows 7

    http://www.sevenforums.com/tutorials/433-disk-check.html


    Then lets refresh the USB Stack

    Control Panel - Device Manager - click anywhere in the blank/white area - then VIEW - Show

    Disabled Devices - look everywhere (except USB Controllers) for any hidden/disabled devices 

    (may have none or more than one) and Right Click on it - UNINSTALL.

    Control Panel - Device Manager - USB Serial Controllers - RIGHT CLICK on EVERYTHING and

    UNINSTALL all except the category itself - REBOOT - this refreshes the driver and the USB stack

    This KB shows the XP how to and the Vista and Windows 7 methods are identical

    http://support.microsoft.com/kb/310575

    Here is a utility to help but do the above 1st.

    USBDeview is a small utility that lists all USB devices that currently connected to your computer,

    as well as all USB devices that you previously used. Run it Options and check the 1st three

    choices to see if any are there.

    http://www.nirsoft.net/utils/usb\_devices\_view.html

    You would remove all instances of the devices then reboot.


    If needed try both of these :

    Tips for solving problems with USB devices - and a Mr Fixit

    http://windowshelp.microsoft.com/Windows/en-US/Help/c39bd203-f729-47a4-8351-83291e13c8a81033.mspx#EGB

    Hardware devices not detected or not working - Mr Fixit

    http://support.microsoft.com/gp/hardware\_device\_problems

    =======================================

    After the above attach one USB device at a time to see if any cause the issue.

    Hope this helps.

    0 comments No comments