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

Anonymous
2012-10-29T18:24:53+00:00

When I'm using my computer running Windows 8 Pro x64 randomly all of the USB's will freeze up, yet the PC will still run fine. Then they will all come back online a little while later. 

By online my WiFi adapter doesn't seem to re-initiate.

Checking the events log I see a flurry of the following error.

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

Thanks,

***Post moved by the moderator to the appropriate forum category.***

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2014-11-12T17:34:51+00:00

Those of you with USB WiFi adapters based on Atheros AR9271 chips (TP-Link WN722N, Netgear WNA1100 etc.) might want to try this.

I found a driver in the windows update catalog that is newer (version 2.0.0.49) than the one offered by windows update (2.0.0.32) that seems to have cured all the WiFi drops I was getting under heavy network load.

Atheros AR9271 Driver x64

You'll have to extract the .cab(inet) archive and then do a manual driver install (right click the adapter in device manager, update drivers and then pick the location manually, point it to where you unpacked the driver, from the 'have disk' dialog)

I have been running this for over a month and have not had any network specific drops since. Now, if I could only find a fix for the joystick drops in FSX...sigh

Notice, this is the 64bit driver, I cannot comment on the x86 driver one way or the other.

Also, if you are already running version 2.0.0.49 of the driver and still have problems, obviously this won't help you.

Hope this helps someone, best of luck.

Much thanks，this REALLY helps on tplink W822N

Problem solved~~~

Was this answer helpful?

2 people found this answer helpful.
0 comments

43 additional answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2013-04-21T21:44:44+00:00

    any chance you can share the reg key entry where you set the wifi parameters?

    thanks

    Was this answer helpful?

    0 comments
  2. Anonymous
    2013-04-21T23:27:13+00:00

    HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class to start with.  Then you'll need to search for *ReceiveBuffers, find your wireless adapter and then you can set them.  You can alternatively set them under your wireless connection properties > configure...good luck!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2013-04-22T08:52:08+00:00

    I have tried with two USB WiFi Cards with the same result:

    • TP-LINK TL-WN722N
    • ASUS USB N-13

    On Asus it goes a lot better (less often cut offs), but it's still a losing connection followed by the same errors in Events Log:

    • A timeout occurred while waiting for the EHCI host controller Interrupt on Async Advance Doorbell response.
    • WLAN Extensibility Module has failed to start.

    Module Path: C:\Windows\system32\Rtlihvs.dll

    Error Code: 126

    Was this answer helpful?

    0 comments
  4. Anonymous
    2013-04-30T20:50:29+00:00

    Same problem here. Random usb dropouts with same error message in event viewer. Definitely something wrong with windows 8 with regard to usb ports.

    I also have random usb joystick disconnects while playing FSX....another microsoft product. woopty-do

    This issue does not seem device related, i.e. not your USB WiFi adapter that causes it, because all usb ports fail when it happens, all my usb devices get re-initialised.

    This issue is not present in windows 7, as previous posters have mentioned.

    This issue seems related to systems with AMD chipsets running Windows 8, I too have a board with 970 chipset.

    It would be interesting to get reports of the same problem from people who have intel chipsets, then AMD could be eliminated from the problem.

    Microsnot know they've buggered the usb implementation as fairly recently they've release a patch to correct a blundering mistake in the way they've implemented the usb subsystem, but it still isn't fixed. (see http://support.microsoft.com/kb/2821819, in particular "Cause: This issue occurs because of incorrect retry logic for enumeration. The USB 3.0 hub cannot enumerate super speed ports. Therefore, all USB ports on the computer start to re-enumerate continuously. Then, all USB ports that are attached to devices stop responding.")

    How long is it going to take to fix something this crucial on your flagship os?

    TIME TO GET IT TOGETHER YET??? sheesh, ridiculous...

    Was this answer helpful?

    0 comments