Game crash to desktop after 1.1.2.0 update (launch, gameplay, map change)
Just downloaded to new update and cant load in to a game on PC EA launcher. Tried to play the new map CRASH Tired to play Blackwell Feilds CRASH Tired to play Breakthough Siege of Ciaro CRASH Tried to get into a ramdom Conquest game CRASH Tried to get into a ramdom Breakthough game CRASH Drivers upto date. CM title editSolved15KViews68likes446CommentsStraight to desktop... No error in evntvwr.
Ever since the new California Resistance update, I, originally, wasn't even able to open my game. Now it will at least open; however, as soon as my character stands up in the lobby, like my group and I are about to join a game, straight to the desktop I go. No crash reports in Windows Event Viewer. Repaired game files twice, doing the supposed "workaround", still nothing. I have seen that I'm not the only person with this problem.[PC] Deploy screen FPS capped at ~30 after Season 1 update (Steam, AMD GPU)
Description After the Season 1 update, overall in-game performance remains normal, but the deploy / spawn screen appears to be capped around 30 FPS despite no framerate limits being enabled. CPU + GPU utilization both drop to ~20–30 % while in the deploy screen, then instantly return to normal values (60–70 % CPU / 80–90 % GPU) the moment the player presses Deploy. FPS also jumps back to the expected 230 – 310 FPS as soon as gameplay begins. Feels as though a hidden 30 FPS limiter or menu context throttle is being applied during the deploy screen. Steps to Reproduce Launch Battlefield 6 (Steam build, Season 1 patch). Join any multiplayer match. Observe FPS and GPU/CPU utilization in the deploy screen. Press Deploy → FPS instantly rises to normal gameplay levels. Expected Result Deploy screen should render at full framerate (same as in-game and main menu) unless an explicit FPS limit is set by the user. Actual Result Deploy screen runs at ~28–40 FPS with 20–30 % GPU/CPU usage until the player spawns, then returns to normal (230–310 FPS). Video of Result Footage: https://youtu.be/tsJfK3peQJQ System Information Component Details CPU AMD Ryzen 7 7800X3D GPU AMD Radeon RX 9070 XT RAM 32 GB DDR5 Driver Version 25.10.33.02-250924a-420421C (Adrenalin Edition) OS Windows 11 24H2 Platform PC – Steam Client Game Version Season 1 Patch (Oct 2025) (Note: user.cfg / PROFSAVE_profile renamed to .txt for upload.)873Views17likes9CommentsConquest ticket bleed ticks every 2 sec instead of 5 sec
Treating this as a bug since it's not in any of the patch notes. Ticket bleed used to be very 5 seconds in conquest but since the new update it seems to be every 2 seconds. This leads to significantly shorter matches, just like when the ticket count was reduced from 1.000 and had to be reverted. Clearly not what the community wants for conquest.359Views31likes5CommentsAudio crash the game after season 1 update
Im using Steel Series Arctis Nova Pro. I did not have any problems but when the season 1 update came my game started to loose audio in 30min of multiplayer game and my PC would freeze and hard crash. Ive have to restart with push power button. Now after the Eastwood upodate game wont crash anymore but i loose audio and i have to restart sonar in midgame. I have found that game audio works in Bluetooth but with headset program no. I have looked every reddit post and youtube video and i have do allmost all i can do. Most of people are saying its the anticheat system or just games bugged audio. I have high end PC so all my hardware is really good and like i said all others games i play work really well with Sonar, only Battlefield 6 is causing problems, i even play Battlefield 4 and i have zero issues. Any devs or some PC wizards here that can help me, or just waiting to EA do audio fix?1View0likes0CommentsEA Javelin Anticheat encountered an error. (7) (2) Internal error #4: C0000210
EA Javelin Anticheat encountered an error. Please restart your PC. : C:\Program Files\EA\AC\EAAntiCheat.GameService.exe ( 7 ) ( 2 ) Dumping failed. Log: Dumping started... Internal error #4: C0000210 Failed. I'm getting this error message every time I try to launch Battlefield 6 through steam. I've tried : Reinstalling the anti-cheat Reinstalling the game Updating Windows Updating all my drivers Verifying the integrity of the game files Verifying the integrity of Windows Giving complete access to my firewall, anti-virus Disabling any third party apps ... honestly I've tried a bunch of stuff I forgot too. Please someone help me. I really like BF 6 and I've never cheated. Attached is a screenshot of exactly what I see every time I try to launch the game.BATTLEFIELD 6 GAME UPDATE 1.1.2.0 - Defibrillator Broken
Defibrillator Operation inconsistent The support gadget - defibrillator operation is inconsistent after this update. It sometimes work with a combination of multiple attempts or approaching the downed teammate from different angles. The "drag revive" maneuverer seems to be unaffected.45Views7likes5CommentsBF6 serious problem with progression!
Hi , I’m playing on PS5 Pro (PSN ID: FastClipVgls or Vgls21) and I need help with my Battlefield 6 progression. My account seems to be stuck in some kind of XP throttle or bug after playing in a bot lobby earlier today. Here’s exactly what happened: * I joined a bot match and leveled up 9–10 different weapons during that session. * After leaving the bot match, all progression stopped completely. * Every single game mode I try (Conquest, Breakthrough, TDM, Battle Royale etc.) gives me only 82 XP at the end of the round. * No weapon XP is progressing at all, even for weapons I didn’t use in the bot match. * Some weapons that showed level increases earlier (for example my L85A3 showing level 1) reverted back to level 0 after restarting the game. * The XP bar either doesn’t move at all or disappears. * This behavior happens in every official matchmaking mode as well, not only in Portal. I already tried: * Restarting the game * Restarting my PS5 * Clearing cache * Rebuilding database * Reinstalling the game None of these helped. At this point it looks like the entire account progression is frozen, both player XP and all weapon XP. Can you please check my account on the backend and see if it is stuck in an XP throttle / restricted state? I cannot progress anything at all right now and the issue has persisted for hours. I hope it's not something permanent. Thank you.139Views1like13CommentsSevere Hit Reg, Netcode, and Ping Problems Since Latest Patch
Hit Registration Issues Since the November 18 update, hit registration has felt significantly worse. I’m frequently landing multiple confirmed headshots—two headshots dealing 62 damage each (124 total)—yet the enemy survives and turns to kill me almost instantly. Overall, gameplay feels off: I’m seeing plenty of hitmarkers, but it seems like only around 40% are actually registering as damage. Netcode Problems Post-update, I’ve been dying behind cover or through walls far more often than before. These deaths feel instantaneous, even from weapons that should deal relatively low close-quarters damage (e.g., the MP7 at 16 damage). Ping / Latency Degradation Since the same update, my ping has noticeably worsened. I’m on a high-speed fibre connection (1Gb down / 600Mb up), hard-wired via CAT6 to an ASUS TUF-AX6000. My ping has gone from a stable 20ms to fluctuating between 38–60ms. Matchmaking Times Matchmaking has also taken a huge hit. During peak hours, Conquest queues are taking 2–4 minutes, which is extremely unusual. DICE, please fix Additional Concern: Cheating Please also look into the companies openly selling cheats on platforms like YouTube and TikTok. Cheating is becoming increasingly blatant and is having a noticeable impact on gameplay.57Views3likes5CommentsNew patch broke the RPG
I play a lot as engineer, so I noticed it right away (on the 18th) that my rockets were all over the place, but I thought it could be latency, server issues or something like this. Now that time has passed, I saw some clips on Reddit with people having the same issue, with this post highlighting it. I can hit my shots as long as I stand still for a little more than a second, but this increases the risk of dying to my target a lot. I don't know if this is intended or a nerf (kinda like the maximum spread after sprint bug), but I'll assume it's indeed an issue and report it here. Hope to see it fixed soon!