What BAD_SYSTEM_CONFIG_INFO means
Bug check 0x74 indicates an error in the registry. Microsoft says it can occur if the SYSTEM registry hive is corrupt, although that is unlikely because the boot loader checks the hive when it loads it. It can also occur when critical registry keys or values are missing, for example after someone edited the registry by hand or an application or service damaged it.
Common causes
- Manual registry edits or a registry “cleaner” that removed an important key
- An application or service that corrupted the registry
- Registry data damaged by an interrupted update or an unclean shutdown
- A failing drive, or a drive with too little free space for Windows to work
How to fix BAD_SYSTEM_CONFIG_INFO
Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.
- Look for registry events in Event Viewer. If Windows starts, open Event Viewer, then Windows Logs, System, and look for registry-related errors around the time of the crash. An event that names a hive or key tells you where to focus.
- Undo the most recent change. If the blue screens began after a Windows update, a new driver or new software, remove that change first. Uninstall the update from Settings, Windows Update, Update history, or roll a driver back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver). If the crash followed a registry edit or a registry-cleaning tool, reverse that change or restore from a restore point.
- Repair Windows system files. Open Terminal (Admin) and run
sfc /scannow. If it reports damage it could not repair, runDISM /Online /Cleanup-Image /RestoreHealth, restart, and runsfc /scannowonce more. - Check free space and drive health. Microsoft advises confirming that the drive has enough free space for Windows to function normally. Check the drive’s SMART health too, because a failing drive can corrupt registry files.
- Try Safe Mode, then restore. Boot into Safe Mode and restart normally. If the crash continues, use System Restore with a restore point from before the problem. If that fails, use the Reset this PC option or Windows installation media to repair or reinstall, with your files backed up first.
Reading the crash evidence for 0x74
Microsoft’s reference says the first three parameters are reserved and the fourth holds an NT status value, when available. That status often names the cause directly: 0xC000014C, for example, is the code for “the registry is corrupt”.
If Windows will not start, you can read the stop code and the status from the blue screen photo or from the minidump after repairing the PC. Booting from Windows installation media and choosing Repair is a safer route than editing the registry offline.
| What you observe | What it may suggest | Next check |
|---|---|---|
| The crash followed a registry edit or cleaner | A critical key or value is missing | Restore from a restore point from before the change |
| The status in the fourth parameter is 0xC000014C | A registry data file is corrupt or could not be recovered | Restore or repair using installation media |
| The drive is nearly full | Windows may lack space to work and write registry data | Free space, then rerun System File Checker |
| Disk errors appear in Event Viewer | The drive may be damaging registry files | Check drive health and back up data |
Source: Microsoft Learn: Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO ↗
If the registry is too damaged to restore, Microsoft’s own guidance runs from a restore point to resetting the PC and finally reinstalling Windows from installation media. Back up what you can before each step, and replace the drive if it reports errors.
Not sure this is your code?
The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.
Related guides
Other start-up and boot errors
- INACCESSIBLE_BOOT_DEVICE (0x7B)
- UNMOUNTABLE_BOOT_VOLUME (0xED)