How to fix hardware crashes (USBHUB3)

[ShadowDisrupter]

Starting today, my desktop (custom built running windows 10 64-bit) has started crashing completely and restarting, typically when I am running games. When it's crashing, it happens every 10-15 minutes. Following tutorials online about checking drivers, I can't seem to have any success finding what "USBHUB3" is.

My report from the problem manager reads as following:
*********************************************************************************
Problem signature
Problem Event Name: LiveKernelEvent
Code: 144
Parameter 1: 3003
Parameter 2: ffffd00021763840
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_10240
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.10240.2.0.0.768.101
Locale ID: 1033
Files that help describe the problem
USBHUB3-20160730-2127.dmp
sysdata.xml
WERInternalMetadata.xml
*********************************************************************************

From there I used WinDbg to open the .dmp provided:
*********************************************************************************
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 144, {3003, ffffd00021763840, 0, 0}

Probably caused by : UsbHub3.sys ( UsbHub3!TelemetryData_CreateReport+c0 )

Followup: MachineOwner
*********************************************************************************

Does anyone know where I would look to remedy this crash, or what other files I should be checking to find the problem?

 

[BadActor]

Go to your motherboard manufacturers website and download/install the motherboard drivers for your board and OS. You might have a corrupt or buggy USB driver.

 

[ShadowDisrupter]

Go to your motherboard manufacturers website and download/install the motherboard drivers for your board and OS. You might have a corrupt or buggy USB driver.

My motherboard comes with Live Update, which automatically downloads needed drivers. Here http:// is a list of the drivers for my board... none seem USB specific. Any idea which would be needed?

EDIT: Updated mostly everything, doesn't seem to fix anything

 

[johnbl]

Update the bios and the motherboard drivers, remove old usb devices from the usb 3 bus.
Generally the bios date needs to be newer than March 2013 in order to have proper success.
Sometimes motherboards will have chips that have bugs in the electronics if you can not get bios updates and custom versions of the usb drivers the electronics will hang the system. Put old usb devices on a usb2 port to try to reduce the number of system hangs. Based on the name of the memory dump you have some issue detected by windows error reporting

Starting today, my desktop (custom built running windows 10 64-bit) has started crashing completely and restarting, typically when I am running games. When it's crashing, it happens every 10-15 minutes. Following tutorials online about checking drivers, I can't seem to have any success finding what "USBHUB3" is.

My report from the problem manager reads as following:
*********************************************************************************
Problem signature
Problem Event Name: LiveKernelEvent
Code: 144
Parameter 1: 3003
Parameter 2: ffffd00021763840
Parameter 3: 0
Parameter 4: 0
OS version: 10_0_10240
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.10240.2.0.0.768.101
Locale ID: 1033
Files that help describe the problem
USBHUB3-20160730-2127.dmp
sysdata.xml
WERInternalMetadata.xml
*********************************************************************************

From there I used WinDbg to open the .dmp provided:
*********************************************************************************
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 144, {3003, ffffd00021763840, 0, 0}

Probably caused by : UsbHub3.sys ( UsbHub3!TelemetryData_CreateReport+c0 )

Followup: MachineOwner
*********************************************************************************

Does anyone know where I would look to remedy this crash, or what other files I should be checking to find the problem?

 

[ShadowDisrupter]

*snip*

I have everything removed from 3.0 ports and also reinstalled bios. I have the front panel USB 3.0's plugged into the board header but nothings plugged into them.. would removing that header possibly help?

 

[johnbl]

Remove the header and see if you still get hangs. If you do, then disable the usb
3 port in bios and see if you still get a bug check.

*snip*

I have everything removed from 3.0 ports and also reinstalled bios. I have the front panel USB 3.0's plugged into the board header but nothings plugged into them.. would removing that header possibly help?

 

[ShadowDisrupter]

*snip*

After unplugging the header and disabling the usb 3.1 in device manager, I still get the crash and at the same frequency, however reliability manager no longer shows the hardware failure. Just "Windows was not properly shutdown"

 

[johnbl]

See if you can disable the usb 3 support In bios.
Put a current memory dump on a server and post a link.

Change the memory dump type to kernel when you get the next bug check put the kernel dump on a Server and post the link

*snip*

After unplugging the header and disabling the usb 3.1 in device manager, I still get the crash and at the same frequency, however reliability manager no longer shows the hardware failure. Just "Windows was not properly shutdown"

 

[ShadowDisrupter]

See if you can disable the usb 3 support In bios.
Put a current memory dump on a server and post a link.

Change the memory dump type to kernel when you get the next bug check put the kernel dump on a Server and post the link

*snip*

After unplugging the header and disabling the usb 3.1 in device manager, I still get the crash and at the same frequency, however reliability manager no longer shows the hardware failure. Just "Windows was not properly shutdown"

It appears my system isn't writing the dumps

 

[johnbl]

set the memory dump type to kernel https://community.sophos.com/kb/en-US/111474
make settings to so you can force a memory dump with a keyboard:
https://blogs.technet.microsoft.com/askpfeplat/2015/04/05/how-to-force-a-diagnostic-memory-dump-when-a-computer-hangs/
(or google for a better instructions)


then force a kernel memory dump while the system is still working. put c:\windows\memory.dmp file on a server, share for public access and post a link.

See if you can disable the usb 3 support In bios.
Put a current memory dump on a server and post a link.

Change the memory dump type to kernel when you get the next bug check put the kernel dump on a Server and post the link

*snip*

After unplugging the header and disabling the usb 3.1 in device manager, I still get the crash and at the same frequency, however reliability manager no longer shows the hardware failure. Just "Windows was not properly shutdown"

It appears my system isn't writing the dumps

 

[ShadowDisrupter]

set the memory dump type to kernel https://community.sophos.com/kb/en-US/111474
make settings to so you can force a memory dump with a keyboard:
https://blogs.technet.microsoft.com/askpfeplat/2015/04/05/how-to-force-a-diagnostic-memory-dump-when-a-computer-hangs/
(or google for a better instructions)


then force a kernel memory dump while the system is still working. put c:\windows\memory.dmp file on a server, share for public access and post a link.

See if you can disable the usb 3 support In bios.
Put a current memory dump on a server and post a link.

Change the memory dump type to kernel when you get the next bug check put the kernel dump on a Server and post the link

*snip*

After unplugging the header and disabling the usb 3.1 in device manager, I still get the crash and at the same frequency, however reliability manager no longer shows the hardware failure. Just "Windows was not properly shutdown"

It appears my system isn't writing the dumps

Still no logs being created, even with ctrl scroll crash. It goes to the bluescreen, has 0% of collecting information, then almost immediately completely shuts down. I only have ~3gb of disk space... is this not enough for logs?

 

[ShadowDisrupter]

Now, it just crashed, {computer started up for 3 seconds, crashed}(happened 3x in a row), then it fully booted. Could it be an issue with my mb..?

 

[johnbl]

free up disk space on the c: drive
there should be room for your pagefile.sys to expand and you want to have plenty of space for your memory dump file.
full memory dump will take the same space as your physical memory. a kernel memory dump should still be .75 to 1.25 GB

if you have any old minidumps in the c:\windows\minidump directory you can copy one of them up to a server and I can take a look at it also. it will not have the proper error logs but it might show some issues.

Now, it just crashed, {computer started up for 3 seconds, crashed}(happened 3x in a row), then it fully booted. Could it be an issue with my mb..?

 

[ShadowDisrupter]

free up disk space on the c: drive
there should be room for your pagefile.sys to expand and you want to have plenty of space for your memory dump file.
full memory dump will take the same space as your physical memory. a kernel memory dump should still be .75 to 1.25 GB

if you have any old minidumps in the c:\windows\minidump directory you can copy one of them up to a server and I can take a look at it also. it will not have the proper error logs but it might show some issues.

Now, it just crashed, {computer started up for 3 seconds, crashed}(happened 3x in a row), then it fully booted. Could it be an issue with my mb..?

My drive has definitely had enough space now, yet still no dumps. I think it's my bios, but I can't get it to flash properly. I'm downloading the file from the aforementioned link and putting it in the root of my USB, but m-flash isn't detecting the bios file

 

[johnbl]

do you have a pagefile.sys on your c: drive? size should be 1.5 to 2 times the size of the physical RAM.
your USBHUB3-20160730-2127.dmp file was generated by a windows error reporting automated debug attempt.

you start cmd.exe as an admin then
cd c:\
dir /s *.dmp

and try to locate that file and put it on a server and post a link. It will have some of the proper debug info.
you are also running a very old version of windows 10 are you blocking updates? There is not much point of letting windows error reporting service debug your machine if it can not install the updates.

free up disk space on the c: drive
there should be room for your pagefile.sys to expand and you want to have plenty of space for your memory dump file.
full memory dump will take the same space as your physical memory. a kernel memory dump should still be .75 to 1.25 GB

if you have any old minidumps in the c:\windows\minidump directory you can copy one of them up to a server and I can take a look at it also. it will not have the proper error logs but it might show some issues.

Now, it just crashed, {computer started up for 3 seconds, crashed}(happened 3x in a row), then it fully booted. Could it be an issue with my mb..?

My drive has definitely had enough space now, yet still no dumps. I think it's my bios, but I can't get it to flash properly. I'm downloading the file from the aforementioned link and putting it in the root of my USB, but m-flash isn't detecting the bios file

 

[ShadowDisrupter]

do you have a pagefile.sys on your c: drive? size should be 1.5 to 2 times the size of the physical RAM.
your USBHUB3-20160730-2127.dmp file was generated by a windows error reporting automated debug attempt.

you start cmd.exe as an admin then
cd c:\
dir /s *.dmp

and try to locate that file and put it on a server and post a link. It will have some of the proper debug info.
you are also running a very old version of windows 10 are you blocking updates? There is not much point of letting windows error reporting service debug your machine if it can not install the updates.

free up disk space on the c: drive
there should be room for your pagefile.sys to expand and you want to have plenty of space for your memory dump file.
full memory dump will take the same space as your physical memory. a kernel memory dump should still be .75 to 1.25 GB

if you have any old minidumps in the c:\windows\minidump directory you can copy one of them up to a server and I can take a look at it also. it will not have the proper error logs but it might show some issues.

Now, it just crashed, {computer started up for 3 seconds, crashed}(happened 3x in a row), then it fully booted. Could it be an issue with my mb..?

My drive has definitely had enough space now, yet still no dumps. I think it's my bios, but I can't get it to flash properly. I'm downloading the file from the aforementioned link and putting it in the root of my USB, but m-flash isn't detecting the bios file

I'm 99.9% sure it's my motherboard now. They're not being generated because I'm pretty sure my bios is failing and just instantly shutting power. My case lights, fans, and system just immediately go off