FC27 PC crash
Problem description:
The game consistently crashes during matches (at random times). Windows Event Viewer initially showed eaanticheat.gameservice.exe crashing via ntdll.dll with exception code 0xc0000374 (heap corruption). After reinstalling the anti-cheat, crashes continued but with a different signature — now crashing directly inside FC27.exe and the engine's render module.
PC specs: [i7-14700KF / NVIDIA GeForce RTX 4080 SUPER / 64GB ram ddr5/Windows 10 Pro 64-bit]
Already tried (no effect):
- Disabled all overlays
- Reinstalled EA AntiCheat
- Reinstalled NVIDIA driver
- XMP disabled (RAM running at stock speed)
- Memory Integrity / Core Isolation — was already off
- sfc /scannow — no errors found
- Cleared Windows shader cache
- tryed run -dx11 throw EA app but dont know does it work
I found an identical crash signature in an old FC 26 bug report (thread from 09/30/2025, still open/unresolved): same FC26.exe + Engine.Render.Core2.PlatformPcDx12.dll, INVALID_POINTER_READ in rc2DeviceInit and INVALID_POINTER_WRITE in SoftMaxNormalize. This looks like the same unfixed engine bug carried over from FC 26 into FC 27. https://forums.ea.com/idea/fc-26-bug-reports-en/ea-sports-fc-26-%E2%80%93-random-crashes-access-violation--software-nx-fault/12686291
Crash dump analysis (collected across several crash sessions):
- Exception code in all cases: 0xC0000005 (ACCESS_VIOLATION)
- Crash #1: address 0x140eb1830, inside FC27.exe itself (offset 0xeb1830 from module base)- Crash #2: address 0x7ffafb9d316b, inside Engine.Render.Core2.PlatformPcDx12.dll (Frostbite's DX12 render module)- Crash #3: address 0x140eb2081, again inside FC27.exe (offset 0xeb2081 — close to crash #1 but not identical)
Attaching all collected crash dump files (.dmp / .mdmp) from the last three crash sessions.
Session ID crashes
1765eb2dc9b3c46f6aacec47
4acd807d7348c0a56aad13a8
4e713fd2899e240e6aad19de
