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 BF63.5KViews2likes157CommentsError when connecting
I haven’t been able to play this game at all for about 2 months keep getting a error that won’t allow me to load into the main menu I’ve contacted ea support multiple times still no fix anyone knows a way round it I’ve tried **bleep** near everything I could find I can play any other ea title but bf64Views0likes0CommentsAMD GPU Driver Deletion- Battlefield 6
When launching into the game (Battlefield 6/BF6) and idling for 1-2 minutes, my AMD graphics drivers and software were entirely deleted from my PC. Main and secondary displays black-screened and required re-install of all graphics drivers and software to function. PC Specs: CPU: AMD Ryzen 5 7600X3D 6-Core Processor RAM: 32 GB GPU: AMD Radeon RX 7800 XT - VRAM: 16 GB1.1KViews1like15Commentsunknown error
My husband and I have 2 xbox x consoles side by side and we are wanting to play Battlefield 6 together. But when we try to load the game we the an unknown error code. They both run on wifi. We have excellent internet so that shouldn't be the problem. We have tried to hardwire one console and that didn't work. We tried logging one console into a different wireless access point and that did work. I even tried connecting one to my mobile hot spot and that didn't work. When we both turn on the game to play together we immediately get the error code however if just one of us tries to play the game slone it works fine. Please help how can we fix this?SolvedUnknown Error on Xbox 0:75030S:-2145844748U
Hello EA, I'm trying to get on Battlefield on my Xbox Series S and it's not letting me get on. I took a picture hoping you can see it. It won't connect to services on my console at all or let me get on the main menu page of the game. This just started for me today and I'm only connect to my EA account to Xbox I believe not on my PC or anything else. Please check this out, I'm hoping it's not just me that it's happening right now. Thank You. [CM edit: title]Solved398Views4likes47CommentsRedsec matchmaking and class selection
Is anyone still having the issue where you are unable to choose the class you want or edit favourite weapons whilst in the chinook in pregame? Happens all the time! There is also a matchmaking bug where you press ‘A’ to start matchmaking, it will look for a game then after about 2 minutes it will make the sounds and carry out the actions that you’ve found a game to which your character will just stare at you for about 15 seconds! Then the prompt box for matchmaking will reappear, almost like you’ve never pressed it and searched for a game.4Views0likes0CommentsBF6 not launching
My issue has been swept up in a variety of driver based issues, so I'm having another go. Since June 7th (after a small ~280MB patch to BF6) I have been unable to launch the game through Steam. The anticheat splash window pops up, does it's normal things, then disappears and the Steam "play" button goes back to play. Checking the Windows Application event logs I have the attached error (it's always been this error). If I install REDSEC in the EA app the game launches, so this specifically is an issue with the Steam version of the game. I have performed the following: Up/downgraded my AMD GPU drivers Upgraded my BIOS firmware Uninstalled Anticheat (completely, as admin, etc) Uninstalled Steam BF6 + reinstalled (as admin, etc) Enabled/Disabled various Exploit Protection settings specifically for BF6.exe & EAAntiCheat.GameService.exe I've been though so many support options with EA Support (Case# 248731113) I'm running Windows 10, MS recently extended ESU (Extended Support) through to the end of October 2027, so the OS is still supported (I enrolled in it). However given REDSEC runs through the EA app, I don't believe my OS is the cause of the problem anyway, but obviously I have no way to prove this. Thanks for any help.BF6 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)Solved1.1KViews2likes48CommentsBF6 NOT LOUNCH
Hello everyone, I hope to receive a solution from you as soon as possible. I've been playing this game since its release, and today when I turned on my computer to start playing, I noticed that the game wouldn't launch! Furthermore, I keep getting different errors each time I try. What's the solution to this problem? The screen also freezes on "Connecting to Servers," "Downloading Updates," and so on. thank you .48Views0likes3CommentsBF6 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.3KViews5likes7Comments