EA Sports FC 26 Crash and Access Violation on PC

What is the EA FC 26 Access Violation Crash?

EA Sports FC 26 on PC suffers from several crash types, the most common being Access Violation error 0xC0000005. Players see the game close to desktop with no warning, or receive an error referencing SOFTWARE_NX_FAULT — an attempt to execute non-executable memory inside FC26.exe. The crash often appears in Windows Event Viewer as: *"The game fc26.exe exited unexpectedly, exit code: 0xC0000005."*

These crashes affect all PC platforms — Steam, EA App, and Epic Games Store — because they originate in the Frostbite engine's DirectX 12 rendering module (Engine.Render.Core2.PlatformPcDx12.dll) and the EA AntiCheat service.

When does it occur?

• During match kickoff, goals, or cutscenes (mid-match freeze)
• At startup — the game window opens then immediately closes
• When EA AntiCheat fails to initialize (Error 87 on Windows 11 24H2)
• After a Windows or EA App update (especially EA App v15.27+)
• On systems with Intel 13th/14th Gen CPUs boosting to unstable clock speeds
• When running AMD GPUs on driver 25.9.1 or older

Common causes

• Corrupted AppData cache — stale config or save data from previous patches
• EA AntiCheat driver conflict — eaanticheat.sys fails on Windows 11 24H2 builds
• Unstable Intel P-core boost — 13th/14th Gen CPUs hitting 5.5 GHz cause stack buffer overruns (0xC0000409)
• Outdated or corrupt GPU drivers — especially AMD 25.9.1 and older NVIDIA drivers
• DirectX 12 rendering bugs — the Frostbite DX12 code path triggers access violations
• Hybrid GPU misconfiguration — laptops defaulting to integrated graphics instead of discrete GPU

Step-by-step fixes

1. Full AppData reset — Close EA App completely. Delete these folders: C:\Users\{user}\AppData\Local\EA SPORTS FC 26, C:\Users\{user}\AppData\Local\EADesktop, C:\Users\{user}\AppData\Roaming\EA, and C:\Users\{user}\AppData\Roaming\Electronic Arts. Restart your PC and relaunch — the game rebuilds fresh config files.

1. Force DirectX 11 mode — On Steam: right-click FC 26 > Properties > Launch Options > type -dx11. This bypasses the problematic DX12 rendering path entirely.

1. Clean GPU driver install with DDU — Download DDU from guru3d.com. Boot into Safe Mode (Settings > Recovery > Advanced startup > Startup Settings > F4). Run DDU, select your GPU vendor, click "Clean and Restart." Install the latest driver manually with "Custom > Clean Install."

1. Repair EA AntiCheat — Navigate to the FC 26 install folder, run EAAntiCheat.Installer as administrator. Verify in Windows Services that EA Background Service is set to Automatic (Running) and EA AntiCheat Service is Automatic (Delayed Start).

1. Reduce Intel CPU boost clocks (13th/14th Gen only) — Open Intel XTU or BIOS. Set P-Core Ratio to 50x (down from 55x) and E-Core Ratio to 43x. This eliminates the 0xC0000005/0xC0000409 crashes caused by unstable boost frequencies.

1. Set GPU preference to High Performance — Go to Windows Settings > System > Display > Graphics. Find EA SPORTS FC 26, click Options, select High Performance. This forces the discrete GPU on laptops.

1. Verify game files — Steam: right-click > Properties > Local Files > Verify integrity. EA App: right-click FC 26 > Repair. Epic: Library > three dots > Verify.

1. Cap framerate and adjust power settings — In NVIDIA Control Panel: set Max Frame Rate to 120 FPS, Power Management to Optimal Power, and V-Sync to On. This reduces GPU power spikes that trigger access violations.

If it still doesn't work

If crashes persist after all the above steps, run sfc /scannow from an elevated Command Prompt to repair Windows system files. For Windows 11 24H2 users experiencing Error 87 with EA AntiCheat, the root cause is a kernel-level conflict with Memory Integrity — try disabling Core Isolation temporarily via Settings > Privacy & Security > Device Security > Core Isolation, then test again.

As a last resort, check C:\Users\{user}\AppData\Local\EA SPORTS FC 26 for crash dumps named CrashDump_YYYY.MM.DD_HH.MM.SS.mdmp and report them on the EA Forums technical issues board. EA has acknowledged the DX12 crashes and is actively investigating.