If you’re seeing the “Bad System Config Info” blue screen on Windows 10, the fix usually involves repairing corrupted system registry hives or driver issues—start by running the built-in Startup Repair tool, then check for recent driver or Windows updates. This error typically appears during boot and prevents Windows from loading normally, but it’s often recoverable without reinstalling the OS. Below, I’ll walk you through the most effective fixes, explain why the error happens, and answer common questions.
What Causes the Bad System Config Info Error?
The “Bad System Config Info” stop code (0x00000074) indicates that Windows cannot read or parse one of its critical registry hive files—specifically the SYSTEM hive, which stores hardware and driver configuration. This can happen for several reasons:
- Corrupted or missing registry files after an improper shutdown or power loss
- A recent driver update that wrote invalid configuration data
- Disk errors on the system drive (bad sectors or file system corruption)
- Interrupted Windows Update installation
- Third-party software that modifies system settings (e.g., registry cleaners)
The registry hive is a binary file that Windows reads at boot. If even a few bytes are corrupted, the boot process fails and triggers the BSOD.
Before You Start: Boot into Recovery Environment
Most fixes require access to the Windows Recovery Environment (WinRE). If the BSOD loops, Windows should automatically enter WinRE after a few failed boot attempts. If not, you can force it by powering the PC off and on three times—turn it on, wait until the Windows logo appears, then hold the power button to shut down. Repeat this three times, and on the fourth boot, Windows should load the recovery menu.
Once in WinRE, go to Troubleshoot > Advanced options. From there, you can access Startup Repair, Command Prompt, System Restore, and other tools. If you have a Windows 10 installation USB, you can also boot from it and select “Repair your computer” on the first screen.
Fix 1: Run Startup Repair
Startup Repair is the easiest first attempt. It scans for common boot problems—including registry corruption—and tries to fix them automatically.
- In WinRE, go to Troubleshoot > Advanced options > Startup Repair.
- Select your account and enter the password if prompted.
- Wait for the repair to complete. It may take several minutes.
- Restart the PC and see if Windows boots normally.
If Startup Repair says it couldn’t fix the problem, move on to the next steps.
Fix 2: Use System Restore
System Restore rolls back system files, registry settings, and drivers to an earlier point in time—without affecting your personal files. This is especially useful if the error started after a recent driver or software installation.
- In WinRE, go to Troubleshoot > Advanced options > System Restore.
- Choose a restore point that predates the problem. If none exist, you’ll need to try other fixes.
- Follow the prompts and let the restore complete.
- After the restart, check if the BSOD is gone.
Note: System Restore only works if you had restore points enabled and created—it’s not a guaranteed option on every system.
Fix 3: Repair the Registry with Command Prompt
If Startup Repair and System Restore fail, you can manually replace the corrupted SYSTEM hive with a backup copy that Windows keeps automatically. This is a more advanced step but often resolves the issue.
- In WinRE, go to Troubleshoot > Advanced options > Command Prompt.
- Type
diskpartand press Enter. - Type
list volumeand press Enter. Note the drive letter of your Windows partition (usually C:, but it might be D: in WinRE). - Type
exitto leave DiskPart. - Run the following commands, replacing
C:with your Windows drive letter if different:cd /d C:\Windows\System32\configren SYSTEM SYSTEM.oldcopy C:\Windows\System32\config\RegBack\SYSTEM SYSTEM - Type
exitto close Command Prompt, then restart your PC.
The RegBack folder contains a backup of the registry hives that Windows updates regularly. If the copy fails because the file doesn’t exist, you may need to try a different fix or use the installation media to repair the system.
Fix 4: Check Disk for Errors
Corrupted disk sectors or file system errors can also cause this BSOD. Running chkdsk from the Command Prompt can find and repair these issues.
- Open Command Prompt from WinRE as described above.
- Type
chkdsk /f /r C:(replace C: with your Windows drive) and press Enter. - If prompted, type
Yto schedule the check on the next restart, then exit and restart. - Windows will scan the drive and attempt to fix errors. This can take a long time, so be patient.
If chkdsk finds and repairs errors, the BSOD may not appear again.
Fix 5: Update or Roll Back Drivers
Sometimes the error is caused by a specific driver—especially storage, graphics, or chipset drivers. If you can boot into Safe Mode (Shift + Restart from the login screen, or via WinRE > Troubleshoot > Advanced options > Startup Settings > Restart > 4), you can try:
- Open Device Manager and check for devices with a yellow exclamation mark.
- Right-click the device and select Update driver to install the latest version.
- If the problem started after a recent driver update, go to Driver Properties > Driver tab and click Roll Back Driver.
You can also use Windows Update to install any pending updates, which often include driver fixes.
Fix 6: Reset This PC (Last Resort)
If none of the above work, you may need to reset Windows. This reinstalls the OS while optionally keeping your personal files. Go to Troubleshoot > Reset this PC in WinRE and choose Keep my files (or Remove everything if you have backups). This will replace system files and registry hives with fresh copies, which almost always resolves the BSOD.
Frequently Asked Questions
Can I prevent the Bad System Config Info error?
Yes, to a degree. Always shut down Windows properly, avoid force power-offs, keep your system drive healthy with regular chkdsk scans, and create restore points before installing major drivers or updates. Also, avoid using registry cleaners that can accidentally delete critical entries.
Will I lose my files if I run Startup Repair?
No, Startup Repair only attempts to fix boot problems—it doesn’t touch your personal files. System Restore also doesn’t affect your documents, photos, or other user data. Only a full reset with “Remove everything” will delete files.
What if I don’t have a restore point?
If System Restore isn’t available, you can still try the registry repair method (Fix 3) or the chkdsk method (Fix 4). If those fail, you might need to use a Windows 10 installation USB to perform a repair install, which keeps your files and apps but replaces system files.
Is this error related to a hardware failure?
Rarely, but possible. A failing hard drive or SSD can cause file corruption that triggers this BSOD. If chkdsk reports bad sectors or the error persists after a reset, consider testing your drive with the manufacturer’s diagnostic tool or replacing it.
Can I boot into Safe Mode to fix this?
Yes, if you can access Safe Mode, you can try uninstalling recent drivers, running System File Checker (sfc /scannow), or using Device Manager to roll back drivers. To enter Safe Mode, use WinRE > Troubleshoot > Advanced options > Startup Settings > Restart > press 4.
Does this error appear on Windows 11 too?
Yes, the same stop code exists on Windows 11, and the fixes are essentially identical. The steps above apply to both operating systems.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- How to View Wi-Fi Password on iPhone
- How to Stream on Twitch from PC
- GTM vs Facebook Pixel: What’s the Difference?
- Windows 10 Won’t Boot? Fix It in 30 Minutes
- Ubuntu 26.04 LTS Requirements & Hardware Checks
- ATK0100 Driver: Do You Need to Install It?