Fix BIOS problems by following a four-step order: verify power and display, load defaults, check boot mode and drive detection, and update firmware only for vendor-listed fixes or recovery. Random resets and unnecessary flashes can break boot, erase settings, trigger BitLocker recovery, or turn a working board into a no-start system. This guide maps startup, boot, reset, password, drive-detection, and update failures to the safest fix order, with clear stop points for laptops, desktops, and recovery-only cases.

Many current PCs start through UEFI firmware, yet setup screens, manuals, support pages, and everyday usage still call it BIOS. The name matters less than the failure pattern. A black screen before the logo, a hang at the startup logo, missing boot options, checksum errors, time resets, and failed flashes do not all belong to the same fix path.

What counts as a BIOS problem?

A BIOS problem usually appears before Windows loads: POST failures, a freeze at the maker logo, storage missing from setup, checksum or CMOS warnings, settings that will not stay saved, or a bad firmware update. Many of those symptoms also come from RAM, GPU, storage, cable, or power faults, so sorting the symptom comes first.

Firmware symptoms that usually fit

Firmware trouble usually appears early. Common signs include a system stuck at the startup logo, hardware not detected in setup, missing boot devices, a BIOS checksum error, repeated date and time resets, a failed BIOS flash, or a BIOS password lock.

Checksum and CMOS errors matter because they point to settings retention trouble rather than a Windows issue. BIOS checksum error is a known startup symptom, and CMOS battery failure is also a known startup symptom. A weak coin-cell battery can erase saved settings between shutdowns and push the system back to defaults.

Look-alikes that are often not firmware

No display is the biggest trap. If the monitor is on the wrong input, the cable is bad, the GPU power lead is loose, or memory fails training, the PC can look dead long before firmware becomes the likely cause.

Boot-device errors also split two ways. If the drive is visible in firmware but Windows still does not load, that usually points to a storage or OS bootloader problem, not a BIOS fault. If the drive does not appear in firmware at all, power, data cable, slot seating, or drive failure moves higher on the list.

Suppose a desktop shows fans and keyboard lights but no logo after a RAM overclock. Many users read that as “bad BIOS.” More often, it is unstable memory training. Loading defaults or clearing CMOS may help, but the root cause is the memory setting, not a damaged firmware image.

How do you get into BIOS or UEFI?

Use the startup key during POST if the system still shows a splash screen, or open firmware settings through Windows Advanced Startup if Windows still boots. On most computers, the BIOS entry key is F2, though Delete and Esc are also common and vary by manufacturer.

Startup keys during POST

Tap the setup key during the first startup screen, right after pressing the power button and before the spinning Windows dots or logo handoff appears. Common choices are F2, Delete, and Esc. On many laptops and prebuilt desktops, F2 is standard; on many desktop motherboards, Delete is common; some systems use Esc to open a startup menu that then leads to setup.

From Windows recovery and Advanced startup

Windows can hand control to firmware setup without guessing the key. Shift+Restart opens the Advanced Boot Menu in Windows 11. The longer path is Settings > System > Recovery > Advanced startup, then restart into recovery.

Inside recovery, Windows can open firmware settings through Troubleshoot > Advanced Options > UEFI Firmware Settings. That is the cleanest route on modern systems that boot normally but need setup changes.

Windows Terminal can boot to recovery with shutdown /r /o /f /t 00. Use that only when Windows is stable enough to accept the command. If BitLocker is active, have the recovery key available before making firmware changes.

When Surface Pro Touch Stops Working in BIOS or UEFI

If a Surface Pro touchscreen works in Windows but stops responding in BIOS or UEFI, the issue is usually narrower than a full display failure. This article explains how to tell whether the problem is firmware-related, a digitizer or cable issue, or a touch break that only shows up outside Windows. It also covers non-touch ways to reach firmware settings and what that means for recovery when you cannot tap through the usual menus.

That distinction matters because it changes the fix: you may need a firmware reset, an update path, or hardware service instead of repeated restarts. For step-by-step guidance, see Surface Pro touch issues.

Bios problems matrix

Symptom Likely cause Safest first fix Escalation step Stop-sign warning
Stuck at startup logo Bad boot order, unstable overclock, USB device hang, memory training issue, corrupted settings Remove new USB devices, disconnect new hardware, load setup defaults Clear CMOS only if setup cannot be entered or defaults do not hold If repeated no-POST starts after reset, stop and check RAM, CPU seating, and board damage
Missing boot options Drive not detected, wrong boot mode, CSM or Secure Boot mismatch, failed storage device Check whether the drive appears in firmware and confirm boot order Reseat storage cables or NVMe drive, then review vendor notes for mode changes Do not flash BIOS just because Windows will not boot if the drive is already detected
Time and date reset on every shutdown Weak CMOS battery or settings not being retained Replace the coin-cell battery and load defaults again Use a CLR_CMOS reset if checksum errors persist after battery replacement If a laptop uses an internal battery pack or sealed board, follow the vendor service method instead of forcing disassembly
Failed BIOS flash Wrong file, interrupted update, model mismatch, bad USB format, power loss Do not reboot repeatedly; check for vendor recovery steps or dual-BIOS support Use the board's documented recovery feature if it has one The wrong BIOS file can brick the motherboard; if no recovery method exists, stop and seek board-level service or replacement
No display before POST Wrong monitor input, bad cable, GPU output issue, loose power, bad RAM, firmware settings after GPU swap Verify display path, monitor input, cable, and RAM seating before touching firmware Try integrated graphics or a different output, then clear CMOS if a display-setting change caused the issue Do not assume a black screen means BIOS corruption; many cases are video path or memory faults
BIOS password lock Supervisor or setup password set in firmware Use documented owner recovery options and proof-of-ownership service channels Contact the system or board maker for model-specific unlock procedure Do not rely on random internet bypass codes, especially on laptops; many modern systems cannot be safely reset that way

Which fixes are safest first?

The safest order is to confirm the display and power path, remove recent hardware changes, load firmware defaults, and then inspect storage detection and boot mode. Physical CMOS resets and BIOS updates come later, because both can erase settings and create new failure points.

Low-risk checks before changing firmware

  1. Verify power path. Confirm the monitor has power, the PC power supply switch is on, laptop AC is connected, and the display cable is fully seated. A black screen with spinning fans often traces back to the display or GPU path rather than damaged firmware.
  2. Remove recent changes. Disconnect new USB devices, remove newly added expansion cards if practical, and undo any recent overclock or XMP or EXPO change through setup if the system still enters firmware. New hardware often triggers logo hangs and failed POST.
  3. Check basic detection. Enter setup and look for CPU, memory amount, and storage detection. If the boot drive is listed, the problem may be boot mode or Windows startup, not the firmware image itself.
  4. Load setup defaults. Use the firmware option to load default or optimized settings, then save and reboot. This is lower risk than a physical CMOS clear because it lets you review current settings first and often fixes bad boot-order or memory settings.

When to load setup defaults

Load defaults when the system still reaches setup, especially after a failed overclock, a startup logo hang, or a new GPU or storage install. Defaults also make sense after checksum warnings if the clock still holds and the battery is not plainly failing.

When a CMOS clear is justified

A CMOS clear makes more sense when setup cannot be entered, defaults will not save, the system loops after a bad setting, or a battery-related checksum error keeps returning. A CMOS clear is not usually the first move for every boot issue.

Say your board shows the logo, enters setup, and still lists the NVMe drive, but Windows says no bootable device. Clearing CMOS first may only erase fan curves, SATA mode choices, or RAID settings. Check boot order and drive mode before any hard reset.

Why is the PC stuck at the logo, missing drives, or resetting time?

Why is the PC stuck at the logo, missing drives, or resetting time?
A computer boot screen shows the Gigabyte logo and a loading bar

A logo hang often points to bad settings, unstable RAM training, or a device blocking POST; missing drives usually mean detection or boot-mode trouble; repeated time resets and checksum warnings strongly suggest settings-retention failure. These symptoms sit on different branches and should not get one blanket fix.

Startup logo hang and boot loops

If the machine stops at the maker logo, remove external drives and USB accessories first. Then enter setup if possible and load defaults. If the system recently got a memory or CPU change, check the CPU support list, minimum BIOS version, and firmware notes on the exact motherboard or laptop support page before assuming the board has failed.

Tom's Hardware says BIOS updates may be needed for newer CPUs. Older Intel 600 series motherboards may need BIOS updates for 13th Gen Raptor Lake. AMD 300, 400 and 500 series boards may need BIOS updates for Ryzen 5000 support. In those cases, a logo hang or no-boot state after a CPU swap can be a compatibility issue rather than a damaged board.

Missing boot options or storage not detected

If the boot menu is empty, first ask whether the drive is absent from firmware or only absent from the boot list. A drive missing from both points to power, cabling, seating, slot sharing, or drive failure. A drive visible in setup but missing from boot choices often points to boot mode mismatch.

Check whether UEFI mode, CSM, RAID, or AHCI was changed. Those settings can affect how the existing installation appears. This is one place where loading defaults can help, but only after noting current storage settings if the system was built around RAID or another custom mode.

Time and date resets, checksum errors, and the CMOS battery

The CMOS battery is the coin-cell on the motherboard that retains time, date, and firmware settings while the system is off. When it weakens, the PC may forget its clock, throw a CMOS or checksum warning, or reset boot order after power loss.

Replace the battery before considering a flash. BIOS checksum error is a known startup symptom, and CMOS battery failure is also a known startup symptom. If replacing the battery stops the clock resets, the firmware itself was likely never the problem.

When should you reset CMOS?

When should you reset CMOS?
A motherboard battery sits beside electronic components

Reset CMOS when firmware settings are clearly broken and normal setup access is blocked or ineffective, not as a reflex for every boot issue. A proper CMOS reset often requires full power removal and board-specific handling, and laptops may have limits that make service documentation more useful than guesswork.

Battery removal reset

  1. Shut down fully. Turn the PC off, switch off the power supply if present, and unplug AC power. On a laptop, shut down and disconnect the charger before opening anything the service manual says is user-accessible.
  2. Drain residual power. Press the power button once after power is removed. This helps discharge leftover board power so the reset can work as intended.
  3. Remove the coin-cell. Take out the CMOS battery only if the board design allows safe access. Note its orientation before removal so it goes back in the same way.
  4. Reinstall and reconfigure. Put the battery back, reconnect power, enter setup, load defaults, and then restore needed settings such as boot order, fan curves, TPM-related choices, or storage mode. Expect time and date to need correction.

CLR_CMOS jumper reset

Many motherboards provide a reset header, often labeled CLR_CMOS or similar. Reset can be done with a CLR_CMOS jumper. This is usually cleaner than battery removal, but only if the board manual confirms the exact pins and power-off procedure.

  1. Remove all power. Unplug the system and switch off the PSU before touching the board. A powered board should never be jumpered for reset unless the maker explicitly says otherwise.
  2. Locate the header. Find the CLR_CMOS marking in the board manual or silkscreen. Similar nearby headers can control other functions, so guessing is a bad idea.
  3. Short the correct pins. Use the supplied jumper cap or the board's documented method for the required moment. The exact method varies, which is why board-specific instructions matter here.
  4. Restore power and check setup. Start the system, enter firmware, and load defaults if prompted. Then put back only the settings you know are required for your hardware and boot drive.

Laptop limits and board-specific cautions

Many laptops hide the battery, use internal main batteries, or place reset pads where accidental damage is easy. Password cases are even tighter. On those machines, vendor service procedures carry more weight than desktop-style jumper advice.

Picture a thin laptop that resets the clock every morning but still boots. The low-risk path is to verify the charger, confirm the time resets after full shutdown, then follow the model's service guide or official support article. Prying into a sealed chassis for a random reset can turn a battery issue into a broken connector.

When does a BIOS update help, and when can it make things worse?

When does a BIOS update help, and when can it make things worse?
A BIOS update confirmation dialog appears on a computer screen

A BIOS update helps when the maker's notes match the problem: new CPU support, memory training fixes, storage compatibility, or a documented bug. It becomes risky when used as a generic cure, because the wrong file or a failed flash can leave the board unable to start.

CPU compatibility and vendor release notes

Firmware updates are most justified after a CPU change or when the maker lists a fix that matches the symptom. The same source says BIOS updates may be needed for newer CPUs. BIOS updates can resolve compatibility problems, but that does not make them routine maintenance for every boot issue.

Match the exact motherboard revision or laptop model, then match the BIOS file format the vendor expects. A board utility may refuse a wrong file, but refusal is the good outcome. Tom's Hardware warns a bad BIOS file can brick the motherboard.

Using built-in update tools such as EZ Flash or Q-Flash

Board makers often include update tools inside setup, such as EZ Flash or Q-Flash. Those utilities are usually safer than flashing from inside a busy desktop session because fewer background variables can interrupt the process.

  1. Confirm exact model. Read the full board or laptop model and revision from the sticker, setup screen, or support page. Similar names can use different firmware files, and a mismatch is one of the fastest ways to create a dead board.
  2. Read release notes. Look for the listed fix or support addition that matches the symptom, such as CPU support or memory compatibility. If the notes do not address the problem, skipping the update is often the safer call.
  3. Use the vendor utility. Start the update from the built-in BIOS tool such as EZ Flash or Q-Flash when the maker recommends that route. Follow the required file format and media instructions exactly.
  4. Protect power during flash. Keep AC power stable and do not interrupt the process. Power loss or forced shutdown during flashing can leave the firmware incomplete and the system unable to boot.

Bad flash risk, recovery features, and stop signs

Some boards have flashback, dual BIOS, or another documented recovery feature. Many do not. If the flash fails and the board has no recovery path in the manual, repeated power cycling rarely helps.

Stop at once if the board will not POST after an interrupted update, if the recovery feature does not start exactly as documented, or if the file used may have been for another model. At that point, further random resets can waste time without improving recovery odds.

What should you do for no display or a BIOS password lock?

No display before POST should be treated first as a video path, RAM, or power problem, while a BIOS password lock should be treated as an ownership and service issue. Both cases often sit outside normal firmware tuning and can get worse with trial-and-error resets.

No display before POST

Start with the monitor input, cable, GPU power leads, and memory seating. If the CPU has integrated graphics, test the motherboard video output after removing the discrete GPU if the platform supports that. Only after those checks should firmware settings move up the list.

If the screen went black right after a display-output or PCIe setting change in setup, a CMOS clear is more reasonable. If there was no settings change and the system has been physically moved, loose hardware connections are more likely than firmware corruption.

Password lock

A setup or supervisor password is not the same as a normal boot issue. Desktop boards sometimes allow documented recovery with proof of ownership and a vendor process. Many laptops do not permit a safe end-user bypass at all.

Use only the maker's published support route for that exact model. Random unlock tools and online “master password” claims are a poor bet and can leave the device in a worse state, especially on business laptops with tighter firmware security.

Keep reading

Frequently asked questions

How to troubleshoot common bios issues

Start before firmware changes: verify power, monitor input, display cable, and new hardware. Then enter setup, load defaults, and check whether storage is detected and the boot mode fits the installed OS. Use a CMOS clear only when settings are stuck or setup access fails.

Can bios update cause problems?

Yes. A BIOS update can help with CPU support and listed bug fixes, but it can also cause a no-start condition if power fails, the update is interrupted, or the wrong file is used. That is why flashing should follow release notes, exact model matching, and a stable power source.

How to fix bios settings

If the PC still enters setup, load defaults first and save. Then restore only required items such as boot order, storage mode, fan settings, and virtualization or TPM-related choices. If settings will not stay saved or the clock resets, replace the CMOS battery before assuming the firmware image is bad.