1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

BUGCODE_USB_DRIVER usbuhci.sys PLEASE HELP

Discussion in 'Windows XP' started by bdsilvano, 2007/06/08.

  1. 2007/06/08
    bdsilvano

    bdsilvano Inactive Thread Starter

    Joined:
    2007/06/08
    Messages:
    3
    Likes Received:
    0
    Just one week ago I buy my new 160 GB SATA Drive and install it into my old computer. now my computer have 1XIDE ata & 1xSATA drive, but when I try to copy data from IDE to sata im having a Blue Screen Error says BUGCODE_USB_DRIVER. Im Having annoy withi this one as I try to fix this for one week now. firstly I thouth sata have problem because i didnt have any error like this for passed 3 years and when I install only SATA im having now.
    Same goes when I copy Anything from DVD to SATA im having problem same.
    But when I try to copy DVD to IDE no problem. Please help. Im posting my Minidump Log Error.



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


    Loading Dump File [C:\Documents and Settings\phoenix\Desktop\Mini060907-05.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path. *
    * Use .symfix to have the debugger choose a symbol path. *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055ab20
    Debug session time: Sat Jun 9 02:58:24.578 2007 (GMT+8)
    System Uptime: 0 days 0:11:27.132
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    * *
    * The Symbol Path can be set by: *
    * using the _NT_SYMBOL_PATH environment variable. *
    * using the -y <symbol_path> argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ..
    Unable to load image USBPORT.SYS, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for USBPORT.SYS
    *** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck FE, {5, 820390e0, 11063038, 81c4ca48}

    ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
    ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

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

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

    kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    BUGCODE_USB_DRIVER (fe)
    USB Driver bugcheck, first parameter is USB bugcheck code.
    Arguments:
    Arg1: 00000005, USB Bugcheck Code:
    Arg2: 820390e0
    Arg3: 11063038
    Arg4: 81c4ca48

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

    ANALYSIS: Kernel with unknown size. Will force reload symbols with known size.
    ANALYSIS: Force reload command: .reload /f ntoskrnl.exe=FFFFFFFF804D7000,214600,41108004
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.


    MODULE_NAME: usbuhci

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 41107d62

    CUSTOMER_CRASH_COUNT: 5

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xFE

    LAST_CONTROL_TRANSFER: from f7ff4cc3 to 805339ae

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8055074c f7ff4cc3 000000fe 00000005 820390e0 nt+0x5c9ae
    8055076c f8001516 82039028 00008fd0 81bc5000 USBPORT+0xecc3
    805507a8 f892905c 33a6c8f0 820399dc 81c4ca48 USBPORT+0x1b516
    805507cc f8926ded 820399dc 81bc5000 805507fc usbuhci+0x305c
    805507dc f7fee2ba 820399dc 81c4ca48 804e3579 usbuhci+0xded
    805507fc f7fef578 026c6f50 820390e0 81c4c8d0 USBPORT+0x82ba
    80550824 f7ff2ed0 82039028 50457270 804e3579 USBPORT+0x9578
    80550854 f8000fb0 82039028 804e3579 82039028 USBPORT+0xced0
    80550890 f8001128 82039028 00000001 80559580 USBPORT+0x1afb0
    805508ac 804dc179 8203964c 6b755044 00000000 USBPORT+0x1b128
    805508b0 8203964c 6b755044 00000000 820390ec nt+0x5179
    805508b4 6b755044 00000000 820390ec 80559320 0x8203964c
    805508b8 00000000 820390ec 80559320 ffdffc50 0x6b755044


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    usbuhci+305c
    f892905c ?? ???

    SYMBOL_STACK_INDEX: 3

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: usbuhci.sys

    SYMBOL_NAME: usbuhci+305c

    BUCKET_ID: WRONG_SYMBOLS

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

    kd> lmvm usbuhci
    start end module name
    f8926000 f892b000 usbuhci T (no symbols)
    Loaded symbol image file: usbuhci.sys
    Image path: usbuhci.sys
    Image name: usbuhci.sys
    Timestamp: Wed Aug 04 14:08:34 2004 (41107D62)
    CheckSum: 00013083
    ImageSize: 00005000
    Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
     
  2. 2007/06/09
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389

  3. to hide this advert.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.