JCN9801
1 Copper

Windows 10 post-FU 1903 issue: Not enough controller resources for this device

Jump to solution

XPS-8930 w/ 16GB and 8700 CPU.

Okay back in Dec 2018 I had 42 hard drives connected directly to front ports and to rear ports via 3 x Anker USB 13-port hubs.  No issues.  This year I had my system occupied for 77 consecutive days doing video re-encodings.  Slow (only 16GB DRAM) by the end but it continued to run.  I had the above error with USB 2 thumb drives but worked around them with USB 3 hard drives instead.  I had one drive, 8TB USB 3.0, connected late that showed 18 MBps (~USB 2) speeds.

Then WINDOWS decided it could no longer defer the FU 1903 thing and rebooted in the middle of my work (last week).

So after some fiddling with drive letters (again), I now have my main cohort of 24+ hard drives (5, 6, 8 and 10TB, Seagate and WD with a couple of HGST).  All USB 3.0 on short cables.

Now I come to attach a single Seagate Slim USB 3.0 portable (2TB) to a front USB 3.1 Gen 1 port and get the above error.  And, in checking in devmgmt, I find two other drives showed the same issue.  When I checked drivers associated with the external hard drives they all report back:  MS 6/21/2006 10.0.18362.1 including the two large externals (4TB and 8TB) reporting problems as below (*).  But both appear to work.

Since I use both drive letters and NTFS mount points for most of the same drives does this double the resource hit?  In any case why the change from Dec 2018 and FU 1803 operation?

I checked out the Windows Club suggestions.  Not much there that applies.

I did notice a MS driver update, 6/19/2019, for the Intel USB 3.0 eXtensible Host Controller, version 10.0.18362.207....  Could this be the culprit?  Naturally being "migrated" with 1903 there is NO ROLL BACK POSSIBLE for this driver.   Nothing more current appears to be available.  My system is not Win Pro so re-imaging backwards to 1803 will just put me in forced feature update **bleep** once again (in mere days I suspect).

(*) In the Other Devices / Unknown list I have:

Windows has stopped this device because it has reported problems (Code 43):

Port_#0001.Hub_#0042

Port_#0002.Hub_#0042

Port_#0004.Hub_#0042

Port_#0019.Hub_#0001

If I wanted a PC that could only connect, say, 14 hard drives (yeah, I have one of those) I would have purchased another LAPTOP!

This is why I despise those 2x per year FU!

Can somebody get MS to look into this, or offer a workaround?

Thanks,

---JCN

0 Kudos
1 Solution

Accepted Solutions
Tesla1856
6 Thallium

Re: Windows 10 post-FU 1903 issue: Not enough controller resources for this device

Jump to solution

Sounds like you might be expanding the USB chain beyond it’s abilities.

When you get tired of playing around ...

I suggest you purchase a real NAS (like Synology) or build a DIY RAID machine.


Registered Microsoft Partner and Apple Developer
- Like many of you, I can appreciate a good game-engine.
- I answer questions here, but I'm not a Dell employee.
- Consider giving posts you like a "thumbs-up"
- Posting models-numbers and software versions speeds trouble-shooting.
- Click "Accept as Solution" button on any post that answers your question best.
2 Replies
Tesla1856
6 Thallium

Re: Windows 10 post-FU 1903 issue: Not enough controller resources for this device

Jump to solution

Sounds like you might be expanding the USB chain beyond it’s abilities.

When you get tired of playing around ...

I suggest you purchase a real NAS (like Synology) or build a DIY RAID machine.


Registered Microsoft Partner and Apple Developer
- Like many of you, I can appreciate a good game-engine.
- I answer questions here, but I'm not a Dell employee.
- Consider giving posts you like a "thumbs-up"
- Posting models-numbers and software versions speeds trouble-shooting.
- Click "Accept as Solution" button on any post that answers your question best.
JCN9801
1 Copper

Re: Windows 10 post-FU 1903 issue: Not enough controller resources for this device

Jump to solution

Thank you for the insults!

I will look elsewhere.

JCN

0 Kudos