USB HOST CONTROLLER ERROR 31.

Hi,

the Installation of "Intel Wireless Display Application; Version  V3.5.40.0" solved the Problem.

Please check your current Intel Driver Installation via:

http://www.intel.com/p/de_DE/support/detect/wireless-Display

Maybe this helps you, as it helped me.

Michael Schulz

This problem is date sensitive.  Today is 1/5/2013 so I changed the date to 12/5/2012 and restarted the computer and everything was as it was when I looked at the Device Manager prior to new years.  I changed the date back to 1/5/2013 and the code 31 come back on the "USB-IF xHCI USB Host Controller."  Also it should be noted that the USB 3 driver disappears and reappears with the change of the date. 

 

Yes, shure it's really a date sensitivity problem. Crazy.

I did the same as quoted above and set the system date to 05. December 2012 on my ASUS ZENBOOK UX31A, restarted and went back to the device manager.

The Problem has gone! Both Intel WiUSB devices looked fine, no Errors anymore.

Both "USB-IF USB 3.0 Hub" and USB-IF xHCI Host Controller appeared without any errors.

Is there any solution in work that fixes the 2013 problem on Win 8 systems?

 I can't work on with last year 2012 to fix it, as anyone can understand! ;-)

Thanks for any help

Michael Schulz

Hi wiscomad,

Thank you for choosing Windows 8 and joining us on our community.

From your description, I understand you get Intel WiUSB USB-IF xHCI Host Controller error 31.

Could you answer few questions to understand the issue well:

1.       What is the make and model of your computer?

2.       Is it a USB 2.0 device or USB 3.0 device?

3.        what is the model number of the WD external drive?

I would suggest you to follow these methods to fix the driver related problem.

Method 1:

Run Hardware and Devices troubleshooter

Follow these steps to run Power troubleshooter.

a.       Press Windows key + W and type troubleshooting.

b.      Select Troubleshooting.

c.       Select view all on the top left corner.

d.      Run Hardware and Devices troubleshooter.

Method 2:

I would suggest you to uninstall all the USB drivers listed in device manager and then restart your computer.

Follow these steps to uninstall the USB drivers.

a.        Press Windows key + X key and click on Device manager.

b.       Search for Universal Serial Bus Controllersand expand it.

c.        Right-click on the USB driver and click on Uninstall.

d.       Uninstall each one of the drivers listed.

Now restart the computer to reinstall all the drivers.

Reference:

Install USB 3.0 and other USB devices

http://windows.microsoft.com/en-US/windows-8/install-usb-3-usb-devices

Hope it helps. For any Windows related queries feel free to get back to us.

P.S.:

In Addition you get these error messages two times on each Startup of system, in the event log when date is set to e.g. 06. January 2013:

Dem Computer wurde (vom DHCP-Server) keine Adresse aus dem Netzwerk für die Netzwerkkarte mit der Netzwerkadresse 0xC485084A15BA zugewiesen. Fehler: 0x79. Der Computer versucht, weiterhin selbständig eine Adresse vom Netzwerkadressserver (DHCP-Server) abzurufen.

After setting date to e.g. 05. december 2012 these errors also disappear from event log. 

Kind regards

Michael Schulz

Details from Event log:

This problem is date sensitive.  Today is 1/5/2013 so I changed the date to 12/5/2012 and restarted the computer and everything was as it was when I looked at the Device Manager prior to new years.  I changed the date back to 1/5/2013 and the code 31 come back on the "USB-IF xHCI USB Host Controller."  Also it should be noted that the USB 3 driver disappears and reappears with the change of the date. 

I have a Toshiba Satellite P875-S7310 with USB-3 hardware.  I searched forums for the problem and from comments of others, the problem occurs in other makes of computers.  In my opinion (and others) it is a Windows 8 problem.

I suppose Intel could have a "date" problem in the hardware but they appears to be saying that it is software.  We need to have a white paper on this problem from Microsoft certifying that the problem is not Windows 8 or Windows 8 driver problem.

Rob Umberger