What this symptom means
This symptom concerns the display path. Start with a neutral DeviceOK test where available so the next step is based on evidence rather than a generic reset sequence.
Fault tree
Display fault tree
Use the observation that best matches what you can reproduce. Do not treat every cause as equally likely.
Evidence: The display works but resolution/refresh is lower than expected.
Next: Check the OS active mode, GPU output, cable/port capability and monitor input mode.
Evidence: Direct connection works but the dock/adapter path does not.
Next: Identify the weakest link by testing direct and then adding one component at a time.
Evidence: Pixel/line/uniformity defect stays in the same physical location across inputs and test patterns.
Next: Document with controlled patterns and compare warranty pixel policy/service guidance.
Evidence: The symptom appears in screenshots/recordings or changes with GPU settings.
Next: Check graphics driver, color mode, scaling and output format.
Interpret the result
Evidence matrix
A test result is useful only if it changes the next troubleshooting branch.
Fast baseline
Rule out the simple causes first
- 1
Run DeviceOK Screen Resolution Test and note the screen/viewport values.
- 2
Open the OS display settings and choose the resolution marked Recommended where appropriate.
- 3
Check display scaling separately from resolution.
Full sequence
Work from reversible checks to invasive ones
Avoid destructive resets, unofficial driver packages, firmware flashing, or replacing hardware before the simpler detection, permission, connection and configuration checks are exhausted.
- 1
If the OS offers the expected native/recommended resolution, select it and retest text/sharpness.
- 2
If the expected mode is missing, inspect cable/adapter/dock capability, display identification and the official graphics/display driver path.
- 3
For external displays, verify the selected monitor and refresh rate in Advanced display settings.
Platform branches
Where the setting lives
Windows
- Settings → System → Display → Advanced display
- Check GPU control-panel output mode only after confirming Windows active mode
- Test one monitor directly before MST/dock chains
macOS
- System Settings → Displays
- Hold Option/advanced controls only when needed to expose supported modes
- Identify the exact Mac display-count limits before buying a dock
Hardware path
- Connector shape does not prove bandwidth/video capability
- Verify cable specification and input mode
- Remove KVM/splitter/dock during baseline testing
A correct OS/native mode with persistent blur shifts attention toward scaling, app rendering, cable/display processing or panel characteristics.
A missing expected mode requires connection/display/GPU capability troubleshooting rather than a browser fix.
Escalation threshold
When software troubleshooting has stopped being high value
- Same panel defect across multiple inputs/sources
- Display loses sync with multiple known-good cables
- Burning smell, swelling or power instability
- Physical crack/liquid damage
- Do not open monitors or power supplies unless qualified; capacitors can retain hazardous voltage.
Related diagnoses