Random BSODs after connecting devices with USB ports

mackandrius

Prominent
Apr 5, 2017
1
0
510
Hello good people!

I saw a few people having similar problems, but not quite the same as mine. I am experiencing BSODs sometimes after I connect a device to my USB ports. Here are my specs:

Asus X99 A-II Mobo
MSI GeForce® GTX 1080 Aero gpu
Intel i7 6800k cpu
Vengeance LPX 16 GB (4x 4 GB) DDR4 ram
EVGA Supernova 850 W Gold G2 psu
Windows 10

The first time this happened was when I connected a HTC Vive adaptor hub into my USB 3.1 port, it was rebooting again and again until I restored the system into a previous build and didn't happen again.

Then the other time was when I was using a Akai EIE pro audio interface and reconnected the USB cable to stop it bitcrushing. I googled that this particular interface is known to cause similar problems to more people (some sort of driver issue that causes a BSOD), although it never went into a BSOD "loop" like the time with the HTC Vive. My system rebooted and was working fine until it became more and more frequent and eventually I changed my audio interface into a Tescam US-122mkII. It was working fine until just now when I once again experienced a BSOD after reconnecting the USB cable...

I realise this is a lot of information and it seems a bit random, but I was thinking maybe someone is experiencing something similar. Perhaps it could be the motherboard since the BSODs always happen when I connect something to my USB ports.

Thanks.
 
Solution
generally, usb device related failures require that you update the BIOS, then the motherboard drivers from the motherboard vendors web site. CPU chipset drivers will update the USB 2.x and the motherboard USB 3.0 drivers will update the add on USB chips. You would then want to update the actual driver for the USB device that is failing.

if you still get a bugcheck, you need to change the memory dump type to kernel memory dump, wait for the next memory dump and then put it on a server like microsoft onedrive, share the file as public then post a link. Minidumps do not save the debug info for USB problems, you have to provide the kernel memory dump to have it debugged. Generally, the fix will be the same in any case, update bios...
generally, usb device related failures require that you update the BIOS, then the motherboard drivers from the motherboard vendors web site. CPU chipset drivers will update the USB 2.x and the motherboard USB 3.0 drivers will update the add on USB chips. You would then want to update the actual driver for the USB device that is failing.

if you still get a bugcheck, you need to change the memory dump type to kernel memory dump, wait for the next memory dump and then put it on a server like microsoft onedrive, share the file as public then post a link. Minidumps do not save the debug info for USB problems, you have to provide the kernel memory dump to have it debugged. Generally, the fix will be the same in any case, update bios, motherboard driver and the device driver for the actual device.

 
Solution