Rightek Rescue · Guides · 0xc000021a / Bad System Config Info

0xc000021a / BAD_SYSTEM_CONFIG_INFO: Check before repairing

These stop codes are clues, not a complete diagnosis. BAD_SYSTEM_CONFIG_INFO points to a registry problem; 0xc000021a describes a fatal process failure with several possible causes. Neither proves that a particular hive is damaged, that the drive is healthy, or that every personal file is intact. Protect important data before repair.

Updated 3 October 2026 · by Rightek IT Services

What you're seeing

• A blue screen: Your PC ran into a problem and needs to restart
• Stop code 0xc000021a, 0xc0000218, or BAD_SYSTEM_CONFIG_INFO
• It often appears after a power loss during an update, a bad shutdown, or disk errors

Why the distinction matters

• 0xc000021a: a critical user-mode process such as Winlogon or CSRSS has failed. Mismatched system files or third-party software can be involved; it is not a registry-only code. See Microsoft's 0xc000021a reference.
• BAD_SYSTEM_CONFIG_INFO (0x74): a registry error can involve a damaged SYSTEM hive or missing critical keys and values. The associated status and event evidence help narrow it down. See Microsoft's 0x74 reference.
• Confirmed registry damage: interrupted writes or storage problems may be involved, but the affected hive and usable recovery material need validation before replacement or repair.

Getting into the Recovery Environment

If the machine reaches the sign-in screen, hold Shift while clicking Restart. From there the route is Troubleshoot → Advanced options. Avoid repeated forced shutdowns, especially while an update may still be progressing.

If recovery is unavailable, Windows installation media made on another working PC can provide access. The affected PC must power on and boot from USB. Choose Repair your computer rather than starting a clean installation. Have the BitLocker recovery key ready if required.

Review recovery options before replacing a hive

1. Protect important data and identify the affected Windows installation before choosing a repair.
2. Review available Startup Repair or System Restore options when appropriate to the evidence.
3. Do not replace a hive merely because its name matches. Recovery material must be usable and belong to the same installation; RegBack may be empty.
4. If considering Reset this PC, review what the selected option removes before proceeding.

A wrong, empty or mismatched replacement can make recovery harder. This guide does not provide a blind hive-copy recipe.

The drive-letter trap

Nearly every set of instructions on the internet tells you to run these commands against C:. Inside the Recovery Environment that is usually wrong — the recovery image takes X:, and your Windows install often lands on D: or E:. Running a repair against the wrong volume either fails harmlessly or, worse, succeeds against the wrong thing.

Check first, every time. From the Command Prompt:

• diskpart
• list volume — note which volume has your Windows folder, by size and label
• exit
• dir D:\Windows — confirm it is the right one before you use it

Built-in repairs also change the installation

The following existing command examples are not a universal sequence. Back up important data, investigate signs of storage failure and confirm the target volume first. D: is only an example; do not run these commands against an unverified volume.

• sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows — verifies protected system files and attempts applicable repairs when suitable replacement files are available.
• DISM /Image:D:\ /Cleanup-Image /RestoreHealth — repairs the component store that sfc draws its replacements from. Run this if sfc reports files it could not fix, then run sfc again.
• chkdsk D: /f — modifies the filesystem to repair detected errors; it does not establish the cause of registry damage or guarantee it will not recur. Do not use repair passes on a drive suspected of physical failure. See Microsoft's chkdsk reference.

Why RegBack is empty, and what that means for you

Older registry-recovery instructions often assume that C:\Windows\System32\config\RegBack contains a usable backup. That assumption must be checked; a stop code alone is not a reason to copy a hive.

Microsoft stopped automatic RegBack backups by default starting with Windows 10 version 1803; entries can be zero bytes. See Microsoft's RegBack explanation. An empty file is not recovery material, and a nonempty file still needs validation.

Check before you copy anything. dir D:\Windows\System32\config\RegBack and look at the sizes. Do not replace a hive with a zero-byte file. Size alone does not establish integrity, matching installation identity or suitability for recovery.

Where the other copies live

If RegBack is empty, there may still be a usable hive elsewhere:

• A System Restore point. Advanced options → System Restore can restore earlier system files and settings when a usable point exists. Recent applications, drivers or settings may be affected; back up important data before recovery.
• Windows.old, if present, may contain older material. Presence alone does not prove that its hives are suitable or belong to the required installation state.
• The hive's own transaction logs — the .LOG1 and .LOG2 files beside it. Windows can sometimes replay these to repair a hive in place when the logs match and contain the necessary surviving data. This is different from restoring a backup, and it is not guaranteed when the required data is missing.

When to stop

If no usable recovery material is available, or repairs fail, reassess the evidence rather than repeating writes to the disk. Reset or rebuild may be options, but applications and settings can be removed — review the recovery trade-offs. Suspected storage failure needs separate attention before software repair.

FAQ