7. OS Troubleshooting¶
Same six-step method as every other troubleshooting lesson in this course: identify → theorize → test → plan and implement → verify → document.
Common OS symptoms¶
| Symptom | Likely cause (check in this order) |
|---|---|
| Won't boot at all, no activity | Power/hardware first (see the PC Building Lab) before suspecting the OS |
| Boots, but hangs before reaching a login screen | Could just still be mid-boot — don't assume failure too early |
| Crashes or freezes randomly | Overheating, failing hardware, or a specific misbehaving driver/program |
| Runs very slowly | Too many startup programs, a resource-hungry process, or a nearly-full drive |
| "No network" right after boot | Networking services may not have finished starting yet |
A real example from this very course¶
Earlier in this course, pve1 appeared completely dead on the network after being physically relocated — no ping, no response at all, despite the switch showing a live link. The theory tested first was a hardware failure. It turned out to be far simpler: the machine just hadn't finished booting and bringing up its network stack yet. Waiting, rather than assuming the worst, resolved it completely.
That's this lesson's entire point in miniature: a slow or silent system isn't automatically a broken one.
Try it
Using the six steps, write out how you'd troubleshoot "a computer is running very slowly," the way you would for a classmate who asked you in person.
Tip
Check Task Manager's (Windows) or top's (Linux) resource usage before assuming a slow computer needs a reinstall — a single runaway process is a five-minute fix; a reinstall is not.
Play it
Open the Operating Systems Lab and use the Troubleshooting tab.