CONFIG_INITIALIZATION_FAILED (0x00000067) Blue Screen Error: Causes and Troubleshooting

Quick Answer

CONFIG_INITIALIZATION_FAILED (0x00000067) is a Windows Blue Screen of Death (BSOD) error indicating that Windows encountered a failure while initializing its registry configuration. According to Microsoft, the Registry could not allocate the memory pool required to contain its registry files during system initialization.

This is an uncommon, low-level Windows startup error. Possible areas to investigate include memory allocation problems, defective RAM, hardware instability, and failures involving Windows initialization. Start by checking recent hardware or software changes, testing system memory, and using Windows Recovery Environment (WinRE) if the computer cannot start.

What Is CONFIG_INITIALIZATION_FAILED (0x00000067)?

Windows uses the Registry to store configuration information required by the operating system, hardware, drivers, and installed applications. During startup, the Windows kernel and Configuration Manager initialize the Registry so that essential system components can access their configuration data.

The CONFIG_INITIALIZATION_FAILED bug check occurs when this initialization process encounters a critical failure. Microsoft's technical documentation identifies the underlying condition as the Registry being unable to allocate the pool required to contain its registry files.

Windows stops the startup process and displays a blue screen to prevent the operating system from continuing in an unstable state.

This bug check has the following characteristics:

• Stop code: 0x00000067
• Error name: CONFIG_INITIALIZATION_FAILED
• Error category: Windows initialization failure
• Related component: Windows Registry and Configuration Manager
• Typical occurrence: During early Windows startup

Common Symptoms

A computer experiencing this error may exhibit one or more of the following symptoms:

• A blue screen appears with the message CONFIG_INITIALIZATION_FAILED.
• Windows crashes during startup before reaching the sign-in screen.
• The computer repeatedly restarts after displaying the stop code.
• Windows cannot start normally or enter the desktop environment.
• The error appears after a hardware change or system maintenance operation.
• The computer experiences repeated startup failures.

The exact symptoms depend on when the initialization failure occurs and which system components are affected.

Common Causes of Error 0x00000067

1. RAM or Memory Allocation Problems

Windows requires memory resources to initialize the Registry. If the required memory pool cannot be allocated, the initialization process may fail.

Defective RAM, unstable memory operation, or an underlying memory-management problem should be investigated, particularly when the error occurs during early startup.

2. Defective RAM Modules

A faulty memory module can cause unpredictable errors during Windows initialization. Memory-related hardware failures may interfere with the operating system's ability to access or manage the resources needed during startup.

Check for memory-related instability, especially if the problem began after installing additional RAM or changing memory configuration settings.

3. Hardware Instability

Unstable hardware can interfere with the early initialization of Windows. Possible areas to investigate include memory modules, motherboard components, power delivery, and recently installed hardware.

Do not assume that every occurrence of this bug check indicates a hardware failure. Use diagnostic results and crash-dump information to identify the actual problem.

4. Recent Hardware or Configuration Changes

If the error started after installing or replacing hardware, changing firmware settings, or modifying system configuration, investigate those changes first.

Incorrect or unstable memory settings, particularly after firmware configuration changes, may contribute to system instability.

5. Windows Initialization or Registry Problems

The bug check specifically identifies a failure involving Registry initialization. An underlying operating-system problem or an abnormal initialization condition may need further investigation.

However, the stop code alone does not establish that a particular Registry hive is corrupted. Avoid manually replacing Registry files without evidence identifying the damaged component.

Before You Begin Troubleshooting

Before attempting repairs, follow these precautions:

• Record the complete stop code and all four bug check parameters if available.
• Note whether the error occurs during every startup or intermittently.
• Identify any recently installed RAM, hardware, drivers, or firmware changes.
• Disconnect unnecessary external USB devices and peripherals.
• If Windows is accessible, back up important files before making system changes.
• Keep the BitLocker recovery key available if device encryption is enabled and recovery tools may be required.

How to Fix CONFIG_INITIALIZATION_FAILED (0x00000067)

Method 1: Perform a Complete Shutdown and Check External Devices

Start with basic checks before attempting advanced recovery procedures.

1. Turn off the computer completely.
2. Disconnect unnecessary USB devices, external storage drives, printers, and other peripherals.
3. Disconnect the power supply from a desktop computer or follow the manufacturer's shutdown instructions for a laptop.
4. Allow the computer to remain powered off briefly.
5. Reconnect the essential devices and start Windows.

If Windows starts successfully, reconnect the disconnected devices individually to determine whether an external device or its associated driver is contributing to the problem.

Method 2: Check RAM and Memory Stability

Because Microsoft's documented explanation involves a Registry memory-pool allocation failure, checking system memory is an important diagnostic step.

If Windows can start:

1. Press Windows + R.
2. Type the following command:

mdsched.exe

3. Press Enter.
4. Select Restart now and check for problems (recommended).
5. Allow Windows Memory Diagnostic to complete its test.
6. After Windows restarts, review the memory diagnostic result.

If Windows cannot start, use the memory diagnostic utility provided by the computer or motherboard manufacturer, where available.

Interpret the results:

• If memory errors are detected, investigate the installed RAM modules and memory configuration.
• If no errors are detected, continue troubleshooting. A successful test does not rule out every intermittent memory or hardware problem.
• If the error started after a RAM upgrade, verify that the installed modules are supported by the motherboard and system firmware.

Method 3: Check RAM Installation and Hardware Connections

If memory testing indicates errors or the problem started after a hardware upgrade, inspect the RAM installation.

For desktop computers:

1. Shut down the computer and disconnect it from the power supply.
2. Follow the motherboard manufacturer's instructions for safe component handling.
3. Inspect the RAM modules and their slots for visible damage or improper installation.
4. Verify that the memory modules are installed in the recommended motherboard slots.
5. Check that the modules meet the motherboard's memory compatibility requirements.
6. Run the memory diagnostic again after completing the inspection.

If multiple removable RAM modules are installed, a qualified technician can test them individually using a supported configuration. This can help identify a defective module or memory slot.

Method 4: Enter Windows Recovery Environment

If Windows cannot start normally, use the Windows Recovery Environment (WinRE) to access built-in recovery tools.

Windows may enter Automatic Repair after repeated unsuccessful startup attempts. If it does not, use Windows installation or recovery media.

To access WinRE using installation media:

1. Create Windows installation media on another working computer using Microsoft's official installation-media instructions.
2. Connect the USB installation media to the affected computer.
3. Start the computer and select the appropriate boot device using the manufacturer's boot-menu instructions.
4. When Windows Setup appears, select your language and keyboard preferences.
5. Select Repair your computer instead of Install Windows.
6. Open Troubleshoot > Advanced options.

From Advanced options, you can access several recovery tools, including Startup Repair, System Restore, Startup Settings, and Uninstall Updates.

For more information, refer to Microsoft's Windows Recovery Environment documentation.

Method 5: Run Startup Repair

Startup Repair is a built-in Windows recovery tool that automatically checks for certain problems preventing Windows from starting.

To run Startup Repair:

1. Start the computer in Windows Recovery Environment.
2. Select Troubleshoot.
3. Open Advanced options.
4. Select Startup Repair.
5. Choose the Windows installation if prompted.
6. Allow the diagnostic and repair process to complete.
7. Restart the computer and check whether Windows starts normally.

Startup Repair can address certain startup-related problems, including some damaged system files, boot configuration problems, and Registry-related startup errors. However, it is not a dedicated repair for every cause of CONFIG_INITIALIZATION_FAILED.

See Microsoft's Startup Repair guide.

Method 6: Use System Restore

If the error started after installing a driver, application, or system update, System Restore may help return Windows system files and settings to an earlier working state.

To use System Restore:

1. Open Windows Recovery Environment.
2. Select Troubleshoot > Advanced options.
3. Select System Restore.
4. Choose an available restore point created before the problem began.
5. Review the selected restore point and follow the on-screen instructions.
6. Allow the restoration process to finish.
7. Restart the computer and check whether the error is resolved.

System Restore can reverse certain system configuration, driver, and application changes. It does not normally remove personal documents, but applications and drivers installed after the selected restore point may be affected.

System Restore is available only if a suitable restore point exists and the feature is available for the Windows installation.

Method 7: Uninstall a Recently Installed Windows Update

If the blue screen started immediately after a Windows update, removing the most recent relevant update may help determine whether the update contributed to the problem.

When Windows cannot start:

1. Enter Windows Recovery Environment.
2. Navigate to Troubleshoot > Advanced options.
3. Select Uninstall Updates.
4. Choose the appropriate option to uninstall the latest quality update or feature update, depending on when the problem started and which options are available.
5. Follow the on-screen instructions.
6. Restart the computer and check the result.

Some updates cannot be uninstalled. Removing a security update can also reduce protection, so investigate the cause and reinstall supported updates when appropriate.

Refer to Microsoft's Windows Update removal instructions.

Advanced Troubleshooting for IT Technicians

1. Examine the Bug Check Parameters

The CONFIG_INITIALIZATION_FAILED bug check provides four parameters that can help identify the failure location and associated status information.

The second and third parameters can provide useful diagnostic information. Record their hexadecimal values from the blue screen, crash report, or debugging output.

Do not interpret these values as direct proof of a defective RAM module or a particular corrupted Registry hive. Additional debugging information is required.

2. Analyze the Memory Dump Using WinDbg

If Windows generates a crash dump, an IT technician can use Microsoft's WinDbg debugger to examine the bug check and the system state at the time of failure.

Common dump file locations include:

• Small memory dumps: C:\Windows\Minidump
• Kernel or automatic memory dumps: C:\Windows\MEMORY.DMP

To analyze an available dump:

1. Obtain WinDbg from Microsoft's official distribution.
2. Open WinDbg on a working Windows computer.
3. Select File > Open dump file.
4. Open the relevant .dmp file.
5. Wait for the debugger to load the symbols and dump information.
6. Run the following command in the WinDbg command window:

!analyze -v

This debugger command displays a detailed analysis of the crash, including the bug check information and other available diagnostic details.

For additional investigation, use the following debugger command:

.bugcheck

This displays the bug check code and its parameters.

Review the analysis output, relevant stack information, and available memory-management details. Because this particular error is associated with early Registry initialization, a dump may not always contain enough information to identify the underlying hardware or software fault.

Refer to Microsoft's WinDbg kernel-mode dump analysis documentation.

3. Investigate the Memory and Hardware Configuration

For systems that continue to experience this bug check, investigate the following:

• Memory diagnostic results and intermittent RAM errors.
• Installed RAM capacity and motherboard compatibility.
• Memory timing, frequency, and firmware configuration.
• Recent hardware replacement or expansion.
• Motherboard and processor stability.
• Power-related instability and hardware diagnostic results.
• Recurring startup failures and other bug check codes.

Where possible, compare the system's current configuration with its last known stable configuration. Avoid changing several hardware or firmware settings simultaneously because doing so makes the original problem more difficult to identify.

What Not to Do

Some commonly suggested BSOD repair procedures are not appropriate as automatic fixes for this particular error.

• Do not manually replace Registry hives: The error does not establish that a particular hive is corrupted.
• Do not delete Registry files: Removing essential Registry files can make Windows unbootable.
• Do not change paging-file settings without evidence: Microsoft's current bug check documentation describes a Registry pool allocation failure, not a universal paging-file configuration problem.
• Do not run Driver Verifier as a first step: It is an advanced driver diagnostic tool and can deliberately trigger additional crashes.
• Do not update BIOS or UEFI firmware without a reason: Firmware updates carry risks and should be performed only when relevant to the diagnosed problem.
• Do not reinstall Windows immediately: First investigate memory and hardware problems, because reinstalling Windows will not repair defective physical components.

How to Verify Whether the Problem Is Resolved

After completing the relevant troubleshooting procedure, verify the system's stability.

1. Restart the computer several times under normal conditions.
2. Confirm that Windows reaches the sign-in screen and desktop without displaying the same stop code.
3. Run a memory diagnostic if RAM instability was suspected.
4. Check that recently installed hardware is functioning correctly.
5. Review available crash dumps and system error records for recurring failures.
6. Observe the computer during normal use to determine whether the problem returns.

If the error continues, collect the complete bug check parameters and diagnostic results before attempting further repairs.

When to Seek Professional Assistance

Consider professional hardware or Windows diagnostic assistance when:

• Memory testing reports hardware errors.
• The computer cannot enter Windows Recovery Environment.
• The error occurs repeatedly despite basic recovery procedures.
• Multiple different BSOD codes appear during startup.
• The motherboard, RAM, or processor may be defective.
• Important data is stored on the affected computer and is not backed up.

A qualified technician can test individual memory modules, inspect motherboard hardware, analyze crash dumps, and investigate Windows initialization failures without immediately resorting to destructive recovery procedures.

Frequently Asked Questions

1. What does CONFIG_INITIALIZATION_FAILED (0x00000067) mean?

It means Windows encountered a critical failure while initializing its Registry configuration. Microsoft identifies the specific underlying condition as an inability to allocate the memory pool required to contain Registry files.

2. Is CONFIG_INITIALIZATION_FAILED a RAM-related error?

It can involve memory allocation problems, and defective RAM is one hardware possibility worth investigating. However, the stop code alone does not confirm that a RAM module is defective. Memory testing and further system diagnostics are necessary.

3. Can a corrupted Windows Registry cause error 0x00000067?

The error indicates a failure during Registry configuration initialization. However, it does not automatically mean that a Registry hive is corrupted. The specific failure should be investigated using bug check parameters and available diagnostic information.

4. Can I fix CONFIG_INITIALIZATION_FAILED without reinstalling Windows?

In some cases, yes. Depending on the underlying cause, checking RAM, correcting hardware instability, using Startup Repair, or restoring an earlier system configuration may resolve the problem without reinstalling Windows.

5. Does Windows Startup Repair fix error 0x00000067?

Startup Repair can resolve certain startup-related problems, including some Registry and system-file issues. However, it cannot be expected to repair defective RAM or every underlying cause of this bug check.

6. Should I replace my RAM if this error appears?

Not immediately. First run an appropriate memory diagnostic and verify the RAM configuration. Replace a memory module only when testing or hardware investigation provides sufficient evidence that it is defective.

7. What information should I collect when reporting this BSOD?

Record the complete stop code, all four bug check parameters, Windows version and build, recent hardware or software changes, memory diagnostic results, and available crash dump files. This information can help a technician investigate the failure more accurately.

Conclusion

CONFIG_INITIALIZATION_FAILED (0x00000067) is an uncommon Windows stop error associated with a failure during Registry initialization. Microsoft's documented explanation points to the inability to allocate the memory pool required for Registry files.

The recommended troubleshooting approach is to investigate memory and hardware stability, check recent configuration changes, and use Windows Recovery Environment when normal startup is unavailable. For recurring failures, examining the bug check parameters and crash dumps with WinDbg can provide additional diagnostic information.

Identifying the underlying cause is more important than applying generic Registry repairs or reinstalling Windows without first checking the hardware.

Sources

• Microsoft Learn – Bug Check 0x67: CONFIG_INITIALIZATION_FAILED
• Microsoft Support – Windows Recovery Environment
• Microsoft Support – Startup Repair
• Microsoft Support – How to Uninstall a Windows Update
• Microsoft Learn – Stop Code Error Troubleshooting
• Microsoft Learn – Analyze a Kernel-Mode Dump File Using WinDbg