Your PC powers on but shows no display, or the time resets to 2000 every morning, and you need to know exactly what the motherboard is doing in the first few seconds. This page walks you through the BIOS initialization sequence step by step, so you can spot where it is failing and why.
In short: BIOS initialization is the firmware routine that runs before the operating system loads. It verifies the CPU, trains the RAM, detects connected hardware, and reads your saved settings from CMOS. If any step fails, the system stops and often signals the problem through beep codes or a stuck screen.
Quick picks
Our shortlist for this job · tap one to see today's price
Replaces the dead CR2032 battery that causes CMOS settings to reset after every shutdown.
Gives you a quick USB media to test whether the problem is the drive or the firmware.
What you need to track the BIOS initialization sequence
Watching the firmware boot sequence requires basic desktop access and the ability to pause for a failed step. You do not need a multimeter, but you do need the right tools at hand when something breaks. We cover shutdown sequence explained in a guide of its own.
- A spare CR2032 coin cell battery for the CMOS, in case the date and time reset.
- A USB flash drive with a recovery tool, for isolating boot device failures.
- A working internal speaker or headphones, to hear POST beep codes.
- A notepad, to write down the exact sequence of lights, beeps, or on-screen errors you see.
The battery is the part most people are missing when they start troubleshooting. A dead CMOS battery resets your BIOS settings and clock, making every other step look like it failed when it was just the settings that vanished.
Pro tip: Before you open the case, take a photo of the current battery orientation and the board's state. It saves you guessing when you reinstall it.
A dead CMOS battery is the most common root cause of settings resetting after shutdown, and this is the exact part you replace to fix it.
- Works with Apple AirTag, all major car key fobs (Toyota, Honda, BMW, Ford, Chevrolet
- BITTER TASTE ON BOTH SIDES TO HELP KEEP CHILDREN SAFE—Duracell CR2032 features a bitter
Step 1: Power-On Self-Test (POST) and the first hardware check
When you press the power button, the power supply sends a signal to the motherboard and the firmware executes its first code. This is the POST phase, and it is a hardware check, not a software one.
The POST routine verifies that the CPU is alive, the system clock is stable, and the RAM controller can train the memory modules. If the RAM sticks are mismatched or a module is failing, this is usually where the sequence halts.
The motherboard also performs a quick check of the keyboard controller and interrupt lines. If the POST fails, the board communicates the error through the internal speaker. Beep codes vary by manufacturer, so you will need to look up the specific sequence for your board’s firmware maker.
- Confirm the system power LED is on.
- Listen for one long beep (often memory) or continuous short beeps (often power or fan).
- Note any display output, such as a stuck logo or a black screen.
Safety first: If you hear beeps immediately after pressing the power button, shut the system down right away. Continuing to power a board that is stuck in POST can sometimes stress the RAM or CPU further. We go through bios uefi initialization step by step in its own article.
Step 2: Hardware enumeration and device initialization order
Once the POST passes, the BIOS expands to detect every piece of hardware on the motherboard. It walks the PCI Express bus, finds the graphics card, and initializes the storage controllers for your drives.
During this phase, the firmware builds the interrupt vector table. This is a critical data structure that maps hardware interrupts to their handlers. Without it, your keyboard and mouse would not be able to talk to the CPU.
The initialization order is fixed and predictable. Understanding this sequence helps you figure out which component failed when the system stops.
- CPU and system bus
- Memory controller and RAM
- Primary PCIe graphics card
- Storage controllers (SATA, NVMe)
- USB and legacy I/O controllers
- Integrated peripherals (audio, network)
Step 3: Loading settings from CMOS or NVRAM
After hardware is detected, the firmware reads your saved configuration from the CMOS chip. This data holds your boot order, overclocking parameters, and power management features.
The CMOS battery keeps this data alive when the system is off. If the battery is weak or dead, your settings reset to factory defaults every time you power down. This is the most common reason your PC thinks the date is 2000 or 1970.
The BIOS also checks a stored checksum against the current configuration. If it fails, you will see a “CMOS Checksum Error” prompt, and you will be forced into the setup menu to reconfigure your settings. For the detail, see our notes on a look at code execution inside the cpu.
Step 4: Boot device selection and the OS handoff
With settings loaded, the firmware looks at your boot device order. This tells the system which drive to check first for an operating system.
On legacy systems, the BIOS reads the Master Boot Record from the first drive. On modern UEFI systems, it looks for the EFI System Partition on your primary SSD or NVMe drive. Once it finds the bootloader, it hands control over to the operating system.
This is the final step of BIOS initialization. On a healthy modern system, the entire sequence takes less than two seconds before you see the Windows or Linux logo.
Common mistakes when troubleshooting BIOS initialization
Most owners get the sequence wrong or make a fix that doesn’t address the root cause. Here are the mistakes to avoid.
- Reseating RAM before checking POST. If the system is not passing POST, reseating the RAM won’t help if the CPU or system clock is the problem. Let the POST finish its check first.
- Ignoring the beep codes. Beep codes are the first diagnostic tool the firmware gives you. Do not skip them and jump straight to swapping parts.
- Replacing the CMOS battery without a backup. If your board is in a laptop or a small form factor, replacing the battery without noting the current settings means you lose your configuration and have to start over.
- Blaming the boot drive when the firmware is stuck. If the system halts before the boot device selection step, the problem is in an earlier phase, not the drive.
Pro tip: Write down the exact step where the system halts. If you stop it at the hardware detection phase, you have your answer: the problem is in enumeration, not in the boot drive.
The bottom line
Most people who are struggling with a time reset or a settings wipe just need a new CMOS battery. If you are trying to track down a stuck system, isolate the failure to the exact phase using the sequence above, and replace only the part that step points to. Start with the battery, then work forward.
- Works with Apple AirTag, all major car key fobs (Toyota, Honda, BMW, Ford, Chevrolet
- BITTER TASTE ON BOTH SIDES TO HELP KEEP CHILDREN SAFE—Duracell CR2032 features a bitter
Frequently asked questions
Why does my computer's date and time reset to 2000 every time I turn it on?
Your CMOS battery is dead or weak. It keeps the BIOS settings and the clock alive when the system is off. Replace the CR2032 coin cell battery on the motherboard, and the time and settings will hold.
What does a continuous series of short beeps mean during POST?
It usually points to a power supply problem or a loose connection. Check that all power cables are seated and the PSU is providing stable power before you look at the RAM or the CPU.
Can I skip the BIOS initialization sequence with Fast Boot enabled?
Fast Boot skips some of the later phases to get you to the operating system faster, but it does not skip POST or the hardware check. It can also make it harder to access the firmware setup menu if you need to change a setting.
What is the difference between BIOS and UEFI initialization?
Legacy BIOS runs 16-bit code and initializes hardware sequentially. UEFI runs 64-bit code and initializes hardware in parallel, which makes boot times much faster. UEFI also supports Secure Boot and TPM integration.