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.
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:
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 notice | Reasonable first check | Then follow the evidence |
|---|---|---|
| PC has no power | Check 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 display | Rule out the display path, then RAM. | Correct monitor input → video cable/port → reseat RAM → GPU/display hardware if present. |
| POST beeps at startup | Look 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 down | Think 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 load | Follow 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 start | Separate hardware slowness from software load. | Check drive health/performance, free space, memory pressure, overheating/throttling, and excessive startup activity. |
| Grinding, clicking, or unusual noise | Locate 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 wrong | Check 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 internet | Check the network path. | Link lights → adapter enabled → correct driver → IP configuration → cable/switch/router path. |
Safety is part of troubleshooting
- Power down and unplug before reseating internal components.
- Use ESD precautions and handle RAM/CPUs by the edges.
- Never open a power supply. Dangerous voltage can remain inside even after unplugging.
- If you smell burning, see smoke, or find a swollen battery, stop using the device and follow proper service/disposal guidance.
- Do not probe mains electricity unless you are trained and using properly rated equipment.
ADHD-friendly way to remember it

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.