attempted_write_to_readonly_memory BSOD fix for Windows 11
If attempted_write_to_readonly_memory appears once, restart and check the last driver or update; if it repeats, treat it as a driver or hardware fault and test memory and storage before changing settings. Repeat crashes can lead to boot loops, damaged files, and lost work. This guide separates a one-off software clash from a repeat fault, and shows what to check first,.
What ATTEMPTED_WRITE_TO_READONLY_MEMORY means
This stop code has a value of 0x000000BE. It is issued if a driver attempts to write to a read-only memory segment.
What to note before you change anything
Write down the exact stop code, the time it happened, and whether the crash followed a driver update, a game launch, a dock attach, or a boot attempt. Save the minidump from C:\Windows\Minidump if one exists, and open Event Viewer to capture the bug check entry before you reinstall or remove anything.
One crash or a pattern?
Classify the crash first. A single BSOD can point to a one-time software clash, while repeat crashes often suggest a bad driver, a flaky device, or hardware that keeps failing under the same conditions. The pattern tells you what to test first and what evidence to keep.
| Branch | First three actions | Evidence to collect |
|---|---|---|
| Single isolated BSOD | 1) Restart normally. 2) Check Windows Update and recent driver installs from the last few days. 3) Note the app or device active at the time. | Minidump file, Event Viewer bug check entry, recent update history. |
| Repeated after one driver update | 1) Open Device Manager. 2) Roll back or uninstall the last driver change. 3) Reboot and retest the original app or boot path. | Driver version before and after, install date, repeat crash timing. |
| Repeated under gaming or load | 1) Check recently changed device drivers. 2) Test with Safe Mode with Networking. 3) Run memory and file checks. | Temp/load pattern, game name, GPU driver version, any artifact or freeze before the crash. |
| Repeated at boot | 1) Enter WinRE and Safe Mode. 2) Remove the last driver or startup change. 3) Test RAM and firmware settings. | Boot loop point, Safe Mode result, any BIOS changes, minidump if available. |
What usually causes this stop code?
Common causes include a recently changed driver, a memory problem, storage corruption, firmware settings that are not compatible with current hardware, or system files damaged during an update. The first clue is usually the crash pattern, not the message text.
Driver problems that rank highest
A recent graphics driver, chipset package, storage controller driver, or security filter driver is the first place to look when the crash follows an update or appears under load. A driver can run fine for a while and then fail when a game, sleep resume, or device handoff pushes a weak path.
RAM and storage faults
Bad RAM can surface here, but it is a stronger suspect when the crash repeats across different drivers and apps. Storage faults usually show extra signs, such as file corruption, install failures, or crashes that happen during updates and large file copies.
Firmware and BIOS settings
BIOS or UEFI settings matter when the system started crashing after hardware changes, a firmware flash, or a major Windows update. A firmware change or default reset can help when custom settings are involved.
Third-party security or filter software
Security suites, encryption tools, backup agents, and filter drivers can trigger this stop code because they sit low in the stack. If the crash started right after installing one of those tools, treat it as a possibility before you blame Windows itself.
How do I troubleshoot in Safe Mode?
Safe Mode helps when normal boot fails because it starts Windows with fewer drivers and services. That gives you a clean path to remove or roll back the last change, and Safe Mode with Networking lets you fetch a clean driver package if the machine still stays stable enough to connect.
Boot to WinRE and open Advanced startup
- Go to Settings > System > Recovery > Advanced startup, then select Restart now.
- Choose Troubleshoot > Advanced options > Startup Settings.
- Select Restart, then choose Safe Mode or Safe Mode with Networking.
Use Safe Mode to remove a suspect driver
- Open Device Manager.
- Find the device with a yellow exclamation mark or the one updated most recently.
- Open Properties > Driver, then choose Roll Back Driver or Uninstall device.
SupportAssist and Dell diagnostics can run after Safe Mode if the machine is a Dell. They are useful when you need a vendor test result or an error code for support.
Safe Mode path: Settings > System > Recovery > Advanced startup > Restart now > Troubleshoot > Advanced options > Startup Settings Driver rollback path: Device Manager > (device) > Properties > Driver tab > Roll Back Driver / Uninstall device Collect: C:\Windows\Minidump\*.dmp Event Viewer > Windows Logs > System Recent driver update history
Which driver should I update, roll back, or uninstall first?
Start with the driver that changed most recently, then move to the driver class most tied to the crash pattern. If the problem began after a driver install, roll it back before trying a newer package. If Device Manager shows a warning icon, work that device first.
