Hardware Essentials
What can fail before Windows even starts
Open interactive version (quiz + challenge)Real-world analogy
A computer is like a restaurant kitchen: CPU is the chef, RAM is the counter space, storage is the walk-in fridge, and the motherboard is the layout connecting everyone. If the fridge dies you lose ingredients; if the counter is tiny everything slows; if the chef overheats, service stops.
What is it?
Hardware essentials are the physical layer of every IT issue. A strong junior can look at a symptom and quickly narrow it to CPU, memory, storage, power, thermals, or peripherals — then choose a safe next test.
Real-world relevance
In a bank branch, a teller’s machine keeps freezing at noon. A junior who just reboots it will get another ticket tomorrow. A junior who checks Event Viewer, disk SMART, temperatures, and memory logs finds a failing SSD and prevents mid-transaction corruption.
Key points
- CPU, RAM, and storage — what each really does — CPU executes instructions, RAM holds active data the CPU is working on, and storage (HDD/SSD/NVMe) keeps data when power is off. Performance problems almost always trace back to one of these three being saturated or failing.
- How to map a symptom to likely component — Random restarts → power/thermals/RAM. Long boot + load spikes on simple tasks → storage. App crashes that spread across many apps → RAM or OS corruption. Frozen mouse + slow everything → CPU or thermal throttling.
- HDD vs SSD vs NVMe — HDD: spinning disks, cheap per GB, slow, mechanical failure risk. SSD: flash, fast, silent, no moving parts. NVMe: flash over PCIe, much faster than SATA SSD. For corporate laptops, NVMe is now the default; HDD is mostly archival.
- POST — the first self-check — When you press power, firmware runs POST (Power-On Self-Test) before any OS loads. If POST fails, you may hear beeps or see codes. No POST means the problem is below the operating system — hardware or firmware.
- Overheating + thermal throttling — Dust, dead fans, dried thermal paste, or blocked vents → CPU slows itself to protect against damage. You feel it as sudden sluggishness. Cleaning + paste replacement is often a junior-level win.
- Safe troubleshooting sequence — Document the symptom, confirm reproducibility, swap one variable at a time, test with a known-good component if possible, check logs, and only then open the case. Never yank hardware before capturing evidence.
- Printers fail more than any other peripheral — Support teams spend huge time on printing. The failure is almost always one of: driver, spooler, network path, queue, permission, paper/toner/jam. Treat printers like mini-networks: many layers, check each.
Code example
// Safe hardware triage script (pseudocode for your brain)
1. Ask: what exactly changes when it fails? (reboot? freeze? blue screen? slow?)
2. Ask: is it one machine or many? (multi-machine often means software/network)
3. Check thermals: dust, fans, case temperature, throttling events.
4. Check storage: SMART, disk errors in Event Viewer, free space, slow reads.
5. Check memory: Windows Memory Diagnostic, recent BSOD dump codes.
6. Check power: battery health, charger watt rating, unstable mains.
7. Swap ONE variable at a time (RAM stick, charger, cable).
8. Document every step in the ticket; keep evidence.
9. Escalate to hardware repair with clear notes if not resolved.Line-by-line walkthrough
- 1. Triage pseudocode for hardware issues
- 2. Step 1 — describe the failure precisely
- 3. Step 2 — scope: single or many machines
- 4. Step 3 — thermals check
- 5. Step 4 — storage health check
- 6. Step 5 — memory check
- 7. Step 6 — power stability check
- 8. Step 7 — isolate by changing ONE variable
- 9. Step 8 — document every step
- 10. Step 9 — escalate with evidence if unresolved
Spot the bug
Ticket: ‘PC is slow, I reinstalled Windows twice. Still slow. Please fix.’Need a hint?
Reinstalling Windows did not help. Which layer is likely the real culprit?
Show answer
OS reinstall rules out software rot. Next suspects are hardware: check disk SMART (likely failing SSD/HDD), RAM diagnostic, thermals/throttling, and dust. Document symptoms with timestamps and Event Viewer entries, then escalate as hardware if confirmed.
Explain like I'm 5
Your computer is a tiny kitchen. CPU is the cook, RAM is the counter, disk is the fridge. If the cook overheats, food slows. If the counter is small, nothing fits. If the fridge breaks, food disappears overnight. That’s basically every hardware ticket.
Fun fact
Many ‘software problems’ in corporate fleets turn out to be failing SSDs. A dying drive can produce ghostly symptoms — slow Outlook, crashing browsers, ‘random’ blue screens — that look exactly like malware or a bad update.
Hands-on challenge
Open Event Viewer (Windows) or ‘Console’ (macOS) on your own machine. Find the most recent critical or error entry. Read it aloud. Explain what you believe happened in plain English.
More resources
- Windows Event Viewer overview (Microsoft Learn)
- How PCs boot (POST to OS) (Professor Messer)
- SMART disk health explained (Wikipedia)