Skip to content
PCDecoder
0x00000051REGISTRY_ERRORStop codeWidely reported

REGISTRY_ERROR (0x51): what it means and how to fix it

Updated Oct 17, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

Stop code REGISTRY_ERROR (0x00000051) indicates that Windows encountered a severe problem reading or handling its registry files. The issue is typically triggered by storage drive I/O errors, file system corruption, or resource exhaustion during security updates. Running Windows Startup Repair or scanning your storage drive is the best place to begin.

What it means

Windows uses the system registry as a central database to track configuration settings, user accounts, and hardware states. These records are saved in binary storage files called hives on your main drive. When Windows issues bug check 0x00000051, a critical failure has halted communication between the operating system and these registry hive files.

The error typically signals that the registry encountered an I/O (input/output) error while attempting to read a hive file from disk. Windows also runs an internal integrity routine called HvCheckHive to verify hive structure; if corruption is detected or if an unreadable sector prevents data retrieval, the operating system stops immediately to prevent wider data damage.

Storage Failures and File System Damage

Physical disk trouble is a primary trigger for this blue screen. When an SSD or hard drive develops failing sectors within the sectors that store registry hive data, Windows cannot access core system configuration parameters. File system structure corruption produces identical results, blocking the operating system from completing read and write commands even if the underlying storage hardware remains physically sound.

Security Refresh Operations and Resource Limits

A separate mechanism involves security subsystems inside Windows. The security architecture occasionally carries out refresh operations on registry components. If the system encounters extreme resource limits while attempting one of these refresh routines, the operation fails and triggers the REGISTRY_ERROR bug check.

Because registry hives are required immediately during the boot sequence, this error frequently traps computers in repetitive restart loops before the desktop environment can load.

Common causes

  • Storage drive read errors or bad sectors preventing Windows from reading registry hives.
  • File system corruption making registry files unreadable.
  • Internal registry hive corruption detected by system validation routines.
  • Resource exhaustion during a security system registry refresh operation.
  • Hardware faults affecting the storage controller or disk connection.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Run Windows Startup Repair

    Use this first if the computer is stuck in a reboot loop and cannot load the Windows desktop.

    1. Power on the PC, then hold the physical power button down for ten seconds as soon as the Windows logo appears to force a shutoff.
    2. Repeat this power interruption three times in a row to launch the Automatic Repair screen.
    3. Select Advanced options, then click Troubleshoot.
    4. Click Advanced options again, then select Startup Repair.
    5. Wait for Windows to scan your boot configuration and attempt repairs, then let the system restart.
    Did this fix it?

  2. Scan the drive with Check Disk

    Use this to detect and repair file system corruption or bad sectors preventing registry file access.

    1. Reach the recovery screen using the forced shutdown method or bootable Windows installation media.
    2. Go to Troubleshoot > Advanced options > Command Prompt.
    3. Type chkdsk C: /f /r and press Enter.
    4. Allow the tool to scan the volume, fix file system structural errors, and locate unreadable disk sectors.
    5. Type exit once the process finishes, press Enter, and restart the PC.
    Did this fix it?

  3. Repair system integrity with SFC

    Use this when storage hardware is healthy but core system and configuration files may be damaged.

    1. Open Command Prompt from the Advanced options recovery menu.
    2. Type sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows and press Enter.
    3. Wait for the System File Checker to scan offline system directories and replace damaged files.
    4. Close Command Prompt by typing exit followed by Enter.
    5. Restart the PC to verify whether Windows boots normally.
    Did this fix it?

  4. Restore Windows to an earlier point

    Use this if registry corruption started recently and you have an existing system restore point.

    1. Navigate to Troubleshoot > Advanced options on the Windows recovery menu.
    2. Select System Restore.
    3. Pick an available restore point timestamped before the REGISTRY_ERROR crashes began.
    4. Confirm your drive selection and click Finish to start the rollback.
    5. Keep the computer powered on until the restoration finishes and reboots into Windows.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 13, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Why is my PC trapped in a reboot loop with REGISTRY_ERROR?

Windows must read core registry hives from disk during the earliest phase of startup. If storage I/O errors or severe file corruption make those hives unreadable, the operating system crashes and restarts before reaching the login screen.

Does this stop code mean my drive is failing?

It can indicate drive failure, but not always. While physical bad sectors often cause registry read failures, logical file system corruption or memory resource exhaustion can produce the exact same stop code.

Can I fix stop code 0x51 using registry cleaner software?

No. Registry cleaner tools do not address drive I/O failures, bad sectors, or low-level hive corruption, and using them often causes additional system damage.

More stop codes decoded