EA App Crashing

Had this issue for months and still no fix in the book works, its not just titanfall 2 aswell, every ea game no matter what launcher does this to me.

It's really disheartening that i had this issue a couple years ago, tried to sleuth around and figure out how to rectify it, and then failed, all while noticing people wern't really recieving support on this issue. Only to get a hankering to play the sims now, give it a shot, run into the same problem, to discover that other users are also running into that problem while failing to get support. It has been literal years since i've been able to get EA desktop to run on my laptop, and i am definitely not a unicorn. This is happening to customers and EA doesn't care.

Hey everyone -- I hear how frustrating this has been, especially seeing it come back after so long without a clear fix.

mlamlah​ -- I want to push back slightly on the idea that this isn’t being looked at. Issues like this do get investigated, but the tricky part is that “EA App crashes on login” isn’t a single root cause problem -- it’s usually tied to specific system conditions (corrupt cache, Windows services, GPU drivers, security software conflicts, or account/session issues). That’s why it can feel like nothing works when trying generic fixes.

Given how long you’ve been hitting this, it’s very likely a persistent system issue rather than the app install itself. A few targeted things that tend to resolve this exact login crash pattern:

• Fully clear EA App cache (not just reinstall):
  C:\Users\[YourUser]\AppData\Local\Electronic Arts\EA Desktop\ → delete everything in this folder
  (Reinstall alone won’t touch this properly)
• Check Windows Credential Manager:
  Remove any saved EA/Origin credentials — stale tokens can cause login crashes
• Disable overlays/security layers temporarily:
  (Discord overlay, MSI Afterburner, RivaTuner, some antivirus tools) — These frequently hook into the login window
• Run the EA app as admin once after a clean boot
  (You mentioned a clean boot, but combining it with cache + credentials reset matters)
• Create a new Windows user profile (quick test)
  This is the fastest way to confirm if it’s profile corruption -- if it works there, we know exactly where the issue sits

If you’re open to it, I’d like to narrow this down properly rather than have you loop through generic fixes again -- things like:

• Does it crash immediately after entering credentials or before?
• Any error code in Event Viewer (Application logs)?
• Laptop model / GPU?

That helps turn this from a “years-long issue” into something we can actually isolate.

Let’s get this one unstuck.