Bot Backfill for Small Game Modes
Squad Deathmatch, KOTH, Team Deathmatch, Domination. All the small gamemodes do not (for me) ever seem to have enough players, and it taking over 30 mins to even fill half a lobby for a (minimum) player count is absurd. I shouldn't have to spend more time searching for games than playing them. Especially since I'm trying to work on the assignments for each of these modes.
BF6 cannot launch on some AMD mobile GPUs (RX6800M) - driver detection problem
Please help me bring some attention from EA or AMD to this issue. This is a bug that has not been fixed since game launch. We are now late March, almost April 2026. This bug prevents users from playing BF6. Not sure if EA or AMD has to review this. This applies to AMD mobile (laptop dedicated GPUs). A temporary fix is included down below. Please help me bring some attention from EA or AMD to this issue. Any vote is appreciated. The Problem: Battlefield 6 is detecting the wrong GPU driver. Even though your main GPU (RX 6800M) is updated, the game is reading the driver version of your Internal Processor Graphics (iGPU). Perhaps Windows Update often forcibly downgrades the iGPU driver to an older version (23.19.x), causing this mismatch error. Detailed pop-up message: Please update your AMD Radeon driver Detected AMD Radeon driver version 23.19.24.0. The required driver version is 25.10.25.1 or later. Please update your drivers at http://www.amd.com/ before playing the game. The Fix: You need to "spoof" the version number in the registry so the game sees the correct version and launches. 1. Open Regedit 2. Navigate to Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{B1E7C0AD-2AE9-11F1-8B19-BD6702B5743D}\0000 (your path might be different) 3. Scroll down until you see DriverDesc, verify it states AMD Radeon(TM) Graphics 4. Afterward, keep scrolling down to ReleaseVersion, double click to edit, then change it to 25.10.25.1 (no need to put the rest, just 25.10.25.1 is fine) Hardware used to obtain this bug: ASUS ROG Strix G513QY This specific laptop does not have a MUX switch, so everything goes via the iGPU first. Even when using an external monitor via HDMI. Some people reported that using the USB-C (DP) with an adapter bypasses the Radeon iGPU. Of course, this was tested with a complete clean install of Windows 11 and the latest AMD mobile drivers as of March 28, 2026 for the AMD RX6800M. AMD Radeon iGPU driver version: 23.19.24-251211a-197843C-AMD-Software-Adrenalin-Edition (problem is that it reads this one) AMD Radeon RX 6800M driver version: 25.10.43.05-260303a-198974C-AMD-Software-Adrenalin-Edition (should be reading this one)
BF6 as well as BF2042 constantly crashing
Since over 2 weeks my BF2042 started crashing without a reason during connecting to a game Now since 3 days, my BF6 starts crashing as well Latest graphic drivers (GeForce RTX 4090) etc installed, repaired game file sevreal times, nothing got better All other games work perfectly Just EA BF related games currently create an unplaybale situation.... Starting from full system reboot to simply returning black screen while trying to connect to a match to closing the game without any error, just back to Desktop as if never started...BF6 BSOD on launch PAGE_FAULT_IN_NONPAGED_AREA eaanticheat.sys
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 - 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 resultNot able to access game
Since the release of season 3 I have not been able to play redsec or multi-player unless I am in a party with someone else and they have to be the party leader. I don't have the options to even load redsec and it's telling me to download multi-player to play anything else. In the browse mode menu I have BULLETIN QUICKPLAY MULTI-PLAYER RANKED PORTAL CAMPAIGN
Matchmaking issue with party
In a party of two or more, no matter who's the leader, my friends are joining the match while I'm left behind in the menu, no error, it just stops matchmaking. It does not matter what mode or type of the game. To make it work (sometimes works) I have to leave the party, start matchmaking by myself, either wait to join a match and then quit or cancel the matchmaking. My friends have to quit the joined match, I have to rejoin with the party or invite them once more and try again. Most of the times after a match is finished and I remain for the next map, it stops searching and leaves me hanging on the map while my friends are on the next match already. I have to mention I'm in UK, and they both are in Romania (maybe is something to do with regions?) We all are on PC, EA app.
"Battlepass acquired" spam every time
So every time I click on the battlepass tab, for the first time after launching the game, it's behaving like if it was the first time in the season - it throws the "Battlepass acquired" screen, along with another one showing the Battlepass pro ad, preorder message and then instant unlocks. You have to wait for every one of those screens to load and then skip it, one by one. Fullscreen Golmund message also appears every time, might be the same issue as it seems forcing it on players 2 weeks into the season seems quite unnecessary and like something that should only pop up for people launching the game for the first time since S3 started.Game not launching
The game worked fine. But it was not launching or crashing within a minute last week. This week it never launched. I uninstalled and reinstalled the game twice. Disabled Core isolation, added compatibility for all files, added the folder on windows security excluded list, added all files on exploit protection. I tried almost every fix online. Reinstalled anticheat several times. Also, I'm attaching windows event viewer message below: Faulting application name: EAAntiCheat.GameServiceLauncher.exe, version: 1.0.25007.0, time stamp: 0x69f93e11 Faulting module name: EAAntiCheat.GameServiceLauncher.exe, version: 1.0.25007.0, time stamp: 0x69f93e11 Exception code: 0xc0000409 Fault offset: 0x000000000075bb45 Faulting process id: 0x366C Faulting application start time: 0x1DCE80C4FE24968 Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Battlefield 6\EAAntiCheat.GameServiceLauncher.exe Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\Battlefield 6\EAAntiCheat.GameServiceLauncher.exe Report Id: ae528335-41ef-4418-995e-3072029b79fe Faulting package full name: Faulting package-relative application ID:
