BSoD worker_thread_returned_at_bad_irql when using USB devices


  1. Posts : 4
    Windows 7 Home Premium 64bit
       #1

    BSoD worker_thread_returned_at_bad_irql when using USB devices


    Hey guys I'm new here, trying to find a solution to this issue, would really appreciate any advice or help!

    This seemed to be a random occurrence to begin with, however I've found it most frequently happens when I'm plugging in/unplugging USB devices (namely my mouse and phone) or when I turn on tethering with my phone. Sometimes it'll happen immediately, other times it seems to happen after locking my computer and unlocking it, or waking it from sleeping, etc.

    I'm really lost as to what the issue could be, I've got a few minidumps attached (if I did it all right), so if anyone could point me in the right direction it would be very much appreciated.

    If you need any more info I'll be checking back very regularly so just let me know and I'll hook it up.

    Thanks guys!

    Edit: I've also tried running driver verifier, and when I did the computer ran at crazy slow speeds. I wanted to keep running it, but it was just unusable.
      My Computer


  2. Posts : 4
    Windows 7 Home Premium 64bit
    Thread Starter
       #2

    Can I bump this? I don't know if I'm allowed to but I guess I'm doing it.

    Anyone able to help me out at all?
      My Computer


  3. Posts : 15,026
    Windows 10 Home 64Bit
       #3

    No you shouldn't bump even if you're allowed to. It's just 2 hours since your post. Think about the ones who never received a reply..and remember that BSoD analysts have a life out of debugging. So please be patient while waiting for a reply.
    STOP 0x000000E1: WORKER_THREAD_RETURNED_AT_BAD_IRQL
    Usual causes: Device driver
    Anyway, none of your dumps provide any probable cause. Just blames windows files.
    You will have to keep driver verifier enabled even if the computer is unusable for 36 hours. Upload the dumps if there are any with verifier enabled.

    Driver Verifier - Enable and Disable

    Also, Please upload your msinfo32.nfo file. To get this:

    • Click on the Start
    • Type msinfo32 into the Search programs and files box
    • When it opens, go to File, Save
    • Save as msinfo32.nfo and save in a place you will remember
    • Let it finish the process of gathering and saving the system info
    • Right click the .nfo file, click send to compressed (zipped) folder
    • Upload the .zip file here.
      My Computer


  4. Posts : 4
    Windows 7 Home Premium 64bit
    Thread Starter
       #4

    koolkat77 said:
    No you shouldn't bump even if you're allowed to. It's just 2 hours since your post. Think about the ones who never received a reply..and remember that BSoD analysts have a life out of debugging. So please be patient while waiting for a reply.
    Hey you guys are helping me out here, I don't mean to be rude and sorry if I came off that way, I was just concerned because several other threads made after mine were replied to, and I was slipping back pages. I was just unsure and don't know the community, so my bad.
    koolkat77 said:
    STOP 0x000000E1: WORKER_THREAD_RETURNED_AT_BAD_IRQL
    Usual causes: Device driver
    Anyway, none of your dumps provide any probable cause. Just blames windows files.
    You will have to keep driver verifier enabled even if the computer is unusable for 36 hours. Upload the dumps if there are any with verifier enabled.

    Driver Verifier - Enable and Disable

    Also, Please upload your msinfo32.nfo file. To get this:

    • Click on the Start
    • Type msinfo32 into the Search programs and files box
    • When it opens, go to File, Save
    • Save as msinfo32.nfo and save in a place you will remember
    • Let it finish the process of gathering and saving the system info
    • Right click the .nfo file, click send to compressed (zipped) folder
    • Upload the .zip file here.
    I'll attach the msinfo file, and will run driver verifier ASAP. Thanks a lot again, if there's anything else I can do let me know!
      My Computer


  5. Posts : 15,026
    Windows 10 Home 64Bit
       #5

    Thanks.

    These devices are disabled in your "problem devices"
    Code:
    facap, FastAccess Video Capture	ROOT\IMAGE\0000	This device is disabled.
    VirtualBox Host-Only Ethernet Adapter	ROOT\NET\0000	This device is disabled.
    Any reason behind them remaining disabled?

    Are you getting these BSoDs recently or it's an on going issue?
      My Computer


  6. Posts : 4
    Windows 7 Home Premium 64bit
    Thread Starter
       #6

    I believe FastAccess is the facial recognition login provided with the laptop, I used to use it but disabled it so it wouldn't log me in. That's the only thing I can think of for that, the VirtualBox Ethernet Adapter is disabled because I thought it may have been giving me issues with my internet at one point I suppose. I'll probably uninstall the program it is used for completely since I no longer use it.

    This started maybe 3-4 weeks ago as random bluescreens from a few varied reasons (bad_pool_header, irql_not_less_or_equal and one or two others I can't recall), however they were infrequent, then just a few days ago, maybe a week at most it started with the worker_thread_returned_at_bad_irql issue, which has been far more severe.
      My Computer


  7. Posts : 15,026
    Windows 10 Home 64Bit
       #7

    Okay, thanks for the info.
    Will wait for the dumps with verifier enabled.
      My Computer


  8. Posts : 15,026
    Windows 10 Home 64Bit
       #8

    Were your BSOD issues resolved?
      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 07:19.
Find Us