USB Device Descriptor Failed??

So this kept happening before and then it stopped being problematic for a while..unfortunately the issue has once again returned. In Event Viewer it says usbhci or something. When this issue occurs a few things happen:

• All USB devices cease to function until system is rebooted
• Network controller ceases to function

Event Viewer also shows an error (in System pane) for Kernel=PnP:

Code:

Log Name:      System
Source:        Microsoft-Windows-Kernel-PnP
Date:          12-Sep-17 1:02:45 PM
Event ID:      219
Task Category: (212)
Level:         Warning
Keywords:      
User:          SYSTEM
Computer:      Kyle-PC
Description:
The driver \Driver\WudfRd failed to load for the device USB\VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android\6&18f52f5f&1&0000.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
    <EventID>219</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>212</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2017-09-12T12:02:45.418437100Z" />
    <EventRecordID>14537</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="304" />
    <Channel>System</Channel>
    <Computer>Kyle-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="DriverNameLength">67</Data>
    <Data Name="DriverName">USB\VID_04E8&amp;PID_6860&amp;MS_COMP_MTP&amp;SAMSUNG_Android\6&amp;18f52f5f&amp;1&amp;0000</Data>
    <Data Name="Status">3221226341</Data>
    <Data Name="FailureNameLength">14</Data>
    <Data Name="FailureName">\Driver\WudfRd</Data>
    <Data Name="Version">0</Data>
  </EventData>
</Event>

USBEHCI:

A timeout occurred while waiting for the EHCI host controller Asynchronous Schedule to transition to the enabled state.

Code:

Log Name:      System
Source:        usbehci
Date:          12-Sep-17 12:59:17 PM
Event ID:      3
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Kyle-PC
Description:
A timeout occurred while waiting for the EHCI host controller Asynchronous Schedule to transition to the enabled state.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="usbehci" />
    <EventID Qualifiers="49153">3</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-09-12T11:59:17.462532700Z" />
    <EventRecordID>14488</EventRecordID>
    <Channel>System</Channel>
    <Computer>Kyle-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\USBFDO-3</Data>
    <Binary>000068000100000000000000030001C000000000000000000000000000000000000000000000000002109643000000006A1200005A12000010000000000000000000000013000000000000000000000000000000000000005174000003000000020000000100000011000000DE7B00000000000000000000100000000000000001000000000000000000000000000000</Binary>
  </EventData>
</Event>

Hi there. Run the troubleshooter within the Settings app > Update & security > Troubleshoot.

You may also want to look in Security Center > Device performance and health.

Done both and they found no issues. Windows has never been so helpful with such troubleshooting. It just says what I already know.

Code:

 

Unknown USB Device (Device  Descriptor Request Failed) is not working properly
 Detected
[IMG]res://sdiageng.dll/warning.png[/IMG]



 Windows has  detected a problem with Unknown USB Device (Device Descriptor Request Failed).

I find that troubleshooters work a majority of times, but not always.

Sounds like a corrupt or faulty USB controller drivers. Have you tried updating that driver? Look on the manufactures site for updated one? You may try uninstalling the USB controllers and reboot. I've done that in the past for a fix.

Have you tried the thumb in another PC? Could be it corrupts the system. Run a virus scan?

System is completely clean from any type of virus. I've done a system integrity and disk check. It's not a USB storage device (I don't think) that's causing it as the same USB devices are connected still when it didn't happen. It just so randomly happens. There is no point really in going to ASUS' website as they don't update the drivers list for my motherboard, or in some cases any board really. The only alternative would really be to try and find a new updated driver for the actual controller manufacturer itself?? I don't know. It's the USB 2.0 controller possibly. I don't have any USBs in USB 3.0 slots.

USB Controller is ASMedia apparently.

The EHCI (enhanced host controller interface) driver simultaneously supports USB 2.0 and USB 1.1 protocols.

Yes, it's probably an Asmedia brand Host Controller. I have an Asus board with it and install the Asmedia driver for it after an OS install. You must have the generic driver as seen in red font below vs mine in my shot? You can look up your board on the Asus site and download the drivers for various peripherals.

Are you plugging in an Android phone? The event is:

The driver \Driver\WudfRd failed to load for the device USB\VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android\6&18f52f5f&1&0000.


Attachment 152989

Yeah, I have my Galaxy S6 Edge connected via USB constantly as I use it for my Internet connection. I use PDANet+. :P

Hmm. It states it can't load the device driver (which actually allows the PC to read the phone) and it works for your connection? This is weird. Perhaps it's attempting to install a second instance of the driver?

I have a Windows phone that it loads a driver for with no problems, but don't use it for a connection. I can see mine in USB devices with Device Manager. What's yours looking like?

I just updated the Samsung Android ADB Interface via the Device Manager and all 3 ASMedia USB3.0 eXtensible Host Controllers. I downloaded this update from the Microsoft Update Catalog and updated it through the Device Manager as well.

Cool. Should be good to go now.

So it loaded the adapter (via your phone) driver, but couldn't install ADB interface driver to read the phone (as a drive) I assume?

You should be better off with the Asmedia drivers, although it had nothing to do with your problem.