CompTIA 220-1201 PC Power, Boot, Storage and Display Issues Guide

Study CompTIA 220-1201 PC Power, Boot, Storage and Display Issues: key concepts, common traps, and exam decision cues.

This lesson covers the support symptoms that make up a large share of Core 1 troubleshooting questions. The exam wants you to classify whether the failure is power, startup, storage, or display related before you start replacing parts.

POST: Power-on self-test, the early hardware check that happens before the normal boot path continues.

Boot order: The firmware sequence that decides which device the system tries to start from first.

What CompTIA is really testing

CompTIA usually wants you to:

  • distinguish no power from no boot from no display
  • recognize storage-detection and startup clues
  • know which simple checks should happen before deep repair

Fast symptom map

Symptom Strong first direction
no lights, no fans power source, cable, PSU, battery, outlet
powers on but will not boot boot order, storage detection, firmware, startup path
drive missing cable, seating, firmware detection, interface support
black screen but system seems active display cable, input source, backlight, GPU or display path

Classify the failure boundary first

Failure type What it usually means
no power the system is not starting the electrical path at all
powers on, no POST startup fails very early, often around board, CPU, RAM, or firmware clues
POST succeeds, no boot storage or boot-path issue after hardware initialization
boots, no visible image display path or graphics issue rather than total startup failure

What this lesson keeps separate

Close-looking symptoms Keep this distinction clear
no power vs no boot electrical start failure is different from startup failure
no boot vs no display system startup is different from video output
missing drive vs corrupt OS hardware detection is different from later software damage
black screen after GPU change vs general system failure display path is different from total platform failure

Evidence beats guessing

Support questions often reward the candidate who notices the exact failure boundary:

  • no power is lower than no boot
  • no display does not always mean the system failed to start
  • missing storage may be compatibility, cable, or firmware configuration

Practical first checks

1Power symptom -> verify source, cable, battery, PSU path
2Startup symptom -> note lights, fan behavior, beeps, or firmware messages
3Storage symptom -> verify detection before formatting or reinstalling
4Display symptom -> verify monitor input, cable path, and known-good display path

Common traps

  • treating a black screen as proof that the system never started
  • reinstalling the OS before confirming the drive is detected
  • skipping seating or power checks after recent hardware changes
  • confusing no power with no boot just because both stop the user quickly

Harder scenario question

A desktop powers on, fans spin, and the keyboard lights flash, but the screen stays black after a new graphics card install. Which answer best fits Core 1?

  • A. Reinstall the operating system immediately
  • B. Check monitor input, display cabling, GPU seating, and required power connectors first
  • C. Disable DHCP and renew the IP lease
  • D. Replace the printer toner

Correct answer: B. The symptom still sits in the display and expansion lane. Core 1 wants the least intrusive check that matches the recent hardware change before any OS-level repair.

What strong answers usually do

  • start with power path and physical checks
  • separate startup from video-only issues
  • verify detection before reinstalling or replacing unrelated parts
  • use the symptom boundary to eliminate overdramatic fixes

Decision order that usually wins

  1. Classify the symptom as no power, early startup failure, no boot, missing storage, or display-only failure.
  2. Use visible evidence such as lights, fan spin, beeps, and firmware detection before replacing parts.
  3. Follow the most recent hardware change if one exists.
  4. Verify the drive or display path before reinstalling the OS.
  5. Escalate only after the symptom boundary stops pointing to a simpler lane.

Quiz

Loading quiz…
Revised on Sunday, May 10, 2026