Heya @SabotageDomingo
Go to your main Apex Directory, then proceed to the Crashpad folder and then the db folder.
If correct, there should be some recent .dmp files.
I could read these for you using some software, you'll have to put them in an .rar archive and attach it to your post:
That way we can check what else could be causing this issue.
Also whenever this issue happens, do you hear any beeps?
Does your cursor lag or are you still able to move it without any lag?
It's also recommended to attach a DxDiag to your post, that way we can look at your hardware and recent errors that would also indicate other causes.
Hi @XHelperZ ,
I have the same issue, I attached the .dmp file. Please have a look for me please. I cannot play the game, it still crash after I open the game for less than 2mins
Community ManagerHi everyone,
When you've got the chance can you try playing again after the update from earlier today? Please let me know if you're still running into any crashes after the update is installed.
Thanks!
I can't even launch the game.
Update was around 430+mbs, since then it cuts right to desktop.
Nothing specified however a family member who also has the game installed with current update on a separate computer can play the game no issue.
This seems to be case specific to possibly the hardware or an inconsistency in comparability.
I'm running windows 7 btw if that means anything.
@EA_Kent It is still crashing today. Bizarrely, I tried playing via Origin (instead of Steam) and it worked yesterday ... and now does not work today, i.e., crashes in both Steam and Origin.
DxDiag from yesterday and today attached.
PS - i gather from @IamKayRaw's thread a patch hit Steam yesterday and Origin today, so that seems like the culprit.
Various users from reddit to discord servers are reporting this crash, they've tried many fixes and nothing seems to fix it.
A general theme seems to follow that they're using Win11.
As for the other users in this thread, I'll probably get around checking your files tommorow.
I've seen several people -- including me -- with this error on other OSes, including in this thread. I'm running W10, someone above is on Windows 7. It's definitely not isolated to W11
Community Manager
