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

  1. 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
    2013-09-02T18:35:14+00:00

    Hi Alexander,

    Fantastic work, and thank you for the informative response! For future reference, when you update a device's driver through Device Manager, it's going to Windows Update to search for it. So as it'll be a newer driver than out of the box, it won't be the latest. It's always best to visit the manufacturer's website for your latest device drivers.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-09-02T12:37:59+00:00

    I have successfully resolved the problem! :)

    After trying to update the device driver software using Window's automatic updater in device manager I was told that it was up to date, however manually reinstalling the driver from Samsung did the trick.

    I am very grateful for your help and support and for being so prompt in answering my question.

    Thank you very much, you are a great help.

    Alexander

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-09-02T09:06:28+00:00

    Thank you for the advice!

    Here is the link to my minidump files:

    https://www.dropbox.com/s/a5o0dyd99j0vtzg/Minidum%20Files.zip

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-09-02T08:44:02+00:00

    Hi,

    In order to assist you, we will need the DMP files to analyze what exactly occurred at the time of the crash, etc.

    If you don't know where DMP files are located, here's how to get to them:

     1.    Navigate to the %systemroot%\Minidump folder.

     2.    Copy any and all DMP files in the Minidump folder to your Desktop and then zip up these files.

     3.    Upload the zip containing the DMP files to Skydrive or a hosting site of your choice and paste in your reply.

    If you are going to use Skydrive but don't know how to upload to it, please visit the following:

    http://www.wikihow.com/Use-SkyDrive

    Please note that any "cleaner" programs such as TuneUp Utilities, CCleaner, etc, by default will delete DMP files upon use.

    If your computer is not generating DMP files, please do the following:

    1. Start > type %systemroot% which should show the Windows folder, click on it. Once inside that folder, ensure there is a Minidump folder created. If not, CTRL-SHIFT-N to make a New Folder and name it Minidump.
    2. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Performance > Settings > Advanced > Ensure there's a check-mark for 'Automatically manage paging file size for all drives'.
    3. Windows key + Pause key. This should bring up System. Click Advanced System Settings on the left > Advanced > Startup and Recovery > Settings > System Failure > ensure there is a check mark next to 'Write an event to the system log' > Ensure 'Automatically restart' is un-checked.

    Ensure Small Memory Dump is selected and ensure the path is %systemroot%\Minidump.

    1. Double check that the WERS is ENABLED:

    Start > Search > type services.msc > Under the name tab, find Windows Error Reporting Service > If the status of the service is not Started then right click it and select Start. Also ensure that under Startup Type it is set to Automatic rather than Manual. You can do this by right clicking it, selecting properties, and under General selecting startup type to 'Automatic', and then click Apply.

    If you cannot get into normal mode to do any of this, please do this via Safe Mode.

    Regards,

    Patrick

    Was this answer helpful?

    0 comments No comments