Mountain View, CA
reply to auggy
Re: USB 3 hub causing BSOD's Overclocking a CPU would not cause this specific error.
This problem is indicative of either a) a driver that is doing something incredibly broken/wrong (holding clock timer interrupt in suspended state too long), b) a BIOS/UEFI bug of some sort (yep really, could pertain to APIC interrupt configuration), or c) a power saving mode exhibited by the chip (or OS) in which the chip never actually recovers from this PM state in certain situations.
If he had a bad CPU or a "wonky" CPU (i.e. overclocking + overheating), he'd be seeing this behaviour randomly throughout normal operation -- in this case he only sees it when removing a device from a hub, where the hub is attached to a USB 3.0 port driven by the on-board Asmedia USB controller.
One thing I can recommend trying would be to uncheck the checkbox in Windows for the related USB devices (the root hub (Asmedia chip) as well as the USB 3.0 hub itself) "power saving" modes. Windows has never made it easy to figure out the USB topology (what's connected to what), so you may have to try unchecking that on every USB-related device.
If that provides no relief, Asus is the only company that can provide a fix (especially if it's either (a) or (b) listed above).
Making life hard for others since 1977.
I speak for myself and not my employer/affiliates of my employer.