via usb extensible host controller 1.0 driver

Update your USB drivers first, THEN if the problem isn't fixed, swap the system board. You may want to try updating your Microsoft driver for your AMD USB 3.0 eXtensible Host Controller to at least this version if you haven't already: Although the Windows Operating Systems from Win8 up natively do support many USB 3.0 Controllers by using a generic Microsoft USB 3.0 driver, it is often better. It is connected only to a Western Digital backup drive, which gets power and spins.

I went to Renesas site and it says the driver is by Microsoft and gives no hint to what is a code 43 error. Just be aware that swapping out the system board did not fix my problem that was just like yours. I have a Renesas USB 3.0 Extensible Host Controller 1.0 (Microsoft) It has stopped working with a ' Code 43 ' error. I'm not advising you to swap out the WiFi NIC. I could not pin down the true fix of my problem-it can only be one of the two following changes:ġ) Microsoft later updated the AMD USB 3.10 eXtensible Host Controller via Windows Update.Ģ) I swapped the WiFi NIC that I was installing in PCI-e slot 4 (and that has a USB-attached Bluetooth card onboard) with the latest and greatest model with the Intel AX200 chipset. HOWEVER, I found out in my own instance that swapping out my own system board did not make the problem go away! Eventually the problem did get fixed, but it was not due to swapping the system board.

Via usb extensible host controller 1.0 driver