Clearing CMOS wipes your motherboard’s saved firmware settings and sends the board back to factory defaults. ASUS’s support page describes it as resetting the real-time clock memory that stores the date, time, BIOS password and BIOS setup parameters. It still lists three ways to do the job: a Clear CMOS button, the CLRTC pin header, or pulling the coin-cell battery.
This tutorial covers all three methods on current AM5 Ryzen boards and Intel 800-series boards, plus the older jumper layouts you will still meet on a used or inherited machine. If your PC shows no sign of life at all, work through our PC won’t turn on checklist first, because a dead power supply and a bad BIOS setting look identical from the outside.
You will finish in about 20 minutes with 13 numbered steps, a before-and-after PowerShell script that proves what changed, a Linux equivalent, and a troubleshooting list for the ten problems that show up most often after a reset. Most short guides skip the part that actually trips people up: the first boot, the BitLocker prompt, and re-applying your memory profile. This one covers all three.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Clearing CMOS Actually Does
CMOS is the old name for the small block of battery-backed memory where a motherboard keeps its setup choices and its clock. Modern boards use UEFI firmware, but the vocabulary stuck, and every vendor still ships a way to wipe those choices. ASUS Support puts the effect plainly: “Clear CMOS clears the Real Time Clock (RTC) random access memory in CMOS, which contains the date, time, BIOS password and BIOS setup parameters.”
In practice that means the following settings go back to their defaults on most boards:
- Boot order and boot mode (UEFI, CSM, Secure Boot state)
- Memory profile (EXPO on AMD, XMP on Intel), which drops to the standard JEDEC speed
- CPU and memory overclocks, Precision Boost Overdrive, Curve Optimizer offsets and voltage tweaks
- Fan curves and fan header modes
- Virtualization switches (SVM on AMD, VT-x on Intel)
- Storage mode (AHCI or RAID), Resizable BAR and above-4G decoding
- The BIOS password, system date and time
Just as important is what it leaves alone. Clearing CMOS does not erase your drives, Windows, or files. It does not touch the processor, change the AM5 socket, or remove platform support. It also does not downgrade or upgrade the firmware itself, so the BIOS version you flashed last month is still the BIOS version you boot afterward. ASUS draws the same line in its documentation: Clear CMOS is the hardware method for restoring defaults, and it is a separate operation from updating firmware with BIOS FlashBack.
That distinction matters because people reach for CMOS clearing when they really need a firmware recovery, or the other way around. If the board will not post after a failed flash, a reset alone may not save you. If the board will not post after a bad overclock, a reset almost always does.
When You Should Clear CMOS (and When You Should Not)
Reset the CMOS when a settings change is the most likely cause of your problem. The classic cases look like this:
- The PC powers on, fans spin, and the screen stays black after you changed a memory or CPU setting
- The board restarts in a loop after a RAM overclock or a failed memory training attempt
- You forgot the BIOS or UEFI password and the board has no recovery option
- The system clock resets every time you unplug the PC, which usually points to a dead battery
- You swapped the CPU or RAM and the board refuses to boot with the old saved profile
- A BIOS update left behind a corrupted or incompatible settings profile
- You bought a used board and want to wipe the previous owner’s configuration
- Windows crashes only after you enable a specific tuning option, and you cannot reach the menu to undo it
An Intel Community thread dated September 30, 2026 shows how routine this is. It discusses no-boot troubleshooting that involves both BIOS settings and clearing CMOS, which is a routine first move before anyone suspects dead hardware.
Do not clear CMOS for problems that firmware settings cannot cause. A game that crashes in one title, a driver that fails to install, or a drive that throws read errors will not improve after a reset, and you will lose your tuned settings for nothing. If your crashes look memory related, test the modules first. Our guide to testing RAM with MemTest86 separates a bad stick from a bad setting in about an hour, and that result tells you whether a reset is worth trying.
Prerequisites: Tools, Versions, and a Five-Minute Prep Check
You need very little for this job. Gather these before you open the case:
- A Phillips screwdriver for the side panel and, on some cases, the GPU bracket
- A plastic spudger, toothpick, or similar non-metal tool for the battery clip
- A flashlight, because the CMOS header often hides under a graphics card or heatsink
- Your motherboard manual as a PDF, since label positions differ by model
- A replacement CR2032 coin cell if the battery is old or the clock keeps resetting
- A USB flash drive for storing the baseline files and, optionally, a BIOS file
On the software side, the scripts in this tutorial run on Windows 10 or Windows 11 with PowerShell 5.1 (built in) or PowerShell 7.x, started as Administrator. The Linux commands use dmidecode and work on any current distribution. Every command is read-only, so none of them changes your settings.
A few facts about the hardware you are likely holding. AMD says it will support the AM5 socket through 2029, so a current Ryzen 7000, 8000 or 9000 board is not a dead-end purchase. ASUS said on January 23, 2026 that its latest AM5 boards are moving from 32 MB to 64 MB BIOS chips, to support broader processor compatibility and larger firmware packages. On the Intel side, ASUS describes Z890 and B860 as the current LGA1851 platforms, and Intel announced the Core Ultra 200S Plus desktop processors on March 11, 2026 for 800-series boards. The reset procedure is the same family of steps on all of them.
Finally, set aside five minutes for the prep check in Steps 1 through 4. People who skip it are the ones who end up locked out by a BitLocker prompt or staring at a BIOS screen they no longer remember how to configure.
The Three Methods at a Glance
Every desktop board gives you at least one of three reset routes. Many give you two. The table below compares them using the timing guidance that vendors publish.
| Method | Where it lives | Tools | Documented hold time | Risk level | Best for |
|---|---|---|---|---|---|
| Clear CMOS button | Rear I/O panel or on the PCB edge | None | About 5 to 10 seconds (ASUS) | Lowest | Current mid-range and high-end boards |
| Two-pin CLRTC or CLRMOS header | Bottom edge of the board, near the front-panel pins | Metal screwdriver tip | About 5 to 10 seconds (ASUS), at least 30 seconds (ASRock) | Low | Boards without a button |
| Three-pin jumper | Near the battery or chipset | Fingers or tweezers | 1 to 5 minutes (Intel documentation) | Low | Older Intel boards, some mainstream models |
| Battery removal | Round coin-cell socket | Spudger | No fixed time, power fully off | Medium | Any board, last resort |
| BIOS FlashBack | Rear I/O port plus USB drive | FAT32 USB stick | Not a reset method | Medium | Recovering a bad flash, not clearing settings |
BIOS FlashBack deserves a short note because people confuse it with a reset. It writes a firmware file from a USB stick, so it belongs in the recovery toolbox rather than the clearing toolbox. Our guide on updating your BIOS safely covers that process.
Sunbeam Tech’s how-to-clear-CMOS reference notes that Clear CMOS buttons appear on many mid-range and high-end desktop boards, either on the rear I/O panel or directly on the PCB. That matches what the current ASUS documentation shows for the ROG Strix B850-E Gaming WiFi, ROG Strix Z890-E Gaming WiFi, ROG Strix X870E-E Gaming WiFi7 Neo and ROG Crosshair X870E Hero, all of which advertise Clear CMOS in pages dated October 19 and 20, 2026.
The vendor times differ, and the spread is wide. ASUS quotes 5 to 10 seconds, while ASRock tells owners to short the CLRMOS pins for at least 30 seconds. A longer hold costs you nothing, so when in doubt, hold past the longest figure you can find for your board.
Board Labels and How to Find Your Reset Point
Vendors do not agree on a name, which is the main reason people cannot find the header. The same function appears under many labels:
| Label on the board | Typical form | Where you will see it |
|---|---|---|
| CLR_CMOS | Button or two-pin header | Used by ASUS and other makers |
| Clear CMOS | Rear panel button | ROG Strix X870-F Gaming WiFi lists a rear-panel button |
| CLRTC | Two-pin header | Named in ASUS documentation for the pin method |
| CLRMOS | Two-pin header | ASRock FAQ, short with a metal object |
| JBAT or JBAT1 | Jumper | Listed among current board labels, check the manual for pin count |
| RTCRST | Two-pin header | Appears on some boards |
| CLR_BIOS | Button or header | Used by some vendors |
| Clr CMOS | Onboard button | Gigabyte GA-Z68XP-UD5 lists one beside the power and reset buttons |
Two real examples show how much layouts vary even inside one generation. Gigabyte’s B650M K specification page, dated October 12 and 13, 2026, lists both a reset jumper and a Clear CMOS jumper, so you need the manual to tell them apart. ASUS’s ROG Strix X870-F Gaming WiFi, updated October 19 through 21, 2026, lists a rear-panel Clear CMOS button. By contrast, the older ROG Strix X99 Gaming lists a jumper, and that page was only refreshed on October 20, 2026 for catalog reasons. A recent page date does not make an old board a new product.
NZXT’s guide to the button, jumper and battery methods shows photos of the same three layouts. The lesson: never assume your board has a button. Open the PDF manual, search for CMOS, CLR, JBAT and CLRTC, and check the board layout diagram for the exact position. On a small form factor board the header often sits near the bottom edge between the audio connector and the front-panel pins. On boards with a rear button, the rear I/O cluster is the first place to look, and you can reset without opening the case.
Steps 1 to 4: Prepare Before You Touch Anything
These first four steps cost nothing and take about five minutes. They save you from the three worst outcomes of a reset: losing your settings, losing access to an encrypted drive, and not knowing which board you own.
Step 1: Identify the board and download the manual. Press Win+R, type msinfo32, and read the BaseBoard Manufacturer and BaseBoard Product lines. Or run the PowerShell command below. Then search the vendor’s support site for that exact model and save the PDF manual. If the PC does not boot, read the model name printed on the board itself, usually near the CPU socket or between the PCIe slots.
Get-CimInstance Win32_BaseBoard | Select-Object Manufacturer, Product, Version
Get-CimInstance Win32_BIOS | Select-Object SMBIOSBIOSVersion, ReleaseDateStep 2: Record your current settings. If you tuned memory by hand, write down the timings now, because our RAM overclocking guide shows which values matter. If the PC still boots, run the baseline script from the project section later in this guide, and also enter the BIOS and photograph every page with your phone. The photos take two minutes and become your re-entry guide. Pay special attention to the memory profile page, the Advanced CPU page, the fan page, and the boot page.
Step 3: Back up your BitLocker recovery key and check device encryption. This is the step most guides skip. A CMOS reset changes what the firmware reports to the TPM, and Windows may respond by asking for a BitLocker recovery key on the next boot. Check your status now and store the key somewhere that is not the encrypted drive, such as your Microsoft account page, a printed sheet, or a password manager.
manage-bde -status
manage-bde -protectors -get C:If the output says Protection Off or Fully Decrypted, you have nothing to worry about. If it says Protection On, copy the 48-digit numerical password from the second command. Treat that number like a master password, because it unlocks the drive.
Step 4: Power down completely. Shut Windows down from the Start menu, not sleep or hibernate. Flip the power supply switch to off, then unplug the power cable from the wall. Press the case power button once for a few seconds to drain any residual charge. Touch bare metal on the case to discharge static before you reach inside. ASUS instructs users to power off and remove AC power before pressing the button or shorting the header, and the same rule applies to every method below.
How to Clear CMOS Three Ways: Steps 5 to 8
Step 5 is the same for every method: locate the reset point on your board. After that, pick the method that your board supports and that you are comfortable with. Start with the button if you have one. Move to the pins only if there is no button. Use the battery only when the other two fail or when you need to replace an old cell anyway.
Step 5: Locate the reset point. Remove the side panel. Use the manual’s board diagram to find the labeled button, header, or battery. If a long graphics card blocks your view, shine the flashlight along the bottom edge of the board. You do not need to remove the card on most layouts, but do not force a tool past it. If the header sits directly under the card, unclip the PCIe latch and lift the card free. The extra two minutes beats cracking a trace.
Method A: The Clear CMOS Button (Step 6)
Step 6: Press the button with the PSU off and the cord out. With the power supply switched off and the cable unplugged, press the Clear CMOS button and hold it. ASUS gives about 5 to 10 seconds. A rear-panel button needs a fingertip or a paperclip, depending on the model, and an onboard button sits flush with the PCB, so a pen tip works. Release it, wait a few seconds, and move on to Step 9.
Some owners ask whether they can press the button with the PC running. Do not. ASUS tells you to remove AC power first, and a board that loses its settings mid-operation can lock up. You gain nothing by skipping the shutdown.
Method B: The Pin Header or Jumper (Step 7)
Step 7: Short the pins, or move the jumper. Two layouts exist, and the manual tells you which one you have.
For a two-pin header (CLRTC or CLRMOS), touch both pins at once with a metal screwdriver tip or a pair of tweezers. ASUS says to short the specified two-pin header for about 5 to 10 seconds. ASRock’s FAQ says to disconnect the PSU, find the CLRMOS header, and short it with a conductive metal object for at least 30 seconds. Choose the longer time and you cover both.
For a three-pin jumper, Intel’s documentation for its desktop boards gives the classic procedure: “Move the jumper from the default position 1–2 to position 2–3 to clear CMOS. Wait 1–5 minutes then move it back to the default position.” The Intel support article covers systems with Intel desktop processors. Moving the jumper back is the step people forget, and a board left in the clear position will reset itself every time you try to save a setting.
Method C: Remove the CMOS Battery (Step 8)
Step 8: Pull the coin cell, wait, and reinstall it. Find the round silver battery near the chipset or PCIe slots. Press the small retaining clip aside with a plastic tool. The cell pops up on its spring. Lift it out by the edges. Wait at least 30 seconds, which matches the longest published header time, then press and hold the case power button briefly with the cord still unplugged to drain remaining charge. Seat the cell again with the positive side facing up, the same orientation it came out.
The standard desktop cell is the CR2032. It is a 3 V non-rechargeable lithium coin cell, about 20 mm across and 3.2 mm thick, with a typical capacity of 220 to 240 mAh depending on the maker. Dell’s desktop battery replacement guide identifies the cell as a 3 V CR2032 and says to replace it with the exact same type the computer specifies. HP describes a typical service life of roughly 2 to 10 years. Replacement cells are cheap, so swap a battery that has lasted several years rather than reinstalling it.
Battery removal has one extra risk compared with the other two methods. You are handling a small part near delicate parts, so work slowly. If the cell has a cable and connector (common in prebuilt systems), unplug the connector instead of prying anything.
Steps 9 to 11: First Boot After the Reset
Step 9: Reassemble and reconnect. Confirm the jumper is back in the default position, the battery is seated, and no tool is left in the case. Refit the graphics card if you removed it. Plug the power cable back in, switch the PSU on, and leave the side panel off until you know the PC boots.
Step 10: Power on and expect a longer first boot. Press the power button and wait. A cleared board has to retrain its memory from scratch, so the first start can take several times longer than normal, and the screen may stay black while the fans spin. This is the single most misread moment in the whole process. Many people assume the reset failed and hit the button again. Give the board a couple of minutes before you intervene. If you get a message such as CMOS checksum error, Overclocking failed, or Press F1 to enter setup, that is normal, and it confirms the reset worked.
You may also see an alert that the system date and time are wrong. That is expected too, since the clock lives in the same memory.
Step 11: Enter the BIOS and load safe defaults. Press Delete or F2 (the key varies by maker), and look for a Load Optimized Defaults or Restore Defaults option. On some boards it appears automatically on the first screen. Accept it, set the date and time, and save and exit. After the board restarts, confirm that Windows or Linux boots without errors. If it does, the reset is done and you only need to restore your preferences.
Steps 12 and 13: Re-Apply Your Settings and Verify
Step 12: Put your tuning back, in order. Restoring settings in a fixed order makes failures easier to trace. Use this order:
- Storage mode and boot order, so Windows starts
- Virtualization (SVM or VT-x) if you use WSL2, Docker, or virtual machines
- Memory profile (EXPO or XMP), the biggest performance item
- Resizable BAR and above-4G decoding for modern GPUs
- Fan curves
- CPU tuning such as Curve Optimizer or undervolting, one change at a time
The table below shows what typically resets, where to restore it, and the symptom you will see if you skip it.
| Setting | Resets to | Symptom if forgotten | How to restore |
|---|---|---|---|
| EXPO or XMP profile | Standard JEDEC speed | RAM runs well below its rated speed | Enable the profile on the memory page |
| Storage mode | Board default (often AHCI) | Boot failure or INACCESSIBLE_BOOT_DEVICE if you used RAID | Set the mode you used before, no reinstall needed |
| Virtualization | Often disabled | WSL2, Docker and VMs fail to start | Turn on SVM or VT-x |
| Resizable BAR | Varies by board | Lower GPU performance in supported games | Enable Above 4G Decoding and Resizable BAR |
| Fan curves | Default profile | Louder or hotter system | Re-enter your curve or load a saved profile |
| Boot order | Board default | Wrong drive boots or USB tried first | Pick the Windows Boot Manager entry |
| Date and time | Firmware default | Browser certificate warnings | Set the clock, then sync in Windows |
The biggest performance loss comes from the memory profile. Our walkthrough on enabling XMP and EXPO shows the exact menu path. Do that before you touch anything else in the performance menus.
Step 13: Verify with the comparison script. Run the comparison script from the project section. It reads the baseline you saved in Step 2 and prints a table of what changed. Anything marked CHANGED is a setting you still need to restore. When every row reads same, you are done.
AM5 and Intel 800-Series Notes
Reset behavior is consistent across vendors, but a few platform details are worth knowing before you start.
AM5 boards. AMD lists support for A620, B650, B650E, X670, X670E, X870, X870E, B840 and B850 chipsets on the platform. Clearing CMOS on any of them leaves the CPU and socket untouched. The most noticeable effect is the memory: an AM5 board that was running an EXPO profile will boot at the standard speed after a reset, and the first start retrains the modules. If you hand-tuned DDR5 timings, the DDR5 overclocking tutorial explains how to rebuild them in small, testable steps. Current ASUS documentation for the TUF Gaming B850-Pro WiFi7 W NEO states that its Clear CMOS button resets BIOS settings to factory defaults and can reboot the PC after incorrect BIOS settings, and the same page documents BIOS FlashBack using a FAT32 USB drive.
Intel LGA1851 boards. Z890 and B860 follow the same pattern. The ROG Strix Z890-E Gaming WiFi page dated October 20, 2026 documents Clear CMOS. Intel said on March 11, 2026 that the new Core Ultra 200S Plus processors remain compatible with 800-series motherboards, and that new 800-series models would keep arriving through 2026. If you recently swapped in one of those CPUs and the board hangs on a code, the fix may be a BIOS update first and a reset second.
Firmware caveat. ASUS’s September 2026 BIOS notes for an Intel board state that the Intel Management Engine update stays installed even if you later roll back the BIOS to an older version. A CMOS reset behaves the same way: it restores settings and leaves the firmware images alone. If your problem started after a flash, resetting will not undo the flash. On AM5, ASUS published BIOS 4004 beta for the PRIME B650M-K-CSM on September 21, 2026 with AGESA ComboAM5 PI 1.3.0.1d and memory compatibility fixes, which shows how often memory-related firmware changes land. If you plan to flash after the reset, do it from a clean, defaults-only state.
Project: Build a CMOS Reset Kit With Before-and-After Scripts
A reset is much less stressful when you can prove what changed. This small project gives you two PowerShell scripts, a Linux script, and a folder layout. It takes about ten minutes to set up and runs in a few seconds.
Create this structure on a USB drive or in your Documents folder:
cmos-reset-kit/
Save-BiosBaseline.ps1
Compare-BiosBaseline.ps1
save-baseline.sh
baseline/ (created by the scripts)
notes.txt (your BIOS photos list and recovery key location)Script 1: Save-BiosBaseline.ps1. Run it from an elevated PowerShell window before you clear anything. It captures the board, BIOS version, CPU virtualization state, Secure Boot state, TPM state, memory speeds, and disk bus types.
$out = Join-Path $PSScriptRoot "baseline"
New-Item -ItemType Directory -Force -Path $out | Out-Null
$bios = Get-CimInstance Win32_BIOS
$board = Get-CimInstance Win32_BaseBoard
$cpu = Get-CimInstance Win32_Processor | Select-Object -First 1
$ram = Get-CimInstance Win32_PhysicalMemory
$tpm = Get-Tpm
$disks = Get-Disk
$sb = try { Confirm-SecureBootUEFI } catch { "unsupported-or-legacy" }
$baseline = [ordered]@{
Captured = (Get-Date -Format "yyyy-MM-dd HH:mm:ss")
BoardMaker = $board.Manufacturer
BoardModel = $board.Product
BiosVersion = $bios.SMBIOSBIOSVersion
Cpu = $cpu.Name
VirtualizationOn = $cpu.VirtualizationFirmwareEnabled
SecureBoot = $sb
TpmReady = $tpm.TpmReady
RamModules = @($ram | ForEach-Object {
[ordered]@{
Slot = $_.DeviceLocator
GB = [math]::Round($_.Capacity / 1GB)
RatedMTs = $_.Speed
ConfiguredMTs = $_.ConfiguredClockSpeed
}
})
Disks = @($disks | ForEach-Object {
[ordered]@{
Name = $_.FriendlyName
Bus = [string]$_.BusType
}
})
}
$baseline | ConvertTo-Json -Depth 5 | Set-Content (Join-Path $out "baseline.json")
Write-Host "Saved baseline for $($board.Manufacturer) $($board.Product)"
Write-Host "BIOS $($bios.SMBIOSBIOSVersion) | RAM running at $($ram[0].ConfiguredClockSpeed) MT/s (rated $($ram[0].Speed))"Example output (illustrative values from a sample build):
Saved baseline for ASUSTeK COMPUTER INC. ROG STRIX B850-E GAMING WIFI
BIOS 1203 | RAM running at 6000 MT/s (rated 6000)Script 2: Compare-BiosBaseline.ps1. Run it after the reset and after you restore your settings. It reads the saved file, captures the current state, and flags each difference.
$file = Join-Path $PSScriptRoot "baseline\baseline.json"
$base = Get-Content $file -Raw | ConvertFrom-Json
$cpu = Get-CimInstance Win32_Processor | Select-Object -First 1
$ram = Get-CimInstance Win32_PhysicalMemory | Select-Object -First 1
$bio = Get-CimInstance Win32_BIOS
$sb = try { Confirm-SecureBootUEFI } catch { "unsupported-or-legacy" }
function Row($name, $before, $after) {
$status = if ("$before" -eq "$after") { "same" } else { "CHANGED" }
[pscustomobject]@{
Setting = $name
Before = $before
After = $after
Status = $status
}
}
$rows = @(
Row "BIOS version" $base.BiosVersion $bio.SMBIOSBIOSVersion
Row "Virtualization" $base.VirtualizationOn $cpu.VirtualizationFirmwareEnabled
Row "Secure Boot" $base.SecureBoot $sb
Row "RAM speed (MT/s)" $base.RamModules[0].ConfiguredMTs $ram.ConfiguredClockSpeed
)
$rows | Format-Table -AutoSize
$bad = @($rows | Where-Object { $_.Status -eq "CHANGED" }).Count
Write-Host "$bad setting(s) still differ from your baseline."Example output right after a reset, before you re-enable EXPO or XMP:
Setting Before After Status
------- ------ ----- ------
BIOS version 1203 1203 same
Virtualization True False CHANGED
Secure Boot True True same
RAM speed (MT/s) 6000 4800 CHANGED
2 setting(s) still differ from your baseline.The two CHANGED rows tell you exactly what to restore: turn virtualization back on and enable your memory profile. After you do, run the script again. It should end with 0 settings that differ.
Script 3: save-baseline.sh for Linux. The same idea works with dmidecode and sysfs. Run it with sudo.
#!/usr/bin/env bash
set -euo pipefail
out="$(dirname "$0")/baseline"
mkdir -p "$out"
{
echo "== Board =="
sudo dmidecode -t baseboard | grep -E "Manufacturer|Product Name|Version"
echo "== BIOS =="
cat /sys/class/dmi/id/bios_vendor /sys/class/dmi/id/bios_version /sys/class/dmi/id/bios_date
echo "== Memory speeds =="
sudo dmidecode -t memory | grep -E "Size:|Speed:|Configured"
echo "== Secure Boot =="
mokutil --sb-state 2>/dev/null || echo "mokutil not installed"
echo "== Virtualization flags =="
grep -o -E -m1 "svm|vmx" /proc/cpuinfo | head -n1 || echo "none"
} | tee "$out/baseline.txt"Run it before and after, then compare the two text files with diff. On Linux, the Configured Memory Speed line is your equivalent of the memory profile check.
Common Pitfalls When Clearing CMOS
These mistakes account for most failed resets. Each one is easy to avoid once you know it exists.
Pitfall 1: Clearing with the PSU still live. A switched-on power supply keeps standby power flowing to the board, so the reset may not take or the board may re-save its settings. Always switch the PSU off and unplug the cord. Every method here assumes that.
Pitfall 2: Not holding long enough. A quick tap on a two-pin header can fail to drain the stored settings. Hold for at least 30 seconds, the longest published figure from ASRock, and you cover the shorter ASUS window as well.
Pitfall 3: Leaving the three-pin jumper in the clear position. A board left on pins 2 and 3 resets itself on every boot. If your settings never stick, check the jumper cap first.
Pitfall 4: Skipping the BitLocker key. Windows may demand the 48-digit recovery key on the first boot after a reset. If the key lives only on the encrypted drive or an account you cannot reach, you lose the data. Back it up in Step 3.
Pitfall 5: Forgetting the storage mode. If you ran RAID mode and the board returns to AHCI, Windows can fail with INACCESSIBLE_BOOT_DEVICE. Switching the mode back in the BIOS fixes it without a reinstall.
Pitfall 6: Replacing the wrong battery. Most desktops use a 3 V CR2032, but a few smaller or older boards use a different cell. Match the exact type your board specifies, as Dell’s guidance says. Do not guess from the size alone.
Pitfall 7: Panicking at the first boot. A black screen for a couple of minutes is memory training, not failure. Interrupting it by holding the power button can restart the whole process.
Pitfall 8: Resetting for a problem that is not a setting. A failing drive, a bad GPU, or a loose power cable will survive any reset. If three resets in a row change nothing, stop and diagnose the hardware.
Troubleshooting: 10 Problems After a CMOS Reset
Work through these in order when something looks wrong after the reset.
1. The PC does not power on at all. Confirm the PSU switch is on, the cable is seated, and the 24-pin and CPU power cables are fully clicked in. A reset cannot cause a dead board, but a loose cable moved during the process can.
2. Fans spin but there is no display. Wait two to three minutes for memory training. If the screen stays black, power off, reseat the RAM, and try one stick in the slot your manual recommends. Make sure the monitor cable goes to the graphics card, not the motherboard.
3. The board shows a CMOS checksum or overclocking failed message. This is the expected result of a reset. Press the key shown on screen, load defaults, and save.
4. The BIOS resets itself on every restart. The battery is dead, a jumper is stuck in the clear position, or the clear button is jammed. Replace the CR2032 first, since it is the cheapest fix, then inspect the jumper cap.
5. Windows asks for a BitLocker recovery key. Enter the 48-digit key from your backup. After Windows starts, suspend and resume protection so the TPM re-learns the configuration, then confirm with manage-bde -status.
6. Windows blue-screens with INACCESSIBLE_BOOT_DEVICE. The storage mode changed. Enter the BIOS and restore AHCI or RAID to match your earlier setting.
7. RAM runs at 4800 MT/s instead of its rated speed. The memory profile reset. Enable EXPO or XMP in the BIOS memory page and verify the speed with the comparison script. On newer AM5 boards, also check the lower-latency option covered in our AMD EXPO ULL setup guide.
8. WSL2, Docker or virtual machines stopped working. Virtualization defaulted to off. Enable SVM Mode on AMD or Intel Virtualization Technology on Intel.
9. The board still will not post after a reset. Try the battery method as a second pass, because it removes the last bit of standby power. Then test with a single RAM stick, no extra drives, and the monitor on the GPU output. If your board has BIOS FlashBack, flash a known good BIOS file from a FAT32 USB stick.
10. The clock is wrong every time you unplug the PC. A weak CR2032 cannot hold the time. Swap it for a fresh cell, set the date, and check that it survives a full shutdown and unplug.
Advanced Tips for Power Users
A few extra moves make the process faster the next time.
Save BIOS profiles before every experiment. Most enthusiast boards let you store several setup profiles on the board or a USB stick. Save one before any tuning session and a single menu action restores your settings after a reset. It beats retyping values from photos. Browse more tuning walkthroughs in our hardware section.
Use the button for fast tuning cycles. If you push memory timings and the board hangs, a rear-panel button lets you reset in seconds without opening the case. It makes a rear-panel button one of the most underrated features when you shop for a board.
Keep a spare CR2032 in the toolbox. A fresh cell costs little and removes the clock-resetting problem entirely. Replace the cell whenever you open an older PC for another reason.
Know the difference between reset and recovery. BIOS FlashBack recovers a corrupted firmware image. CMOS clearing recovers settings. When you cannot tell which one you need, try the reset first because it is faster and non-destructive.
Watch for retained firmware changes. ASUS notes that an Intel ME update stays in place after a BIOS rollback. Plan flashes carefully, because no hardware reset will take you back to the earlier state.
Log changes in a notes file. Keep a short text file next to your scripts listing each tuning change and the date. When a future crash appears, the list narrows down the cause.
Frequently Asked Questions
Does clearing CMOS delete my files or Windows? No. It resets firmware settings only. Your drives, operating system and files stay untouched.
How long should I hold the Clear CMOS button? ASUS says about 5 to 10 seconds with the PC off and unplugged. Hold for the longer end of that range if you are unsure.
Is it safe to clear CMOS on an AM5 or Intel 800-series board? Yes. The process resets settings and leaves the CPU, socket and firmware version alone. The main side effect is a slower first boot while memory retrains.
Will clearing CMOS fix a forgotten BIOS password? On most boards, yes, because the password lives in the same memory the reset clears. ASUS lists the BIOS password among the items the reset removes. Some business-class machines use extra protections, so check the vendor’s guide.
Do I need to replace the CMOS battery after a reset? Not necessarily. If the battery is several years old or the clock keeps losing time, replace it with the same 3 V CR2032 type. HP describes a typical service life of about 2 to 10 years.
Why does my PC take so long to start after clearing CMOS? The board is retraining memory with default settings. Wait a few minutes. Subsequent boots return to normal speed once the training data is saved.
Can I clear CMOS while the computer is on? No. Shut down, switch off the PSU and unplug the cable first. Clearing a live board risks lockups and does not reset reliably.
Do I lose my EXPO or XMP memory profile? Yes. The profile reverts to the standard speed and you must enable it again in the BIOS after the reset.
