USB‑C dock stops enumerating devices after laptop lid close (S3) following vendor firmware update

Environment

Dell XPS 13 9310, Windows 11 22H2, connected to Thunderbolt 4 dock (vendor firmware v1.2.4 installed last week) via a certified USB‑C cable. Dock supplies power, two external monitors via DisplayPort MST, and multiple USB devices (keyboard, external NVMe enclosure).

Symptoms

When the laptop lid is closed to suspend (S3) and later reopened, the dock remains powered but peripheral devices (keyboard, NVMe enclosure) no longer show up in Device Manager and monitors remain black. Replugging USB-C cable occasionally forces device re-enumeration and restores functionality, but a simple sleep/wake can lead to persistent non-enumeration requiring host reboot or cable reinsert.

Observations

Windows Event Viewer logs Kernel-PnP warnings around the suspend/resume timestamps indicating 'A device doesn't have enough resources' and multiple VID/PID enumeration retries. Thunderbolt controller shows devices as connected in Thunderbolt Control Center but drivers report error code 31 or device not migrated. Rolling back to earlier dock firmware not yet attempted. Disabling USB selective suspend and enabling 'Allow the computer to turn off this device to save power' settings had inconsistent effects. Reproduced issue reliably after firmware update; before update the dock did not exhibit the problem.

Already attempted

Updated host BIOS and Windows drivers to latest versions. Disabled USB selective suspend and set power options to prevent USB power off. Reinstalled Thunderbolt and USB drivers. Swapped USB‑C cable for another certified cable and tried alternate USB-C port on laptop; issue persisted. Tested with another laptop (same model) and same firmware: reproduction rate lower but occasional failures occurred. Rolled back display drivers with no effect.

Question

What diagnostic steps can isolate whether the problem is dock firmware regression, host Thunderbolt driver interaction, or Windows power-management behavior? Is it safe to roll firmware back on the dock, and what reversible tests should be performed before escalating to vendor support?

Post timeline

COMMUNITY RESPONSES

Verified community troubleshooting

0 replies

No answers yet..

Showing 0 of 0 community responses

AI DIAGNOSTICS

Incident analysis

Updated 1w ago• Trouble ID

Most likely causes

Dock firmware regressed and fails to properly enumerate or re-negotiate Thunderbolt/USB-C alternate modes after host enters/exits S3. 90%

Host Thunderbolt driver or Windows power management interactions changed (driver/Windows update) causing devices not to be reattached after sleep. 60%

Thunderbolt security policy or device authorization issue preventing re-attestation after resume (some docks require re-authorizing). 30%

Summary

The timing (started after dock firmware update) strongly implicates a firmware regression in the dock's handling of USB/Thunderbolt re-enumeration after host S3 sleep. Event log kernel messages about resource allocation and device migration suggest the host detects devices but cannot allocate required resources or driver stack fails to rebind. Reproducing on another host with same dock firmware increases likelihood of dock-side issue, but host Thunderbolt driver and BIOS interplay can also matter. Reversible diagnostics and controlled rollbacks are the safest path before formal escalation.

Suggested Fixes

Diagnostic step 1

Reproduce the failure while collecting Windows kernel logs (use Windows Performance Recorder / Windows Event Tracing for Windows) and capture USB/Thunderbolt device enumeration traces to correlate timestamps with resume.

Diagnostic step 2

Temporarily roll back the dock firmware to the previous known-good version (if vendor provides rollback and instructions) on one unit to confirm regression; do not perform firmware changes on production-critical units without a recovery plan.

Diagnostic step 3

Test with a different certified USB‑C/Thunderbolt cable and an alternate Thunderbolt-capable host to see if reproduction is host- or dock-specific.