Forum Discussion
Hopefully this can help ppl. that only started having problems today with starting the game, and maybe others too.
I've confirmed this solution 3 times, and what causes it in my case.
Solution:
-MAKE A NEW WINDOWS PROFILE (Normal computer account, not a Microsoft Account)
-REBOOT and log into your new account and start Origin
-Disable all notifications in Origin, so hopefully on the next invite, this won't repeat until a fix is out.
-Start Apex
It works for me... UNTIL someone invites me to a game, and the crash + process repeats.
I've tried clearing all cache, flushing dns, reinstalling drivers and uninstalling the game + origin + multiple restarts without success etc. etc..
So after someone invited me again and the problem reappeared, I made another profile.... AGAIN. And it worked. Games starts normally.
I saw someone reinstalled windows and still got the same error.
Question - Did it crash after someone invited you and then you couldn't start the game anymore?
More background info:
I've had a couple of the issues regarding crashing game and not being able to start the game the last week. (Fixed some off them by following advice on this forum)
Also had a couple of days with no problem.
Today I played full 3 games, until I was in the lobby and a friend invited me to a match, game crashed into windows with no error, after that I couldn't start the game again normally at all.
I only get the Respawn Logo and then back to desktop with no error message.
After trying everything previously mentioned in this thread without success, I tried what works normally on random/hard to find errors at my work.
(50 000 customers and 3500+ applications in a windows environment within health care, which in 80% of cases just takes too much time to troubleshoot, so we make A NEW WINDOWS PROFILE and if that doesn't work we reinstall the PC)
After the last crash (and 2 new profiles), I uninstalled Origin + Apex and deleted all Origin-folder in AppData, User\Local and User\Roaming and reinstalled Origin but it still won't start.
Only works when making a new profile.
So my best guess at this time is that some files are still somewhere that needs to be deleted and/or it's some strings in the registry that needs to go after a full uninstall.
Sorry for the lengthy post, hope this can help someone else and @EA_Blueberry to have some more data.
- Twitch_Coolbtw7 years agoNot applicable
- x_meffe7 years agoNot applicable
Ok, so here's my dxdiag.
fyi: i've tried every suggested solution/fix in this thread so far, and there's nothing that works. Everything is random, as someone earlier said - you might be able to play for a few games, maybe a few hours at times.. but sooner or later, you will have your crash/crashes, probably sooner then later - and every single game at times.
I really hope EA fix this soon, it shouldn't be such a big issue for the devs imo.. this can't be something new.
I've started to think it has something to do with the anticheat, that finds something on the computer that it thinks is bad - and then forcequits the game - i cant think of anything else after everything ive tried.
- Vulpes377 years agoNot applicable
Same problem, but I noticed that once the issue starts, the issue become ACCOUNT RELATED. I can't use that account on other PCs (pc that never had that issue with apex), and I can run in my pc other accounts with no issues.
- ISirReaperI7 years agoNot applicable
I don't know if anyone is still having those random crashes without error, but I've been playing the game without AMD External Events Utility and AMD user Experience Program services that I switched off on MSconfig services and so far no crashes in weeks. At first I though it was MSI afterburner, but doesn't seem so.
- EA_Blueberry7 years ago
Community Admin
@ISirReaperI wrote:
I don't know if anyone is still having those random crashes without error, but I've been playing the game without AMD External Events Utility and AMD user Experience Program services that I switched off on MSconfig services and so far no crashes in weeks. At first I though it was MSI afterburner, but doesn't seem so.
Thanks for sharing what helped you out, @ISirReaperI
We can't confirm that's a fix but it would be interesting to know if that helps other AMD users out.