Fix Attempted Write to Readonly Memory BSOD in Windows 10

The ATTEMPTED_WRITE_TO_READONLY_MEMORY blue screen in Windows 10 means a driver or other kernel-mode component tried to write to a memory area that should not be changed. Start by noting what changed just before the crash, then update or roll back the relevant driver; if the blue screen repeats, use Safe Mode and work through the checks below.

What the Stop Code Means

Windows protects parts of memory used by the operating system and drivers. A component that attempts an invalid write can trigger a stop error so the system halts rather than continue in an unstable state. The stop code is commonly displayed as ATTEMPTED_WRITE_TO_READONLY_MEMORY; Windows may also show the bug-check name and a technical code on the blue screen.

This error often points to a faulty, incompatible, or damaged driver, but the stop code alone does not identify the exact cause. A recent driver or Windows update, new hardware, security or monitoring software, and—less commonly—memory or other hardware trouble can also be involved. Avoid assuming that the first driver named in a crash report is always the root cause: it may be the component that detected the problem rather than the component that introduced it.

1. Record the Crash and Recent Changes

Before changing settings, write down the full stop-code text, when the crash occurs, and whether Windows names a file on the blue screen. Note anything recently installed or changed, such as a graphics, network, storage, or printer driver; a Windows update; a new device; or software that installs low-level drivers.

If Windows restarts too quickly to read the screen, check Settings > Update & Security > Windows Update > View update history for recent updates, and review installed apps or devices. Do not delete unfamiliar system files based only on a filename shown in a crash. A driver file may be shared by multiple devices, and manual deletion can make Windows unbootable.

2. Update or Roll Back the Suspected Driver

If Windows starts normally, use the computer or device manufacturer’s support source for drivers where practical. Windows Update can also provide driver updates. Avoid third-party “driver updater” utilities: they can install incorrect drivers and make troubleshooting harder.

1. Right-click Start and open Device Manager.
2. Expand the category for the device you suspect, right-click the device, and select Properties. On the Driver tab, note the provider and date.
3. To install an available Windows driver, right-click the device and choose Update driver, then follow the prompts. If you obtained a suitable driver from the device manufacturer, use Browse my computer for drivers and select its provided folder.
4. If the crashes began after a driver update, open Properties > Driver > Roll Back Driver if that option is available. Restart and see whether the issue stops.

Change one driver at a time and test before making other changes. If the problem began after installing a new device, disconnect it when safe to do so and check whether the crashes stop. For a computer that will not start normally, enter Windows Recovery Environment and use Troubleshoot > Advanced options > Startup Settings > Restart; then select Safe Mode. The route into recovery can vary, but Windows may enter it automatically after repeated failed starts. Do not repeatedly force power-offs if you can reach recovery another way.

3. Check Windows Files and Recent Updates

Damaged system files can contribute to instability. In Windows, search for Command Prompt, right-click it, choose Run as administrator, and run these commands in order, allowing each to finish:

• DISM.exe /Online /Cleanup-image /Restorehealth
• sfc /scannow

DISM repairs the Windows component store that System File Checker uses; SFC then checks and repairs protected system files when possible. Restart afterward. If the crashes began immediately after a Windows update, check Settings > Update & Security > Windows Update > View update history. Windows 10 may offer Uninstall updates from the update-history area. Remove a recent update only when timing supports it, and check for a later fix rather than leaving the system unpatched indefinitely.

4. Test Memory and Look for Hardware Clues

Windows Memory Diagnostic can check for some memory problems. Save your work, search for Windows Memory Diagnostic, open it, and choose to restart and check. The test runs during startup; results may appear in Windows notifications or in Event Viewer. A clean result does not rule out every intermittent hardware fault.

Also consider whether crashes occur under a specific workload, after a device is connected, or alongside other signs such as unexpected shutdowns. If memory errors are reported, or the computer continues to crash after software troubleshooting, stop treating it as a routine driver issue. Hardware diagnosis may require help from the computer’s manufacturer or a qualified repair professional. Do not open a device or reseat parts unless you know how to do so safely and it is appropriate for that model.

5. Use Recovery Options Carefully

If the error persists, Windows Recovery Environment offers options such as System Restore, which can return system settings and drivers to an earlier restore point without being intended as a personal-file deletion tool. Restore points are not always available, and the option may undo apps or drivers installed after the selected point. Back up important files before using major recovery steps whenever Windows is accessible.

Resetting or reinstalling Windows is a later option, not the first fix for a driver-related stop code. Those processes can remove apps and, depending on the choice made, personal files. Read each recovery screen carefully and make a separate backup first. If the device is managed by an employer or school, contact its administrator before changing drivers or recovery settings.

Common Misconceptions and Prevention

A blue screen does not automatically mean the RAM is defective, and reinstalling Windows is not guaranteed to fix a hardware fault. Likewise, changing registry settings or downloading a driver from an unknown site is not a safe shortcut. The most useful evidence is the timing of the crash, recent changes, repeatability, and whether a particular driver update or rollback changes the behavior.

Once stable, install Windows and device-driver updates from trusted sources, avoid installing multiple driver packages for the same device, and keep a backup of important files. If the stop code returns, record what happened immediately beforehand; a repeatable pattern is more helpful than making several unrelated changes at once.

Frequently Asked Questions

Is ATTEMPTED_WRITE_TO_READONLY_MEMORY always caused by a bad driver?
No. Drivers are a common cause, but damaged system files, incompatible software, and hardware problems can also trigger it. The stop code is a clue, not a diagnosis.

Can I fix this blue screen without reinstalling Windows?
Often, yes. Start with a recent driver rollback or update, then check Windows files and recent changes. Reinstallation is a last resort because it takes more effort and may remove apps or data.

What should I do if Windows keeps crashing before I can log in?
Use Windows Recovery Environment to start in Safe Mode, then undo a recent driver or software change. If recovery is unavailable or the computer will not remain stable, seek device-specific support.

Does this error mean my RAM is bad?
Not necessarily. Run Windows Memory Diagnostic if appropriate, but remember that a passing test cannot exclude every memory or hardware issue. Repeated crashes or reported errors warrant further diagnosis.

Should I download a driver-fixer program?
No special fixer is required. Use Windows Update or the device or computer manufacturer’s driver source, and avoid utilities that install drivers without clearly identifying their origin and compatibility.

Related

• Microsoft Bing Image Creator: How to Use It
• Error Executing Updater Binary in ZIP on Android
• Android Battery Life: Settings to Change on Any Flagship