Share via

Blue screen after plugging in USB 3.0 device.

Anonymous
2013-09-02T08:43:05+00:00

I am experiencing an issue with my USB 3.0 port. I attempted to plug in a USB 3.0 hard drive into my 3.0 port and every time I do this the blue screen of death (as attached below) comes up. I have plugged in a different USB 3.0 hard drive into that port with the same result. I note that USB 2.0 devices do not cause this problem, nor does plugging any device (including this hard drive) into my other USB port (which is 2.0).

I attempted to update the driver software for all my USB drivers, however no updates were found.

Any help on the issue would be very much appreciated :)

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

Answer accepted by question author

Anonymous
2013-09-02T09:34:42+00:00

Thanks!

Both of the attached DMP files are of the **SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)**bugcheck.

A system thread generated an exception that the error handler did not catch.

Usual causes are a bug in a device driver.

If we take a look at the call stack:

0: kd> kv

Child-SP          RetAddr           : Args to Child                                                           : Call Site

fffff880089606a0 0000000000f8009e : fffff8a00378ecc2 000000000000000f 0000000000000000 fffffa80041afe80 : rusb3xhc+0x1c2dd

fffff880089606a8 fffff8a00378ecc2 : 000000000000000f 0000000000000000 fffffa80041afe80 fffff8800777af7b : 0xf8009e

fffff880089606b0 000000000000000f : 0000000000000000 fffffa80041afe80 fffff8800777af7b fffffa80041afe80 : 0xfffff8a0`0378ecc2

fffff880089606b8 0000000000000000 : fffffa80041afe80 fffff8800777af7b fffffa80041afe80 0000000000000000 : 0xf

FAILURE_BUCKET_ID:  X64_0x7E_rusb3xhc+1c2dd

We see mention of rusb3xhc.sys which is the Renesas Electronics Corporation USB 3.0 Host Controller Driver. Have you checked Samsung's support & drivers website to ensure this driver is up to date? Yours is dated from 2011:

0: kd> lmvm rusb3xhc

start             end                 module name

fffff8800775f000 fffff8800779a000   rusb3xhc T (no symbols)          

    Loaded symbol image file: rusb3xhc.sys

    Image path: \SystemRoot\system32\DRIVERS\rusb3xhc.sys

    Image name: rusb3xhc.sys

    Timestamp:        Wed Sep 14 21:15:00 2011 (4E715194)

If you are sure it's up to date, it's possible another device driver is conflicting and causing it to fault, so here are my recommendations:

1. Remove and replace AVG with Microsoft Security Essentials for temporary troubleshooting purposes:

AVG removal tool - http://www.avg.com/us-en/utilitiesMSE - http://windows.microsoft.com/en-us/windows/security-essentials-download

2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

Regards,

Patrick

Was this answer helpful?

0 comments No comments

6 additional answers

Sort by: Most helpful
  1. Anonymous
    2014-07-03T18:32:26+00:00

    You probably installed series 8 usb 3.0 drivers instead of series 7.  They use the same device id.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-03-18T02:52:52+00:00

    After days of trying to fix this exact problem by trying everything offered by techies found by googling the problem, I can tell you all, that I found an easy fix all by myself. Hopefully it'll help others like me.

    Go to control panel- device manager- scroll down to USB controller- click on roll back driver- Voila!

    Plug in your mouse and/or other USB devices; no crash, no blue screen.

    Then re-update your drivers the same way.

    I had Driver Booster that had updated all my drivers and the USB controller driver was incompatible.

     so if you have a third party driver updater, just unclick their USB controller update.

    Was this answer helpful?

    0 comments No comments