Error 0xFFFFFFFF
i have the same problem but with EA WRC and i've done all the steps you mentioned in the message. Not even one worked and i still have the same problem. I also have a decent PC to run the game and i also used to play it with no problems just few days ago [Thread moved to WRC board and updated Title. EA_Claus]
WRC BSOD: eaanticheat.sys – 0x7F DOUBLE_FAULT – never launched on PC
EA SPORTS WRC has never successfully launched on this PC. The game was purchased through the Epic Games Store. Every attempt to launch WRC results in a Windows kernel BSOD involving EA Javelin AntiCheat / eaanticheat.sys. SYSTEM: Lenovo Legion 7 16IAX10 (83KY) Windows 11 Home 25H2, build 26200.9445 Intel Core Ultra 9 275HX NVIDIA GeForce RTX 5070 Laptop GPU 8 GB 32 GB RAM BIOS: Lenovo RXCN78WW CPU microcode: 0x121 CRASH: BugCheck: UNEXPECTED_KERNEL_MODE_TRAP (0x7F) Arg1: 0x8 – EXCEPTION_DOUBLE_FAULT Process: EAAntiCheat.GameService.exe Module: eaanticheat.sys EA AntiCheat image version: 1.0.33258.0 Failure bucket: 0x7f_8_eaanticheat!unknown_function I now have TWO independent usable Windows crash dumps from separate WRC launch attempts. Both reproduce the same fault at the exact same EA AntiCheat offset: eaanticheat+0x1766a24 The failing instruction is: mov qword ptr [rsp+68h],rax In both dumps, the trap frame contains a kernel stack pointer far outside the valid stack range of the EAAntiCheat.GameService.exe thread. Latest dump: Valid thread stack: Limit: ffff860f`eebb9000 Base: ffff860f`eebc0000 Current: ffff860f`eebbd790 Fault RSP: ffff860f`ffffffff CR2: ffff860f`ffffffe8 !pte on CR2 reports the address as NOT VALID. The earlier independent dump shows the same pattern: Fault offset: eaanticheat+0x1766a24 Fault RSP: ffffb801`ffffffff CR2: ffffb801`ffffffe8 !pte: not valid Therefore the failure is highly deterministic and reproducible in the EA AntiCheat execution path. I am NOT claiming that eaanticheat.sys must necessarily be the first component that corrupts the stack pointer, because the double-fault trap frame may already represent corrupted processor/stack state. However, two independent crashes reaching the exact same eaanticheat.sys offset with the same invalid-stack pattern strongly justify investigation by the EA Javelin AntiCheat engineering team. TARGETED DRIVER VERIFIER TEST: I also tested Windows Driver Verifier specifically against eaanticheat.sys using: - Special Pool - Force IRQL checking - Pool Tracking WRC immediately reproduced the same visible: UNEXPECTED_KERNEL_MODE_TRAP (0x7F) What failed: eaanticheat.sys Verifier did not produce an earlier/different verifier-specific bugcheck. Driver Verifier has since been fully disabled and verified as OFF. TROUBLESHOOTING ALREADY COMPLETED: - Full EA AntiCheat removal/reinstall - Full WRC deletion and clean reinstall through Epic Games Store - Game installed again to default location - EA AntiCheat files checked: Authenticode signatures are VALID and signed by Electronic Arts, Inc. - Windows 11 repair reinstall of the current 25H2 installation while preserving apps/files/settings - Windows Memory Integrity tested OFF + reboot; same BSOD; restored ON - Hypervisor tested OFF + reboot; same BSOD; restored to AUTO - NVIDIA / system drivers checked - BIOS and CPU microcode checked - Third-party filter/service isolation performed - Nahimic isolated - DAEMON Tools drivers isolated - Logitech joystick/G29-related drivers isolated; G29 physically disconnected - Lenovo SmartConnect / SmartEngine components isolated - SENetFilter completely removed and confirmed absent; WRC still produced the same BSOD - steamxbox driver isolated - RFDriveFs2 isolated - lenovoDriverBus isolated - No relevant third-party AV/VPN/EDR filter identified - Code Integrity logs checked; no blocked/unsigned driver failure corresponding to the crash - Storage/NTFS logs checked; no corresponding disk/storage failure - Windows crash-dump configuration repaired after earlier dump-writing failures The latest WRC crash successfully produced a completed kernel bitmap dump at 100%. Approximately 30 system restarts have occurred during this investigation, including planned troubleshooting reboots and BSOD-induced reboots. Conservatively, I estimate that more than 10 hours of active troubleshooting have been spent on this issue, excluding breaks and waiting time between tests. At this point I do not believe another generic reinstall, clean boot, Secure Boot toggle, Memory Integrity toggle, Windows repair, or similar first-line troubleshooting cycle is appropriate. These steps and significantly deeper kernel-level diagnostics have already been performed. REQUEST: Please escalate this report to the EA Javelin AntiCheat technical/engineering team. I would specifically like EA to investigate the reproducible eaanticheat.sys execution path at offset +0x1766a24 and whether there is a known compatibility issue involving this platform, particularly the Intel Core Ultra 9 275HX / Windows 11 25H2 environment. I can provide: - WinDbg output from both independent dumps - BSOD screenshots - minidump - system information - driver/service inventory - Code Integrity logs - additional diagnostic information requested by EA engineering The full latest kernel dump is approximately 2.9 GB, so it cannot be attached directly to this forum post, but I can provide relevant WinDbg analysis and smaller diagnostic files. Because the game has never successfully launched on this PC despite extensive troubleshooting, I would also appreciate guidance regarding the purchase through Epic Games Store and any available resolution/refund path if EA cannot provide a technical fix. Thank you.
EA Javelin Anti Cheat crashes with DXVK
Adding DirectX DLLs d3d11.dll and dxgi.dll into WRC\Binaries\Win64 no longer works. In fact, it violently crashes the computer. What the dump shows: BugCheckCode: 0x50 → PAGE_FAULT_IN_NONPAGED_AREA Param1 (address referenced): 0xffffd1858a242000 Param2 (access type): 0x0 (read) Param3 (faulting instruction): 0xfffff8017bdddafd And the dump itself flags the culprit directly: *** eaanticheat.sys - Address FFFFF8017BDDDAFD base at FFFFF8017A580000, DateStamp 6a42e478 I sadly can't attach the crash dump or the crash event log from the blue screen event because the file format is not allowed here. Already reported this to mailto:[edit: email address removed] because you are accessing memory you are not supposed to. They said they judge it as not a security problem, so I post it here publicly. Please fix it. :(EA WRC crashes in menu - EADesktop.exe ntdll.dll 0xc0000005
Hello, I am reporting a crash issue with EA SPORTS WRC on PC through the EA App. The game was working perfectly before. I played for around 3 hours without any issues, but suddenly it started crashing after launching the game. The game starts normally, loads into the main menu, and I can navigate for around 60 seconds. After that, it closes silently to desktop without any crash report or error message. Windows Event Viewer shows: Faulting application: EADesktop.exe Faulting application: EAGEP.exe Faulting module: ntdll.dll Exception code: 0xc0000005 (Access violation) System: Platform: EA App (PC) OS: Windows 11 GPU: NVIDIA EA App version: 13.743.0.6256 Troubleshooting already performed: Repaired game files through EA App Completely reinstalled EA App Reinstalled EA Anti-Cheat Cleared EA App cache Clean installed NVIDIA graphics drivers Ran DISM and SFC system repairs Tested RAM with MemTest86 (no errors found) Created a new Windows administrator account Tested with Exploit Protection changes The issue remains unchanged. I have also found other recent reports from users experiencing similar behaviour: the game works normally, then suddenly starts crashing shortly after entering the main menu. Could this be related to EA App, EA Anti-Cheat, or a recent compatibility issue? Thank you.EA SPORTS WRC will not launch - Javelin Anticheat Error 87
EA SPORTS WRC will not launch - Javelin Anticheat Error 87 / Invalid game directory Game: EA SPORTS WRC (PC, EA App) Computer name: VENGEANCE OS: Windows 11 Summary: WRC fails to launch every time. Event Viewer (Application log) logs an EA Javelin Anticheat error (Event ID 1000) each attempt: "The game wrc.exe exited unexpectedly, exit code: 0x1." Most recently, the EA App itself also returned a generic error: "Failed to launch game. An error on our end caused the launch to fail. Try again a little later." Troubleshooting already completed (no change in behavior): - Repaired the game via EA App (My Collection > WRC > Repair) - Ran EAAntiCheat.Installer.exe from both C:\Program Files\EA\AC\ and the game's own bundled installer folder - both give "Invalid game directory" when selecting Repair, even when pointing to the correct install path (C:\Program Files\EA Games\EA SPORTS WRC) - Manually starting the EAAntiCheatService in services.msc fails with "Error 87: The parameter is incorrect" - Deleted and recreated the EAAntiCheatService via sc delete / sc create, pointing to EAAntiCheat.GameService.exe - no change - Ran sc query EAAntiCheatService to confirm the service exists (STOPPED, WIN32_EXIT_CODE 0) - Ran sfc /scannow - no integrity violations found - Ran DISM /Online /Cleanup-Image /RestoreHealth - completed, no change - Ran fsutil resource setautoreset true C: and rebooted - no change - Confirmed DNS resolves gateway.ea.com correctly (tested via 8.8.8.8 after finding ISP DNS was timing out; switched system DNS to 8.8.8.8/8.8.4.4 - no change to the anticheat error) - Verified no third-party antivirus is installed (Windows Defender only) - Temporarily disabled Core Isolation / Memory Integrity - no change - Checked Reliability Monitor - no critical events logged for the crash - Checked %localappdata%\WRC\Saved\Logs\WRC.log - file is empty - Ruled out a WRC_Trial.exe file in the Win64 folder as a cause (temporarily removed it, error persisted) - Confirmed install folder structure and installerdata.xml manifest are present and intact Given that Windows-level checks (SFC, DISM, service registration) all come back clean and the anticheat installer consistently rejects the correct install directory as invalid, I believe this may require backend access to my account/entitlement or install-token data to diagnose further. Could you please investigate on your end? Thank you for your help.
