Question "Not enough USB controller resources" after plugging in USB DAC

[Vauff]

I recently purchased the FiiO E10K and immediately began having USB controller issues after starting to use it. My keyboard would have movement keys get stuck while playing games and Windows would keep greeting me with this message.

I read into this issue and discovered that USB 3.0 controllers had a limited number of endpoints available. Unfortunately my motherboard only has 3.0 ports available, so I resolved into buying a USB expansion card. Unfortunately after setting it up and plugging my DAC into it, I am still receiving the same controller resource message from Windows. I don't understand how this could be since the card should be running its own USB controller (and only the DAC is on it), with my other 3 USB peripherals on my motherboard USB. The issue also does not occur when I only have those other 3 USB peripherals plugged in to my motherboard.

Full involved components list:

• Gigabyte Z390-UD
• SupaHub PCI-E USB 3.0 Expansion Card
• FiiO E10K
• Blue Yeti Nano
• Zowie EC1-B
• Ducky Shine 7

 

[hang-the-9]

Did you check for a newer BIOS, chipset and USB drivers from the motherboard vendor? Run Windows update? If you remove the Yeti but keep the DAC in does it run normally?

 

[Vauff]

Apologies for the delay in responding, I've been trying different combinations of things over the past week. I found that installing the FiiO E10K drivers resolved the USB controller overload issue. But as reported here, I get random blue screens and the audio going to static when using them. Meaning that I'm currently stuck between having USB controller overload or random BSOD/static audio.

I ran updates for everything you listed and am still experiencing the USB controller issue, and yes the issue does still happen with my Yeti unplugged. It even happens with only my mouse and DAC plugged in. I do not get the warning if the DAC is removed though.

 

[hang-the-9]

Test this DAC on another system see if it does the same thing there or not.

 

[Vauff]

Turns out that this was caused by the DAC being registered by the default Windows drivers as both a playback and recording device. After I disabled the recording device this issue went away.

 

[ZvFarina]

Turns out that this was caused by the DAC being registered by the default Windows drivers as both a playback and recording device. After I disabled the recording device this issue went away.

Are you serious? I've been trying to figure this out for so long. Gonna see if it works when I get home.