These errors can cause system instability and data loss, therefore today we’re going to show you how to fix this error.

How can I fix ATTEMPTED_WRITE_TO_READONLY_MEMORY?

1. Update your drivers and Windows 10

1.1 Manually update the drivers Blue Screen of Death errors are often caused by outdated or incompatible drivers, therefore it’s important that you update them as often as you can. Windows 10 relies heavily on drivers in order to recognize and use certain hardware, and if your drivers are corrupted, or simply not compatible with Windows 10, that will cause an ATTEMPTED_WRITE_TO_READONLY_MEMORY or any other BSoD error to appear. In order to fix this error, it’s highly recommended that you update your drivers. Updating drivers in Windows 10 is fairly simple, and you can do that right from the Device Manager by following the steps above. Using Device Manager to update your drivers is pretty straightforward, but some users claim that Device Manager doesn’t always download the latest drivers for your device. To download the latest drivers, it’s always better to visit your hardware manufacturer’s website and download the necessary drivers manually. Bear in mind that you’ll have to update as many drivers as you can in order to fix this issue. 1.2 Update drivers automatically Searching for drivers on your own can be time-consuming. So, we advise you to use a tool that will do this for you automatically. Using an automatic driver updater will certainly save you from the hassle of searching for drivers manually, and it will always keep your system up to date with the latest drivers. The tool recommended below will help you update drivers automatically and prevent PC damage caused by installing the wrong driver versions. DriverFix is able to update multiple drivers at the same time. Just let it scan your whole PC and then approve all updates necessary and wait for the process to complete. It can also automatically update your drivers on a regular basis with no effort on your part. You only have to schedule how often you want the app to scan, update and repair your drivers and you are all set. ⇒ Get DriverFix

2. Run the dedicated troubleshooter 

If updating your drivers didn’t get the job done, let’s try Windows 10’s troubleshooting tool. This is a universal tool that basically deals with all sorts of issues within Windows 10. And it might also be helpful with the BSOD issues.

3. Run the SFC scan

The next troubleshooting tool we’re going to run is the SFC scan. This is a command-line troubleshooter that scans your system for potential issues and resolves them (if the solution is possible, of course).

4. Run DISM

4.1 Standard way 4.2 With the Windows installation media DISM is the third troubleshooter we’re going to try, in case the previous two failed to resolve the problem. DISM stands for Deployment Image Servicing and Management, and as its name says, it reloads the system image. So, maybe this process will resolve the BSOD issue. SPONSORED

5. Remove problematic applications

Errors such as ATTEMPTED_WRITE_TO_READONLY_MEMORY can be caused by certain applications, therefore it’s necessary that you find and remove them. Users reported that Gigabyte On/Off software is the common cause for this error, so if you have this software installed, be sure that you remove it. Another common cause for BSoD errors can be your antivirus software. Users reported that tools such as NoVirusThanks can cause these types of errors, and according to them, the issue was fixed after removing this tool. We have to mention that almost any antivirus program can cause this error, and if you want to fix this problem, you’ll have to remove all third-party antivirus programs from your PC. To completely remove an antivirus program, we strongly suggest that you use a dedicated removal tool. Many antivirus companies have dedicated removal tools available for their software, so be sure to download one for your antivirus program. If uninstalling the antivirus fixes the issue, you might want to download the latest version of the same antivirus program that you were using before, or you can switch to any another antivirus software.

6. Reset BIOS to default

Few users reported that they managed to fix this error by resetting BIOS to default, and you can do that easily. To see how to access and reset BIOS, be sure to check your motherboard manual for detailed instructions. Before you reset BIOS, we advise you to check your SATA Controller and see what mode you are currently using. Controller mode will be set to IDE, AHCI, or RAID, so be sure to set the SATA controller mode to the same value after you reset BIOS.

7. Use System Restore or Windows 10 reset

7.1 Perform a System Restore If the ATTEMPTED_WRITE_TO_READONLY_MEMORY error is caused by a software problem, you should be able to fix it by performing System Restore. If System Restore didn’t fix the issue, you’ll have to perform a Windows 10 reset. To complete Windows 10 reset you might need Windows 10 installation media. You can easily create an installation media by using Media Creation Tool and an empty USB flash drive. 7.2 Perform a Windows 10 reset We have to warn you that the reset process is similar to a clean install, so make sure that you back up important files from your C partition before you start this procedure. If the BSoD error appears even after Windows 10 reset, the error is most likely caused by faulty hardware.

8. Check your hardware

ATTEMPTED_WRITE_TO_READONLY_MEMORY error can be caused by your hardware, so we urge you to check if your RAM is working properly. The easiest way to do that is to test your RAM modules one by one, but you can also use tools such as MemTest86+ to perform a detailed scan of your RAM. If your RAM is not the problem, you should check all other major hardware components. The BSoD such as the Windows error ATTEMPTED_WRITE_TO_READONLY_MEMORY can be sometimes hard to fix, but we hope that you managed to fix this error by using one of our solutions. If you have any other suggestions or solutions, don’t hesitate to leave them in a comment below.

SPONSORED Name * Email * Commenting as . Not you? Save information for future comments
Comment

Δ