I've spent an entire week troubleshooting this widespread crashing error, and I'm posting all the information I have in the exact detail suggested by the CMs. Thank you guys for trying your best, I understand that your job here is to gather feedback and offer assistance while Respawn works on this. I appreciate what you're doing in the meantime, and I hope that there may be something of use here that you can forward to the developers @EA_Blueberry @EA_David .
For anyone reading or commenting, this is specifically discussing the common crash with either of these errors:
- "r5apex.exe - Application Error The instruction at 0x00000000 referenced memory at 0x00000000. The memory could not be written."
- "r5apex.exe - Application Error The instruction at 0x(characters vary here) referenced memory at 0x(characters vary here). The memory could not be read."
To avoid confusion, please ensure that any comments are related to these specific errors. There are active threads for other types of crashing where you can find the information that pertains to your issue.
System, including all peripherals (dxdiag file attached):
- Windows 7 Ultimate 64 bit, Fully updated on latest build
- Nvidia GeForce GTX 1060 6GB, Driver 417.71 @ Stock Clock
- Intel i3-8350k @ 4.0 GHZ Stock Clock
- 16 GB DDR4 RAM
- 256 GB Samsung 860 Evo SSD
- Gigabyte Z370XP SLI Motherboard
- Zowie BenQ XL2411Z 144hz Monitor
- ASUS VX228 60hz Monitor
- Logitech G903 Wireless Mouse
- Topre Realforce 87u 55g Keyboard
- HyperX Cloud II Headset
- Antlion ModMic 4.0
- Ethernet Connection
When did I first notice this?
- This has happened ever since I first installed the game, a few days before the Havoc was introduced. This happens frequently, on average every 2 or 3 games.
What have I noticed about these memory errors (20 example error screenshots linked at the bottom of this post)?
- The "Memory could not be read" error is much more common than the "Memory could not be written" error.
- The "Memory could not be read" error seems to happen mostly when interacting with something, such as picking up items.
- The "Memory could not be written" error seems to happen much more randomly, often while walking around with nothing happening.
- The "Memory could not be written" error always reports "0x00000000" as the instruction, as well as the memory referenced.
- The "Memory could not be read" error reports seemingly random numbers for the instruction, as well as the memory referenced.
- Sometimes either of these errors will appear a few seconds after launching the game client, but with much less frequency than they do in-game. Both the "read and written" errors have occurred during client startup.
- Sometimes these errors also appear as I'm loading into the Legend Selection screen - again, much less common than getting them during the real gameplay.
- I did not notice any distinct correlation between the time I had been in-game, and how long it took me to crash due to a memory error. My friends and I experience these errors seconds into the round, minutes into the round, or even in the final battle of the round.
- The vast majority of these errors take place during relatively quiet moments in the game, with no distinct correlation to large amounts of action, effects, or explosions.
- The game's performance on my machine, in terms of framerate, is surprisingly excellent, and the memory error crashes are not accompanied by frame drops or signs of degraded performance - they simply eject me from the game abruptly.
What steps have I taken to troubleshoot the issue?
- I enabled "Run as administrator" in the properties of both r5apex.exe and origin.exe.
- I enabled "Run in compatibility mode for Windows 7" in the properties of both r5apex.exe and origin.exe.
- I have disabled the Origin Overlay for Apex Legends.
- I have tested and confirmed the same memory crashing errors on Nvidia Drivers 417.71 through 419.17 using DDU and a full clean installation of the drivers.
- I have uninstalled GeForce Experience following my clean installations of new drivers.
- I have tested forcing r5apex.exe to run at High Priority via regedit (If you're reading this, do not attempt this please).
- I have tested changing EasyAntiCheat.exe to Low Priority via the Task Manager.
- I have uninstalled Origin and Apex Legends, and repaired the game several times in between these steps.
- I have also cleared my user Cache multiple times throughout troubleshooting.
- I restart my PC after every troubleshooting step when applicable.
- I have ran a repair of EasyAntiCheat.
- I have fully uninstalled all existing "Microsoft Visual C++ versions" on my PC, and installed only the versions that are shipped with the Apex Legends installation (x64 and x86).
- I have fully uninstalled all existing "Microsoft Visual C++ versions" on my PC, and installed the 2010-2015 versions (x64 and x86) directly from Microsoft's download page.
- I have set custom pagefile settings on my C:drive where Windows, Origin, and Apex Legends are all installed. I set the minimum value to 147,000 MB, and the maximum value of 220,000 MB.
- I have tested disabling the "Windows Error Reporting" process.
- I have tried +fps_max 0, +fps_max 75, +fps_max 80, and +fps_max 144 in my launch options.
- I always do my testing while no other non-essential background services are running. This means no Discord, no Logitech Software, no MSI Afterburner, no GeForce Experience, no Shadowplay. I ensure that they are completely shut down or uninstalled and do not interfere whatsoever with the troubleshooting process.
- I never have any overlays enabled other than Shadowplay, which I've uninstalled a few days ago.
- I have played games with all graphics settings to low, medium, and high.
- I am not using an AntiVirus, including Windows Defender.
- I have confirmed that "Samsung Rapid Mode" is disabled for my SSD.
- I have no settings in my Nvidia Control Panel's 3D Settings that conflict with the in-game settings. All options are application controlled other than the Prefer Maximum Performance Setting and the Maximum Possible Refresh Rate setting.
- I have also tried overriding the available in-game graphics settings with their counterparts in the Nvidia Control Panel's 3D Settings.
- I have attempted to play with my second monitor enabled, and with my second monitor disabled.
- I have attempted to disable unused audio output devices that were not in use.
- I have tried to play after stopping then restarting the Windows Audio Endpoint service.
- I have attempted to toggle my language in-game.
- I have tested these memory errors on Fullscreen Mode, Borderless Windowed Mode, and Windowed Mode.
I play regularly with a large community of friends with different versions of Windows. The Community Crashing Thread fixes for these Memory Reading/Writing errors on Windows 8.1 and Windows 10 have all been successful according to those I play with. However, every single person in my community who uses Windows 7 gets these exact same errors, has tried most of the fixes I've listed here, and not a single one has managed to escape the constant crashes. This is also extremely apparent by the abundance of related threads and comments posted in this forum.
Windows 7 is supported according to the game's system requirements, but cannot function due to these memory errors. Please help us! Thank you for reading, everyone here would wholeheartedly appreciate it if you could forward any useful information to the correct eyes.
Imgur Album of 20 Memory Read/Write Crash Errors
Attached: dxdiag
