BSOD usb_bugcode_driver


  1. Posts : 3
    Windows 7 home
       #1

    BSOD usb_bugcode_driver


    I get random USB device not recognized messages, when nothing is plugged into my usb drives. When I click the message it shows me generic usb hub (6 ports) with an unknown device in bold. My computer also randomly shuts down and gives me the bsod with the code usb_bugcode_driver message. I am not computer savvy (at all!) but I have attached the DM log collector file. I hope this helps. I have updated all drivers previously and have had other people work on my system with no luck. I'm hoping someone can help me!
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi mrskeen.

    Update the Critix USB monitor program/driver. It is too old.
    Code:
        Image name: ctxusbm.sys
        Timestamp:        Mon Sep 07 23:39:28 2009 (4AA54C58)
    Search for a possible update in http://www.citrix.com/products/all-p...ml?posit=glnav .... if there is no feasible update, better you uninstall this program.

    Also upload the list of all the third party drivers Using NirSoft DriverView :

    • Download and execute Driverview
    • View > Hide Microsoft Drivers
    • Edit > Select all
    • File > Save Selected Items
    • In the Save dialog, Set the path to desktop, Put "Driverview" in the name field, and save.
    • Zip the .txt file and upload it.

    ________________________________________________
    Code:
    BugCheck FE, {8, 6, 5, fffffa8006a51640}
    
    Probably caused by : usbhub.sys ( usbhub!UsbhHubProcessChangeWorker+ec )
    
    Followup: MachineOwner
    ---------
      My Computer


  3. Posts : 3
    Windows 7 home
    Thread Starter
       #3

    Thank you. I removed citrix as I no longer need that program for work. I have attached the driverview zip.
      My Computer


  4. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #4

    OK, apparently there is nothing more problematic elements relating to USB, but a lot of factory bloatwares are there.

    Run the computer normally now. Let us know for any further BSOD. If the issues occur, we will have to concentrate on bloatware removal.
      My Computer


  5. Posts : 3
    Windows 7 home
    Thread Starter
       #5

    Got bsod again today. I have attached the log. Hope that gives something that can help. Thank you!
      My Computer


  6. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #6

    Do you use the inbuilt webcam? If so, upload the driver to it, from Lenovo : Laptops and netbooks :: IdeaPad Z Series laptops :: IdeaPad Z370 - Lenovo Support (US) Camera Driver for Microsoft Windows 7 (32-bit, 64-bit) - IdeaPad Z370, Z470

    Otherwise, if you dont use it, you may disable the webcam in device manager.
    _______________________________________________
    Code:
    *** WARNING: Unable to verify timestamp for rtsuvc.sys
    *** ERROR: Module load completed but symbols could not be loaded for rtsuvc.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 1000007E, {ffffffffc0000005, fffff8801c217c69, fffff880031d32d8, fffff880031d2b30}
    
    Probably caused by : rtsuvc.sys ( rtsuvc+1c69 )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff8801c217c69, The address that the exception occurred at
    Arg3: fffff880031d32d8, Exception Record Address
    Arg4: fffff880031d2b30, Context Record Address
    
    Debugging Details:
    ------------------
    
    
    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    FAULTING_IP: 
    rtsuvc+1c69
    fffff880`1c217c69 0fb74801        movzx   ecx,word ptr [rax+1]
    
    EXCEPTION_RECORD:  fffff880031d32d8 -- (.exr 0xfffff880031d32d8)
    ExceptionAddress: fffff8801c217c69 (rtsuvc+0x0000000000001c69)
       ExceptionCode: c0000005 (Access violation)
      ExceptionFlags: 00000000
    NumberParameters: 2
       Parameter[0]: 0000000000000000
       Parameter[1]: 0000000000000001
    Attempt to read from address 0000000000000001
    
    CONTEXT:  fffff880031d2b30 -- (.cxr 0xfffff880031d2b30;r)
    rax=0000000000000000 rbx=fffffa800492f000 rcx=0000000000000000
    rdx=fffffa8009478365 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8801c217c69 rsp=fffff880031d3510 rbp=0000000000000003
     r8=0000000000000010  r9=0000000000000040 r10=fffff80003600000
    r11=0000000000000505 r12=fffffa800492f3b0 r13=fffff8801c9c94c0
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    rtsuvc+0x1c69:
    fffff880`1c217c69 0fb74801        movzx   ecx,word ptr [rax+1] ds:002b:00000000`00000001=????
    Last set context:
    rax=0000000000000000 rbx=fffffa800492f000 rcx=0000000000000000
    rdx=fffffa8009478365 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff8801c217c69 rsp=fffff880031d3510 rbp=0000000000000003
     r8=0000000000000010  r9=0000000000000040 r10=fffff80003600000
    r11=0000000000000505 r12=fffffa800492f3b0 r13=fffff8801c9c94c0
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
    rtsuvc+0x1c69:
    fffff880`1c217c69 0fb74801        movzx   ecx,word ptr [rax+1] ds:002b:00000000`00000001=????
    Resetting default scope
    
    CUSTOMER_CRASH_COUNT:  1
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
    
    EXCEPTION_PARAMETER1:  0000000000000000
    
    EXCEPTION_PARAMETER2:  0000000000000001
    
    READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038ad100
    GetUlongFromAddress: unable to read from fffff800038ad1c0
     0000000000000001 Nonpaged pool
    
    FOLLOWUP_IP: 
    rtsuvc+1c69
    fffff880`1c217c69 0fb74801        movzx   ecx,word ptr [rax+1]
    
    BUGCHECK_STR:  0x7E
    
    DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    LAST_CONTROL_TRANSFER:  from fffffa8008af7420 to fffff8801c217c69
    
    STACK_TEXT:  
    fffff880`031d3510 fffffa80`08af7420 : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`0864baf0 : rtsuvc+0x1c69
    fffff880`031d3518 00000000`00000000 : 00000000`00000000 00000000`00000001 fffffa80`0864baf0 fffffa80`082d9300 : 0xfffffa80`08af7420
    
    
    SYMBOL_STACK_INDEX:  0
    
    SYMBOL_NAME:  rtsuvc+1c69
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: rtsuvc
    
    IMAGE_NAME:  rtsuvc.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4d0882df
    
    STACK_COMMAND:  .cxr 0xfffff880031d2b30 ; kb
    
    FAILURE_BUCKET_ID:  X64_0x7E_rtsuvc+1c69
    
    BUCKET_ID:  X64_0x7E_rtsuvc+1c69
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x7e_rtsuvc+1c69
    
    FAILURE_ID_HASH:  {eb4bb06d-68c3-ab3b-78d0-3d81b76025ac}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm rtsuvc
    start             end                 module name
    fffff880`1c216000 fffff880`1c9e6700   rtsuvc   T (no symbols)           
        Loaded symbol image file: rtsuvc.sys
        Image path: \SystemRoot\system32\DRIVERS\rtsuvc.sys
        Image name: rtsuvc.sys
        Timestamp:        Wed Dec 15 14:27:03 2010 (4D0882DF)
        CheckSum:         007E1061
        ImageSize:        007D0700
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 19:47.
Find Us