Hi, I was hoping someone could help me or give me advice about my problem. My computer was working fine until I installed a new CPU cooler yesterday to get rid of my very loud, older one. I was able to get new cooler in and it all seemed to be working fine. I then tried to play a game and each time I play a game I get a blue screen after a few minutes. I do not know what to do about it anymore.
I have tried updating my drivers, changing the setting in game (I have a powerful PC), doing a system restore to factory settings, verifying my windows, checking my RAM for errors,stress tested my parts and no blue screen when i stressed everything fully, and other stuff I do not remember it was a long night last night. After trying all of that it didnt help, I get the same problem.
It is bugcode_usb_driver error.
Thanks for reading this hopefully someone can help me! I just have no idea how to fix this. I am guessing it may be a hardware problem now if I restored and it still happens. Thanks so much.
Here is the dmp file (I think) if it helps with this:
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022316-11437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*DownstreamStore*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*DownstreamStore*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.103.amd64fre.th2_release.160126-1819
Machine Name:
Kernel base = 0xfffff800`3b874000 PsLoadedModuleList = 0xfffff800`3bb52cf0
Debug session time: Tue Feb 23 11:34:25.333 2016 (UTC - 8:00)
System Uptime: 0 days 0:27:46.033
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, ffffe001540ca1a0, 10024397, ffffe001538d82d8}
Probably caused by : usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+6b )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: ffffe001540ca1a0, Device extension pointer of the host controller
Arg3: 0000000010024397, PCI Vendor,Product id for the controller
Arg4: ffffe001538d82d8, Pointer to Endpoint data structure
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
DPC_STACK_BASE: FFFFF8003D402FB0
LAST_CONTROL_TRANSFER: from fffff800bdd3ede4 to fffff8003b9b6480
STACK_TEXT:
fffff800`3d3fb6d8 fffff800`bdd3ede4 : 00000000`000000fe 00000000`00000005 ffffe001`540ca1a0 00000000`10024397 : nt!KeBugCheckEx
fffff800`3d3fb6e0 fffff800`bdd02007 : 00000000`fffffff0 00000000`00000000 ffffe001`540cbda0 ffffe001`540ca050 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x127d4
fffff800`3d3fb720 fffff800`bdd23aa9 : ffffe001`540ca1a0 00000000`00000004 ffffe001`540ca050 00000000`00000002 : usbohci!OHCI_PollIsoEndpoint+0x6b
fffff800`3d3fb780 fffff800`bdd235c9 : ffffe001`540cac28 ffffe001`540ca050 ffffe001`540ca1a0 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x199
fffff800`3d3fb7e0 fffff800`bdd2c965 : ffffe001`540cab90 ffffe001`540ca1a0 00000000`f4296c6f ffffe001`533da060 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x309
fffff800`3d3fb840 fffff800`3b8e23c0 : fffff800`3d3fb9c0 ffffe001`567e3010 fffff800`3d3fbb30 fffff800`3bb90f44 : USBPORT!USBPORT_Xdpc_Worker_HcIntDpc+0x205
fffff800`3d3fb8c0 fffff800`3b8e1ad9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x270
fffff800`3d3fba10 fffff800`3b9b923a : 00000000`00000000 fffff800`3bb91180 fffff800`3bc07740 ffffe001`53819080 : nt!KiRetireDpcList+0xe9
fffff800`3d3fbc60 00000000`00000000 : fffff800`3d3fc000 fffff800`3d3f6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usbohci!OHCI_PollIsoEndpoint+6b
fffff800`bdd02007 8bd3 mov edx,ebx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbohci!OHCI_PollIsoEndpoint+6b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbohci
IMAGE_NAME: usbohci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5632d90d
IMAGE_VERSION: 10.0.10586.0
BUCKET_ID_FUNC_OFFSET: 6b
FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollIsoEndpoint
BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollIsoEndpoint
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xfe_invalid_physical_addr_usbohci!ohci_pollisoendpoint
FAILURE_ID_HASH: {888386cf-3fa9-05fe-5e98-626dde26e5a1}
Followup: MachineOwner
---------
I have tried updating my drivers, changing the setting in game (I have a powerful PC), doing a system restore to factory settings, verifying my windows, checking my RAM for errors,stress tested my parts and no blue screen when i stressed everything fully, and other stuff I do not remember it was a long night last night. After trying all of that it didnt help, I get the same problem.
It is bugcode_usb_driver error.
Thanks for reading this hopefully someone can help me! I just have no idea how to fix this. I am guessing it may be a hardware problem now if I restored and it still happens. Thanks so much.
Here is the dmp file (I think) if it helps with this:
Microsoft (R) Windows Debugger Version 6.3.9600.17336 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\022316-11437-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred srv*DownstreamStore*https://msdl.microsoft.com/download/symbols
Symbol search path is: srv*DownstreamStore*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.103.amd64fre.th2_release.160126-1819
Machine Name:
Kernel base = 0xfffff800`3b874000 PsLoadedModuleList = 0xfffff800`3bb52cf0
Debug session time: Tue Feb 23 11:34:25.333 2016 (UTC - 8:00)
System Uptime: 0 days 0:27:46.033
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
.............................................................
................................................................
.........................................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck FE, {5, ffffe001540ca1a0, 10024397, ffffe001538d82d8}
Probably caused by : usbohci.sys ( usbohci!OHCI_PollIsoEndpoint+6b )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BUGCODE_USB_DRIVER (fe)
USB Driver bugcheck, first parameter is USB bugcheck code.
Arguments:
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: ffffe001540ca1a0, Device extension pointer of the host controller
Arg3: 0000000010024397, PCI Vendor,Product id for the controller
Arg4: ffffe001538d82d8, Pointer to Endpoint data structure
Debugging Details:
------------------
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xFE
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) amd64fre
DPC_STACK_BASE: FFFFF8003D402FB0
LAST_CONTROL_TRANSFER: from fffff800bdd3ede4 to fffff8003b9b6480
STACK_TEXT:
fffff800`3d3fb6d8 fffff800`bdd3ede4 : 00000000`000000fe 00000000`00000005 ffffe001`540ca1a0 00000000`10024397 : nt!KeBugCheckEx
fffff800`3d3fb6e0 fffff800`bdd02007 : 00000000`fffffff0 00000000`00000000 ffffe001`540cbda0 ffffe001`540ca050 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x127d4
fffff800`3d3fb720 fffff800`bdd23aa9 : ffffe001`540ca1a0 00000000`00000004 ffffe001`540ca050 00000000`00000002 : usbohci!OHCI_PollIsoEndpoint+0x6b
fffff800`3d3fb780 fffff800`bdd235c9 : ffffe001`540cac28 ffffe001`540ca050 ffffe001`540ca1a0 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x199
fffff800`3d3fb7e0 fffff800`bdd2c965 : ffffe001`540cab90 ffffe001`540ca1a0 00000000`f4296c6f ffffe001`533da060 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x309
fffff800`3d3fb840 fffff800`3b8e23c0 : fffff800`3d3fb9c0 ffffe001`567e3010 fffff800`3d3fbb30 fffff800`3bb90f44 : USBPORT!USBPORT_Xdpc_Worker_HcIntDpc+0x205
fffff800`3d3fb8c0 fffff800`3b8e1ad9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x270
fffff800`3d3fba10 fffff800`3b9b923a : 00000000`00000000 fffff800`3bb91180 fffff800`3bc07740 ffffe001`53819080 : nt!KiRetireDpcList+0xe9
fffff800`3d3fbc60 00000000`00000000 : fffff800`3d3fc000 fffff800`3d3f6000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
STACK_COMMAND: kb
FOLLOWUP_IP:
usbohci!OHCI_PollIsoEndpoint+6b
fffff800`bdd02007 8bd3 mov edx,ebx
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: usbohci!OHCI_PollIsoEndpoint+6b
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: usbohci
IMAGE_NAME: usbohci.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 5632d90d
IMAGE_VERSION: 10.0.10586.0
BUCKET_ID_FUNC_OFFSET: 6b
FAILURE_BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollIsoEndpoint
BUCKET_ID: 0xFE_INVALID_PHYSICAL_ADDR_usbohci!OHCI_PollIsoEndpoint
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xfe_invalid_physical_addr_usbohci!ohci_pollisoendpoint
FAILURE_ID_HASH: {888386cf-3fa9-05fe-5e98-626dde26e5a1}
Followup: MachineOwner
---------