Skip to content
PCDecoder
0x00000074BAD_SYSTEM_CONFIG_INFOStop codeWidely reported

BAD_SYSTEM_CONFIG_INFO (0x74): what it means and how to fix it

Updated Oct 11, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

Stop code 0x00000074, known as BAD_SYSTEM_CONFIG_INFO, indicates that Windows cannot load critical registry configuration files during startup. The error typically happens when the SYSTEM registry hive is corrupted or essential keys have been deleted. The first step to try is booting into Safe Mode and restarting your computer normally.

What it means

Windows relies on system registry files to configure hardware, mount drives, and load device drivers during the startup process. When bug check 0x00000074 (BAD_SYSTEM_CONFIG_INFO) appears, Windows has detected that its configuration data cannot be read correctly or is structurally invalid.

What happens during startup

Early in the boot sequence, the Windows boot loader reads the SYSTEM registry hive from your primary drive. The boot loader inspects this hive to confirm it is readable before passing control to the operating system kernel. If critical registry keys are missing, or if the internal layout of the file is damaged, startup halts with a blue screen. Diagnostic logs for this bug check often record an NT status code in parameter 4, such as 0xc000014c, which signifies that the file structure containing registry data is corrupt or unrecoverable.

Why configuration hives fail

Registry data can become corrupt when an application, background service, or driver writes invalid entries to the system files. Sudden power cuts or running critically low on hard drive or SSD storage space can interrupt disk writes and leave configuration files partially written. Manual edits, such as deleting keys using registry editing utilities, can also strip away entries that the boot loader expects to find.

System event logs may record specific events identifying the exact hive or key involved in the failure. When the operating system cannot load these settings, standard recovery steps—such as starting Safe Mode to rebuild temporary configurations or using System Restore—are necessary to bring the registry back to an undamaged state.

Common causes

  • A corrupted SYSTEM registry hive file on the boot drive.
  • Critical registry keys or values missing due to manual editing or third-party tools.
  • Registry data corrupted by a misbehaving application or background service.
  • Insufficient free storage space on the primary SSD or hard drive preventing proper file updates.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Boot into Safe Mode and restart normally

    Try this first, as booting into Safe Mode forces Windows to refresh registry handles and can resolve minor configuration faults.

    1. Power on your PC and hold the power button for 10 seconds as soon as the Windows logo appears to interrupt startup. Repeat this twice more to trigger the Automatic Repair screen.
    2. Select Advanced options on the repair screen.
    3. Navigate to Troubleshoot, then Advanced options, then Startup Settings, and click Restart.
    4. Press 4 or F4 to choose Enable Safe Mode.
    5. Sign in to your account once Safe Mode loads, open the Start menu, and restart the computer normally.
    Did this fix it?

  2. Free up storage space on the Windows drive

    Use this if your main drive has little to no free storage left, which prevents Windows from writing configuration files.

    1. Access the Automatic Repair screen and choose Troubleshoot, then Advanced options, then Command Prompt.
    2. Check available space on your primary Windows drive.
    3. Remove large unneeded installation files or temporary directories using command-line commands if the drive is full.
    4. Reboot the system to see if the operating system can load its hives with adequate free storage.
    Did this fix it?

  3. Run the System File Checker tool

    Use this when Windows cannot boot normally and you need to verify the integrity of protected system files.

    1. Select Advanced options from the Automatic Repair screen.
    2. Click Troubleshoot, select Advanced options, and choose Command Prompt.
    3. Type sfc /scannow and press Enter.
    4. Allow the scan to reach 100 percent completion.
    5. Close the Command Prompt window and restart your computer.
    Did this fix it?

  4. Restore Windows to an earlier restore point

    Use this if you recently installed new software or modified settings and have a restore point saved.

    1. From the Automatic Repair menu, select Advanced options.
    2. Click Troubleshoot, then select Advanced options.
    3. Choose System Restore from the list of tools.
    4. Select a restore point date that predates the blue screen crashes.
    5. Follow the prompts to restore the configuration and restart your PC.
    Did this fix it?

  5. Reset your PC or reinstall Windows

    Use this as a final step when registry damage is too severe for automated repair utilities to fix.

    1. Open the Troubleshoot menu from the Automatic Repair screen.
    2. Select Reset this PC and pick whether to keep your personal files or wipe the drive.
    3. If the recovery partition fails, insert a USB drive containing Windows installation media and boot from it.
    4. Select your language preferences, click Next, and choose Repair your computer, or proceed with a clean installation of Windows.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 9, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What is the BAD_SYSTEM_CONFIG_INFO blue screen?

It is Windows stop code 0x00000074, which means the operating system encountered a corrupted registry hive or could not find required configuration keys while starting up.

Can low disk space cause error 0x74?

Yes. Windows requires adequate free hard drive or SSD space to update system hives, and running out of storage can lead to corrupted registry files.

Does stop code 0x74 mean my hard drive is broken?

Not necessarily. The error indicates logical corruption inside Windows registry files, which is commonly caused by software errors, failed updates, or abrupt shutdowns rather than physical hardware failure.

More stop codes decoded