Bug Check 0xC0000218: STATUS_CANNOT_LOAD_REGISTRY_FILE
The STATUS_CANNOT_LOAD_REGISTRY_FILE bug check has a value of 0xC0000218. This indicates that a registry file could not be loaded.
Important Info If You Have Received a STOP Code
If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.
These actions might prevent an error like this from happening again:
- Download and install updates and device drivers for your computer from Windows Update.
- Scan your computer for computer viruses.
- Check your hard disk for errors.
STATUS_CANNOT_LOAD_REGISTRY_FILE Parameters
The following parameters are displayed on the blue screen.
| Parameter | Description |
|---|---|
|
1 |
Address of the name of the registry hive that could not be loaded. |
|
2 |
Zero (Reserved) |
|
3 |
Zero (Reserved) |
|
4 |
Zero (Reserved) |
This bug check displays a descriptive text message. The name of the damaged file is displayed as part of the message.
Cause
This error occurs if a necessary registry hive file cannot be loaded. Usually this means the file is corrupt or is missing.
In rare instances, this error can be caused by a driver that has corrupted the registry image in memory, or by a memory error in this region.
Resolution
Try using the the startup recovery mechanism (for example Startup Repair, Recovery Console, or Emergency Recovery Disk) provided by the operating system. If the problem is a missing or corrupt registry file, that usually fixes the problem.
Send comments about this topic to Microsoft
Build date: 4/9/2013
