No-Display Troubleshooting Checklist When a user reports “no display,” which initial question best helps determine whether the display subsystem is functioning at a basic level?

Difficulty: Easy

Correct Answer: All of the above

Explanation:


Introduction / Context:
“No display” can originate from the monitor, GPU, cable, power, or POST failure. Smart triage questions quickly isolate whether the system is powering, posting, and driving the screen. This item asks which checks are useful as a first pass.


Given Data / Assumptions:

  • A conventional desktop or laptop with a separate or integrated display.
  • Technician can query user/observe system immediately after power-on.
  • Standard POST beep codes and monitor HV behavior are relevant.


Concept / Approach:

All three prompts provide complementary evidence. A visible cursor or on-screen activity shows the GPU/monitor path is working. A POST beep or chime indicates the system has initialized core hardware. Feeling/hearing high-voltage static on CRTs (or power/LED and backlight activity on LCDs) indicates the monitor powers up. Together, they rapidly narrow the fault domain.


Step-by-Step Solution:

Ask about any on-screen text, cursor, or backlight glow.Confirm POST beeps/chimes and other signs (keyboard LEDs flash).Check monitor power: indicator LED, relay click, or HV static (for CRTs).If absent, test with a known-good cable/monitor and reseat the GPU/RAM.


Verification / Alternative check:

Connect an external display, use onboard graphics, or run with minimal hardware. Each check corroborates the initial triage.


Why Other Options Are Wrong:

Each single question alone may miss failures; all together provide broader coverage. Thus, the combined option “All of the above” is best.


Common Pitfalls:

Ignoring beep codes, overlooking loose cables, or forgetting to test with a different monitor input (HDMI/DP selection).


Final Answer:

All of the above

Discussion & Comments

No comments yet. Be the first to comment!
Join Discussion