Battlefield 6 reproducible BSOD in EA Javelin AntiCheat
Hello, (IRQL_NOT_LESS_OR_EQUAL 0xA) I am reporting a reproducible kernel-level BSOD that occurs only while playing Battlefield 6. The issue has now reproduced multiple times with essentially the same crash signature, including after completely reinstalling EA Javelin AntiCheat, verifying the Battlefield 6 installation through Steam, updating the NVIDIA driver, and rebooting the system. SYSTEM CPU: Intel Core i9-14900K RAM: 32 GB DDR5-6400 Motherboard / System: Monster SEMRUK Z790 GAMING BIOS: 6.01 CPU microcode currently loaded: 0x12F Operating System: Windows 11 Build 26200.8875 x64 Game: Battlefield 6 Steam version GPU: NVIDIA Driver updated to the latest available version before reproducing the issue again. ANTI-CHEAT EA Javelin / eaanticheat.sys is installed. I performed a complete game-specific EA AntiCheat reinstall using: C:\Program Files\EA\AC\EAAntiCheat.Installer.exe Procedure performed: Battlefield 6 → Uninstall Reboot Battlefield 6 → Install Reboot Steam → Verify integrity of game files The BSOD still reproduced afterward with the same signature. REPEATED BUGCHECK SIGNATURE Multiple crashes reproduce: BugCheck: 0x0000000A – IRQL_NOT_LESS_OR_EQUAL Arg1: 0x00007FFFFFFF0000 Arg2: 0x00000000000000FF Arg3: varies between crashes (for example 0xCE, 0xEE, 0x4E, 0xAE, 0x0E) Arg4: resolves into the same ntoskrnl / RtlVirtualUnwind2 code path for the corresponding Windows build. Process at the time of the crash: bf6.exe The important part is that Arg1 = 0x7FFFFFFF0000 and Arg2 = 0xFF remain reproducible across the crashes. KERNEL DUMP ANALYSIS I captured a full kernel memory dump, not only a minidump. Analysis of the kernel dump shows an exception occurring while executing code inside eaanticheat.sys. The relevant EA AntiCheat offset observed in the dump is: eaanticheat.sys + 0x4B480F3 At this location the instruction sequence ends in an indirect control transfer: jmp rax The register used as the jump target contains a non-canonical / invalid virtual address at the time of the exception. An initial 0xC0000005 access violation is therefore observed in the EA AntiCheat execution path. Windows subsequently enters its exception / stack-unwind path. The crash then proceeds through: nt!RtlVirtualUnwind2 During the unwind/exception handling path, Windows encounters the recurring: 0x00007FFFFFFF0000 address and the machine eventually bugchecks with: IRQL_NOT_LESS_OR_EQUAL (0xA) This makes ntoskrnl.exe appear in Windows Error Reporting, but the kernel dump indicates that the exception sequence begins while executing the EA AntiCheat code path before Windows reaches RtlVirtualUnwind2. I understand that without EA's private PDB symbols/source code I cannot identify the exact internal EA function responsible. However, the same EA AntiCheat offset and the same subsequent Windows unwind path are reproducible. REPRODUCTION CHARACTERISTICS The crash occurs during Battlefield 6 gameplay. It is not a random collection of different BSODs. Across multiple occurrences I repeatedly get: bf6.exe 0xA IRQL_NOT_LESS_OR_EQUAL Arg1 = 0x7FFFFFFF0000 Arg2 = 0xFF eaanticheat.sys execution context RtlVirtualUnwind2 / exception-unwind path The machine can otherwise operate normally. There are no WHEA-Logger hardware-error events associated with these crashes. TROUBLESHOOTING ALREADY COMPLETED NVIDIA driver updated. Battlefield 6 fully updated. Steam game-file integrity verified. EA Javelin AntiCheat completely uninstalled and reinstalled. System rebooted after AntiCheat reinstall. BIOS is already updated. Intel Core i9-14900K is currently running microcode revision 0x12F. The issue reproduced again after all of the above. Windows kernel memory dump collection was enabled specifically to investigate this issue, and the BSOD reproduced again afterward. REQUEST Could this please be escalated to the EA Javelin AntiCheat engineering team? In particular, please investigate the eaanticheat.sys execution path around: eaanticheat.sys + 0x4B480F3 and its interaction with Windows exception/unwind handling / RtlVirtualUnwind2. The crash is deterministic enough that multiple dumps reproduce the same unusual 0xA signature. I can provide: 1. The latest minidump. 2. Previous minidumps showing the repeated signature. 3. A kernel MEMORY.DMP containing the full crash context. 4. Windows Event Viewer BugCheck records. 5. System / BIOS / driver information. Because a kernel MEMORY.DMP may contain private information from system memory, I would prefer to provide the full kernel dump through a private EA support/upload channel rather than attaching it publicly to a forum post. Please let me know where I can securely upload the kernel dump for the Javelin engineering team. Thank you. [edit: email address removed]
Battlefield 6 / EA Javelin Anti-Cheat Crash Investigation Report
Multiple users appear to report similar EA Javelin Anti-Cheat crashes after recent updates. So I hope this will help. Issue Summary Battlefield 6 launches successfully through Steam and EA App. EA Javelin Anti-Cheat initializes correctly and the game reaches the main menu. The crash does NOT occur during startup. The game consistently crashes after approximately 2-7 minutes, either while sitting in the main menu or during active gameplay. No BSOD occurs. No DirectX error appears. No NVIDIA driver crash is reported. Windows Event Viewer repeatedly logs EA Javelin Anti-Cheat related errors. System Information Windows 11 Pro Build 26200 AMD Ryzen 7 9800X3D ASUS ROG Crosshair X670E Hero BIOS 3702 64 GB DDR5 RAM Secure Boot enabled UEFI enabled Reproduction Steps Launch Battlefield 6 through Steam EA App starts normally EA Javelin Anti-Cheat initializes Battlefield reaches main menu Stay in menu or join a server Crash occurs after approximately 2-7 minutes Observed Event Viewer Errors EA Javelin Anti-Cheat Event ID: 1000 Message: Invalid argument count Additional recurring entries: Exit Type 95 Count 267 Observed after every crash. Additional Error StartServiceCtrlDispatcher failed with error 1063 Troubleshooting Already Performed Battlefield: Full reinstall File verification completed EA Anti-Cheat: Full reinstall Service verified Hardware: EXPO tested Hardware stability checked RAM instability appears unlikely CPU instability appears unlikely Windows Security: Secure Boot enabled Memory Integrity disabled Core Isolation disabled Hypervisor Investigation: Hyper-V Windows Features disabled hypervisorlaunchtype set to Off Hyper-V not active Device Guard / VBS: VBS indicators still present EnableVirtualizationBasedSecurity = 1 observed Driver Investigation: fltmc reviewed No suspicious third-party filter drivers found ASUS Investigation: Armoury Crate previously installed Remaining ASUS background services observed No definitive correlation confirmed Important Observation The game successfully launches and remains playable for several minutes before crashing. This suggests: Anti-Cheat installation is functional Secure Boot requirements are satisfied Battlefield launches successfully The failure appears to occur during runtime rather than startup. Requested Investigation Please review: EA Javelin Event ID 1000 “Invalid argument count” Exit Type 95 Count 267 Runtime crash occurring 2-7 minutes after successful launch At this point most common causes have already been investigated and excluded.
Apex Legends Crash on Launch / EAC Fail (Secure Boot Error)
Since the recent game update, Apex Legends fails to launch on the EA App. The game crashes or closes immediately after the splash intro screen, and EasyAntiCheat_Setup.exe flashes briefly and closes without launching. The game directory is missing the standard EAC installer, and there is no option to repair or reinstall EAC manually. Details from Case #252049873: During my previous chat with EA Support under Case #252049873, Advisor Yash suggested running bcdedit commands via CMD to force re-register EAC services. However, the system blocked this with the error: "The value is protected by Secure Boot policy and cannot be modified or deleted." Troubleshooting Steps Already Attempted: I have already tried reinstalling the EA App, using the Repair function for Apex Legends in the EA App library, clearing EAC cache files from %localappdata% and C:\Program Files (x86)\EasyAntiCheat, updating GPU drivers to the latest version, and running both the EA App and Apex Legends as Administrator. Since the EAC setup cannot be repaired manually and the CMD workaround is blocked by Windows Secure Boot, I am unable to launch the game. Please investigate this issue or pass this to the game team for a fix. I have attached my DxDiag file and error screenshots for your review. Thank you!
IA Javelin AntiCheat banindo players injustamente
Olá a todos. Estou criando este tópico porque acredito sinceramente que fui banido por engano e espero que alguém da EA possa analisar meu caso de forma manual. Sou jogador da franquia Battlefield desde 2014. Ao longo desses mais de 10 anos comprei diversos títulos da série, investi muito dinheiro na franquia, passei centenas de horas jogando e nunca recebi qualquer advertência, suspensão ou banimento. Minha conta sempre teve um histórico completamente limpo. No dia 01/08/2026 fui surpreendido com um banimento permanente por "Gameplay Enhancement". O problema é simples: eu nunca utilizei qualquer tipo de cheat. Nunca usei aimbot, wallhack, ESP, Cheat Engine, macros, injetores, modificadores de memória ou qualquer software desenvolvido para obter vantagem competitiva. Após o banimento enviei um recurso explicando meu histórico e solicitando uma revisão manual. Infelizmente o recurso foi negado sem qualquer explicação técnica sobre o que realmente ocasionou essa punição. Apenas fui informado que houve "Gameplay Enhancement". Gostaria de entender qual software foi detectado, qual comportamento foi considerado irregular e qual evidência justificou um banimento permanente. Até hoje não obtive nenhuma resposta objetiva. Nos últimos dias tenho visto diversos relatos na comunidade de jogadores antigos afirmando que receberam banimentos semelhantes e questionando o funcionamento do novo sistema anticheat Javelin. Muitos desses jogadores possuem anos de histórico limpo na franquia e afirmam nunca terem utilizado qualquer tipo de trapaça. Não sei se esses relatos representam um problema geral, mas acredito que merecem atenção e uma análise cuidadosa. Entendo perfeitamente que um anticheat é essencial para proteger Battlefield dos verdadeiros trapaceiros. Todos nós queremos um jogo justo. Porém, nenhum sistema automatizado é perfeito. Quando existe a possibilidade de um erro, acredito que todo jogador deveria ter direito a uma revisão humana antes de receber uma punição permanente. Sou um jogador fiel à franquia Battlefield desde 2014. Continuei comprando os jogos, apoiando a marca e acreditando na série durante todos esses anos. Jamais colocaria em risco uma conta construída ao longo de mais de uma década utilizando qualquer tipo de trapaça. Não estou pedindo privilégio. Estou apenas pedindo transparência, justiça e uma análise humana do meu caso. Caso realmente exista alguma evidência de que utilizei cheats, gostaria que ela fosse apresentada. Caso tenha ocorrido um erro, espero sinceramente que ele seja corrigido. Se meu caso continuar sendo ignorado e eu não receber uma análise humana adequada, infelizmente terei que buscar orientação jurídica e exercer os direitos que a legislação brasileira me garante para discutir este banimento e os prejuízos que ele me causou. Ainda assim, meu objetivo continua sendo resolver essa situação diretamente com a EA, de forma respeitosa, transparente e amigável. Espero sinceramente que alguém da equipe leia este relato e realize uma nova revisão do meu caso. Obrigado a todos que dedicaram seu tempo para ler esta mensagem.
Apex S30 crash: EAC Untrusted amdihk64.dll on AMD RX 500 series
After the Season 30 "MARKED" update on August 5, 2026, Apex Legends crashes the moment I click "Play" to join a match, with this popup: Easy Anti-Cheat: Untrusted system file (\\?\GLOBALROOT\Device\HarddiskVolume3\Windows\System32\amdihk64.dll) The game enters the lobby fine, but joining any match triggers the EAC popup and immediate crash. My setup: - GPU: AMD Radeon RX 590 GME (Polaris / RX 500 series) - Driver: AMD Software Adrenalin Edition 26.5.2 (DriverVersion 31.0.21925.1001), the latest WHQL driver available for my card - amdihk64.dll version 2.00.00.1788 (Radeon Settings: Host Service), valid AMD signature verified - OS: Windows 10 64-bit - Launcher: Steam (D:\SteamLibrary\steamapps\common\Apex Legends) Background: I had this exact same issue earlier this year. AMD released a driver update on/around May 2, 2026 (Adrenalin 26.5.x) that explicitly fixed Apex crashes, and it worked perfectly for months. After the Season 30 update on August 5, 2026, the issue is back and blocking me from every single match. What I have already tried (every single one): - Clean reinstall of AMD drivers (DDU in Safe Mode + fresh install) - Completely disabled Windows Security Center and Windows Update - Reinstalled Windows from scratch, then reinstalled drivers cleanly - Reinstalled Apex Legends from scratch - Verified game files multiple times via Steam - Repaired EAC service via EasyAntiCheat_Setup.exe - Disabled OBS Studio and Watt Toolkit (Steam++) to rule out overlay conflicts - Disabled all AMD Radeon Software scheduled tasks and services - Renamed C:\Windows\System32\amdihk64.dll (kills the popup, but EAC then silently terminates the game because it detects a missing driver file = "system tampered") - Tried to rename the DriverStore copy under C:\Windows\System32\DriverStore\FileRepository\u0201039.inf_amd64_* - blocked by Windows Resource Protection (WRP) in both normal mode and Safe Mode Key observations: - amdihk64.dll has a valid AMD digital signature (verified) - The new Adrenalin 26.7.1 driver does NOT support RX 500 series GPUs, so there is no newer driver I can install - AMD has effectively ended driver support for Polaris (RX 400/500 series), so 26.5.2 is the final driver for the entire installed base of these cards - Many RX 500 series AMD users are likely affected by the same problem Temporary workaround: Following the accepted solution in another thread, I deleted the EasyAntiCheat folder inside the Apex installation directory and ran Steam's "Verify integrity of game files" to redownload a fresh copy. This sometimes lets me into a match, but the problem recurs. Request: - Please update the Easy Anti-Cheat trust list to include amdihk64.dll version 2.00.00.1788 shipped with AMD Software Adrenalin Edition 26.5.2 (or whichever specific build/version is needed). - Since RX 500 series GPUs cannot be updated past 26.5.2, this is the only driver version that entire installed base can have. The EAC trust list needs to recognize it. - Many AMD users are likely being silently blocked from playing Apex. Reproduction steps: 1. Install AMD Software Adrenalin Edition 26.5.2 on any RX 500 series GPU 2. Launch Apex Legends via Steam 3. Enter the lobby 4. Click "Play" to join a match 5. EAC popup appears, game crashes immediately Thank you.