Bios / Uefi Driver
Initialises hardware before the operating system loads.
What Is It?
Boot firmware (Bios / Uefi) is the low-level software that initialises hardware before the operating system loads. It runs the moment the system is powered on, checking memory, processor, storage and graphics components, and preparing them for use. Without it, no operating system could ever start.
Modern systems use Uefi — the successor to the legacy 16-bit Bios standard. Uefi offers a richer interface, faster boot, secure-boot verification, support for partitions over 2 TB, and a network stack that can fetch firmware updates directly from the manufacturer.
It also exposes user-configurable settings such as boot order, power profiles, virtualisation toggles, fan curves, memory timing profiles and the platform trust module. Adjusting these is normally done via a setup screen reached by pressing a key — usually Delete, F2 or F12 — during the first seconds after power-on.
Although users rarely interact with it directly, Boot firmware quality affects boot speed, hardware compatibility and platform security. Manufacturers publish updates to support new processors, fix stability issues and patch security advisories.
How It Works
When power is applied, the firmware checks each major component, configures memory and CPU features, and selects a boot device. It then loads the bootloader and provides a minimal interface used until the system's own drivers are ready.
Key Functions
- Runs power-on self-test (POST) to verify each major component before boot.
- Selects the boot device and hands control to the bootloader.
- Verifies signed bootloaders via Secure Boot to block unauthorised code.
- Exposes user-configurable hardware settings — boot order, fan curves, memory profiles.
Components & Examples
| Component | Role |
|---|---|
| POST | Hardware self-checks |
| Boot manager | Selects bootloader |
| Secure Boot | Trust verification |
Why It Matters
Firmware quality affects boot speed, hardware compatibility and platform security. A reliable, up-to-date Boot firmware ensures new processors are recognised, peripherals enumerate cleanly and modern security features such as Secure Boot are available.
Common Issues & Symptoms
Recognising the symptom is the first step in narrowing down whether the problem really is the firmware, the hardware or another part of the system.
| Symptom | Likely Cause |
|---|---|
| New CPU not recognised after fitting | Firmware microcode predates the chip. |
| System won’t boot after firmware change | Settings reset; boot order or secure boot incorrect. |
| Fans run at full speed | Fan curve table missing in current firmware. |
| Slow boot after firmware update | Fast Boot or legacy-compatibility settings reset to defaults. |
Best Practices
A short checklist to keep firmware healthy and reduce the chance of running into the issues above.
- Plug the system into mains power before flashing — power loss mid-update can brick the board.
- Read the change-log; flash only when a fix or feature is genuinely needed.
- Note your current firmware settings (memory profile, fan curves, boot order) before updating.
- Use the manufacturer’s official tool, not third-party flashers.
- After flashing, re-enable virtualisation, the platform trust module and secure boot if you rely on them.
Frequently Asked Questions
The older option is a legacy 16-bit firmware standard, while the modern replacement offers a richer interface, faster boot, secure boot, modern partition support and drive sizes beyond 2 TB. Most systems since 2012 use the newer standard.
Modern flashing tools are robust, but there is always a small risk if power is lost mid-update. Only flash when you have a clear reason — a fix, new CPU support, or a security advisory.
Sometimes — many vendors lock newer microcode releases. Check the manufacturer page; if downgrade is supported, the change-log will mention it explicitly.