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 for how to get there. Different stop code each time? Start at how to fix a BSOD.

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

If Windows boots to the desktop, use Settings → System → Recovery → Advanced startup → Restart now.
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.
Choose Advanced options → Troubleshoot → Advanced options.
From here you can reach Startup Repair, Command Prompt, System Restore, and Uninstall Updates.
If the loop never reaches this menu: fix the automatic repair loop.

Step 2: Try Startup Repair First

In Advanced options, click Startup Repair.
Select your account and enter the password if prompted.
Let it run — it can take 15-30 minutes and may restart on its own.
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.

In Advanced options, choose Command Prompt.
Run these in order, answering Y when asked to add the installation to the boot list:
```
bootrec /repairbcd
```
```
bootrec /osscan
```
```
bootrec /rebuildbcd
```
Restart and see whether Windows starts.
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.

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

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.

From Command Prompt:
```
bcdedit /enum {default}
```

If you see truncatememory or removememory listed, delete them:

bcdedit /deletevalue {default} truncatememory

bcdedit /deletevalue {default} removememory

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.
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.

In Command Prompt:
```
cd C:\Windows\System32\config
```
```
dir
```

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\

Check whether restore copies exist:
```
dir C:\Windows\System32\config\RegBack
```
If the files are 0 bytes, stop — there is nothing to restore. Skip to Step 7.

If they have real sizes, copy them over:

copy C:\Windows\System32\config\RegBack\* C:\Windows\System32\config\

Answer A to overwrite all.

Restart.

Step 7: Use System Restore

Often the fastest route back, and it restores the registry as part of the snapshot.

In Advanced options, choose System Restore.
Pick a restore point dated before the crashes started.
Confirm and let it run without interrupting.
Documents are untouched; programs installed after that point are removed.
If no restore points exist, create them in future: create a system restore point.

Step 8: Uninstall the Update That Caused It

In Advanced options, choose Uninstall Updates.
Try Uninstall latest quality update first. Use Uninstall latest feature update only if the crashes began after a version upgrade.
Restart.
Then pause updates until a newer build ships: fix Windows 11 after a bad update and stop Windows 11 automatic updates.

Step 9: Run Disk and System File Repairs Offline

From Command Prompt in recovery:
```
chkdsk C: /f /r
```

Then run SFC against the offline installation:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

And repair the image:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth

Drive letters in recovery often differ from those in Windows — run diskpart → list volume → exit to confirm which letter holds Windows before running these.
Once back in Windows, repeat properly: how to run SFC and DISM.

Step 10: Test the RAM

Corrupt reads into memory damage the registry as it is written.

Back in Windows, press Windows + R → mdsched.exe → Restart now and check for problems.
Press F1 during the test and choose the Extended mix.
Confirm with MemTest86 from USB over four or more passes.
Related: fix MEMORY_MANAGEMENT BSOD.

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. 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.

How to Fix BAD_SYSTEM_CONFIG_INFO in Windows 11