CONFIG_LIST_FAILED Blue Screen Error 0x00000073: Causes and Troubleshooting

Quick Answer

CONFIG_LIST_FAILED (0x00000073) is a Windows Blue Screen of Death (BSOD) error that occurs when Windows cannot link one of its core registry hives into the registry tree during system initialization.

The affected hive may be SAM, SECURITY, SOFTWARE, or DEFAULT. Microsoft identifies insufficient system-drive space and insufficient system resources as possible causes. The second bug check parameter provides an important clue about the underlying failure.

To troubleshoot this error, examine the bug check parameters, check available disk space, investigate storage and memory problems, and use Windows Recovery Environment if Windows cannot start.

What Does CONFIG_LIST_FAILED Mean?

Windows uses the Registry to store configuration information required by the operating system, hardware, drivers, services, and applications.

The Registry contains important system files called registry hives:

• SAM: Stores information associated with local user and group accounts.
• SECURITY: Stores Windows security configuration information.
• SOFTWARE: Stores configuration information for Windows and installed software.
• DEFAULT: Contains the default user profile configuration used by the system.

During startup, Windows must load and organize these hives into its registry tree. CONFIG_LIST_FAILED occurs when a core hive cannot be linked into that tree.

This error does not necessarily mean that the registry hive is corrupted. Microsoft explains that a hive may load successfully while the subsequent linking operation fails.

CONFIG_LIST_FAILED Bug Check Parameters

Important NT status codes

These are documented examples, not an exhaustive list. Parameter 4 is a memory pointer and requires appropriate debugging context for interpretation.

Common Causes

1. Insufficient system-drive space

Windows may need additional space for registry operations. A nearly full system volume can cause registry log operations to fail.

2. Insufficient memory resources

Windows may fail to allocate the memory pool resources required to complete registry initialization.

3. Storage problems

Disk errors, SSD problems, file-system inconsistencies, or storage-controller issues may contribute to startup failures.

4. Unexpected shutdown

Power failures or interrupted write operations can leave Windows in an unstable state.

5. Other system resource failures

Other NT status codes may indicate different underlying resource or system-operation failures.

Before You Begin

• Disconnect unnecessary external USB devices.
• Back up important files if Windows starts intermittently.
• Record the complete stop code and its parameters.
• Check whether the problem started after a driver, software, hardware, or Windows update.
• Keep the BitLocker recovery key available if device encryption is enabled.

How to Fix CONFIG_LIST_FAILED

Solution 1: Check available disk space

1. Press Windows + E to open File Explorer.
2. Select This PC.
3. Locate the Windows installation drive, usually C:.
4. Check its available free space.
5. Remove unnecessary temporary files and backed-up files if the drive is nearly full.
6. Empty the Recycle Bin if appropriate.
7. Restart Windows.

This is particularly relevant when Parameter 2 contains 0xC000017D.

Solution 2: Disconnect recently installed hardware

1. Shut down the computer.
2. Disconnect recently added USB devices, external drives, and docking stations.
3. Keep essential peripherals connected.
4. Start the computer again.
5. Reconnect devices individually if Windows starts normally.

Solution 3: Start Windows in Safe Mode

1. Enter Windows Recovery Environment.
2. Select Troubleshoot.
3. Open Advanced options.
4. Select Startup Settings.
5. Choose Restart.
6. Select Safe Mode after restarting.
7. Investigate recently installed drivers and software.

Solution 4: Run Startup Repair

1. Enter Windows Recovery Environment.
2. Select Troubleshoot.
3. Select Advanced options.
4. Choose Startup Repair.
5. Select the Windows installation if prompted.
6. Follow the on-screen instructions.
7. Restart after the repair finishes.

Startup Repair can address certain startup problems but is not guaranteed to resolve every CONFIG_LIST_FAILED occurrence.

Solution 5: Use System Restore

1. Open Windows Recovery Environment.
2. Select Troubleshoot and Advanced options.
3. Choose System Restore.
4. Select an available restore point created before the problem began.
5. Review affected programs if available.
6. Confirm the restoration.
7. Restart Windows.

System Restore requires an available restore point and is not intended to restore personal documents.

Solution 6: Check the storage device

If Windows starts, open Command Prompt as administrator and run:

chkdsk C: /scan

Replace C: if Windows is installed on another volume. This command scans an NTFS volume for file-system problems.

Review the results before performing additional repairs. If the drive is physically failing, prioritize data recovery.

Solution 7: Analyze the memory dump

Advanced users and system administrators can investigate the bug check using WinDbg and an available memory dump.

Examine:

• The second parameter and its NT status code.
• The third parameter identifying the hive-list index.
• The fourth parameter pointing to the hive filename structure.
• Relevant memory and system information in the dump.

Do not assume registry corruption without supporting diagnostic evidence.

What to Do If Windows Cannot Start

If Windows repeatedly displays the error, access Windows Recovery Environment.

1. Connect Windows installation media or a recovery drive.
2. Boot the computer using the firmware boot menu.
3. Select the language and keyboard preferences.
4. Choose Repair your computer.
5. Select Troubleshoot.
6. Open Advanced options.
7. Use Startup Repair or System Restore as appropriate.

Do not select Install Windows unless you have deliberately chosen to reinstall the operating system and have protected your data.

Advanced Registry Recovery Considerations

Manual registry hive restoration should not be the first troubleshooting step. Establish the affected hive, NT status code, available disk space, and storage-device health before considering manual recovery.

Never copy SAM, SECURITY, SOFTWARE, or DEFAULT hive files from another computer. These files contain system-specific configuration and security information.

Use a documented recovery procedure appropriate to the exact Windows installation. Consult an experienced Windows administrator when manual registry recovery is necessary.

How to Verify the Fix

• Windows starts without displaying CONFIG_LIST_FAILED.
• The computer completes multiple normal restarts.
• The system drive has adequate free space.
• Storage diagnostics do not report unresolved problems.
• Important applications and user accounts work normally.
• The same stop code does not recur.

Frequently Asked Questions

1. What is Windows error 0x00000073?

It is the CONFIG_LIST_FAILED bug check. Windows cannot link a core registry hive into its registry tree during initialization.

2. Does CONFIG_LIST_FAILED always mean registry corruption?

No. The affected hive may have loaded successfully. The failure can occur during the subsequent linking operation.

3. What does STATUS_NO_LOG_SPACE mean?

It indicates insufficient space for the required registry log operation. Check available space on the Windows system volume.

4. What does STATUS_INSUFFICIENT_RESOURCES mean?

It indicates that Windows could not obtain the system resources required to complete an operation. Memory pool allocation failure is one documented possibility.

5. Can Startup Repair fix this error?

Startup Repair may resolve certain startup problems, but it cannot guarantee a fix for every occurrence.

6. Can I manually replace registry hive files?

Manual replacement is not recommended as a general solution. Incorrect registry files can cause additional startup and security problems.

7. Can a faulty SSD cause this error?

Storage problems should be investigated when diagnostic results indicate drive or file-system errors. However, a faulty SSD is not established as the cause of every occurrence.

Conclusion

CONFIG_LIST_FAILED (0x00000073) is a Windows initialization error associated with the inability to link a core registry hive into the registry tree. Insufficient system-drive space and memory resource allocation failures are two documented causes.

Examine the bug check parameters, check available disk space, investigate storage and system resources, and use appropriate Windows recovery options. Avoid unnecessary registry modifications and destructive repair procedures. Identifying the actual failure condition is essential to choosing the correct recovery method.

Sources

• Microsoft Learn – Bug Check 0x73: CONFIG_LIST_FAILED
• Microsoft Support – Windows Recovery Environment
• Microsoft Support – System Restore
• Microsoft Learn – Analyze a Kernel-Mode Dump File with WinDbg