New
#11
Mmmm.....let me research this a bit more please.
Sorry, I've had no luck. My only suggestion is to uninstall it - use an alternative mouse/keyboard and see if the problem persists.
I know it's been a while, but I finally managed to get my hands on a non-razer mouse. I swapped out the mouse/keyboard, uninstalled everything related to razer, and went ahead and ran the verifier again. It crashed within a few minutes with hidclass.sys listed as the cause. I've attached the dmp file that was created.
Can you confirm that Windows is fully updated - be sure to check Optional Updates too.Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {23b, fffff880073b0710, fffff9801fc10dc0, 0} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 ) Followup: MachineOwner ---------
Besides the mouse and keyboard, what other USB devices are attached to the system at the time of the crash?
Yes, Windows is fully up to date. I make it a habit to keep it updated.
The only other devices that are consistently plugged in are an external hard drive, a wireless headset (I had the blue screens well before I added both of these), and a wireless receiver for an Xbox 360 controller with drivers straight from Microsoft.
Please unplug the XBox controller, then run Driver Verifier again:
Please do the following:
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.
Driver Verifier - Enable and Disable
Driver Verifier will cause your computer to run very sluggishly - this is normal. What it is trying to do is force your system to BSOD and isolate the offending driver/s. When it does, reboot, disable driver verifier, reboot as normal and upload the new dmp file/s here.
I recommend creating a system restore point before turning on driver verifier:
System Restore Point - Create
If your system fails to boot to desktop once driver verifier is enabled, turn it off by booting into Safe Mode:
Safe Mode
I ran it with the receiver removed and got a blue screen right after logging in again. For good measure I also ran verifier a second time, with the other 2 devices unplugged, and got the same blue screen.
OK. Its most certainly a USB port driver problem. Can you check for updated drivers for any USB3.0 ports?Code:******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C9, {23b, fffff8800882d710, fffff9801942edc0, 0} Probably caused by : HIDCLASS.SYS ( HIDCLASS!HidpMajorHandler+0 ) Followup: MachineOwner ---------
Also : are/have there been any Bluetooth devices installed to the system?
The most recent USB drivers on the manufacturers website are from early last year (before my last clean install of windows), but I went ahead and updated them to be safe and it's still crashing.
There aren't currently any Bluetooth devices on my system. I did try to add a USB dongle in the past, but I am fairly positive that I've re-installed since then.