I hope to avoid reinstalling windows as that would mean reloading all apps and files. Here is a picture of my device manager as it stands now.
I am wondering if that's what the error I'm seeing is - not having that ASMedia USB root hub driver that I need for Oculus. I am wondering if that's the problem as I don't see one for 3.1? When I google device manager images randomly with some of my key search words, I do see some device managers having "ASMedia USB Root Hub" under that last USB Controllers section. One question I have is should I have a second USB root hub in the device manager USB controllers section at the bottom? The only one I have says USB Root Hub (USB 3.0). But I have 30 days and want to be sure it's not my USB root hub before I do that. Some backstory here is that I went through Oculus support for over a week and now have an RMA to send the Quest 2 back to them. I have tried it in both the USB-C port and a regular fast USB port (blue ones) with an adapter which should work (USB 3.1 GEN 2 Male to Type-C Female Adapter ). So now the only device manager errors I have are related to ASMedia root hubs.Īll of my USB ports seem to work for typical peripherals (webcam, headphones, mouse, keyboard) except that my Oculus Quest 2 does not. I also removed the CSR bluetooth chip which boosts bluetooth because it also creates an error and I'm not using it anyway. Asus driver from 2018 and creates the error. Strangely, when I update the adapter using Driver Booster 8, it loads a driver from 2019 vs. Both 3.1 and 3.0 ASMedia controllers were now running the same driver on the same workstation.Ok, I fixed the Bluetooth drivers. We installed an older ASMedia ASM1042 USB 3.0 PCI-E controller card in our USB test workstation and installed the ASMedia 1.16.23.0 drivers once again. We did some digging and found that the “asmtxhci.inf” driver file from the ASMedia driver installer not only worked for the new ASM1142 USB 3.1 controller, but it appeared to be a unified driver covering all ASMedia USB host controllers. This was not a compromise we were willing to make. We found that the controller became as stable as the Intel controller but with the tradeoff of losing USB 3.1 functionality for future USB 3.1 devices. If you are not able to update to the latest version of the driver by following the steps in that article, download the latest. We recommend that you check for updates by following the steps in this article: Update drivers in Windows 10. The driver version that you currently have is outdated. We decided to remove the ASMedia 1.16.23.0 drivers and roll back to the built-in Microsoft “0110” drivers to see what would happen. In reply to EricSmith778s post on May 10, 2017.
When connecting these same devices to the on-board Intel 9 Series USB 3.0 controller there were no issues. Sometimes the crash would occur with a simple USB 3.0 flash drive, other times with our 7-port hub and all 7 ports occupied with USB graphics adapters.
After several reboots and experimentation, we found the crashes to vary widely in frequency.
0 kommentar(er)
