Good work, I can see you have successfully removed what I have asked. The attached DMP files are of the BUGCODE_USB_DRIVER (fe)
There is a problem with the USB hardware (motherboard or attachments) or the USB device driver has a bug.
USB Driver bugcheck, first parameter is USB bugcheck code.
Arg1: 0000000000000005, USBBUGCODE_INVALID_PHYSICAL_ADDRESS The host controller is
using a physical memory address that was not allocated by
the USBport driver.
Arg2: fffffa800e02a1a0, Device extension pointer of the host controller
Arg3: 0000000080863a3a, PCI Vendor,Product id for the controller
Arg4: fffffa800dda1258, Pointer to Endpoint data structure
10: kd> kv
Child-SP RetAddr : Args to Child : Call Site
fffff880`034e8a58 fffff880`071a9f7e : 00000000`000000fe 00000000`00000005 fffffa80`0e02a1a0 00000000`80863a3a : nt!KeBugCheckEx
fffff880`034e8a60 fffff880`02ec5fac : 00000000`be0f9180 fffffa80`0e02b6a0 00000000`00000000 fffffa80`0dda14f0 : USBPORT!USBPORTSVC_MapHwPhysicalToVirtual+0x18a
fffff880`034e8aa0 fffff880`02ec5b73 : fffffa80`0dda1258 fffffa80`0e201740 fffffa80`0dda14f0 00000000`00000000 : usbehci!EHCI_sMode_PollEndpointSlot+0x6c
fffff880`034e8b30 fffff880`02ecad91 : fffffa80`0dda1258 c5d0e708`56836b63 00000000`00000000 00000000`00000000 : usbehci!EHCI_PollPerAsyEndpoint+0x53
fffff880`034e8b70 fffff880`0717de8b : 00000000`00000002 fffffa80`0e02a1a0 00000000`00000000 00000000`00000030 : usbehci!EHCI_PollEndpoint+0x41
fffff880`034e8bb0 fffff880`071829d1 : 00000000`00000030 00000000`00000004 fffffa80`0dda1010 fffffa80`0e02a050 : USBPORT!MPf_PollEndpoint+0x9b
fffff880`034e8be0 fffff880`0718e077 : fffffa80`0e02a1a0 00000000`00000030 fffffa80`0000000e 00000000`00000000 : USBPORT!USBPORT_iSetGlobalEndpointStateTx+0x7c1
fffff880`034e8c40 fffff880`0717ef89 : fffffa80`0e02a050 00000000`00000000 fffffa80`0e02aa02 fffffa80`0e02aa18 : USBPORT!USBPORT_Core_UsbHcIntDpc_Worker+0x1c3
fffff880`034e8ca0 fffff800`040932fc : fffff880`034c0180 fffffa80`0e02aa18 fffffa80`0e02aa30 00000000`00000000 : USBPORT!USBPORT_Xdpc_Worker+0x1d9
fffff880`034e8cd0 fffff800`0408090a : fffff880`034c0180 fffff880`034cb1c0 00000000`00000000 fffff880`0717edb0 : nt!KiRetireDpcList+0x1bc
fffff880`034e8d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a
What USB devices do you often use / what's often attached to your system via USB?
I'd also like to check out device driver conflicts in general, so please enable Driver Verifier:
What is Driver Verifier?
Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.
Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.
Before enabling Driver Verifier, it is recommended to create a System Restore Point:
Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 - Restore Point - Create in Windows 8
How to enable Driver Verifier:
Start > type "verifier" without the quotes > Select the following options -
1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7)
- Concurrentcy Stress Test (Windows 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT
provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
Important information regarding Driver Verifier:
- If Driver Verifier finds a violation, the system will BSOD.
- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.
If this happens, do not
panic, do the following:
- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.
- Once in Safe Mode - Start > type "system restore" without the quotes.
- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:
- Start > Search > type "cmd" without the quotes.
- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・ Restart and boot into normal Windows.
How long should I keep Driver Verifier enabled for?
It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.
My system BSOD'd, where can I find the crash dumps?
They will be located in C:\Windows\Minidump
Any other questions can most likely be answered by this article:
Using Driver Verifier to identify issues with Windows drivers for advanced users