I have a recurring problem with my Mind 2s in combination with the Mind Graphics 4060TI 16GB. After some time (usually a few minutes after startup), the USB connection and the Ethernet port of the Mind Graphics sporadically disconnect.
The following error message then appears in the Device Manager:
Unknown USB device (Error resetting the port.)
As a result, the mouse, keyboard, and Ethernet no longer work – only a restart brings them back. The problem then reappears at some point.
I have already tried updating the USB driver and graphics driver, but unfortunately without success.
The following entry appears in the Windows Event Viewer:
DeviceInstanceId: USB\VID_0000&PID_0001\5&1f8e66e1&0&13
DriverName: usb.inf
ClassGuid: {36fc9e60-c465-11cf-8056-444553540000}
DriverDate: 06/21/2006
DriverVersion: 10.0.26100.3912
DriverProvider: Microsoft
DriverInbox: true
DriverSection: BADDEVICE.Dev.NT
DriverRank: 0xff0000
MatchingDeviceId: USB\RESET_FAILURE
OutrankedDrivers: usb.inf:USB\RESET_FAILURE:00FF2000
DeviceUpdated: false
Status: 0x0
ParentDeviceInstanceId: USB\ROOT_HUB30\4&2eddd907&0&0
DriverPackageId: usb.inf_amd64_5a2240bed0005a37
Has anyone else experienced similar issues with the Mind 2s or the external GPU?
Or perhaps you have an idea how to resolve this (e.g., via BIOS, power saving options, or alternative drivers)?
we will provide you with a link later today. It contains a software tool for accessing your Hub’s firmware. Please install it and retrieve the firmware version. Based on your report, it appears the issue may be related to the firmware version.
We appreciate your cooperation.
Hello, I’m having a similar issue with Mind 2s and mind graphics. The videocard and finger reader works, but the ethernet, usb and the unlock button don’t work. Thank you
I have a Mind 1 with a Mind Graphics (v1) dock, and everything inside the dock enumerates on a USB 2.0 root port instead of a SuperSpeed one. Ethernet tops out at 302 Mbps, on a dock specified at 2.5 Gbps.
The internet line is not the limit. A phone on 5 GHz Wi-Fi through the same router gets 540 Mbps down. The Ethernet link negotiates 1 Gbps with zero packet errors and 0-1 ms to the router, and going from one download stream to eight moved throughput only from 293.6 to 302.7 Mbps. That flat ceiling sits right at the practical maximum of USB 2.0.
Windows reports the Ethernet controller (RTL8156, VID_0BDA&PID_8156) at this location path:
HS02 is a High-Speed (USB 2.0) root port. The card reader, the dock audio and the dock USB ports all sit behind the same two chained hubs on HS02. A webcam plugged into the Mind’s own port shows up on SS02 and works normally, so the host controller and its SuperSpeed lanes are fine. Only the path into the dock is affected.
I have already re-seated the Mind in the dock, done a full restart so Fast Startup is bypassed, disabled USB selective suspend on all hubs, and confirmed that BIOS 1.1 and EC 1.02 are the newest published versions for Mind 1. None of it changed the enumeration.
Before that restart I also had repeated dropouts on dock devices, including an Unknown USB Device (Set Address Failed) node that persisted until reboot, which looks like the same family of problem as USB and Ethernet disconnections with Mind 2s & Mind Graphics.
So: is the dock supposed to enumerate at SuperSpeed, and does HS02 indicate a fault? Is the hub firmware tool mentioned in that thread available yet? And if anyone else has a Mind Graphics, I would like to know whether yours reports HS or SS, so I can tell whether this is my unit or the design.
That USB\RESET_FAILURE error on an eGPU dock like the Mind Graphics is super frustrating. It usually happens when the Thunderbolt/USB controller drops its handshake due to power management states or PCIe power-saving features tripping up under load.
A couple of things to check: go into your Windows Device Manager, find the USB Root Hubs / eGPU controller properties under Power Management, and uncheck ‘Allow the computer to turn off this device to save power.’ Also, check your BIOS for any aggressive C-states or USB selective suspend settings that might be killing the port connection shortly after boot.
Troubleshooting hardware bottlenecks and data flow like that is all about tracing where the connection drops—much like how organizing logic pathways or decoding personal insights on a destiny matrix chart relies on keeping data streams clear and structured. Hope disabling those power-saving flags stops the disconnects