How to Fix Apex Legends Memory Could Not Be Read Error [Solution]
Key Notes
- Common causes include corrupted game files or outdated drivers.
- Perform essential preliminary checks before troubleshooting.
- Follow the step-by-step instructions to fix the issue effectively.
Resolve the ‘Memory Could Not Be Read’ Error in Apex Legends Quickly and Easily
If you’re an avid player of Apex Legends, encountering the ‘Memory Could Not Be Read’ error while trying to launch or enjoy the game can be frustrating. This guide aims to help you identify the common causes behind this error and provide you with straightforward, expert-backed solutions. Let’s dive into how you can get back to gaming without interruptions.
Step-by-Step Solutions for Fixing the ‘Memory Could Not Be Read’ Error
Essential Preliminary Checks
Before diving into detailed solutions, ensure that you conduct the following preliminary checks:
- Ensure that your Windows OS and graphics drivers are updated; restart your computer afterward.
- Check the EA server status to rule out downtime or technical issues.
- Press Ctrl + Shift + Esc to access the Task Manager, select unwanted processes, and click End task.
Step 1: Clear the Assets Folder
Navigate to the following path, replacing Username with your actual profile name:
C:\Users\Username\Saved Games\Respawn\Apex\assets
Open the folder, press Ctrl + A to select all files, then hit the Delete key to remove the contents.
Pro Tip: Always create backups before deleting files if you’re unsure about the contents.
After this, launch your game to see if the problem persists.
Step 2: Remove the Certification Folder
Right-click on Apex Legends on your desktop and select Properties. Then, go to the Shortcut tab and click on Open File Location.
Locate the Easy Anti Cheat folder. Inside this folder, find and delete the certification folder.
Step 3: Adjust Compatibility Settings
In the Properties menu for Apex Legends, head to the Compatibility tab.
Check the box next to Run this program in compatibility mode for and select Windows 8 from the dropdown menu.
Check Run this program as administrator and disable fullscreen optimizations before clicking Apply and OK to save your changes.
Step 4: Repair Game Files
Open the EA app by pressing the Windows key and typing ea. In My Collection, find Apex Legends and click the three dots icon for settings. Then select Repair.
This will ensure the integrity of your game files and download any necessary components.
Step 5: Fix the EasyAntiCheat Service
In Apex Legends Properties, click Open File Location from the Shortcut tab.
Navigate to the EasyAntiCheat folder and run EasyAntiCheat_Setup.exe. Select Repair Service to fix any issues.
Reboot your computer to complete the process and check if the issue remains.
Step 6: Temporarily Disable Windows Firewall
Press the Windows key, type control panel, and select it.
Go to System and Security and open Windows Defender Firewall. Click on Turn Windows Defender Firewall on or off, and select to turn it off for both Public and Private networks. Click OK.
Test if the game launches properly. If it does, remember to enable the firewall and add Apex Legends to the exclusion list.
Step 7: Regain Control with Registry Modifications (Windows 7 only)
Press Windows + R to open the Run dialogue, type regedit, and hit OK.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options .
Create a new key named r5apex.exe, then within it, create PerfOptions and a DWORD (32-bit) Value called CpuPriorityClass. Set the value to 3.
Restart your PC after changes.
Pro Tip: Modifying the registry can be risky; consider creating a backup before proceeding.
Summary
In this guide, we’ve covered the ‘Memory Could Not Be Read’ issue in Apex Legends and provided comprehensive steps to resolve it. From clearing game files to modifying registry settings, the outlined methods offer multiple approaches to get back into the action smoothly. Always ensure that your systems and drivers are up to date to prevent future occurrences.
Conclusion
Experiencing the ‘Memory Could Not Be Read’ error in Apex Legends can be disruptive, but with the methods we’ve outlined, you should be able to troubleshoot and resolve the issue effectively. Remember to stay informed about updates and support options from EA, and don’t hesitate to reach out if problems persist.
FAQ (Frequently Asked Questions)
What should I do if none of these solutions work?
If these troubleshooting steps do not resolve the error, visiting the official Apex Legends support forums is a good idea to seek further assistance.
Does updating Windows really make a difference?
Yes, keeping Windows updated can help prevent various issues, including performance problems and compatibility errors with games like Apex Legends.
Related posts:
- How to Resolve Apex Legends Error Code 100 on PC and Xbox Consoles
- 5 Easy Solutions to Resolve Apex Legends Anti-Cheat Errors
- Resolve r5apex.exe Application Error: Memory Could Not Be Read Issue
- Ultimate Guide to Optimal DualSense Edge Settings for FPS Gaming
- Fix for Windows 11 KBYou’re not alone if you have issues with the Windows 11 KB5034765. February 2024 security update for Windows 11 causes File Explorer to crash when rebooting the system, and some have found it’s causing the taskbar to disappear. Additionally, many users are having problems installing the Windows 11 February 2024 update.Windows Updates are designed to automatically install without affecting productivity, but that doesn’t appear to be the case with the February 2024 update. In our tests, we observed that the Windows 11 KB5034765 update repeatedly fails to install with 0x800f0922, 0x800f0982, and 0x80070002.Multiple users told me that when they tried to install the security patch, everything seemed fine at first. The update downloads and asks for a restart. But during the installation, Windows Update stopped and confirmed there was a problem. It tries a few more times and then goes back to the desktop without updating.KB5034765 is not installing, but there’s a fixWindows 11 January 2024 Update fails with 0x80070002 | Image Courtesy: WindowsLatest.comOur device also attempted the “rollback” after successfully downloading the February 2024 cumulative update, but the process was stuck on the following screen for ten minutes: Something didn’t go as planned. No need to worry—undoing changes. Please keep your computer on. I tried tried a few things to fix it. For example, I removed programs that didn’t come with Windows, cleared the Windows Update cache and used the Windows Update troubleshooter. None of these solutions have worked.However, there’s some good news. It looks like we can successfully install KB5034765 by deleting a hidden folder named $WinREAgent. There are multiple ways to locate and delete this folder from Windows 11 installation, and you choose your preferred one: Method 1: Run Disk Cleanup as an administrator, select the system drive, and check the boxes for “Temporary files” and other relevant options. Finally, click “OK” to remove the system files, including Windows Update files. This will delete unnecessary files within $WinREAgent. Method 2: Open File Explorer and open the system drive, but make sure you’ve turned on view hidden items from folder settings. Locate $WinREAgent and remove it from the system. Method 3: Open Command Prompt as Administrator, and run the following command: rmdir /S /Q C:\$WinREAgent Windows Update causes File Explorer to crash on rebootSome PC owners are also running into another problem that causes the File Explorer to crash when rebooting or shutting down the system.This issue was previously observed in Windows 11’s January 2024 optional update, and it seems to have slipped into the mandatory security patch.The error message indicates an application error with explorer.exe, mentioning a specific memory address and stating, “The memory could not be written” .“The instruction at 0x00007FFB20563ACa referenced memory at 0x0000000000000024. The memory could not be written. Click on OK to terminate the program,” the error message titled “explorer.exe – Application Error” reads.explorer.exe crashes with a referenced memory error when rebootingThis issue seems to persist regardless of various troubleshooting efforts. Users have tried numerous fixes, including running the System File Checker tool (sfc /scannow), testing their RAM with Windows’ built-in tool and memtest86+, and even performing a clean installation of the latest Windows 11 version.Despite these efforts, the error remains.Interestingly, a common factor among affected users is the presence of a controller accessory, such as an Xbox 360 controller for Windows, connected to the PC. This connection has been observed, but it’s unclear if it directly contributes to the problem.Microsoft’s release notes for the KB5034765 update mentioned a fix for an issue where explorer.exe could stop responding when a PC with a controller accessory attached is restarted or shut down.However, despite this so-called official fix, users are reporting that the problem still occurs.Source&Images
Alex Ruben
My goal is to make complex technical topics simple and accessible. On this site, I gather unique and useful content that not only solves users problems but also helps them better understand the capabilities of Windows.