Not enough USB controller resources

Question

Split from this thread.

On a Surface Pro 2 running latest Microsoft USB 3.0 xHCI Host Controller driver (6.3.9600.13031, 2/21/2014) I'm seeing this USB controller resources error with three different USB hubs.  I'm running a mix of USB gamepads and USB Audio speakers, 500mA USB 1.0 and 1.1 devices respectively.

1. Using Plugable USB2-HUB-AG7 connected directly to Surface Pro 2

I get the error when I attach (4) gamepads and (3) speakers, but not when I attach (5) gamepads and (2) speakers.  I also get the error when I attach (0) gamepads and (4) speakers, but not when I attach  (0) gamepads and (3) speakers.

2. Using D-Link DUB-H7 connected directly to the Surface Pro 2

I get the error when I attach (4) gamepads and (3) speakers, but not when I attach (5) gamepads and (2) speakers.  I also found this 7-port hub presents itself as two chained 4-port hubs internally, and I am able to get (4) speakers attached to the hub if I put (3) of them on the ports associated with the parent hub.

When I daisy chain the USB2-HUB-AG7 off the DUB-H7, I can only get one USB speaker to run on the USB2-HUB-AG7 child hub.  Adding the 2nd speaker causes "Not enough USB controller resources".

3. Using Plugable USB3-HUB7A, the results were identical to the D-Link DUB-H7.  This 7-port hub also presents itself as two chained 4-port hubs. 

Seems to be a USB 2.0 resource limit with the xHCI or root hub driver.  Most PCs have separate USB2 ports with a more "mature" USB 2.0 controller.  Not the Surface Pro 2 which only exposes a port on the Intel USB 3.0 controller.

USB Enumeration on Surface Pro 2 with (4) external USB speakers on Plugable USB2-HUB-AG7

Controller DeviceCount: 11

Power:  USB2-HUB-AG7 self-powered

Problems:  No sound from speaker (1-1-4), Not enough USB controller resources.

1 USB Root Hub (xHCI) - Intel USB 3.0 xHCI (Microsoft)  6.3.9600.17031 2014-02-22

 1-1 Generic USB Hub (Plugable USB2-HUB-AG7)

  1-1-1 USB Composite Device - HID, Audio (500mA Logitech USB speakers)

  1-1-2 USB Composite Device - Audio, HID (500mA Logitech USB speakers)

  1-1-3 USB Composite Device - HID, Audio (500mA Logitech USB speakers)

  1-1-4 USB Composite Device - HID, Audio (500mA Logitech USB speakers)

 1-2 USB Composite Device - Marvell AVASTAR (WiFi/Bluetooth)

 1-3 USB Composite Device - HID, HID, HID  (touch cover, keyboard, mouse, pen, sensors, buttons)

 1-4 USB Composite Device - HID, HID (touch screen)

 1-5 USB Composite Device - Image (front camera)

 1-6 USB Composite Device - Image (rear camera)

NOTE:  Devices 1-2 thru 1-6 are built in to the Surface Pro 2.   Device 1-1 is connected to the external USB port.

Answer 1

I read on the pluggable website that there is a problem with the Microsoft USB 3.0 eXtensible host controller driver. they said that the Intel windows 7 driver will work and they take you through the process of changing over. That will not work with the surface because half way through the process USB is disabled and you have no way to finish the process. I wonder if Microsoft is looking at this for Surface 3. Maybe if they recognize this and fix the driver for Surface 3 we will get the fix also.

Is anyone from Microsoft involved in this community?

Answer 2

I have a Surface Pro 2 with 51`2gb, use the Surface Dock and a Samsung touch external display (certified for Windows 8). I am running Windows 8.1. If I have the touch line from the monitor plugged in (USB) AND have headphones plugged into the Dock, I receive the error message and the touch function does not work. I have communicated with Microsoft numerous times and always get the same response: "reset ;you Surface to the factory install". This is my third device (the first had a defective USB port and the second bricked in the middle of doing routine writing in Word). The same problem has occurred with all three devices.

I also have a Surface Pro with 128gb and the problem never occurs.

Has anyone had success with getting Microsoft to look at this problem with USB resources? I haven't and have been trying for almost 6 months.

Answer 3

Hello,

This is Josh at Plugable Technologies. We've been working with Microsoft behind the scenes and rest assured they are aware an issue exists. That being said, when and if we will see a solution is hard to say. We don't have any direct involvement in driver development, but we've been reporting our findings to Microsoft and hopefully they will be able to analyze the data and come up with a solution.

We're involved mainly because our primary product line is comprised of USB docking stations and hubs and we have run into this issue. (It also helps that we're basically next door neighbors as we're both located in Bellevue, WA).

At first we suspected it might have been an issue with the firmware on our hub chipsets but after many different test cases we have narrowed this down to what we believe is a driver issue. This issue does not appear to happen on Windows 7 but can eventually be reproduced on the same computer with Windows 8 equipped with an Intel USB 3.0 controller. You just need enough USB devices to make it happen.

My main workstation is a 128GB Surface Pro 2 and I too have run into this issue many times. I have to be very selective about what devices I have attached. I believe the reason us Surface users see the issue is because almost every device in the Surface Pro 2 is attached through USB. I've also had this issue happen on an older Sony Vaio but far less frequently (less built in USB devices).

1. Bluetooth
2. WiFi
3. Audio
4. Touch sensor
5. Gyro sensor
6. Ambient light sensor
7. Micro SD reader
8. Front webcam
9. Rear webcam

I'm sure I'm forgetting some other possibilities...

I currently have the following connected to my Surface:

• Plugable UD-3900 universal docking station
• Plugable USB3-HUB4AC1 4 port USB 3.0 hub
• Plugable PSS-SDH1 hard drive dock with integrated 4 port USB 3.0 hub
• Two flash drives, keyboard, mouse
• USB 2.0 external touch screen DisplayLink monitor

By my count here is the total number of actual devices (including hub chipsets) attached:

1. DisplayLink DL-3900 chipset - integrated dual video outputs, gigabit Ethernet, & audio controller (UD-3900 dock)
2. VIA 811+ 4 port USB 3.0 hub (UD-3900 dock)
3. Terminus 4 port USB 2.0 hub (UD-3900 dock)
4. VIA 812 B2 USB 3.0 hub (USB3-HUB4AC1 hub)
5. VIA 812 USB 3.0 hub (PSS-SDH1 dock/hub combo)
6. ASMedia ASM1051e SATA to USB (PSS-SDH1 dock/hub combo)
7. Sandisk Extreme 16GB USB 3.0 flash drive
8. Plugable USB2-OTGTF Micro SD card reader
9. Keyboard
10. Mouse
11. DisplayLink DL-125 chipset (for the additional touch screen display)
12. Touch screen HID device (for the additional touch screen display)

Excluding hub chipsets, I only have 8 devices attached externally. If I try to attach just one more device, I get the resources error. It doesn't seem to matter if I attach a USB 2.0 or 3.0 device. It appears to be a total device limit.

I'm not sure what we've learned here, this is just a lunchtime ramble.

Answer 4

Thank you for your reply. It helps to know it is not a one off problem. Iwish MS would just admit these problems instead of stonewalling. I don't think any reasonable person expects a flawless product, but at least this type of information helps with figuring out workarounds.

Answer 5

Do you know if the surface 3 will have the same problem?