BIOS/UEFI Firmware drivers
Low-level updates for system stability and new hardware support.
You might also need
BIOS/UEFI Firmware drivers we cover
What does a bios/uefi firmware driver do?
BIOS, now almost universally implemented as UEFI, is the first code the processor executes at power-on. It is stored on a small SPI-connected flash chip, typically 16 or 32 megabytes, and it is responsible for turning an inert board into a platform an operating system can load. Everything Windows later takes for granted, working memory, an enumerated PCIe tree, a bootable disk, has already been arranged by firmware before the Windows loader runs.
Memory training is the heaviest early task. The firmware reads the SPD chip on each DIMM, applies the timing and voltage the modules request, and runs a training routine that tunes signal delays until the memory bus is stable. On systems using XMP or EXPO overclock profiles the firmware applies those aggressive timings and retrains; a marginal profile is why a machine sometimes takes a long, dark pause on first boot or fails to POST until settings relax.
Why keeping it updated matters
A UEFI update is the only way to change behaviour that happens before Windows exists, and it fixes a distinct class of problems. New CPU microcode ships inside firmware, so support for a processor released after the board, and mitigations for silicon errata, arrive as a BIOS revision rather than a Windows patch. On AMD boards especially, an AGESA update inside a new BIOS routinely improves memory compatibility and fixes fTPM stutter that no OS-level change could touch.
Stability and compatibility fixes are common. Revisions correct memory training that failed with certain DIMM kits, repair PCIe link training that dropped a fast NVMe drive to a slower gear, and adjust ACPI tables so sleep and wake behave. Where a board shipped early in a platform's life, later firmware often transforms how many memory kits will run their rated XMP or EXPO profile.
Common warning signs of bios/uefi firmware driver failure
- The machine sits on a black screen after a memory or CPU change and only POSTs once XMP/EXPO is disabled
- A newly released CPU is not recognised until firmware carrying its microcode is installed
- BitLocker demands its recovery key after a UEFI setting such as Secure Boot or CSM was toggled
- A fast NVMe drive trains at a slower PCIe generation until a firmware revision corrects link training
- Windows 11 setup reports the PC does not meet requirements because Secure Boot or fTPM is off in UEFI
- The system will not enter deep sleep, or wakes immediately, because the ACPI tables are stale
How to fix bios/uefi firmware driver problems
Confirm the current firmware version
Enter the UEFI menu at boot or run msinfo32 in Windows and read the BIOS Version/Date line. Compare it to the versions listed for your exact model so you know whether an update is even the right move before touching the flash chip.
Flash with the vendor's own tool
Place the model-specific image on a FAT32 USB drive and use the in-UEFI updater, or run the vendor's Windows flashing app. Let it complete untouched; the board will reboot itself one or more times as it writes and verifies the SPI flash.
Reapply and verify settings
After the flash, re-enter UEFI, load optimised defaults, then reapply your XMP/EXPO profile, boot order, Secure Boot, and fTPM settings. Reconfirm the memory posts and trains, and check the NVMe drive reports its rated PCIe generation.
Recover a failed flash
If the board will not POST after a flash, use BIOS FlashBack or the dual-BIOS switch if the board has one, supplying the correct image on USB with no need for CPU or memory. This is why an enthusiast board's flash button exists, and it is the intended recovery path.
Helpful guides
Should You Use Driver Updater Software?
Driver updater tools promise one-click fixes but add risk. Here's what they really do, when they cause problems, and the safe way to check drivers yourself.
DCH vs Legacy Drivers in Windows 10/11
DCH drivers split hardware support from control-panel apps in Windows 10/11. Why the change happened and how to tell which type you have.
How to identify unknown devices with hardware IDs
A practical walkthrough for naming every mystery entry in Device Manager using hardware IDs, driver details, and Windows' built-in tools.
Frequently asked questions
Why does my PC only POST after I disable the XMP or EXPO memory profile in UEFI?
XMP and EXPO apply aggressive DDR timings the firmware must train against. On a marginal kit or early firmware, training fails and the board either sits dark or falls back to defaults. A newer BIOS with updated memory code often makes the profile stable; until then, a slightly relaxed profile lets the board POST reliably.
Why doesn't my motherboard recognise a newer CPU until I update the BIOS?
CPU microcode and the initialisation code for a processor generation live inside the firmware. A board that shipped before a CPU launched has no code to bring it up, so it will not POST with that chip. Flashing the BIOS revision listed as adding support installs the microcode the processor needs to initialise.
Why is BitLocker asking for my recovery key after I changed a UEFI setting?
BitLocker seals its key to firmware measurements stored in the TPM. Toggling Secure Boot, enabling CSM, or clearing fTPM changes those measurements, so the seal no longer matches and BitLocker demands the recovery key. Enter the key, then suspend and resume BitLocker so it re-seals to the new state.