ErrorBase
Independent technical referenceOfficial site
  • Software and digital services
  • Operating system

BAD_SYSTEM_CONFIG_INFO

BAD_SYSTEM_CONFIG_INFO (0x74) on Windows: registry error

Verified with sources3 sourcesReviewed Oct 4, 2026
Technician coming? See the 2 steps they must show you

Risk level

High

Professional inspection is recommended.

Urgency

High

Quick answer

Windows stopped because of a registry error: critical keys are missing or the SYSTEM hive is damaged. Start in Safe Mode, restart normally and, if that fails, use a restore point before thinking about a reset.

Safety first

Stop and check this first

  • Do not edit the registry or use registry cleaners to try to fix it: Microsoft names manual editing as one of the causes of this code.
  • If the recovery options ask for the BitLocker recovery key, do not try random keys: look for it only in your Microsoft account (aka.ms/myrecoverykey), your work or school account, a printout or the USB drive where you saved it. Microsoft support cannot retrieve it.

Safe checks you can perform

  • Safe Mode and a normal restart
  • Free space and file check
  • Restore to an earlier point

Leave these tasks to a qualified professional

  • Do not attempt this professional task: Analyse the dump and the registry
  • Do not attempt this professional task: Recover data before resetting

What a technician must be able to justify

Technician visit

These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.

These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.

  1. Analyse the dump and the registry

    What they doThe technician runs !analyze -v, looks up the parameter 4 NT status with !error and reviews loaded hives and open keys with !reg hivelist and !reg openkeys.

    They must show youthe output with the NT status and the affected hive.

    In writingwhich key or hive was damaged and how it was recovered.

  2. Recover data before resetting

    What they doIf a reset or reinstall from installation media is needed, the technician first copies your files from the recovery environment or with the drive in another PC.

    They must show youthe list of files recovered before resetting.

    In writingwhich recovery option was used and which data was kept.

Before accepting a part or repair

Nothing has been shown yet. Do not accept a part swap based on the code alone.

Follow these steps

Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.

  1. Safe Mode and a normal restart

    No special tools

    Who:
    you.
    How:
    if Windows will not start, open the recovery options and start in Safe Mode; then restart normally.
    Result that matters:
    whether normal startup works again.
    If it works:
    starting in Safe Mode fixed the problem; watch for a repeat.
    If 0x74 returns:
    Microsoft considers the registry damage more extensive.
    Evidence to keep:
    date and result of each start.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO

  2. Free space and file check

    No special tools

    Who:
    you, from Safe Mode if needed.
    How:
    check the system drive has enough free space and run SFC /scannow from a Command Prompt as administrator.
    Result that matters:
    whether SFC finds and repairs damaged files.
    If it repairs files and the crash stops:
    Windows files were damaged.
    If not:
    go on to the restore point.
    Evidence to keep:
    screenshot of the SFC result and free space.

    Evidence: Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO

  3. Restore to an earlier point

    No special tools

    Who:
    you.
    How:
    in the recovery options, Troubleshoot, Advanced options, System Restore, pick a point from before the first crash.
    Result that matters:
    whether a suitable point exists and Windows starts afterwards.
    If it starts:
    the registry change came after that point.
    If there is no point or it fails:
    the next options (reset or reinstall) can erase data; ask a technician first.
    Evidence to keep:
    date of the point used.

    Evidence: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO

Still not solved

If the error persists, stop here. See what the technician must do and show you.

Where this code applies

A code is meaningful only inside the right product and version context.

Primary scope

System
Software and digital services
Brand
Microsoft Windows
Product type
Operating system

Known code variants

  • 0x00000074
  • 0x74
  • BAD SYSTEM CONFIG INFO
  • STOP 0x00000074
  • stop code BAD_SYSTEM_CONFIG_INFO

What it means

Microsoft defines bug check 0x00000074 as an error in the registry. It can happen when the SYSTEM hive is corrupt, which is unlikely because the boot loader checks the hive when loading it, or when critical keys and values are missing, for example because someone edited the registry manually or an application or service corrupted it. Parameter 4 may give an NT status code with more detail. The code points to the Windows registry, not a hardware fault.

Warnings and stop conditions

  • Higheditorial warning

    Do not edit the registry or use registry cleaners to try to fix it: Microsoft names manual editing as one of the causes of this code.

    Evidence: Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO

  • Highsource verified

    If the recovery options ask for the BitLocker recovery key, do not try random keys: look for it only in your Microsoft account (aka.ms/myrecoverykey), your work or school account, a printout or the USB drive where you saved it. Microsoft support cannot retrieve it.

    Evidence: Find your BitLocker recovery key

Symptoms and causes

Probable causes · in order

  • Manual registry editingCommon

    Microsoft names manual editing as a source of missing critical keys; suspect it if someone changed the registry or used a cleaning tool before the failure.

    Evidence: Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO

  • Application or service that corrupted the registryPossible

    You can tell because the failure began after installing or removing a program, and the event log may name the affected hive or key.

    Evidence: Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO

  • Corrupt SYSTEM hiveLess common

    Microsoft considers it unlikely because the loader checks the hive when loading it; dump analysis confirms it.

    Evidence: Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO

Virtual technician

Does BAD_SYSTEM_CONFIG_INFO still appear after these checks?

Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.

Start diagnosis

Sources and technical references

  1. 1

    Troubleshooting Windows unexpected restarts and stop code errors

    Microsoft · 2026 · official_doc

  2. 2

    Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO

    Microsoft · 2026 · official_doc

  3. 3

    Find your BitLocker recovery key

    Microsoft · 2026 · official_doc

Sources: Troubleshooting Windows unexpected restarts and stop code errors · Bug Check 0x74 BAD_SYSTEM_CONFIG_INFO · Find your BitLocker recovery keyreviewed 2026-10-04 · verified

Was this entry useful?