False Positive Permanent Ban – Battlefield 6 (Case #230638423)
Hello EA Team,
I'm requesting a review of my permanent Battlefield 6 ban, which I strongly believe is a false positive caused by a Windows system transition and EAAC instability, not gameplay modification.
Case Number: #230638423
Date of Ban: November 26, 2025
Penalty Reason: “Gameplay Enhancement”
Platform: PC (EA App)
EA ID: esteman8x64
Why I believe this ban is a false positive
I have never used cheats, trainers, DLL injectors, memory editors, overlays, or any software capable of modifying gameplay. However, my PC was in a very unstable state at the exact moment the ban was triggered.
1. My PC updated from Windows 11 Technical Preview → Stable 25H2
Right after leaving the Technical Preview, Windows applied multiple kernel-level changes. Device Guard and Memory Integrity were reconfigured, EAAC reinstalled itself several times, and Battlefield 6 began crashing on startup.
2. The game was crashing with Access Violation errors (c0000005)
The Frostbite minidumps showed missing shadercache, corrupted memory regions, EAAC initialization failures, and mismatched ntdll symbol maps — all consistent with OS transition instability, not gameplay modification.
3. Battlefield 6 failed to generate cache files
Inside Documents\Battlefield 6, the game was unable to create:
- shadercache
- cache
- pso.cache
This typically indicates corrupted runtime environment, not tampering.
4. No unauthorized software installed
I do NOT use:
- Cheats
- Performance enhancers
- DLL modifications
- Memory editors
- Overlays
- Input automation
- Injectors
Nothing on my system modifies BF6 gameplay.
What likely happened
EAAC may have detected corrupted game memory during the Windows transition, misinterpreting it as gameplay enhancement. This matches other past cases triggered by:
- Windows kernel updates
- Missing PSO/shadercache files
- EAAC reinstall loops
- Memory integrity changes
Request
I kindly request a manual review of my ban. The issue is technical, not intentional. I have never cheated, and the timing matches system instability during the Windows update.
If you need any logs or diagnostics, I can provide them.
Thank you.
EA ID: esteman8x64
Case Number: #230638423
