BAD_SYSTEM_CONFIG_INFO: Stop Code 0x00000074
Stop code 0x00000074 means the SYSTEM registry hive or boot configuration is damaged. Startup Repair, BCD checks and System Restore, least destructive first.
The machine stops during the boot sequence, before the sign-in screen, with a blue screen whose text reads BAD_SYSTEM_CONFIG_INFO and a stop code of 0x00000074. The code is produced by the kernel while it is loading the registry: specifically, while it reads the SYSTEM hive, the file that holds the services, drivers and hardware configuration the kernel needs before anything else can start. If that hive cannot be read, is internally inconsistent, or points at a boot device that is no longer where it was, the kernel has nothing to hand control to and halts with this code. The failure is therefore almost always a storage or configuration problem rather than a dead processor or a failed graphics card. The disk may be perfectly healthy and the fault may be a single damaged registry file or a boot entry that names the wrong partition.
The same code appears in two situations that look identical on screen. In the first, the hive file itself is corrupt or truncated. In the second, the hive is intact but the boot configuration data (BCD) tells Windows to load it from a volume that no longer exists, has changed drive letter, or has been replaced. Both produce 0x00000074, and the repairs overlap, so the order below starts with the least destructive checks and only reaches the registry files after the boot path has been ruled out.
What the kernel is doing when 0x00000074 appears
Windows Setup and the normal boot process both read the SYSTEM hive early. The hive is a transaction-logged file; if the log and the hive disagree, or if the hive’s checksum fails, the loader refuses it. A sudden power loss during a registry write, a failing sector in the middle of the hive, an interrupted update, or a cloned disk whose partition layout no longer matches the BCD can all leave the hive unreadable. The stop code is the kernel’s way of saying it reached the point where it needed the hive and could not use it.
A boot loop is the common presentation: the machine restarts, shows the code for a second or two, and restarts again. On machines with automatic restart enabled, the blue screen may flash past before it can be read. The first practical step is to stop the loop so the message stays on screen long enough to confirm the code, then work from the Windows Recovery Environment (WinRE).
Stopping the restart loop to read the code
If the machine restarts before the stop code can be read, boot into WinRE. From a working PC, create Windows installation media and start the broken machine from it, then choose Repair your computer. On a machine that still reaches the recovery menu on its own, choose Troubleshoot, then Advanced options, then Command Prompt.
Inside the recovery command prompt, disable automatic restart on failure so the next boot leaves the blue screen visible:
bcdedit /set {default} recoveryenabled No
This changes the boot entry only; it does not touch user data. The output confirms the operation completed. If the command reports that the specified entry was not found, the BCD itself is damaged and the boot-configuration section below applies first.
Ruling out the boot configuration before touching the registry
The BCD is a small store that tells the loader which partition holds Windows and which file to load. If it is wrong, the kernel can be handed a SYSTEM hive from the wrong volume or from a volume that no longer exists. Check the entries from the recovery command prompt:
bcdedit /enum
The output lists identifiers such as {default} and the device and osdevice paths. A path that names a partition which is not the one Windows is installed on, or a device entry of unknown or partition=C: when Windows lives elsewhere, points at a BCD problem rather than a corrupt hive. The repair is to rebuild the store from the installation itself, not to edit entries by hand. Identify the Windows volume and the EFI system partition first:
diskpart
Inside diskpart:
list volume
Note the letter of the volume containing the Windows folder and the letter or absence of letter on the EFI system partition. If the EFI partition has no letter, assign one:
select volume S
assign letter=S
Replace S with the number of the EFI volume from list volume. Then exit diskpart and rebuild the boot files, using the Windows volume letter in place of D:
exit
bcdboot D:\Windows /s S: /f UEFI
The output reports that boot files were copied successfully. This rewrites the EFI boot files and the BCD entries for the installation; it does not format any partition and does not touch user documents. On a legacy BIOS machine the equivalent uses the active system partition and the /s switch without /f UEFI. A guide to the related 0xC000000F boot error covers the same BCD rebuild in more detail; the two codes often appear on the same machine at different stages of a failed boot.
Startup Repair and the checks that follow it
If the BCD is correct, run Startup Repair from the recovery menu: Troubleshoot, Advanced options, Startup Repair. It examines the boot records, the BCD and the presence of the SYSTEM hive, and attempts automated fixes. It does not delete user files, but it can rewrite boot files, so a machine with a custom multi-boot layout may need its entries re-created afterwards. Run it once, note what it reports, and do not loop it repeatedly; if it finds nothing, the fault is inside the hive or on the disk and the next sections apply.
After Startup Repair, check the file system for damage that could have corrupted the hive in the first place. From the recovery command prompt, with the Windows volume letter identified:
chkdsk D: /f
The output lists the stages and any repaired indexes or bad sectors. This command can modify the file system on the volume it is given; confirm the letter is the Windows volume and not a data disk before running it. If chkdsk reports unreadable sectors in the region holding the registry, the disk is failing and the registry repair below will not hold.
System Restore before registry file surgery
System Restore rolls back registry hives, drivers and installed programs to a restore point. It does not remove personal files, but it does undo software changes made after the chosen point, including updates and application installs. From the recovery menu choose Troubleshoot, Advanced options, System Restore and select the most recent point before the failure began. If no restore points exist, the option is unavailable and the next section applies. A restore is the least destructive way to replace a damaged SYSTEM hive, because Windows supplies a consistent copy from its own backup rather than one copied by hand.
The RegBack folder and why it is usually empty
Older instructions tell the reader to copy the SYSTEM file from C:\Windows\System32\config\RegBack over the live hive. On current Windows versions that folder is no longer populated by default, so the copy either fails or replaces a damaged hive with a zero-length file and makes the boot worse. Before using it, list the folder from the recovery command prompt and check the size:
dir D:\Windows\System32\config\RegBack
If the SYSTEM entry is absent or reports 0 bytes, do not copy it. Only a non-zero SYSTEM file dated before the failure is worth restoring, and even then the copy replaces the live hive: any change made after that file was written is lost, including service and driver configuration. The command below is shown for completeness and should only be run after the size check passes:
copy D:\Windows\System32\config\RegBack\SYSTEM D:\Windows\System32\config\SYSTEM
This overwrites the current SYSTEM hive. It destroys the configuration stored in that hive since the backup was written. If the file is empty, skip it and use System Restore or a reinstall of Windows over the existing installation, which keeps personal files but removes installed programs.
When the disk is healthy and a setting is wrong
A large share of 0x00000074 cases involve no failing hardware at all. The common non-hardware causes are a BCD that points at a removed or relettered partition, a cloned drive whose identifiers no longer match, an interrupted update that left the hive half-written, and a dual-boot configuration edited by another operating system. The table separates these from genuine storage failure.
| Symptom | Likely cause | When this cause does not apply |
|---|---|---|
| BCD lists a device path that is not the Windows volume | Boot configuration wrong after clone or partition change | The path matches the installation volume |
| chkdsk reports no errors and the hive file is present | Interrupted write or update, hive internally inconsistent | chkdsk reports bad sectors or unreadable files |
| Machine worked until a disk was cloned or resized | Partition identifiers changed | No disk work preceded the failure |
| Failure follows a power loss during an update | Hive and transaction log disagree | The machine shut down cleanly |
| SMART data shows reallocated or pending sectors | Physical disk failure | Drive reports healthy and chkdsk is clean |
If the pattern points to a failing disk, stop repairing the registry and recover the data first. A drive with reallocated sectors will corrupt the replacement hive as readily as the original.
Recovering data before any destructive repair
Any step that formats a partition, deletes a volume or reinstalls Windows destroys what is on it. Before reaching that point, attach the drive to a working machine or boot the broken one from external media and copy the user folders off it. If the partition table itself is damaged, TestDisk can rebuild it from the drive’s own backup structures; it writes to the disk, so confirm the correct disk is selected before proceeding. Initializing a disk in Disk Management erases its partition table and is appropriate only for a new or unneeded disk, never for one that held data.
What to do when the hive cannot be recovered
If Startup Repair finds nothing, System Restore has no points, RegBack is empty and chkdsk is clean, the remaining option is to reinstall Windows over the existing installation from the installation media, choosing to keep personal files. This removes installed programs and settings and replaces the registry, but leaves documents in place. Back up anything important to external media first, because a failed reinstall can leave the volume in a worse state than the original fault.
Common questions
What does bad system config info mean?
It is stop code 0x00000074, produced when the kernel cannot read or validate the SYSTEM registry hive during boot. The hive holds the services and driver configuration Windows needs before the sign-in screen. The cause is usually a damaged hive file or a boot configuration that points at the wrong partition, not a failed processor.
How do I fix bad system config info boot loop?
Boot into the Windows Recovery Environment and run Startup Repair first. If that finds nothing, check the BCD entries with bcdedit /enum and rebuild them with bcdboot if the device paths are wrong. System Restore is the next step, because it replaces the hive with a consistent copy without hand-copying files.
Can I copy SYSTEM from RegBack to fix 0x00000074?
Only if the file in RegBack is present and not zero bytes. Current Windows versions no longer populate that folder by default, so the copy often replaces the damaged hive with an empty file and makes the boot fail earlier. Check the size with dir before copying anything.
Is bad system config info caused by a bad hard drive?
Sometimes. A failing sector in the middle of the hive, or a power loss during a registry write, produces the same code as a wrong boot entry. Run chkdsk on the Windows volume and check the drive's SMART data; if either shows errors, recover the data before attempting registry repairs.
Does reinstalling Windows fix bad system config info?
Yes, because a reinstall writes a new SYSTEM hive. It is the last option, after Startup Repair, a BCD rebuild, chkdsk and System Restore have all been tried. Choose to keep personal files if offered, and back up important data to external media first, since a failed reinstall can leave the volume worse.
Read next
- How to Read a Blue Screen: Stop Codes, Parameters, and Dumps Learn to decode a BSOD: what stop codes mean, how to interpret parameters, which file matters, and how to find and read the crash dump.
- STOP 0x0000007B: Inaccessible Boot Device Fix STOP 0x0000007B is a blue screen caused by a missing storage driver. Learn to fix it by adjusting BIOS settings or registry keys, without reinstalling.
- Fix Boot BCD Error 0xc000000f on Windows Learn what causes Windows boot error 0xc000000f and how to fix it. Step-by-step repair using bootrec, BCD rebuild, and firmware checks.
- Windows Boots Slowly: Measure Before You Change The event log records boot duration and startup impact ranks the culprits. Fast Startup is both a cause and a cure depending on the machine.
- Windows Event Log: Reading and Finding the Error Learn to read the Windows event log: understand levels, find critical errors, and correlate crashes with preceding events. Practical steps for Event Viewer.