Windows BSOD 0x0000011C — ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE — What It Means & How to Fix It

What Does This Error Mean?

Windows BSOD 0x0000011C — ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE — means something tried to write data to a protected area of the Windows Registry while in kernel mode. The Windows Configuration Manager (CM) protects certain critical Registry hives from being modified directly. When a driver or system component attempts an unauthorized write to these protected areas, Windows immediately crashes to prevent system corruption. This is a security and stability protection mechanism.

Affected Models

Windows 10 version 1903 and newer
Windows 11 all versions
Systems with kernel-mode drivers from security software
Systems after malware infection or removal
Systems with corrupted Registry hives

Common Causes

A kernel-mode driver or rootkit attempted to write directly to a protected Registry hive
Malware or a rootkit previously installed on the system is trying to modify protected system areas
A security software driver has a bug that causes it to write to protected Registry storage
Windows Registry hive is corrupted and the Configuration Manager is in an unexpected state
A Windows update or system tool attempted to modify a protected Registry key incorrectly

How to Fix It

Run a full malware scan immediately using Windows Defender or a trusted scanner like Malwarebytes. This BSOD can indicate that malware or a rootkit is attempting to modify protected Registry areas.

Boot from Windows Safe Mode to run the scan, as malware can disable or evade scanners when running normally. Search for Safe Mode in Windows Help.
Run System File Checker to repair corrupted system files. Open Command Prompt as Administrator and type: sfc /scannow and press Enter. Wait for the scan to complete.

Corrupted system files can put the Configuration Manager in a state where legitimate operations are misidentified as unauthorized writes.
Run DISM to repair the Windows image. In Command Prompt as Administrator type: DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This repairs deeper Windows component issues.

DISM downloads replacement files from Microsoft's servers. An internet connection is required.
Check recently installed drivers and software. Go to Settings, Apps, and sort by install date. Uninstall anything installed around the time the BSOD started. Focus on security software, system utilities, and hardware drivers.

A newly installed kernel driver that writes to the Registry incorrectly is a common trigger. Removing suspect software and seeing if the BSOD stops is an effective diagnostic approach.
If the BSOD persists, use System Restore to roll back to a point before the issue started. Search for System Restore in the Start menu and select a restore point from before the BSOD began.

System Restore reverts system files and drivers to an earlier state without affecting personal files. It is one of the most effective tools for BSOD recovery.

When to Call a Professional

0x0000011C is a serious error that can indicate a security compromise or deep system corruption. If malware scanning and SFC repairs do not resolve it, have a professional examine the system. A technician can analyze the crash dump to identify what attempted the unauthorized write. Data recovery may be needed if the Registry is severely corrupted.

Frequently Asked Questions

Does 0x0000011C mean my computer has a virus?

It is a strong indicator to investigate for malware, but it does not definitively confirm infection. A buggy driver from legitimate software can also trigger this BSOD. Run a thorough malware scan as the first step. If the scan is clean, focus on driver and system file issues.

What is the Windows Configuration Manager?

The Windows Configuration Manager (CM) is the kernel component that manages the Windows Registry. It loads Registry hives, manages reads and writes, and protects critical areas from unauthorized modification. When CM detects an unexpected write attempt to a protected area, it crashes Windows with 0x0000011C to prevent damage.

Can I recover my system after 0x0000011C without reinstalling Windows?

In most cases yes. SFC, DISM, System Restore, and driver rollback resolve the majority of cases. If the Registry is severely corrupted or malware has damaged core files, a repair install of Windows (which preserves your data) is the next option. A clean install is only necessary in the most severe cases.