iusb3xhc.sys and ntoskrnl.exe BSODs

[chenujay]

Hi all,
I've been getting lots of BSOD's on a computer I built this past summer. I am home again for break, and thought I had diagnosed the issue after memtest86 gave tons of errors. So I replaced the memory. I ran memtest and prime95 (18 hrs) and the system seemed to be fine.

However, I am still having intermittent BSODs.

1. Yesterday I got the IRQL NOT LESS OR EQUAL error.
2. I googled that error, and turned on driver verifier. Upon reboot, the computer BSOD, and I did several things such as uninstall Glary Utilities, Deamon Tools and Avast.
3. The computer now booted, but still BSOD with an error in "iusb3xhc.sys". I updated the drivers for all my usb devices and then tried to see if I could eliminate BSODs. I also removed the driver verifier because it was slowing down my computer immensely.

- I have a USB keyboard, mouse, and webcam and they seem fine. Ran for several hours without issue.
- Next I reconnected my usb wireless adapter (Realtek RTL8191SU based). It was previously connected to a usb3 port, I connected it to a usb2 port. Again, ran for several hours and it was fine.
- Overnight, I ran sfc /scannow and chkdsk on reboot. No errors found.
- I reconnected my WD Elements USB2 harddrive. Within a few hours, this led to another BSOD with the error IRQL NOT LESS OR EQUAL
- Updated the Intel usb 3 driver. Did verifier again and still getting BSOD with iusb3xhc as cause

Any ideas if its the harddrive or something else that is causing the issue? I'm honestly lost as to how to troubleshoot.

Thanks in advance!

 

[Golden]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88004b89b53, fffff8800338b6f8, fffff8800338af50}

Probably caused by : iusb3xhc.sys ( iusb3xhc+64b53 )

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

2: kd> lmvm iusb3xhc
start             end                 module name
fffff880`04b25000 fffff880`04bec000   iusb3xhc T (no symbols)           
    Loaded symbol image file: iusb3xhc.sys
    Image path: \SystemRoot\system32\DRIVERS\iusb3xhc.sys
    Image name: iusb3xhc.sys
    Timestamp:        Thu [B][COLOR="Red"]Oct 30[/COLOR][/B] 20:35:19 [B][COLOR="red"]2014[/COLOR][/B] (54520D5F)
    CheckSum:         000CB888
    ImageSize:        000C7000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Did you run the Intel Driver Update Utility?
Intel® Driver Update Utility

Does the BSOD only occur when you plug that WD drive into that port? What about other devices? Do they cause the same BSOD?

 

[chenujay]

I ran the driver update utility, it did not find any updates. Earlier today I found an update for iusb3xhc.sys and installed that.

https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22824&lang=eng&ProdId=3467

This update did not fix the BSOD issue.

It's quite strange, when verifier was running it kept giving BSODs. Without Verifier running, I can plug and unplug the disk without getting BSOD. I also plugged in a USB 2.0 and 3.0 flash drives and have been fine.

 

[Golden]

In that case, don't use Driver Verifier for now, and see if it stays stable.