2 MIN READ · AUG 3, 2026
You press the button. Half a second later, a logo appears. In that gap, more happens than most people realize — here's the chain of events, start to finish.
The power button doesn't turn the computer on directly — it sends a signal to the motherboard's power circuitry, which checks that voltages are stable before releasing a signal called PWR_OK. Only once that signal is confirmed does the CPU actually wake up. This exists to stop your machine from booting into garbage if the power supply hasn't settled yet.
Every x86 CPU is wired to start execution at the exact same memory address the instant it's reset. That address doesn't point at your operating system — it points at the motherboard's firmware, stored on a small flash chip separate from your hard drive or SSD entirely.
This firmware — BIOS on older boards, UEFI on modern ones — runs the Power-On Self-Test, or POST. It's a quick internal audit:
If something fails here, you get beep codes or blinking lights instead of a screen — because the video output itself hasn't been confirmed working yet.
Once POST passes, firmware looks for a bootable device using an ordered list you can edit yourself in the BIOS/UEFI menu. It hands control to a small bootloader stored there — GRUB on most Linux systems, Windows Boot Manager on Windows — which is the last handoff before your actual operating system kernel loads.
From here, the kernel loads drivers, mounts your file system, and starts background services. This is the part that actually varies in length — it's also the part most people mistakenly think is "the whole boot process," when it's really just the last stage of one.
Comments