When one monitor is blank, isolate the signal path before changing drivers
Use a controlled cable-and-port swap to distinguish monitor input, cable, adapter and host problems when only one display has a picture.
Read guideTroubleshooting
Use controlled comparisons to locate a fault. Separate an individually working screen from a failing combination, trace missing modes and signal loss, and record enough evidence to make the next troubleshooting step meaningful.
8 practical guides
A display that works alone but fails with a second screen suggests a shared limit
Investigate combined display counts, dock bandwidth and power dependencies when two individually working monitors cannot operate together.
Read guide
Recover a window that opens on a disconnected screen
Bring an off-screen application back into view using system window controls, then repair the saved layout so the problem does not recur after every disconnect.
Read guide
Intermittent blackouts need a controlled test at a lower signal demand
Investigate brief signal loss by separating cable movement, link bandwidth, power and wake behavior, rather than changing several display settings together.
Read guide
Blurry text on one application may be a scaling issue rather than a bad monitor
Compare desktop-wide softness with application-specific blur, inspect native resolution and mixed scaling, and avoid sharpening controls that merely add halos.
Read guide
Unexpected audio after connecting a monitor is often an output-selection change
Check HDMI and DisplayPort audio destinations, monitor speakers and meeting-app settings when sound moves or disappears after a display connection.
Read guide
A monitor missing after sleep needs a repeatable wake test
Document sleep and wake behavior with one screen and two, check dock and direct connections, and distinguish a wake failure from unsupported display modes.
Read guide
A missing refresh option can be a connection limit rather than a settings bug
Trace an unavailable display mode through the source, dock, adapter, cable and monitor input, and compare documented combinations before forcing custom timings.
Read guide