bugcheck was in usb code extensions.
i would guess it was from this device:
"HID\VID_1B1C&PID_0A52&MI_03&Col01\8&7552ab9&0&0000"
https://devicehunt.com/view/type/usb/vendor/1B1C
it is some corsair device but id did not see 0a52 as a device in the list.
this could be:
the device itself: Look for a firmware update, maybe move the device to a different USB host by itself, or remove the device, depending on what it is. (move it to usb 2.x port if you have one, usb3 ports are more likely to have bugs)
this could also be: a bug in your bios setup for the usb, or the wrong usb extension driver USBXHCI.sys or UsbHub3.sys
looks like you have the microsoft generic driver for both of these.
see if your motherboard has a custom USB 3 driver to install.
(custom drivers have to match the bios version)
so, for each of your usb devices, you need to make sure you have updated the firmware. Also check for firmware updates for the usb chips on the motherboard.
the video device indicated a Mouse. Does your mouse have lights that you can control? see if there is a firmware update for the mouse
looks like all of the cosair devices are listed as vid on the usb port. all have custom logs that I can not read with the debugger. I I can really read is one asked to see what other devices were connected to the USB bus and the bus just stopped working. then you got a bugcheck since a bogus memory location (address 19) was used.
I think it is just going to be a stupid bug where some device passed the contents of a memory pointer rather than the memory pointer itself. ie the number 19 is the size of the memory block not the address.
you might consider going into windows control panel, device manager and find every single USB port and right clicking on them and find the power management tab and tell windows not to put them to sleep. just in case this is some sleep issue with one of the devices on the USB bus.
found a internal error for device
USB\VID_1B1C&PID_0A52&REV_2041
it indicated that it was doing something that is only allowed by an audio device but the device was a video device. look for firmware update.
I am guessing it is corsair speaker that were set up as a video device.
------------
debugger internal log:
496: HUBPDO_CreatePdoInternal - Device Context 0xFFFF878B68E3A170 - USB\VID_1B1C&PID_0A52&REV_2041 - Port Path 6:0:0:0:0:0
497: HUBPDO_EvtDevicePrepareHardware - DeviceHackFlags:0x8
498: HUBDESC_InternalValidateEndpointDescriptor - HW_COMPLIANCE:Configuration Descriptor Validation warning due to the bLength value (0x9) of the endpoint descriptor at offset (0xb7) is greater than expected (0x7). This is allowed by the audio class, but others should avoid it.
499: HUBDESC_InternalValidateEndpointDescriptor - HW_COMPLIANCE:Configuration Descriptor Validation warning due to the bLength value (0x9) of the endpoint descriptor at offset (0xfa) is greater than expected (0x7). This is allowed by the audio class, but others should avoid it.
500: HUBDESC_InternalValidateLastInterface - HW_COMPLIANCE:Configuration Descriptor Validation Failed due to the number of endpoint descriptors found (0x0) for an interface was not equal to the number specified (0x1) in the corresponding interface descriptor (bInterfaceNumber 0x2 and bAlternateSetting 0x2). Ignoring failure for further validation.
501: HUBPDO_EvtDeviceWdmIrpPreprocess - Failing the MS OS Descriptor request by client as the device does not support it
------------
usb c port was reset in the logs right before the crash.