Game won't start after the Season 4 update (Steam)
So i press "Play" in Steam library, the splash window shows up (checking for updates, launching anticheat etc) and then it just stops. It fully closes on its own. Everything was just fine right before the update. Tried everything. Verifying files, full uninstall and redownload, firewall/antivirus, tried older nvidia drivers and then tried the newest ones - still nothing, literally DOA for now and i want to play soooo much please send help. Am I alone?Solved318Views2likes13CommentsXbox Series X - Game won’t launch
Hi. Everytime i try to play battlefield 6 on the Xbox i get an error which says; “Undefined Error Occurred”. this happens everytime i launch the game. The only way to fix this is to try again or completely shutdown the Xbox. This seems like a tedious thing to do. All other games work fine. I have also tried to uninstall and reinstall, this hasn’t fixed the issue either. Please look into this and help.BF6 Crash on Launch, Black Screen
Hi, has anyone come across this problem - BF6 was working fine on my computer until last update (i think!!). Steam loads ok, game starts to load, no error messages, anticheat loads etc then when the black screen comes up just before the start menu appears the game Shuts Down (Steam still remaining open) I have cleared caches; checked latest drivers; deleted and reinstalled both Steam and BF6Solved3.3KViews2likes152CommentsBF6 Black Screen Crash Fixed by AMD Driver Rollback to 26.3.1
Hello, I want to share my full troubleshooting process and the final solution in case it helps other AMD users and EA/DICE developers investigate the issue. Problem: Since 23/06/2026, Battlefield 6 would no longer launch. The launch sequence was always the same: EA AntiCheat starts. AntiCheat loading bar completes. EA App says “Launching game”. A black screen appears for a few seconds. The game closes. EA App opens again. There was no in-game error message. The game simply returned to the EA App. The issue started after I had played Battlefield 6 for hours without any problem on 22/06/2026. I shut down the PC normally, and the next day the game started crashing on launch. System Specs: CPU: AMD Ryzen 5 7600X GPU: Sapphire RX 7800 XT Nitro+ Gaming OC 16GB Motherboard: Gigabyte B650M DS3H RAM: Patriot DDR5 6400 MHz SSD: XPG GAMMIX S70 Blade 1TB NVMe PCIe 4.0 PSU: Rampage 750W 80+ Bronze OS: Windows 11 Pro Monitor: AOC 27” 1080p 165Hz FreeSync + secondary ASUS 75Hz monitor Things I Tried Before Finding the Fix: Cleared EA App cache Reinstalled EA App Repaired Battlefield 6 files Reinstalled Battlefield 6 Repaired/reinstalled EA AntiCheat Deleted EA AntiCheat folder and forced EA App to reinstall it Added Windows Defender exclusions for Battlefield 6 and EA AntiCheat folders Disabled Windows real-time protection temporarily Ran EA App and BF6 as administrator Cleared Battlefield 6 cache and crash dump folders Renamed/reset the Documents\Battlefield 6 folder Tested with clean PROFSAVE_profile Restored original PROFSAVE_profile and multiplayer profile files Cleared AMD shader cache folders Cleared DirectX shader cache Disabled AMD overlay Disabled Razer Synapse / Razer Cortex Disabled MSI Afterburner / RTSS Disabled HYPR-RX Disabled AMD Fluid Motion Frames / AFMF Disabled FSR / upscaling Disabled Radeon Boost, Chill, Enhanced Sync Checked Windows Event Viewer Checked Reliability Monitor Ran SFC /scannow Ran DISM checks Checked Volume Shadow Copy / COM+ services Tested with reduced background apps Important Crash Dump Findings: I analyzed the Battlefield 6 .mdmp crash dump using WinDbg Preview. Relevant output: PROCESS_NAME: bf6.exe Failure.Bucket: INVALID_POINTER_READ_c0000005_amdxc64.dll!Unknown ExceptionCode: c0000005 - Access Violation Faulting module: amdxc64.dll IMAGE_NAME: amdxc64.dll MODULE_NAME: amdxc64 The crash occurred here: amdxc64!GetSettingsBlobsAllDecoded+0x5fa mov rcx,qword ptr [rax+18h] The register value showed: RAX = 0000000000000000 So the driver attempted to read from: 0000000000000018 This looks like a NULL pointer / invalid pointer read during the DX12 render initialization path. The call stack included: amdxc64.dll amd_fidelityfx_framegeneration_dx12.dll amd_fidelityfx_loader_dx12.dll bf6.exe The loaded AMD DX12 driver module was: amdxc64.dll File version: 32.0.31021.5001 ProductName: AMD Radeon DirectX 12 Driver Timestamp: Fri Jun 26 2026 The FidelityFX Frame Generation module was loaded from the Battlefield 6 install directory: C:\Program Files\EA Games\Battlefield 6\amd_fidelityfx_framegeneration_dx12.dll File version: 4.0.0.0 ProductName: AMD FidelityFX Frame Generation Final Fix: The issue was fixed by performing a clean AMD driver rollback. Steps that fixed it: Backed up AMD Adrenalin settings and Battlefield 6 settings. Downloaded AMD Adrenalin 26.3.1 from the official AMD website. Disconnected the internet. Booted into Safe Mode. Used DDU to completely remove the current AMD GPU driver. Rebooted into normal Windows. Installed AMD Adrenalin 26.3.1. Rebooted. Launched Battlefield 6. After installing AMD Adrenalin 26.3.1, Battlefield 6 launched successfully. I tested the game for more than 15 minutes, then restored my original Battlefield 6 settings files: PROFSAVE_profile PROFSAVEbf6mp PROFSAVEbf6mp_profile The game still worked normally. I also tested with: Radeon Anti-Lag: ON FPS limit: 120 Razer software: ON MSI Afterburner: ON The game remained stable. Conclusion: In my case, the issue was not caused by: EA App cache Battlefield 6 game files EA AntiCheat installation Windows Defender Windows system corruption PROFSAVE settings Razer Synapse / Cortex MSI Afterburner AMD shader cache Battlefield 6 cache The issue appears to be related to a newer AMD Adrenalin driver branch conflicting with Battlefield 6’s DX12 / AMD FidelityFX Frame Generation initialization path. The crash dump consistently pointed to: amdxc64.dll amd_fidelityfx_framegeneration_dx12.dll amd_fidelityfx_loader_dx12.dll c0000005 Access Violation Rolling back to AMD Adrenalin 26.3.1 fixed the black screen crash loop completely. I hope this helps other AMD RX 7000 series users and helps EA/DICE/AMD investigate the compatibility issue.Solved2.1KViews4likes6CommentsBF6 BSOD on Launch: EA AntiCheat Crash
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)Solved972Views2likes47CommentsGame freezes the computer during a match
Hello, I ve got a common problem on my setup Ryzen 5800x MSI b550 Radeon 7900xt 32gb ddr4 850w corsair Game is just freezing my pc. I cant do anything, only restart whole setup. There is no dump file, there is no error code. Just frozen screen. I tried many things. Different gpu drivers, deleting cache, runnin as admin, changing settings on Adrenaline, still no hope. Sometimes there is also problem with DirectX. I have to reinstall drivers to solve it... I was hoping the Season 4 update would help but after 73gb of files installed on pc the problem isnt solved. Thats kinda embarrasing, i ve got 430lvl , spend big money in game and cant play single match. Sorry for my eng, tryin my best.137Views0likes10CommentsLast 3 hours cant play or log in
Ive reset everything xbox, internet nothing works been getting this error anytime i try to connect to battlefields online service.. nothing working. I guess its unplayable today? Servers say they are up though. image attached with example, ive gotta couple different codes but same error when trying to log in. Been on going for 3-4 hour today -_- anyone have any information on this? Im hearing its just xboxServer ping
Hello EA Team, Could you please let us know when the Middle East servers will be fixed? Many players in the region are experiencing extremely high ping, unstable connections, and poor overall gameplay. The game has become very difficult to enjoy because of the constant latency issues, and the community has been waiting for an update. Please provide us with any information regarding when the Middle East servers will be restored or improved. We would really appreciate an official update. Thank you.Ranked Battleroyal is unstable and almost unplayable for me
It used to work well but for some reason in the last month it has become unplayable. 1 out of every 3 games I try to play I am dropped before the battle royal starts and lose the initial game points. During the game, there is 1 out of 4 change I will be kicked out mid game due to "inactivity" even if I just killed someone 2 seconds ago. Just now I was playing a nice game and bum, disconnected due to "inactivity" winning in middle of a fight. Could you implement some better checks before dropping someone due to inactivity? + before kicking out people from a match that just started (no rage quit, no bad performance) know if it was intentional or not in order to decide if points are deducted or not?