Forum Discussion
After a lot of testing, I was finally able to narrow down the issue on my system, although I still don’t fully understand the root cause.
My System:
- CPU: AMD Ryzen 9 5900X
- GPU: PowerColor RedDevil RX 7900 XTX
- RAM: 32GB G.Sklill DDR4-3600
- Motherboard: ASUS ROG Strix X570-E Gaming
On my system, the game runs completely fine when I restrict the CPU affinity of EAAntiCheat.GameServiceLauncher.exe to CCD0 (cores 0–11) using Process Lasso. In this configuration, I can join matches and play without any crashes.
However, when I use CCD1 (cores 12–23) or both CCDs (cores 0–23), the game crashes again as usual while loading a map (around ~30% loading progress), without any error message.
This behavior is 100% reproducible.
So at this point it seems like:
- The game is stable on CCD0
- But becomes unstable when running on CCD1 or both CCDs
I don’t know whether this is a scheduling issue, an engine problem, or something related to anti-cheat, but it clearly seems to be linked to specific CPU cores / CCD usage on my system.
That being said, I can’t completely rule out a hardware-related issue on my side. It’s possible that something is wrong with the CPU (e.g. communication between CCDs), although synthetic stress tests (Prime95) did not show any instability when testing CCD1.
Its not you´re PC its the Engine. This problem happend in every Frostbite engine game since forever. Unfortunate for never to an extent like this time. Get a refund have fun with other games. Zero chance that they even try to fix it.
- Gustavo0803991 month agoSeasoned Traveler
Hey have you experienced this crash on season 2?
- DieWollmilchsau1 month agoRising Scout
I am the lucky guy who has a AMD System with 7900XTX and a Intel/nividia Gaming Laptop with a 4070 and i have this crash since the beta. And i can tell you for sure nothing of that try this or try that worked ever (not only for me beacuse the most guys come back sooner or later). And i tried everything on 2 Systems.
- Gustavo0803991 month agoSeasoned Traveler
I'm on the same boat brother, i also refunded the game thanks to this error. But if you go back a few posts, there has been some silent "updates" by EA that might have fixed it, even if not on purpose LMAO.
I also played for over 13 hours during the free week with no crashes, that's why i'm asking people if they experienced this error after the season 2 update, specially those who have been getting it since the launch.
So have you played yet on season 2? Got any crashes?