BAD_SYSTEM_CONFIG_INFO is a Windows stop code that appears when Windows finds a problem in its configuration data, most often a corrupt registry or damaged boot configuration data (BCD). It can also come from a faulty driver or failing RAM. Windows stops because the settings it needs to run correctly are damaged or inconsistent, so it cannot continue safely.
Why this happens
The registry and boot data tell Windows how to start and what to load. When those become corrupt or point to something invalid, this error appears. Common causes include:
- A corrupt registry, often after an improper shutdown, power loss, or failed update.
- Damaged or misconfigured boot configuration data.
- A faulty or outdated driver.
- Recently installed software or hardware that changed system settings.
- Failing RAM or a failing drive corrupting the configuration files.
Is this normal?
No. This is a fatal error, not normal behavior. It often shows up after a rough shutdown or an interrupted update, and a single event may clear on reboot, but repeated crashes mean the configuration data needs repair.
Does it cause any problems?
Yes. It forces a restart and can leave the PC unable to boot if the boot data is damaged. Because it involves the registry, it can also cause other odd behavior until the underlying corruption is fixed.
How to fix or check it
- Restart first, since a one-time glitch sometimes clears on the next boot.
- If it began recently, use System Restore to go back to a point before the problem, from the recovery menu if you cannot boot.
- Repair system files: open Command Prompt as administrator and run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth.
- Rebuild boot data from a recovery Command Prompt: run bootrec /repairbcd, bootrec /osscan, and bootrec /rebuildbcd if the PC will not boot.
- Run chkdsk C: /f /r to fix disk errors that can corrupt configuration files.
- Update or roll back drivers you changed just before the crashes, especially if you can only work in Safe Mode.
- Test memory with Windows Memory Diagnostic or MemTest86, since bad RAM can corrupt this data.
- If nothing else works and your files are backed up, a repair install of Windows restores a clean configuration.
Frequently asked questions
Is the registry always the cause?
A corrupt registry or boot data is the most common cause, but the same error can come from a bad driver or failing RAM. Run the file, disk, and memory checks to confirm which it is.
Can I fix it if Windows will not boot?
Yes. Boot from a recovery drive or interrupt startup three times to reach the recovery menu, then use Startup Repair, System Restore, or Command Prompt to run the repairs.
Will I lose my files fixing this?
Most repairs, including sfc, DISM, chkdsk, and rebuilding boot data, do not delete your files. A clean install would, so back up first and try the repairs before resorting to that.