New to the forums? Click here to read the "How To" Guide.

Developer? Click here to go to the Developer Forums.

Oculus owned USB device constantly throwing errors

TenaciousJTenaciousJ Posts: 58
Hiro Protagonist
How do I stop these errors from happening over and over again?!

First variant is Event ID 411:

Device USB\VID_2833&PID_3031\MSFT30123456789A had a problem starting.

Driver Name: usbhub3.inf
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Service: USBHUB3
Lower Filters: 
Upper Filters: 
Problem: 0x1F
Problem Status: 0xC00000BB

Second variant is Event ID 441:

Device USB\VID_2833&PID_3031\MSFT30123456789A could not be migrated.

Last Device Instance Id: USB\ROOT_HUB30\7&f3051e4&0&0
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: 
Migration Rank: 0xF000FFFFFFFFF110
Present: false
Status: 0xC0000719

The USB VID belongs to Oculus, but it's using a generic USB3 Hub driver from Microsoft, which makes very little sense, and is likely to be the reason it fails all the time.

I've uninstalled, reinstalled, reloaded, searched for, and otherwise banged my head against a wall trying to figure out what's causing this but I can't find any answers.

I'm running windows 10 pro on a Gigabyte Z170x-UD5 TH motherboard with a skylake i7-6700k cpu and 16gb DDR4 3200.

There are two USB controllers on the board, one is an intel alpine, and the other is a genesys.  The oculus sensors (x2) are plugged into USB 3.0 ports on the Alpine controller, and the HMD is plugged into a USB 3.1 port.   

The errors come in batches, usually occurring between 3 and 10 times in a row within a few minutes time, and the sources is always Kernel-PNP. with Event ID 411 or 441 

I've already made sure that the power settings are not allowing the ports to be turned off to save power.

Any info would be appreciated, since this is annoyingly causing my operating system to notify me every time the device decides to take a nap or be generally uncooperative. 

Thanks.


Comments

  • cyberealitycybereality Posts: 26,156 Oculus Staff
    You can try different USB ports. USB 2.0 tends to be more reliable. I would avoid using USB 3.1. 
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
  • TenaciousJTenaciousJ Posts: 58
    Hiro Protagonist
    Well, I think I found at least a potential source of the problem.  I had the xHCI option in my bios disabled, and turned that back on.  It didn't immediately fix the issue, but after uninstalling, moving the sensors to different usb 3 ports (the same 3 ports I was already using, just different oculus devices in each port), and then running oculus setup again, the driver has cooperated and stopped throwing that driver error.  

    My instinct is that the likely solution was turning the xHCI option back on, since the intel usb 3.0 extensible usb hubs are xHCI based.  The sensor is STILL reading USB 2.0 even though it's in a USB 3.0 port though.. that indicates to me that there is still an underlying issue with the detection of the sensors, but as long as it works that's all I really care about.  

    Thanks for the pointer.

    (here's the error I was dealing with, in case it comes up again for someone else)





  • cyberealitycybereality Posts: 26,156 Oculus Staff
    Don't worry if it says it's running at USB 2.0. There is no problem with USB 2.0, it works fine.
    AMD Ryzen 7 1800X | MSI X370 Titanium | G.Skill 16GB DDR4 3200 | EVGA SuperNOVA 1000 | Corsair Hydro H110i
    Gigabyte RX Vega 64 x2 | Samsung 960 Evo M.2 500GB | Seagate FireCuda SSHD 2TB | Phanteks ENTHOO EVOLV
Sign In or Register to comment.