ATTEMPTED_WRITE_TO_READONLY_MEMORY, the blue screen, explained and fixed

This stop code (0x000000BE) means a driver attempted to write to a segment of memory that is marked read-only, memory Windows deliberately protects because changing it (kernel code and constants live there) would corrupt the system. Windows stops everything instead. The crash almost always names the driver at fault, and the fix is dealing with that driver, or with the bad RAM that made an innocent driver look guilty.

The fix, in order

  1. Note the driver file named in the crash. The parameters of this bug check identify the driver that attempted the write in most cases, and the blue screen or the dump viewer will show a .sys name. Start there.
  2. Update or roll back that driver. Get the current version from the device manufacturer, or use Device Manager → Properties → Driver → Roll Back if the crashes began with an update.
  3. Uninstall the software the driver belongs to if updating fails. Security suites, VPNs, disk utilities, and hardware-tuning tools install the kind of low-level drivers that earn this code. Remove the newest such addition first.
  4. Boot into Safe Mode to work. Hold Shift + Restart → Troubleshoot → Advanced options → Startup Settings → Safe Mode, where third-party drivers do not load.
  5. Test the RAM. Run Windows Memory Diagnostic, then extended passes. A memory fault can flip an address or an instruction and send a healthy driver writing to the wrong place; rotating blame between drivers is the tell.
  6. Repair system files. DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow from an admin Command Prompt.

If it still happens

If the same driver is convicted after a clean reinstall of its current version, its vendor has a bug: check the vendor’s support pages for a fixed release and use an older stable version meanwhile. If different drivers rotate through the blame, treat it as a memory problem until testing proves otherwise, and check the drive with chkdsk /f for completeness.

Common questions

Why is some memory read-only in the first place? To protect the system from exactly this failure. Kernel code, driver code, and constant data are mapped read-only so that a buggy write cannot silently rewrite the operating system. When a driver tries anyway, Windows faces a choice between stopping now or running corrupted, and it stops.

How is this different from MEMORY_MANAGEMENT (0x1A)? MEMORY_MANAGEMENT is the general verdict that memory management structures were misused or corrupted. 0xBE is one specific prohibited act, writing to protected memory, caught at the moment of the write and usually with the driver identified. The driver-first, RAM-second workup is shared between them.

Related errors

MEMORY_MANAGEMENT · KMODE_EXCEPTION_NOT_HANDLED · CRITICAL_STRUCTURE_CORRUPTION · BAD_POOL_HEADER