Ok so what I had to do here was I had to install the Visual C++ redistributables stored in the Program Files (x86)\Origin Games\Apex\__Installer\vc\vc2015\redist\ folder. It wouldn't install because I had a later version installed (2017 to be specific) so I uninstalled that via "remove programs and features" and then installed the 2015 one. After that, I had a separate error with "Update available for origin please exit and relaunch origin" etc. etc. So I disabled the ingame origin overlay, stopped the origin web helper service in task manager, and now I can play the game without error on windows 7. Good luck hope this works for others.
*edit* I should mention that the previous failures to install the 2015 Visual C++ redistributable were not caught by the update/repair functions of Origin, so it is worth checking that manually even if the Origin Launcher says that the installation checks out. It's possible that Origin does not check that things like this were installed properly as they are separate installers.
@EpicToastedy Hey Toastedy, I've seen multiple treads on this issue. I have it myself aswell. But for how long have you been able to play without errors? Since sometimes I can play a good 3 hours with no error. While at other times it happens every bloody game. Please report back with your findings and stability!
Thanks,
Desperate person who just wants to play.
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!
Community Manager
