7. Troubleshooting Common Problems¶
CompTIA's official troubleshooting method is six steps, in order, and it's worth memorizing exactly like this — it's as central to the A+ exam as it is to actually fixing things:
- Identify the problem. What exactly is happening? What changed recently?
- Establish a theory of probable cause. Start with the obvious/simple explanations before exotic ones.
- Test the theory. Confirm it before you start taking things apart.
- Establish a plan of action, then implement it.
- Verify full system functionality. Not just "it turned on" — does everything work?
- Document findings, actions, and outcomes. Future-you (or a classmate) will thank present-you.
Notice step 2 comes before step 4 — the biggest troubleshooting mistake is jumping straight to fixing something before confirming that's actually the problem.
Common symptoms and likely causes¶
| Symptom | Likely cause (check in this order) |
|---|---|
| No power at all, no fans | PSU switch off / unplugged, PSU dead, front-panel power cable loose |
| Fans spin, no display, no beep | GPU not seated, monitor cable in wrong port, RAM not seated |
| Fans spin, repeated beep code | Check the beep pattern against your motherboard's manual — usually RAM or GPU |
| Boots, but randomly shuts off | Overheating (check cooler is seated, case airflow) or an undersized PSU |
| Boots, but no boot device found | Storage drive not detected — check its cables, check boot order in BIOS/UEFI |
| Works, but is very slow | Check RAM is running at its rated speed, check storage isn't nearly full, check for overheating under load |
Try it
Pick one symptom from the table and, without actually breaking anything on purpose, write out all six troubleshooting steps for it as if it had happened to your build.
Tip
Step 1 almost always has an answer hiding in plain sight: "what changed right before this started happening?" Most problems trace back to the most recent change.