Humble Tech by Eeva ♡← Back to the blog
UPDATED FOR COMPTIA A+ CORE 1 • 220-1201

Hardware Troubleshooting Without the Overwhelm

See the symptom → choose the safest first check → follow the evidence.

Core 1 troubleshooting is scenario-driven. You are not trying to prove that your first guess was right—you are trying to choose the next reasonable test, verify what changed, and avoid making the problem worse.

28%Hardware & Network Troubleshooting domain
25%Hardware domain
53%Hardware + troubleshooting together
Important: This is an independent study article, not an official CompTIA publication. Exam objectives and wording can change, so always compare your study plan with CompTIA’s current 220-1201 objectives.

The troubleshooting mindset

CompTIA’s current Core 1 objectives still emphasize troubleshooting in real job scenarios. The familiar methodology is presented as useful competency knowledge even though the methodology itself is not a formal test objective. For a beginner, it is still an excellent way to keep your thinking organized:

1Identify the problem
2Form a probable cause
3Test the theory
4Plan + fix
5Verify function
6Document it

My memory hook: same symptoms, different causes. Evidence decides—not assumptions.

Core 1 hardware symptoms: what do I check first?

These are first suspects, not guaranteed diagnoses. A single symptom can have several causes, and beep/error codes can vary by manufacturer.

What you noticeReasonable first checkThen follow the evidence
PC has no powerCheck the power path first.Outlet/power strip → power cable → PSU switch → after unplugging, inspect the motherboard power connections. Do not open the PSU.
Fans/lights are on, but no displayRule out the display path, then RAM.Correct monitor input → video cable/port → reseat RAM → GPU/display hardware if present.
POST beeps at startupLook up the manufacturer’s beep pattern.RAM seating is a common early check, but the code is the evidence. Do not assume every beep means RAM.
Windows/BIOS loads, then the PC shuts downThink heat first.Check CPU-fan operation, cooler seating, blocked airflow, dust, and temperature. If the cooler was removed, verify thermal paste and proper reinstallation.
BIOS appears, but Windows will not loadFollow the storage/boot path.Is the drive detected? Check SATA data + SATA power on SATA drives, NVMe seating when applicable, boot order, and startup repair.
PC is sluggish or takes forever to startSeparate hardware slowness from software load.Check drive health/performance, free space, memory pressure, overheating/throttling, and excessive startup activity.
Grinding, clicking, or unusual noiseLocate the sound before replacing parts.Fan blade/cable contact and worn fan bearings are common. If a storage drive is clicking, protect data and escalate quickly.
Screen flickers, looks fuzzy, or colors are wrongCheck input source and physical video connection.Reseat/replace the cable, test another port/display, then consider GPU or monitor hardware.
Ethernet is connected but there is no internetCheck the network path.Link lights → adapter enabled → correct driver → IP configuration → cable/switch/router path.

Safety is part of troubleshooting

ADHD-friendly way to remember it

No power = follow powerDo not jump straight to the motherboard. Start outside the case and work inward.
No display = follow videoInput, cable, port, RAM, GPU. One change at a time.
Shuts down = think heatFan, cooler, airflow, thermal interface, temperature.
BIOS but no Windows = follow storageDetection, cable/drive, boot order, repair.
Don't Panic. Check This First. by Maryam Zishan

Want this in a keep-by-your-desk format?

Don’t Panic. Check This First. turns these ideas into visual troubleshooting conditions, cable recognition, safety reminders, and technician case logs for first-time troubleshooters.

Explore Maryam’s book →

Study source note

This article was updated against the current CompTIA A+ Core 1 (220-1201) structure available in 2026. CompTIA lists Hardware as 25% and Hardware & Network Troubleshooting as 28% of Core 1. The troubleshooting methodology remains recommended competency knowledge while scenario troubleshooting is emphasized in the exam objectives.

Check CompTIA’s official A+ certification page →