ATTEMPTED_WRITE_TO_READONLY_MEMORY: Windows Blue Screen Fix

Quick answer

The Windows stop code ATTEMPTED_WRITE_TO_READONLY_MEMORY (0x000000BE) means: A driver tried to write to read-only memory. If it happened once, restart and keep an eye on it. If the blue screen repeats, follow the steps below; it is usually fixed by updating or removing a driver or program.

Before you start: note the stop code shown on the blue screen. If Windows will not start normally, it usually opens Automatic Repair after two failed starts; from there choose Advanced options to reach Safe Mode or System Restore.

Is it serious? Can I keep using my PC?

Severity: Medium

If it happened once, restart and keep an eye on it. If the blue screen repeats, follow the steps below; it is usually fixed by updating or removing a driver or program.

Common causes

Faulty, outdated or incompatible driver
Conflict with antivirus, VPN or system utility software

How to fix it

Restart the PC. If the blue screen happened only once and does not return, no further action is usually needed
Find the faulting driver: check Event Viewer and the dump files in C:\Windows\Minidump
Update or roll back the driver of the faulting device in Device Manager (look for yellow warning icons)
Install the latest Windows updates
Uninstall recently installed programs, especially antivirus, VPN or system tools
Test the RAM with Windows Memory Diagnostic (mdsched.exe)

Frequently asked questions

What does ATTEMPTED_WRITE_TO_READONLY_MEMORY mean?

The Windows stop code ATTEMPTED_WRITE_TO_READONLY_MEMORY (0x000000BE) means: A driver tried to write to read-only memory.

Is ATTEMPTED_WRITE_TO_READONLY_MEMORY serious?

Severity: Medium. If it happened once, restart and keep an eye on it. If the blue screen repeats, follow the steps below; it is usually fixed by updating or removing a driver or program.

How do I fix ATTEMPTED_WRITE_TO_READONLY_MEMORY?

Start with these steps: Restart the PC. If the blue screen happened only once and does not return, no further action is usually needed; Find the faulting driver: check Event Viewer and the dump files in C:\Windows\Minidump; Update or roll back the driver of the faulting device in Device Manager (look for yellow warning icons); Install the latest Windows updates; Uninstall recently installed programs, especially antivirus, VPN or system tools.

Related codes

0xA IRQL_NOT_LESS_OR_EQUALA driver or system process tried to access memory it was not allowed to use, usually because of a faulty driver.0x1E KMODE_EXCEPTION_NOT_HANDLEDA program running in the Windows kernel caused an error that it did not handle.0x3B SYSTEM_SERVICE_EXCEPTIONAn error occurred while a system service was running, often caused by a driver (frequently graphics) or security software.0x3F NO_MORE_SYSTEM_PTESWindows ran out of system page table entries, usually because a driver is not releasing memory.0x50 PAGE_FAULT_IN_NONPAGED_AREAWindows tried to use memory that does not exist or is not available, often due to a driver, security software or faulty RAM.0xC2 BAD_POOL_CALLERA driver or program made an invalid memory request.0xC5 DRIVER_CORRUPTED_EXPOOLA driver corrupted the system memory pool.0xD1 DRIVER_IRQL_NOT_LESS_OR_EQUALA driver tried to access memory at a time it was not allowed to, almost always a faulty driver.0x109 CRITICAL_STRUCTURE_CORRUPTIONWindows detected that critical kernel code or data was corrupted.