Terminal Flashing Green and Red Screen Loop on Startup
Hello, I am reporting a severe visual rendering bug that has made my game completely unplayable. The game worked fine initially, but now it freezes right after the initial splash loading screen. By the way I purchased the game through Steam. It drops into a solid green screen, and pressing 'Enter' or the spacebar causes the entire display to cycle aggressively between solid green and solid red screens. The main menus never render. My Hardware Specs: GPU: NVIDIA GTX 1080 (8GB) CPU: Intel Core i5-11400F RAM: 32GB Dual-Channel OS: Fresh clean installation of Windows 10 Storage: Crucial P2 M.2 NVMe SSD (380GB free out of 465GB) Troubleshooting Already Done: I have completely reinstalled Windows 10, used DDU for fresh graphics drivers, completely reinstalled the EA Anti-Cheat utility as an administrator, wiped local AppData/EA App cache directories, and attempted Steam windowed launch parameters. The issue persists across a completely flawless, clean PC environment. EA Case ID: [Case number:-249530725]. Please look into this compatibility issue with Pascal architecture graphics cards. Thank you!
FC 25 not launching
FC 25 installed via Xbox Game Pass on PC. Game launches to splash screen then crashes. Event Viewer shows EA Javelin Anticheat Event ID 1000, fc25.exe exited unexpectedly with exit code 0xFFFFFFFF. Issue started around 21-22 May 2026. Verified game files, reinstalled EA Anticheat, SFC scan clean, all drivers up to date. Valorant and other games work fine
FC 25 won’t launch on Windows 11 24H2 – Splash screen crash, no error, no logs
My system GPU RTX 3080 CPU Ryzen 7 3800X OS Windows 11 Pro 24H2 Build 26100.3476 No overlays or RGB tools active All drivers and system updates are current The issue The game crashes right after the splash screen and goes back to the EA App There is no crash dump, no error, no log What I already tried - Uninstalled FC25 via EA App - Manually deleted leftover files and folders - Uninstalled and reinstalled EA App - Uninstalled and reinstalled EA AntiCheat via the official installer - Reinstalled Visual C++ Redistributables x64 and x86 - Installed DirectX End User Runtime - Ran EA App and FC25 as Administrator - Tried compatibility mode (Windows 7 and 8) - Cleared EA App cache - Created and tested a new Windows user - Closed all background apps and overlays (Razer, HyperX, MSI Afterburner, Discord, etc.) - Used DDU to reinstall NVIDIA drivers without GeForce Experience - System is fully updated - Deleted EA AntiCheat registry entry - Disabled antivirus and firewall Nothing worked. Help.
Controller Fix
If your controller doesn’t work or the game won’t detect it (especially in games using anti-cheat like EA AntiCheat or Easy Anti-Cheat), try this: 🔧 Solution: Turn OFF Bluetooth completely on your PC/laptop Connect your controller using a USB cable Launch the game Once the game is running, you can: keep using USB or turn Bluetooth back on (optional, may still work wirelessly) ⸻ ❗ Why this works: When Bluetooth is ON, Windows may detect the controller twice: once as a wireless device once as a wired device This can confuse the anti-cheat system, which may block the controller entirely. ⸻ 🧠 Conclusion: ❌ Bluetooth ON at launch = controller not detected ✅ Bluetooth OFF + USB at launch = works perfectly ⸻ This is a simple fix, but it solves a lot of controller issues in anti-cheat protected games 👍
EA Javelin Anticheat. Event ID: 1000 FC 25 Crashing During Gameplay
I just installed this game and ever since I've been unable to finish a single match. Keeps crashing mid game. The Event viewer says the source is EA Javelin Anticheat. Event ID is 1000. I tried various solutions I've read and seen online, nothing seems to be working. It's very frustrating. Please pay attention to this EA.Technical problem
Actually, this issue started around 10 AM. Whenever I try to launch EA SPORTS FC 25 STANDARD EDITION , it says the game is already running. However, I haven’t logged in on any device other than my own. I’ve also checked my devices and email account, and it only shows my device. I don’t understand why this message is still appearing.
