The Computer Hardware Picture Book
motherboard = the kitchen floor plan CPUthe chef RAMthe counter SSDthe pantry GPUthe specialist PSUthe gas line Fansventilation the chef works fast, but only on what's on the counter
PLATE 0 — Every part has one job. Speed comes from keeping the right data close to the chef.
A picture book for grown-ups · with commands

Computer Hardware, Part by Part

Nine spreads on what's inside a computer: CPU, memory, storage, motherboard, GPU, power, cooling, ports, and how to build and troubleshoot one.

Say it like a pro

"It's a 12-core CPU, 32 GB of dual-channel DDR5, a PCIe 4.0 NVMe SSD, and a 750 W gold PSU. The bottleneck is the GPU."

Commands for Linux and Windows show how to inspect your own machine. Use the tabs or the ← → keys.

Input Output CPU control ALU (math) Memory (RAM) The cycle that runs everything, billions of times a second 1 · FETCH the next instruction from memory 2 · DECODE what it means · 3 · EXECUTE it (math, move data, jump) 4 · STORE the result · repeat · all data is bits: 0s and 1s
PLATE 1 — Instructions and data live in memory. The CPU fetches, decodes and executes.
Chapter 1 · The big picture

Bits, bytes, and the parts list

UnitSizeThink of it as
bit0 or 1one switch
byte8 bitsone character
KB / MB / GB / TB×1,000 each (KiB… ×1,024)page / song / movie / library
Hz / GHzcycles per secondthe clock's tick rate
CPU
runs instructions
RAM
fast, temporary working memory (lost at power off)
storage
slower, permanent (SSD, HDD)
motherboard
connects everything and routes power and data
PSU / cooling
feed and de-heat it all
# see your machine's inventory
$ lscpu ; free -h ; lsblk ; lspci ; lsusb ; sudo dmidecode -t baseboard   # Linux
PS> Get-ComputerInfo | Select CsProcessors,CsTotalPhysicalMemory,BiosVersion   # Windows
PS> Get-CimInstance Win32_Processor, Win32_BaseBoard, Win32_PhysicalMemory
Say it like a pro

"Fetch, decode, execute. Everything else is about feeding the CPU faster."

CPU package Core 02 threadsL1+L2 Core 12 threadsL1+L2 Core 22 threadsL1+L2 Core 32 threadsL1+L2 L3 cache · shared memory controller PCIe lanes · iGPU Speed ≠ just GHz cores × threads × clock × instructions-per-cycle × cache
PLATE 2 — Several cores, each with private caches, sharing a bigger cache and the road to memory.
Chapter 2 · The CPU

The chef: cores, threads, cache

core
an independent processor; more cores help parallel work (video export, compiling, servers)
thread
a stream of instructions; SMT/Hyper-Threading runs two per core
clock
GHz; boost clock is the short-burst maximum
cache
tiny, ultra-fast memory on the chip: L1 (fastest, ~KB) → L3 (largest, ~MB)
TDP
rough heat to cool in watts
socket
physical + electrical fit: AM5, LGA1700… must match the motherboard
ISA
x86-64 (Intel/AMD) vs ARM (phones, Apple Silicon): different instruction sets
$ lscpu | grep -E 'Model name|^CPU\(s\)|Thread|Core|Socket|MHz|L[123]'
$ nproc ; watch -n1 "grep MHz /proc/cpuinfo | head -4"
$ sensors                       # temperatures (lm-sensors)
PS> (Get-CimInstance Win32_Processor | Select Name,NumberOfCores,NumberOfLogicalProcessors,MaxClockSpeed)
WorkloadCares about
gamingsingle-core speed + GPU
video, compile, VMsmany cores, more RAM
office, webalmost any modern CPU
Say it like a pro

"8 cores, 16 threads, 4.7 GHz boost, and a big L3. The workload is lightly threaded, so clocks matter most."

regs L1 · ~1 ns L2/L3 · ~5–15 ns RAM · ~80 ns SSD · ~100 µs HDD / network · ms faster, smaller, pricier ↑slower, bigger, cheaper ↓
PLATE 3 — The closer to the CPU, the faster and tinier. Computers hide this with caching.
Chapter 3 · Memory

The counter: RAM and cache

RAM holds what's running right now. When it fills, the OS pushes data to disk (swap / pagefile), and everything slows down. Adding RAM helps when you're running out, not otherwise.

SpecMeaning
DDR4 / DDR5generation; not interchangeable (different notch)
capacity8 GB basic · 16 GB comfortable · 32 GB+ pro work
speed (MT/s)3200–3600 (DDR4) · 4800–7200 (DDR5)
latency (CL)fewer clock cycles of delay = better
dual channeltwo matched sticks in the right slots ≈ double bandwidth
ECCdetects/corrects bit errors; servers and workstations
$ free -h ; vmstat 1 5              # used, cache, swap activity (si/so)
$ sudo dmidecode -t memory | grep -E 'Size|Speed|Type:|Locator'
$ sudo memtester 1G 1                  # basic RAM test (or run MemTest86 from USB)
PS> Get-CimInstance Win32_PhysicalMemory | Select Capacity,Speed,Manufacturer
Say it like a pro

"Two 16 GB sticks in dual channel, XMP/EXPO enabled in the BIOS so it runs at rated speed."

HDD ~150 MB/s · cheap · moving parts SATA SSD ~550 MB/s · no moving parts NVMe SSD 3,500–12,000 MB/s · via PCIe Choosing boot drive + apps → NVMe SSD (the biggest everyday speed-up) bulk archives, backups → large HDD (cheapest per TB) important data → RAID is not a backup; keep 3-2-1 copies flash wears with writes (TBW rating) · HDDs fail from age and shocks
PLATE 4 — Flash is thousands of times quicker than spinning disks for random access.
Chapter 4 · Storage

The pantry: SSD, HDD, and RAID

form factors
2.5″ and 3.5″ drives (SATA) · M.2 sticks (SATA or NVMe) · check the slot's keying and protocol
IOPS
small reads/writes per second; what makes a system feel snappy
RAID 0 / 1 / 5 / 6 / 10
stripe (fast, no safety) · mirror · parity (1 or 2 disks may fail) · mirror+stripe
filesystem
NTFS / ext4 / APFS / exFAT: how files are laid out on the drive
$ lsblk -o NAME,SIZE,TYPE,MODEL,ROTA,MOUNTPOINT      # ROTA 1 = spinning
$ sudo smartctl -a /dev/nvme0         # health: wear %, errors, temps (smartmontools)
$ sudo hdparm -t /dev/sda            # quick read speed
$ df -h ; sudo fio --name=t --rw=randread --bs=4k --size=1G --runtime=10 --filename=/tmp/f
PS> Get-PhysicalDisk | Select FriendlyName,MediaType,Size,HealthStatus
PS> Get-Disk ; Get-Volume
Say it like a pro

"NVMe for the OS and apps, an HDD mirror for bulk, SMART monitoring, and a real backup, since RAID doesn't protect against deletion."

rear I/O · USB · LAN · audio CPU socket+ VRM RAM slots 24-pin ATX power 8-pin CPU power PCIe x16 · graphics card PCIe x1 · cards M.2 NVMe Chipset SATA ports+ front panel BIOS/UEFI chip + CMOS battery
PLATE 5 — The motherboard decides what fits: CPU socket, RAM type, expansion, and connectors.
Chapter 5 · The motherboard

The floor plan and the highways

form factor
ATX (full) · micro-ATX · mini-ITX (small); the case must match
chipset
decides how many USB, SATA, M.2 and PCIe lanes you get, and overclocking support
PCIe
the expansion highway; lanes (x1–x16) × generation (3.0/4.0/5.0) set bandwidth
VRM
voltage regulators that turn 12 V into the CPU's ~1 V
BIOS / UEFI
firmware that starts the machine; set boot order, RAM profile, Secure Boot, virtualization
TPM
security chip for disk encryption and Windows 11
Compatibility checkMust match
CPU ↔ boardsocket + chipset (and BIOS version)
RAM ↔ boardDDR generation, max speed and capacity
board ↔ caseform factor, standoffs
GPU ↔ case/PSUlength, slots, power connectors
$ sudo dmidecode -t bios -t baseboard
$ sudo lspci -vv | grep -E 'LnkCap|LnkSta'      # PCIe link speed/width actually negotiated
PS> Get-CimInstance Win32_BIOS | Select Manufacturer,SMBIOSBIOSVersion,ReleaseDate
Say it like a pro

"AM5 socket, B650 chipset, DDR5, one PCIe 5.0 x16 slot, and two M.2 slots, so it fits the plan."

CPU · few, smart cores GPU · thousands of simple cores VRAM (GDDR6/7) · very wide bus Good at: the same math on lots of data 3D graphics · video encode · AI training/inference · simulations What to compare VRAM size (textures, models) · memory bandwidth · power draw (watts) integrated GPU (shares RAM, fine for office) vs discrete card needs the right PSU connectors and case clearance
PLATE 6 — A CPU is a few experts. A GPU is a stadium of workers doing the same task.
Chapter 6 · The GPU

The specialist: graphics and parallel math

A GPU renders images, but its parallel design also powers video editing, scientific computing and machine learning. For AI work, VRAM capacity usually decides what models you can run.

iGPU
built into the CPU; fine for desktop use and video playback
dGPU
separate card with its own VRAM and power; for games, 3D and AI
ray tracing / upscaling
lighting simulation / rendering fewer pixels then reconstructing (DLSS, FSR)
bottleneck
the slowest part limits the whole; balance CPU, GPU, and RAM
$ lspci | grep -iE 'vga|3d'
$ nvidia-smi                          # NVIDIA: temp, power, VRAM use, processes
$ nvidia-smi --query-gpu=name,memory.total,memory.used,temperature.gpu --format=csv
$ glxinfo -B ; radeontop                # Mesa / AMD
PS> Get-CimInstance Win32_VideoController | Select Name,AdapterRAM,DriverVersion
Say it like a pro

"24 GB of VRAM matters for the model size, and I'll check the PSU has the 12 V high-power connector."

Wall AC PSUAC → 12 V, 5 V, 3.3 V board · CPU · GPUdrives · fans intake exhaust cool air in front/bottom → hot air out back/top watts in = heat out Throttling too hot → the CPU/GPU slows itself to survive → low performance, not damage
PLATE 7 — Power comes in, heat goes out. Both need headroom.
Chapter 7 · Power & cooling

The gas line and the ventilation

wattage
add CPU + GPU peak power, plus ~100 W for the rest, then ×1.3 headroom
80 Plus
efficiency rating: Bronze · Gold · Platinum · Titanium (less wasted as heat)
rails & cables
24-pin motherboard · 4/8-pin CPU · PCIe 6/8-pin or 12VHPWR for GPUs · SATA/Molex
modular
detachable cables = tidier airflow
cooling
stock cooler · tower air cooler · AIO liquid (240/280/360 mm radiator)
thermal paste
a thin layer fills microscopic gaps between chip and cooler
UPS
battery backup that rides out outages and surges
$ sudo apt install lm-sensors && sudo sensors-detect && sensors
$ watch -n1 sensors
$ stress-ng --cpu 0 --timeout 120s && sensors        # load test, then check temps
PS> powercfg /batteryreport ; powercfg /energy      # laptop battery + power diagnostics
  • Target under ~80 °C CPU and ~85 °C GPU under sustained load.
  • Never run a hot PC in a closed cabinet; clean dust filters every few months.
  • Don't skimp on the PSU: a bad one can take other parts with it.
Say it like a pro

"A 750 W Gold PSU with headroom, front intake and rear exhaust, and temps hold at 70 °C under load."

USB-Creversible · data+power+video Thunderbolt 4/540–80 Gb/s docks USB-Akeyboards, drives (older) HDMI / DisplayPortvideo Ethernet RJ451–10 Gb/s wired Wi-Fi / Bluetoothwireless USB speeds, roughly USB 2.0 480 Mb/s · USB 3.0 5 Gb/s · 3.1 Gen 2 10 Gb/s USB 3.2 Gen 2×2 20 Gb/s · USB4 / Thunderbolt 40 Gb/s the port shape doesn't tell you the speed: check the spec, the cable, and the device Mb = megabits · MB = megabytes (÷ 8)
PLATE 8 — The same plug can carry very different speeds. Cable and port both matter.
Chapter 8 · Ports & peripherals

Connecting to the world

monitor
resolution (1080p/1440p/4K) · refresh rate (60–240 Hz) · panel (IPS, VA, OLED) · response time
keyboard / mouse
mechanical switches, DPI/polling rate, wired vs wireless
NIC
network interface (Ethernet/Wi-Fi) with a unique MAC address
sound
DAC/amp on the board or external; 3.5 mm, USB, optical
printer / scanner
usually USB or network; driver support matters
$ lsusb -t                         # USB tree with negotiated speeds (480M / 5000M / 10000M)
$ ip -br link ; ethtool eth0 | grep -E 'Speed|Duplex'
$ xrandr --verbose | head -30        # monitors, modes, refresh rate
$ bluetoothctl devices ; iw dev
PS> Get-PnpDevice -PresentOnly | Where Status -ne OK       # devices with problems
PS> Get-NetAdapter | Select Name,LinkSpeed,Status
Say it like a pro

"A Gen 2 USB-C cable only gives 10 Gb/s, so I need a Thunderbolt cable for the 40 Gb/s dock."

1 CPU 2 cooler 3 RAM 4 M.2 SSD 5 board do 1–4 on the board, outside the case, then: 6 PSU 7 GPU 8 cables+fans 9 BIOS + OS It won't turn on, in this order 1 · power: PSU switch, wall, 24-pin + 8-pin seated, front-panel pins 2 · display: monitor on the GPU's port (not the motherboard's) 3 · RAM: reseat, try one stick, try each slot 4 · CPU power and cooler contact · 5 · GPU power + reseat 6 · clear CMOS · update BIOS · read the debug LEDs / beep codes ground yourself · handle by the edges · no force: parts slot in gently
PLATE 9 — Build on a table, test before you close the case, and change one thing at a time.
Chapter 9 · Building & troubleshooting

Put it together, and find what's wrong

  1. Plan with a parts checker (PCPartPicker) for socket, RAM, size and power compatibility.
  2. Prepare: anti-static care, a clear table, the board's manual, and a magnetic screwdriver.
  3. Assemble CPU, cooler, RAM and SSD on the board first. Then install in the case, PSU, GPU and cables.
  4. First boot: enter BIOS, enable XMP/EXPO, check all RAM and drives are detected, then install the OS.
  5. Stress test and watch temps before you trust it.
$ sudo smartctl -H /dev/sda                    # drive health PASS/FAIL
$ sudo journalctl -k -p err --since today    # kernel hardware errors
$ dmesg -T | grep -iE 'error|fail|thermal|usb|nvme'
$ sudo badblocks -sv /dev/sdX                # surface scan (read-only default)
PS> mdsched.exe                                  # Windows Memory Diagnostic
PS> Get-WinEvent -FilterHashtable @{LogName='System';Level=1,2} -MaxEvents 20
PS> sfc /scannow ; chkdsk C: /scan
symptoms
random reboots → PSU or heat · blue screens → RAM or drivers · slow with disk at 100% → failing HDD · artifacts on screen → GPU or its cable
next steps
read your motherboard manual, build one, then learn BIOS tuning, RAID, and virtualization
Say it like a pro

"I narrowed it down by reseating RAM, testing one stick at a time, and checking the SMART data and temperatures."