USB controller out of Resources - Valve Index VR

[MrSheep110]

Sorry if this has been answered but I can't find it.

When I plug in my Index I get a USB controller doesn't have enough resources for this device error. At the moment I have all uptodate drivers as well as 2 devices plugged in that being my mouse and keyboard these are in 3.0 while my headset is in 3.10 which uses a different driver says my documentation. Is there a fix someone has found for the use of USB 3? 

Keep in mind I have already tried 
Disable the xHCI Mode option in BIOS.

Disabling the Legacy mode in BIOS 
Reinstall the Universal Serial Bus Controller drivers.

Using a 3.0 hub 

Reinstalling the Drivers for the Index (more than 3x) 

System info
Ryzen 7 1700x 3.77GHz
Asus prime x370-pro (USB 3.0 3.1 3.10Gb Tried them all) 

        Running Bios 5216 
16gb Ram
R9 390 (Is my Video card holding me back?)

 

Thanks

[Crunchy Dragon]

Do you still get that error if you unplug something like your headset?

[MrSheep110]

2 minutes ago, Crunchy Dragon said:

Do you still get that error if you unplug something like your headset?

I do not. I also didn't get this error with the original Vive Did forget to mention that in the initial post. It is linked to the headset itself.

[Crunchy Dragon]

1 minute ago, MrSheep110 said:

I do not. I also didn't get this error with the original Vive Did forget to mention that in the initial post. It is linked to the headset itself.

What if you plug your headset into a USB2 port?

[MrSheep110]

3 minutes ago, Crunchy Dragon said:

What if you plug your headset into a USB2 port?

The Index does require 3.0 to operate but let me get back to you on that, if you think that it would work

 

[Crunchy Dragon]

Just now, MrSheep110 said:

The Index does require 3.0 to operate but let me get back to you on that, if you think that it would work

Actually, try USB2 on your keyboard and mouse first.

 

Sorry, I completely blanked on the fact that you were doing VR, and thought you meant a headset as in for sound. My bad.

[MrSheep110]

1 minute ago, Crunchy Dragon said:

Actually, try USB2 on your keyboard and mouse first.

 

Sorry, I completely blanked on the fact that you were doing VR, and thought you meant a headset as in for sound. My bad.

How fun that that is already what Im doing 

[MrSheep110]

I have actually now uninstalled and reinstalled drivers again and it still wont work but has no longer given me the USB resource error. I do wonder if that is just my computer being completely done with my BS or if its actually trying to work... When its still not 

[Crunchy Dragon]

6 minutes ago, MrSheep110 said:

I have actually now uninstalled and reinstalled drivers again and it still wont work but has no longer given me the USB resource error. I do wonder if that is just my computer being completely done with my BS or if its actually trying to work... When its still not 

Interesting.

 

I've never heard of that error before.

[MrSheep110]

Just now, Crunchy Dragon said:

Interesting.

 

I've never heard of that error before.

me to not till i got it, but my index still isn't working which is :(. Time to troubleshoot that. Looks already like a Video card thing. Possibly because its a R9-390 and not a RX480. 

Is IT at all possible that my CPU could be a bottle neck for the USB as its the controller for the USBs except the 3.10 which uses it own controller. I am running a Ryzen 7 1700x 

[Crunchy Dragon]

1 minute ago, MrSheep110 said:

me to not till i got it, but my index still isn't working which is :(. Time to troubleshoot that. Looks already like a Video card thing. Possibly because its a R9-390 and not a RX480. 

Is IT at all possible that my CPU could be a bottle neck for the USB as its the controller for the USBs except the 3.10 which uses it own controller. I am running a Ryzen 7 1700x 

You shouldn't have any bottlenecks there, even the R9 390 was marketed as a VR-ready GPU.

[MrSheep110]

2 minutes ago, Crunchy Dragon said:

You shouldn't have any bottlenecks there, even the R9 390 was marketed as a VR-ready GPU.

It is though about a year older in terms of architecture. and Indexes own minimums are the Rx480

[Crunchy Dragon]

Just now, MrSheep110 said:

It is though about a year older in terms of architecture. and Indexes own minimums are the Rx480

Interesting.

 

I wonder if that's due to something in drivers, the Polaris architecture, or performance.

[MrSheep110]

 

1 minute ago, Crunchy Dragon said:

Interesting.

 

I wonder if that's due to something in drivers, the Polaris architecture, or performance.

The Driver but less likely as they are both running the same radeon drivers. possibly architecture. and maybe performance but when Rx480 came out the benchmarks weren't much to be amazed about compared to R9-390 

[Crunchy Dragon]

Just now, MrSheep110 said:

The Driver but less likely as they are both running the same radeon drivers. possibly architecture. and maybe performance but when Rx480 came out the benchmarks weren't much to be amazed about compared to R9-390 

Architecture differences would be my second guess, after VR companies recommending the newest cards for a more or less seamless experience.

 

Assuming there's nothing in any documentation that specifically says Polaris architecture or better is needed.

[MrSheep110]

2 minutes ago, Crunchy Dragon said:

Architecture differences would be my second guess, after VR companies recommending the newest cards for a more or less seamless experience.

 

Assuming there's nothing in any documentation that specifically says Polaris architecture or better is needed.

Nope because if it was that simple then i would be so happy all it says is the minimum requirements are the rx490 https://store.steampowered.com/valveindex

[ToumeiSamurai]

For other people googling their issue like I am, I wanted to contribute that I also experience this issue with:

 

GPU: GTX 1080ti

CPU: Ryzen 7 2700X

RAM: 16GB

Mobo: GA-AB350N-Gaming WIFI

 

[ToumeiSamurai]

Bonus: Updating my motherboad chipset drivers seems to have solved the issue. If the issue occurs in the future, I will update this thread, otherwise, if you hear nothing from me, please assume this solved the issue for my case.