BIOS Boot Process Explained

Flowchart of the BIOS/UEFI boot process showing power sequence, reset vector with SPI flash read (CLK/MOSI/MISO/CS#), hardware init, security checks, UEFI ESP vs legacy MBR branch, boot manager, and ExitBootServices()

BIOS Boot Process Explained

When you press the power button, a carefully staged BIOS/UEFI sequence brings the platform to life. This guide explains the full boot pipeline—from power sequencing and POST to security checks and OS handoff—so you can diagnose no‑POST, boot loops, and black‑screen cases with confidence. For the complete reference hub, see the BIOS Guide.

1) Power Sequence & Reset Vector

The embedded controller (EC) and power rails start the platform. When the CPU exits reset, it fetches the first instruction from a fixed reset vector that maps into the SPI flash address space (the BIOS chip). If that code region is unreadable, you’ll typically see a black screen with no POST.

Background articles: How SPI Flash Works, What Is a BIOS Chip?.

2) POST: Power‑On Self‑Test

The firmware validates and brings up critical blocks:

  • CPU & microcode
  • Memory training (topology, timings, stability)
  • Chipset/PCH configuration and clocks
  • GPU (iGPU/dGPU) init and graphics output
  • USB & storage controllers
  • Embedded controller (EC) sync

If POST fails, you may observe no‑beep, code LEDs, or a reboot loop. Helpful reads: Common BIOS Chip Failure Symptoms, No POST, No Beep Fix.

3) Firmware Phases & Hardware Initialization

UEFI organizes work into clear phases (SEC → PEI → DXE → BDS). In early phases, memory is trained and the system state is described to later phases; in DXE, most drivers load, peripherals enumerate, and boot services/runtime services are created. For a deeper architectural view, see BIOS Firmware Architecture.

4) UEFI Security Checks

Modern platforms enforce trust before handing control to an OS loader:

  • Secure Boot signature validation
  • TPM/fTPM measurements
  • OEM policies (e.g., Boot Guard)

If policy or signatures don’t match, the system intentionally blocks boot. Learn more in Secure Boot Firmware Architecture and Intel Boot Guard Explained.

5) Boot Device Selection & OS Handoff

After devices are ready, firmware consults NVRAM boot entries and the boot order. In legacy BIOS this means loading an MBR sector; in UEFI it loads an EFI application (e.g., Windows Boot Manager) from the ESP. When the loader is ready, it calls ExitBootServices(), ending firmware boot services and handing control to the OS.

Compare models: BIOS vs UEFI and UEFI vs Legacy BIOS.

6) Troubleshooting Map

  • Black screen, no POST → suspect BIOS region corruption, unreadable SPI flash, or early power rail issues.
  • Stuck at logo / keyboard unresponsive → likely DXE driver or device init fault.
  • Boot loop after update → bad image, interrupted flashing, or security policy mismatch; see Laptop Not Booting After BIOS Update.

Further Reading

Shop BIOS Chips

Browse all BIOS chips

Back to the Hub

Return to the BIOS Guide

0 comments

Leave a comment