1
Diagnostic step 1
Reproduce the issue with verbose logging: enable Windows Event Viewer logs for graphics driver (WDDM) and collect timestamps; reproduce and save the event sequence for vendor escalation.
FULL AI ANALYSIS
External USB‑C/Thunderbolt dock causes external 4K60 monitor to flicker and re-detect during GPU‑heavy workloads on Windows laptop
Generated Oct 3, 2026, 12:35:03 AM
Analysis summary
Symptoms point to a re-enumeration of the display path caused by a display driver reset or by the dock re-negotiating DisplayPort link when the discrete GPU becomes active. The fact that direct connection is stable implicates the dock/its firmware or the dock‑to‑GPU handover path (USB‑C alt‑mode / DP MST). Optimus systems that switch or power the dGPU differently under load can trigger transient link changes through the dock. Driver timeouts or dock USB power negotiation glitches under increased bandwidth/power draw are common triggers.
Possible causes
Dock firmware or USB‑C cable failing to sustain stable DP alt‑mode link under high pixel clock / bandwidth load.
80%DP MST chain instability in dock hardware triggered by high bandwidth or EDID re-negotiation.
75%Graphics driver bug or TDR (Timeout Detection and Recovery) when discrete GPU ramps up, causing a brief driver reset that re-enumerates displays.
70%Power negotiation with dock fails briefly when dGPU draws more power, causing the dock to reset internal hub or MST chains.
40%Suggested fixes
2
Diagnostic step 2
Test with a different, known-good dock and cable and with direct connection to isolate whether the dock hardware or the laptop GPU/driver triggers the problem (you already tested direct connection; repeat with another dock model if available).
3
Diagnostic step 3
Temporarily set the discrete GPU to 'Prefer maximum performance' in the GPU control panel to test whether reducing GPU power state transitions prevents the re-enumeration (reversible change).
4
Diagnostic step 4
Disable USB selective suspend and power-saving options for the USB and Thunderbolt controllers in Windows power settings and Device Manager (reversible) to rule out power management-induced resets.
5
Diagnostic step 5
If logs show driver TDRs, reduce the likelihood by updating/reinstalling the graphics driver and raising the TdrDelay in registry only as a diagnostic (not recommended as long-term fix). Collect a minidump of the crash if produced and escalate to the GPU vendor and dock vendor with captured logs and steps to reproduce. If the dock is at fault, request firmware-level debug from the dock vendor; if the driver is at fault, escalate to GPU vendor with the exact Event Viewer records and any minidumps. Avoid leaving power management disabled indefinitely—use these steps to confirm root cause and then implement a targeted fix.