Usb hub blue screen

[Deurklink]

Hi guys, ive had allot of problems with the new windows OS.
I opened the memory dmp file but iam not sure how to fix this problem.
The problem is i get allot of bluescreens.
It seems that usb hub driver is causing the problem.
Heres a copy of the dmp:

BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000008, USBBUGCODE_RESERVED_USBHUB
Arg2: 0000000000000006, USBHUB_TRAP_FATAL_TIMEOUT
Arg3: 000000000000000a, TimeoutCode
Arg4: fffffa8005163640


MODULE_NAME: usbhub

FAULTING_MODULE: fffff8000281b000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 49ee99ed

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xFE

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff880048129ec to fffff80002899f80

STACK_TEXT:
fffff880`02fa8c18 fffff880`048129ec : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`0000000a : nt!KeBugCheckEx
fffff880`02fa8c20 fffff800`02b6dee3 : fffffa80`04fc0050 00000000`00000001 ffffffff`dc3a58a0 fffff800`02a2c638 : usbhub+0x129ec
fffff880`02fa8c80 fffff800`0289f744 : fffff800`02a2c600 fffffa80`050da701 fffffa80`03a00b00 fffffa80`03a00b60 : nt!SeCreateAccessStateEx+0x743
fffff880`02fa8cb0 fffff800`02b1fe66 : 00000538`00000000 00000000`00000001 fffffa80`03a00b60 00000538`00000000 : nt!ExAcquireResourceExclusiveLite+0x324
fffff880`02fa8d40 fffff800`0284ca86 : fffff880`02d63180 fffffa80`03a00b60 fffff880`02d6dfc0 00000538`00000000 : nt!PsCreateSystemThread+0x1da
fffff880`02fa8d80 00000000`00000000 : fffff880`02fa9000 fffff880`02fa3000 fffff880`02fa8970 00000000`00000000 : nt!KeInitializeTimerEx+0x66


STACK_COMMAND: kb

FOLLOWUP_IP:
usbhub+129ec
fffff880`048129ec cc int 3

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: usbhub+129ec

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: usbhub.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------


Could it be that my OS blues screens because i have to much usb ports?
My motherboard has about 6, and my case has 2 more.
Can anyone explain to me how to fix this problem.
Thanks,

 

[H2SO4]

STACK_TEXT:
fffff880`02fa8c18 fffff880`048129ec : 00000000`000000fe 00000000`00000008 00000000`00000006 00000000`0000000a : nt!KeBugCheckEx
fffff880`02fa8c20 fffff800`02b6dee3 : fffffa80`04fc0050 00000000`00000001 ffffffff`dc3a58a0 fffff800`02a2c638 : usbhub+0x129ec
fffff880`02fa8c80 fffff800`0289f744 : fffff800`02a2c600 fffffa80`050da701 fffffa80`03a00b00 fffffa80`03a00b60 : nt!SeCreateAccessStateEx+0x743
fffff880`02fa8cb0 fffff800`02b1fe66 : 00000538`00000000 00000000`00000001 fffffa80`03a00b60 00000538`00000000 : nt!ExAcquireResourceExclusiveLite+0x324
fffff880`02fa8d40 fffff800`0284ca86 : fffff880`02d63180 fffffa80`03a00b60 fffff880`02d6dfc0 00000538`00000000 : nt!PsCreateSystemThread+0x1da
fffff880`02fa8d80 00000000`00000000 : fffff880`02fa9000 fffff880`02fa3000 fffff880`02fa8970 00000000`00000000 : nt!KeInitializeTimerEx+0x66

That stack doesn't look right. Having the kernel call into usbhub.sys because it wants to "PsCreateSystemThread" seems a little unlikely. The stack itself may have been damaged during the crash.

Can you upload the minidump?

Could it be that my OS blues screens because i have to much usb ports?

No. There's no such thing as a BSoD-inducing number of USB ports, and if there was it would certainly be higher than single digits