Battles Crashing
I've had 3 combat missions crash after clearing the first phase during Territory Battle. Today I had a crash just as I was starting a GAC battle. TB crashes are sad as they hurt the guild but GAC crashes cost me crystals. Running on IOS 26.5 on ipad 9th generation. Tried clearing cache, reinstalling, rebooting.5Views0likes0CommentsError Message - "We've noticed your computer is currently offline."
I have done every single possible solution/troubleshoot known Reinstalled FC 26 Verified game files through Steam Reinstalled EA AntiCheat Confirmed EA App is online and functioning Confirmed FC 26 appears in my EA Library and shows a Play button Confirmed my Steam account is linked to my EA account Confirmed internet connectivity is working Successfully pinged ea.com Successfully resolved ea.com through DNS Confirmed no proxy server is enabled Attempted launching through both Steam and directly through the EA App Cleared EA App cache Restarted PC multiple times Confirmed Secure Boot is enabled Confirmed BIOS is set to UEFI Nothing has worked and I know for a fact the problem isn't Steam its you guys. Please fix your game EA Fifa isn't the same anymore you don't care about the experience of customers. Please just help me. Thanks.92Views1like3CommentsBSOD Crash (Bugcheck 0x50) caused by eaanticheat.sys
BSOD Crash (Bugcheck 0x50) caused by eaanticheat.sys on Windows 11 Build 29613 Description: While running the game, the system consistently encounters a BSOD. A native minidump analysis confirms that the crash is an invalid system memory reference (PAGE_FAULT_IN_NONPAGED_AREA) directly triggered by the eaanticheat.sys kernel component driver. System & Hardware Environment: Windows 11 (Build 29613) AMD Ryzen 7 9800X3D / NVIDIA RTX 4070 SUPER / 32GB RAM Debugger Triage Metrics: BUGCHECK_CODE: 50 BUGCHECK_P1: fffff80402a264aa BUGCHECK_P3: fffff803b2768feb FAULTING_MODULE: eaanticheat.sys Relevant WinDbg Stack Output: Unable to load image eaanticheat.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for eaanticheat.sys PAGE_FAULT_IN_NONPAGED_AREA (50) Invalid system memory was referenced. I have completed the steps below, consistently repeating the above error. Repaired game files via EA app EAAntiCheat.Installer.exe: Uninstalled, installed and repaired BF6 EA App, help, recovery, clear cache. Uninstalled game, then deleted all EA folders from all drives, removed all EA references from registry. Installed BF6 from EA App Windows Security, disabled Core Isolation, Memory Integrity, and added all EA folders to the exclusions list.29Views1like2CommentsBattlefield 6 BSOD 0x50 in eaanticheat.sys
Battlefield 6 is consistently causing a Windows BSOD during launch / shortly after launch. This is not a normal user-mode Battlefield crash. It is a Windows kernel bugcheck, and WinDbg identifies EA AntiCheat / Javelin as the faulting module. WinDbg summary from C:\Windows\Minidump: PAGE_FAULT_IN_NONPAGED_AREA (50) Arguments: Arg1: ffffe40011bbd000, memory referenced Arg2: 0000000000000000, read access Arg3: fffff8036cb007f6, instruction address that referenced bad memory Arg4: 0000000000000000 Key WinDbg fields: PROCESS_NAME: bf6.exe MODULE_NAME: eaanticheat IMAGE_NAME: eaanticheat.sys SYMBOL_NAME: eaanticheat+1b407f6 FAILURE_BUCKET_ID: AV_eaanticheat!unknown_function FAILURE_ID_HASH: {d544cf09-4735-e698-77c3-5df5924e5448} Faulting instruction: eaanticheat+1b407f6: mov r9d,dword ptr [rbx+rax+8] Relevant stack excerpt: nt!KeBugCheckEx nt!MiSystemFault nt!MmAccessFault nt!KiPageFault eaanticheat+0x1b407f6 System: Windows 11 10.0.26200 Build 26200 CPU: Intel Core i9-12900KF GPU: NVIDIA RTX 3080 RAM: 64 GB Motherboard: Gigabyte B660M DS3H DDR4 Secure Boot: On TPM: Present VBS: Running Credential Guard: Running Hyper-V / hypervisor: Present NVIDIA driver at time of dump: 32.0.16.1047 What I have already tried: Reinstalled EA AntiCheat / Javelin multiple times Cleared EA App cache Cleared Battlefield cache Cleared shader caches Reinstalled NVIDIA drivers Disabled Discord overlay Disabled NVIDIA overlay Tried different monitor configurations Updated motherboard BIOS Disabled MSIO / Asusgio2 / Asusgio3 kernel drivers Ran extended memory diagnostics Verified Secure Boot and TPM are enabled/present The crash still occurs, even after the last Battlefield update. This has been happening for a month now. I am not asking for generic advice such as reinstalling Windows, reinstalling the game, checking Secure Boot, checking TPM, or scanning for malware. The dump points to a kernel-mode crash in eaanticheat.sys. This should be escalated to the EA AntiCheat / Javelin team. Questions: 1. Is FAILURE_ID_HASH {d544cf09-4735-e698-77c3-5df5924e5448} already known internally? 3. Is there a known workaround other than disabling core Windows virtualization/security features? 4. Can EA provide a fixed EA AntiCheat / Javelin build or acknowledge this crash signature? I can provide the minidump, full WinDbg !analyze -v output, msinfo32 export, DxDiag, and any requested Code Integrity / Event Viewer logs privately to EA staff. If other players are seeing a BSOD with eaanticheat.sys and the same failure hash, please reply with your Windows build, CPU, GPU, NVIDIA/AMD driver version, and whether Hyper-V/VBS is active.145Views4likes6CommentsBF6 BSOD on Launch
Battlefield 6 has BSOD'd on launch every attempt since May 22, 2026 — one day after the May 21 Javelin anti-cheat depot update. No software, hardware, BIOS, or driver changes were made on my end before onset. The crash is deterministic, reproducible 100% of the time, and the dump analysis points to a regression inside the current Javelin build, not a system configuration issue. Crash signature (identical across 8 minidumps) - Process: bf6.exe - Bug check: 0x50 PAGE_FAULT_IN_NONPAGED_AREA eaanticheat.sys - Parameter 2 (access type): 0 (read) - Faulting instruction: inside eaanticheat.sys at the same fixed module-relative offset +0x80BA2C in every crash (raw RIP varies only by KASLR base) - Faulting address (P1): varies per crash, always page-aligned, always in kernel pool (unmapped) - R12 register at fault: ntoskrnl.exe + 0xE38040, identical across all dumps — a fixed kernel global serving as the anchor for a list-traversal - OS: Windows 11 24H2 (build 26100) Interpretation: a single instruction in eaanticheat.sys reads through a pointer that points to unmapped kernel pool memory. The instruction is constant, the data it loads is garbage that differs per crash. This is the classic signature of a deterministic code defect — most likely a use-after-free or stale pointer in a list-walk anchored at a fixed kernel global. Not random memory corruption; not hardware. What I ruled out (so you don't have to ask) - Hardware / RAM: EXPO/XMP disabled the entire time the system has existed. No overclock anywhere on the system. System ran BF6 and every other workload flawlessly for ~11 months prior. The deterministic same-instruction fault is mathematically inconsistent with random memory corruption. - BF6 install: full uninstall/reinstall, file verification, and a complete reinstall to a separate physical drive — no change. Reinstalling pulls the same Javelin build, which is the broken one. - Anti-cheat reinstall: EAAntiCheat.Installer.exe uninstall + reinstall — no change. - Conflicting drivers (driver uninstall, kernel-level verification of removal): - Radmin VPN (RvNetMP60.sys) — uninstalled, confirmed gone via pnputil/sc query, still crashes - FACEIT Anti-Cheat (FACEIT_AC.sys) — uninstalled, confirmed gone, still crashes - VirtualBox kernel drivers — not loaded in subsequent crashes either, still crashes - Driver Verifier on every non-Microsoft driver with Special Pool + Pool tracking + Force IRQL + I/O verification + Misc checks: caught nothing. Bug check remained 0x50 in eaanticheat.sys at the same +0x80BA2C offset. No third-party driver implicated. - Recently unloaded drivers list in the dumps: only one non-Microsoft transient driver appears (CorsairVHidDriver, normal HID re-enumeration), and the faulting address never falls in any unloaded driver's range. The fault is on freed/invalid pool, not on unloaded driver code. Correlation with the May 21 Javelin push - First crash: May 22, 2026. SteamDB shows a Javelin depot update on May 21, 2026. - Pre-May 22: ~11 months of stable BF6 play, no changes to system. - Pattern matches the previously documented April 16, 2026 Javelin regression that caused identical kernel-mode failures across multiple Battlefield titles. - Multiple players in the EA forums are reporting the same onset date with similar symptoms. What would actually help - Revert the Javelin client to the pre-May 21 build, or push a hotfix targeting the list-traversal at module offset +0x80BA2C. - A way for affected players to roll Javelin back to the prior depot while a fix is prepared. System specs - OS: Windows 11 24H2 (build 26100) - CPU / platform: AMD AM5 (EXPO disabled) - Memory Integrity / Core Isolation: OFF - BF6 install: tested on two separate physical drives, same result (Cm edit title for vis)Solved299Views1like12CommentsBSOD at game startup
PAGE_FAULT_IN_NONPAGED_AREA eaanticheat.sys When I start the game, I have a little splash art screen with the EA Javelin loading. Game tries to start and after around a minute of black screen there is BSOD with the given details. I have tried everything I found except reinstalling the OS and updating the BIOS. I have been playing golmud just fine, had exams, didn't play for few days and when I tried to play again now I get this every single time, making me unable to even get to the menu. I have tried: - updating the Windows to 25H2 - reinstalling the game - deleting the EA anticheat and starting the game to make it reinstall - sfc /scannow - check disk - updating/rolling back the drivers - disabling hyper-v - disabling old drivers I had or updating them - made sure I have TPM on - I tried starting it with 16 out of 32gb ram - tried disabling XMP - enabling Core Isolation - I believe i also did mdsched - and others... I have zero idea what could be causing it, analysed the minidumps with Claude and as I understand it, eaanticheat tries to read paged memory region from nonpaged context. I dont understand why it happened just after I have played few games at Golmud I am attaching 2 dumpfiles (one with hyperV enabled, the other with hyperV disabled), DxDiag and few logs from event viewer. If I should attach anything else let me know.177Views3likes11CommentsIt’s been a year and game is still buggy
I play madden 26 on my ps5. I only play ultimate team when I log in. And there has been a bunch of glitchy things when I played ultimate team. Just now, I was playing in a ai match and I was kicked off for no apparent reason. So I got no reward no nothing in the end after all the grinding and work I did. Sometimes when I open selected packs, I also get kicked off the game. I still got my items after all but it’s very annoying to get kicked off the game 24/7 and having to re-log every time. It’s been a whole year of madden 26 yet y’all still don’t listen to anyone’s advice and it keeps on happening. I hope your new 27 isn’t garbage like 26.9Views0likes0CommentsMore Redsec bugs
So, after playing Ranked Redsec on PC quite regularly since it's launch, here are some of the issues I regularly run into: Problems with menus on game start - these manifest as lack of ability to change class as the menu doesn't load (or loads with significant delay) Graphics glitches during game start - player models not loading Getting randomly stuck in map - not too often but there have been severals situations in which I got stuck (in Downtown) and got killed by fire as I couldn't get out Deploying into an alredy ongoing game and losing a second chance in the process - sometimes I'm basically redeployed into a match that is already ongoing and through that redeployment I lose my initial second-chance redeployment, which is obviously very annoying General netcode issues - getting insta-killed, seeing shots being registered on target only to get killed by that player and see that he has full health (on the after-kill cam), getting killed behind cover, all still an issue Weapons not fireing sometimes - occasionaly I will have a situation in CQB where I run into an opponent, press mouse to fire but nothing happens on my side I get killed (I presume this relates to netcode as well) Various bugs when starting a new match - I've had situations where I hear all the sound indicating that the game has started but my screen is just static, issues where members of my party would drop out during loading screen, game just crashing out of the blue etc.11Views1like1Comment