ReadIt — Fundamentals
Comprehensive GuideQuick read · 4 min

What Happens When You Power On a Computer?

When you press the power button on your computer, a sequence of complex low-level checks and loads triggers behind the scenes. This hardware-to-software handoff process is known as booting.

Booting is the multi-stage initialization process that prepares a computer for use when powered on. It checks whether physical components are functioning correctly, runs the motherboard's built-in firmware, locates the bootloader program, and copies the operating system kernel into system memory (RAM).

What Happens First After Pressing the Power Button?

The moment you press the power button, a hardwired electrical signal routes straight to the computer's Power Supply Unit (PSU). The PSU regulates voltage and distributes electricity across the motherboard components.

Once power stabilizes:

  • Electricity is supplied: Current energizes the motherboard, graphics card, and storage drives.
  • Motherboard becomes active: The system clock oscillator begins pulsing its synchronization heartbeat.
  • CPU starts execution: The processor is released from its reset state and immediately runs firmware code stored on the motherboard.

What Is BIOS or UEFI?

Because RAM is completely empty at startup, the CPU cannot run operating system software directly. Instead, it routes to a tiny read-only ROM chip on the motherboard containing the system's firmware: the BIOS (Basic Input/Output System) or modern UEFI (Unified Extensible Firmware Interface).

UEFI and BIOS act as low-level bridges responsible for checking hardware states, initializing chipsets, and identifying storage drives. Modern computers use UEFI because it supports faster boots, large drive architectures, and advanced security (Secure Boot).


What Is POST?

Before launching any software, the motherboard must ensure that its critical physical organs are alive and healthy. It executes the Power-On Self-Test (POST) routine:

  • Hardware check: The firmware polls the CPU, reads registers, checks RAM stability, verifies graphics hardware, and detects connected drives.
  • Diagnostic codes: If a key component (like RAM) is damaged or missing, the system will halts boot, displaying an error screen or sounding unique motherboard beep codes.

Basic Boot Process Flow

The low-level booting timeline behaves like a sequential pipeline passing execution down the stack:

Linear Boot Sequence Pipeline
1. Power On
Electricity flows from PSU to motherboard; CPU starts up.
2. BIOS / UEFI Init
Firmware loads from motherboard ROM to initialize buses.
3. POST Check
Self-test routine verifies CPU, RAM, and GPU functionality.
4. Bootloader
Firmware finds drive, loading Windows Boot Manager or GRUB.
5. OS Kernel
OS files are copied into fast RAM; desktop UI starts.

What Is the Bootloader?

Once the POST finishes successfully, the UEFI/BIOS searches the configured boot drive for a tiny, specialized script called the Bootloader. Because the full operating system is too large to fit in basic firmware, the bootloader's only job is to locate the primary OS files and pull them into memory.

Common examples include:

  • Windows Boot Manager: Used in Microsoft systems.
  • GRUB (Grand Unified Bootloader): Used widely across Linux systems.

How Is the Operating System Loaded?

Once active, the bootloader reads the drive partition tables, copies the core Operating System Kernel from persistent storage (SSD) into temporary workspace memory (RAM), and hands absolute control over to it.

As the OS takes control, the final boot stages trigger:

  • Services start: Core system processes, networking stacks, and user accounts load.
  • Drivers initialize: Low-level hardware handlers start, waking up hardware components.
  • UI becomes active: The graphical login panel and desktop workspace render.

What Are Device Drivers?

A Device Driver is a translator program that allows the operating system to communicate with physical hardware. Since the OS doesn't inherently know how to interact with every keyboard, microphone, or graphics chip, drivers provide standard programming interfaces. These start up during the loading stage to guarantee immediate hardware functionality.


Why Is RAM Important During Booting?

During the entire boot process, RAM acts as the critical high-speed launching pad. Reading instructions directly from SSDs or HDDs during CPU execution cycles would cause massive bottlenecks. Copying the kernel, system services, and drivers into volatile RAM allows the processor to access operational commands at nanosecond speeds, enabling high system responsiveness.


What Happens If Booting Fails?

Because the boot sequence is a strict linear chain, a single break will halt the entire process. Boot failures commonly stem from:

  • Corrupted OS files: Broken system updates or malware damage the kernel.
  • Faulty RAM: Memory blocks fail POST parity checks.
  • Damaged storage: Corrupted sectors make the drive unreadable.
  • Missing bootloader: The firmware cannot find where the boot files reside, displaying the classic "No Bootable Device Found" error.

Why Is the Boot Process Important?

The boot process is essential because it guarantees that the CPU never operates in a corrupted, unpredictable state. By checking physical circuits, clearing RAM workspace, and loading authorized driver and OS layers sequentially, booting ensures a stable computing workspace.


Summary

  • The computer startup sequence is called booting.
  • BIOS or UEFI firmware stored on motherboard ROM starts first to manage low-level buses.
  • POST (Power-On Self-Test) checks physical CPU, memory, and graphics health at startup.
  • The Bootloader (GRUB/Windows Boot Manager) acts as the handoff bridge to find the OS on disk.
  • Operating system core files are copied from storage into fast volatile RAM workspace.
  • Device Drivers load during startup to allow system-to-hardware communications.