# How to Fix BAD_SYSTEM_CONFIG_INFO in Windows 11

URL: https://www.mytechnician.tech/tips/fix-bad-system-config-info-windows-11/
Published: 2026-07-28 | Author: Ankit Kumar
Tags: Windows 11, BSOD, Boot, Troubleshooting, Fix
Summary: BAD_SYSTEM_CONFIG_INFO means the registry or boot configuration is damaged. Repair BCD, restore the registry hives, and get back into Windows 11 with these ordered steps.
Recommended app: PC-Troubleshooter — https://www.mytechnician.tech/apps/windows-troubleshooter/ (Microsoft Store: https://apps.microsoft.com/detail/9N7RWKW8SP24?hl=en-us&cid=mytechnician-web). Optional; every step below uses built-in Windows tools.

## The Problem
**BAD_SYSTEM_CONFIG_INFO** (stop code `0x00000074`) means Windows could not read a valid system configuration at startup. In practice that is one of two things: the **Boot Configuration Data** store (BCD) is wrong or corrupted, or a **registry hive** — usually `SYSTEM` — is damaged.

It commonly appears after an interrupted update, a failed driver install, a sudden power loss, or a change to boot settings such as memory count or a dual-boot entry. Unlike hardware stop codes, this one is nearly always repairable without reinstalling.

> **PC will not reach the desktop at all?** Everything below runs from the recovery environment — see [how to enter Safe Mode](https://www.mytechnician.tech/tips/how-to-enter-safe-mode-windows-11/) for how to get there. **Different stop code each time?** Start at [how to fix a BSOD](https://www.mytechnician.tech/tips/how-to-fix-bsod-blue-screen/).

## Symptoms
* Blue screen reading **BAD_SYSTEM_CONFIG_INFO**, usually during boot.
* The PC loops: blue screen → restart → blue screen.
* Automatic Repair runs, fails, and offers advanced options.
* Started right after a Windows update, a driver install, or a BIOS change.

## Step 1: Get into the Recovery Environment
1. If Windows boots to the desktop, use **Settings** → **System** → **Recovery** → **Advanced startup** → **Restart now**.
2. If it does not boot, force the recovery environment: press the power button to start, and when the Windows logo appears, hold the power button for five seconds to shut it off. Repeat **three times**. On the fourth start Windows loads **Automatic Repair**.
3. Choose **Advanced options** → **Troubleshoot** → **Advanced options**.
4. From here you can reach **Startup Repair**, **Command Prompt**, **System Restore**, and **Uninstall Updates**.
5. If the loop never reaches this menu: [fix the automatic repair loop](https://www.mytechnician.tech/tips/fix-automatic-repair-loop-windows-11/).

## Step 2: Try Startup Repair First
1. In **Advanced options**, click **Startup Repair**.
2. Select your account and enter the password if prompted.
3. Let it run — it can take 15-30 minutes and may restart on its own.
4. If it reports it could not repair the PC, that is normal for this stop code. Continue to Step 3; the log at `C:\Windows\System32\Logfiles\Srt\SrtTrail.txt` sometimes names the failing file.

## Step 3: Rebuild the Boot Configuration Data
This fixes the BCD half of the problem.

1. In **Advanced options**, choose **Command Prompt**.
2. Run these in order, answering `Y` when asked to add the installation to the boot list:
   ```
   bootrec /repairbcd
   ```
   ```
   bootrec /osscan
   ```
   ```
   bootrec /rebuildbcd
   ```
3. Restart and see whether Windows starts.
4. If `bootrec` reports **"Total identified Windows installations: 0"**, the boot store is beyond repair in place — go to Step 4.

## Step 4: Recreate the Boot Store from Scratch
Only do this if Step 3 found no installations.

1. In **Command Prompt**, find the EFI partition:
   ```
   diskpart
   ```
   ```
   list volume
   ```
   Look for a small volume (roughly 100-500 MB) formatted **FAT32**. Note its number.
2. Assign it a letter and exit:
   ```
   select volume 3
   ```
   ```
   assign letter=Z
   ```
   ```
   exit
   ```
   Replace `3` with the volume number you found.
3. Rebuild the boot files, where `C:` is the Windows volume:
   ```
   bcdboot C:\Windows /s Z: /f UEFI
   ```
4. Restart.
5. Related: [fix no bootable device](https://www.mytechnician.tech/tips/fix-no-bootable-device-windows-11/) and [fix INACCESSIBLE_BOOT_DEVICE](https://www.mytechnician.tech/tips/fix-inaccessible-boot-device-windows-11/).

## Step 5: Check the Memory Count in Boot Settings
A stale `truncatememory` or `removememory` entry, often left by a benchmarking tool, causes this stop code directly.

1. From **Command Prompt**:
   ```
   bcdedit /enum {default}
   ```
2. If you see `truncatememory` or `removememory` listed, delete them:
   ```
   bcdedit /deletevalue {default} truncatememory
   ```
   ```
   bcdedit /deletevalue {default} removememory
   ```
3. Also check the processor count is not artificially limited:
   ```
   bcdedit /deletevalue {default} numproc
   ```
   An error saying the element is not found simply means it was not set — that is fine.
4. Restart.

## Step 6: Restore the Registry Hives from RegBack
This addresses the registry half. Windows keeps a copy of the hives; on Windows 11 the folder is often empty by default, but check it.

1. In **Command Prompt**:
   ```
   cd C:\Windows\System32\config
   ```
   ```
   dir
   ```
2. Back up the current hives before touching anything:
   ```
   mkdir C:\RegBackup
   ```
   ```
   copy C:\Windows\System32\config\SYSTEM C:\RegBackup\
   ```
   ```
   copy C:\Windows\System32\config\SOFTWARE C:\RegBackup\
   ```
3. Check whether restore copies exist:
   ```
   dir C:\Windows\System32\config\RegBack
   ```
4. **If the files are 0 bytes, stop — there is nothing to restore.** Skip to Step 7.
5. If they have real sizes, copy them over:
   ```
   copy C:\Windows\System32\config\RegBack\* C:\Windows\System32\config\
   ```
   Answer `A` to overwrite all.
6. Restart.

## Step 7: Use System Restore
Often the fastest route back, and it restores the registry as part of the snapshot.

1. In **Advanced options**, choose **System Restore**.
2. Pick a restore point dated before the crashes started.
3. Confirm and let it run without interrupting.
4. Documents are untouched; programs installed after that point are removed.
5. If no restore points exist, create them in future: [create a system restore point](https://www.mytechnician.tech/tips/create-system-restore-point-windows-11/).

## Step 8: Uninstall the Update That Caused It
1. In **Advanced options**, choose **Uninstall Updates**.
2. Try **Uninstall latest quality update** first. Use **Uninstall latest feature update** only if the crashes began after a version upgrade.
3. Restart.
4. Then pause updates until a newer build ships: [fix Windows 11 after a bad update](https://www.mytechnician.tech/tips/fix-windows-11-after-bad-update-rollback/) and [stop Windows 11 automatic updates](https://www.mytechnician.tech/tips/stop-windows-11-automatic-updates/).

## Step 9: Run Disk and System File Repairs Offline
1. From **Command Prompt** in recovery:
   ```
   chkdsk C: /f /r
   ```
2. Then run SFC against the offline installation:
   ```
   sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows
   ```
3. And repair the image:
   ```
   DISM /Image:C:\ /Cleanup-Image /RestoreHealth
   ```
4. Drive letters in recovery often differ from those in Windows — run `diskpart` → `list volume` → `exit` to confirm which letter holds Windows before running these.
5. Once back in Windows, repeat properly: [how to run SFC and DISM](https://www.mytechnician.tech/tips/how-to-run-sfc-dism-repair-windows-11/).

## Step 10: Test the RAM
Corrupt reads into memory damage the registry as it is written.

1. Back in Windows, press **Windows + R** → `mdsched.exe` → **Restart now and check for problems**.
2. Press **F1** during the test and choose the **Extended** mix.
3. Confirm with **MemTest86** from USB over four or more passes.
4. Related: [fix MEMORY_MANAGEMENT BSOD](https://www.mytechnician.tech/tips/fix-memory-management-bsod-windows-11/).

## What Not to Do
* **Don't overwrite registry hives without backing up the current ones first.** Step 6 makes that copy for a reason — a bad restore leaves the PC unbootable with no way back.
* **Don't reset the PC before trying System Restore and Uninstall Updates.** Both are non-destructive and fix this stop code most of the time.
* **Don't run `bcdboot` against the wrong volume.** Confirm letters with `diskpart` first.

## Still Not Working?
If BCD is rebuilt, restore points fail, and the registry hives cannot be repaired, do a repair install that keeps files and programs: [reinstall Windows without losing data](https://www.mytechnician.tech/tips/reinstall-windows-without-losing-data/). If Windows will not start far enough for that, copy your data off from the recovery Command Prompt with `robocopy` before anything else, then clean install: [how to clean install Windows 11](https://www.mytechnician.tech/tips/how-to-clean-install-windows-11/).

Related: [fix CRITICAL_PROCESS_DIED](https://www.mytechnician.tech/tips/fix-critical-process-died-windows-11/) and [how to use Event Viewer to find why your PC crashed](https://www.mytechnician.tech/tips/how-to-read-event-viewer-find-crash-cause/).

---
Source: https://www.mytechnician.tech/tips/fix-bad-system-config-info-windows-11/ — My Technician, free Windows 10/11 troubleshooting guides.
Related tool: PC-Troubleshooter (PC-Troubleshooter is a system diagnostic and repair tool for Windows 10 and Windows 11—hardware, drivers, network, and common fixes in one app.) — https://www.mytechnician.tech/apps/windows-troubleshooter/
More guides: https://www.mytechnician.tech/llms.txt