Forum Discussion
I haven't had a problem since, I did notice that this issue occurred more frequently while partied up with Origin friends before the fix though. It went from happening every few games to not at all, so far, and I have a few hours in since then. If I experience the problem again I'll come back here and update. I should also mention that I have tried a previous fix (involving regedit and something about creating a registry key for r5apex.exe and setting cpu priority to 3), but I don't have the specifics, it was in another thread. I had not removed this registry edit at the time of implementing this current fix, and it is possible that my current stability is a result of both fixes being implemented at the same time (before the regedit fix, the error message referenced a hex address that wasn't all 0's, after that regedit fix the error message referenced hex addresses made of all 0's, after this vcredist fix, nothing errored so far), suggesting two possible causes for extremely similar errors.
*update* still no more instances of the "memory could not be read" error. I am still getting the "an update is available for Origin" error, but that has been isolated thusly: if you close your Origin launcher on windows 7, the origin web helper service keeps running. Stopping that service and launching Origin fresh appears to fix it. Again, still haven't gotten the "memory could not be read" error since the VC Redist fix, and I have since removed the regedit fix and still got in several more hours without the error. Good luck all.
Okay thanks for the info. I've also uninstalled the 2017 Vcredist and now installed the 2015 one. I'll see if it works, thanks a lot!
- 7 years agoDid it work and how did u do that
- 7 years agoFor more on Visual C++ check this post
https://answers.ea.com/t5/Technical-Issues/How-to-make-Apex-Legends-WORK-if-you-re-game-is-not-starting-up/td-p/7453246/jump-to/first-unread-message
- 7 years ago
Also changed my registry like that. The error also changed to 0x00000000000. Now I tried uninstallin 2017 and installing 2015. So far so good. Will edit if does not work.
- 7 years ago
Ok 5 minutes after writing this I got another error. So yeah... :D gotta wait for them to fix it
- 7 years ago
same sh.. here. todays update must have been something different. sad.
About Apex Legends Technical Issues
Community Highlights
- EA_Blueberry7 years ago
Community Manager
Recent Discussions
- 5 hours ago
- 7 hours ago
- 7 hours ago