Forum Discussion
Hey, Everyone
As this thread is a bit old, things have changed and been updated; we will lock this down to prevent any necro-posting.
If you run into any further issues, please create a new thread or add your information to an existing thread so we can begin tracking accordingly!
Cheers!
- rolandin955022 hours agoNewcomer
Same issue here, and it matches the crash signature from the original post exactly.
PvZ: Garden Warfare 1 (bought in the EA app) will not launch. When I start it from the EA app, the app closes for a second and reopens. When I run PVZ.Main_Win64_Retail.exe directly, the loading window appears and the game closes at the "Syncing cloud updates" step.
System:
- Windows 10
- NVIDIA GTX 1050 Ti
- Game path: C:\Program Files\EA Games\Plants vs Zombies Garden Warfare\
Event Viewer (Application log):
Faulting application name: PVZ.Main_Win64_Retail.exe, version: 1.0.3.0, time stamp: 0x540f7b89
Faulting module name: PVZ.Main_Win64_Retail.exe, version: 1.0.3.0, time stamp: 0x540f7b89
Exception code: 0xc0000005
Fault offset: 0x00000000003de75f
The crash happens inside the game executable itself, not in a driver or third-party DLL, and the fault offset is identical on every attempt.
What I have already tried (none of it helped):
- Clean reinstall of the game (deleted the game folder, reinstalled to C:\Program Files\EA Games\)
- Full uninstall and reinstall of the EA app, including leftover folders
- Repair from the EA app
- Cleared the EA app cache (Help > App Recovery)
- Renamed the Documents\Plants vs. Zombies Garden Warfare folder to reset settings
- Changed the EA app language
- Launching with no internet connection (same crash at the same step)
- Clean boot, in-game overlay off, antivirus and Controlled Folder Access off
- Visual C++ 2012/2013/2015-2022 and DirectX runtime reinstalled
- sfc /scannow and DISM /RestoreHealth
- Run as administrator and compatibility modes
- Ending EABackgroundService.exe before launching
Since the same offset appears in other reports on a fresh install (Windows 10 and Windows 11, up-to-date drivers), this looks like a bug in the game or in how the current EA app handles it, rather than a problem on our PCs. Could the EA team please look into this? Happy to provide a DxDiag report or a crash dump if needed.