Matchmaking errors for PS5 - Unable to play the game at all.
The menu removes all character models, tiles and anything to physically select at internment and random points, usually when trying to load into game. Following a reset, the timer on most deep six modes will hit 5 mins, then say a timeout message with a changing error code. This has persisted since the last update. It's currently making the game unplayable.
black screen upon leaving a match
This bug was fixed but now in season 4 it came back. now it's pretty bad on PC every other match if you leave the game after it ends to avoid wasting time on seeing your progress the game stops responding and you have a black screen nothing works. I regularly leave match if they are about to end or just because but most of the time is after the match is over to avoid seeing all the progress bars. please fix this. it's very repeatable bug. This won't be an issue but loading the game takes a long time.
EA, please don’t ignore us. 🔧 Ongoing DirectX crashes, BSODs, PC restarts
Hi EA team, I’m writing here after trying way to reach the developers through the Steam discussions. I’m hoping this post will finally get some attention here on EA Answers HQ. ⚠️ The Issue Since release, many PC players (myself included) have been dealing with constant DirectX crashes, BSODs, and full PC restarts — typically within 20 minutes to 2 hours of gameplay. This has made Battlefield 6 practically unplayable for a significant portion of the community. Meanwhile, smaller issues (like the campaign access bug or Battlefield Coins not being delivered) have been fixed and officially acknowledged within just a few days. That’s great — but it’s hard not to notice the difference in priorities when a game-breaking issue has been left unresolved for over three weeks. 🧠 Community Findings After extensive testing and sharing information across multiple discussions, the community has identified the issue appears to be related to the new anti-cheat system. Running a Steam file integrity check after a crash usually finds and redownloads 2–3 files, after which the game may run slightly longer — sometimes up to two hours — before crashing again. This workaround is inconsistent and does not permanently resolve the problem. Players have gone to great lengths — clean Windows installs, BIOS updates, GPU driver rollbacks, memory checks, and even fresh game reinstalls. None of these have worked for the majority. 🧩 Community Contribution Players have been actively collecting crash logs, comparing system specs, and testing potential fixes for weeks. We’ve done everything we can from our side — sharing data, reproducing crashes, and trying to isolate the cause. Still, despite all this collaborative effort, the core issue remains, and there’s been no meaningful communication or update from the team. 💬 About Communication We appreciate the community management presence here, especially from EA_Shepard, but the repeated “team is aware” messages without any follow-up have left many players feeling ignored and frustrated. We’re not looking for copy-pasted replies — we’re looking for transparency, updates, and acknowledgement of the scope of the problem. If this issue is being worked on, please confirm it officially. If the team needs more specific data from players, please let us know what exactly is needed — many of us are ready to help. ❓Questions for the Dev Team Is the anti-cheat currently being investigated as a potential cause of instability? Will there be any form of compensation for lost XP, progress, or time due to these crashes? Can we expect any official statement confirming that the problem is being actively worked on? 💬 Final Thoughts Vince Zampella once called the “purchase-to-play” issue “frankly shameful.” Right now, thousands of players are unable to play the game they’ve paid for due to repeated crashes and reboots — and the silence surrounding it feels just as frustrating. We’re asking for one simple thing: clear communication and a concrete update on the status of the investigation. Thank you in advance for your time and attention — we just want to be able to play the game we love. UPD: I’ve just been banned from the Steam discussions for Battlefield 6(📌🚨 STOP IGNORING US, EA (DIRECTX ERROR, RANDOM CRASH, PC REBOOT, BSOD) :: Battlefield™ 6) Apparently, trying to reach the developers and help other players is now considered a violation. It’s honestly beyond frustrating — instead of addressing the real issue, moderation seems more focused on silencing those who talk about it. But you know what this means? They’re definitely reading everything. They see the complaints, they know what’s going on — and they’re choosing to ignore it. If you’re reading this, please help spread the word on the Steam forums or anywhere you can. Let’s make sure they can’t just sweep this under the rug. Thank you again to everyone supporting this thread. Stay strong💪 UPD2: I just found out why I was banned from the Battlefield 6 Steam discussions — and the reason field is completely blank. No explanation. No warning. Just a permanent ban for trying to raise awareness about a critical issue affecting thousands of players. This is beyond disappointing. It’s one thing to ignore the problem — it’s another to silence players who are simply asking for answers. UPD3: I just got a response from Steam Support. The ban wasn’t from Steam — it was issued directly by the Battlefield developer moderation team. You promised that this time things would be different. You said you’d listen to the community, fix your mistakes, and rebuild trust. I believed you when Battlefield 2042 launched — and I was disappointed. I believed you again now… and once more, you’ve proven us wrong. Silencing players who are simply trying to help the community and reach the developers is beyond unprofessional — it’s shameful. This is not how you treat the people who still care about your game. Honestly, EA — this is very disappointing. You should be ashamed. 📢 📢 📢 UPD4: I just reached out directly to Steam Support to report what’s been happening — the bans, the silence, and the complete lack of respect toward the player base. Here’s what I told them: EA’s moderation team is abusing their power inside Steam’s own community — silencing players who are simply trying to discuss game-breaking technical issues like DirectX crashes, BSODs, and PC restarts. I asked Steam to take action — just like they did before with The Last of Us, when the game launched in a broken state and Steam allowed refunds outside normal policy. Battlefield 6 is in the same situation: it’s not a finished product and it shouldn’t be sold as one. And here’s the response I got back from Steam Support: They said they recommend developers take moderation seriously and warned that poor moderation decisions can harm the game’s reputation — but they also confirmed that EA fully controls their own community and Steam cannot reverse their bans. However, they also told me that we can report this situation through the official complaint system — using the flag icon on the Battlefield 6 store page — and that all such reports are reviewed by Steam’s internal team. So, this is where we are now: EA won’t listen. Steam won’t interfere — unless enough of us speak up. If you’ve been affected by the same issues — the crashes, the silence, or unfair moderation — please, take two minutes to send a complaint through the Steam flag system or contact support directly. The more voices there are, the harder it’ll be to ignore. Here’s what you can do 👇 1️⃣ Go to the Battlefield 6 Steam page. 2️⃣ Click the flag icon (next to “HTML code”). 3️⃣ Choose the option to report issues with the game or its community. 4️⃣ Mention the ongoing technical problems and EA’s mistreatment of players. We’ve done our part as a community — collecting data, helping each other, and trying to get heard. If EA won’t respect its players, then it’s up to Steam to see what’s really happening here. Stay strong, everyone. Keep spreading the word, keep reporting. They can silence one person — but not all of us. 🟩 To save you time, I’ve prepared two ready-to-use messages you can send directly: Message for Steam Support: Hello, I’m one of many players affected by a critical DirectX / anti-cheat issue in Battlefield 6 that causes constant crashes, BSODs, and even full PC restarts. Despite numerous reports from players, EA has ignored the issue for weeks, leaving everyone without any official response or fix. This is not a finished or stable product, yet it continues to be sold on Steam as if it were complete. Please take action and request that the developer properly address this issue and ensure the game meets Steam’s quality standards. Flag report (on the Battlefield 6 Steam page): Battlefield 6 has a severe DirectX / anti-cheat issue causing crashes, BSODs, and PC restarts for many players. EA has ignored player reports for weeks and hasn’t acknowledged the problem. This is not a finished or stable product and should not be sold on Steam until it’s fixed. You can also insert links to my posts and write about my blocking on the steam forum. 📢 UDP 5 I recently remembered another great game — The Finals — and thought it could help narrow down the investigation. The Finals, made by former DICE developers, also uses a kernel-level anti-cheat (Denuvo) that works in a very similar way to EA’s Javelin. So I decided to test a simple theory: if the issue is truly caused by the anti-cheat itself, the game should crash there too. And you won’t believe it — it did. After about an hour and a half of playing, I got the exact same DirectX error as in Battlefield 6. This strongly suggests that the root cause isn’t the Frostbite engine or the game itself, but rather a shared architectural flaw in how next-gen anti-cheats interact with modern GPU and PCIe systems at the kernel level. This also explains why some players reported temporary improvements after updating their BIOS — these updates often include PCI Express behavior fixes, which could slightly change how the system communicates with the GPU under load. A player under my Steam discussion mentioned that after upgrading from an RTX 3080 Ti (PCIe 4.0) to an RTX 5080 (PCIe 5.0), Battlefield began throwing DirectX errors almost instantly. When he reverted back to the 3080 Ti, the crashes disappeared. That’s an important clue — though I can’t yet say what to do with this information, perhaps someone with more low-level or driver experience can shed some light. At this point, one thing is clear: We’ve already done more meaningful diagnostics than EA’s own QA department. The problem is not engine-related, and most likely not even specific to Battlefield — it lies in the deep system-level behavior of modern kernel-mode anti-cheats. Huge thanks again to everyone who keeps sharing logs, reports, and theories — this feels like a real breakthrough. P.S. Before Denuvo Anti-Cheat was added to The Finals, I had over 150 hours in the game — without a single crash. Draw your own conclusions. P.S.S. A thought just came to mind. What if EA Javelin Anticheat is actually Denuvo Anticheat, just rewritten specifically for EA's needs (on Frostbite)? This is also supported by the fact that players complain about the high CPU usage, which is exactly what Denuvo is “famous” for. 🥴 UPD6: EA_Shepard HELLOOO??? You're kidding me... EA_Shepard really IMMEDIATELY responded to the player's trolling, but IGNORES US FOR THE FOURTH WEEK. Im doneFrequent Stuttering During Driver Weapon Zoom in Certain Vehicles
Hello, There has been a bug in Battlefield 6 since day one. It's ruining my vehicle combat experience. ISSUE: When playing as the driver of an MBT, IFV, Mobile AA or Patrol Boat, holding the right mouse button to zoom in frequently causes the game to stutter. What I've tried: - Setting graphics settings to lowest/highest. - Disabling and enabling upscaling techniques, frame generation, future frame rendering, v-sync, etc... - Disabling and enabling pagefile, Windows Game Mode, Hardware-accelerated GPU scheduling, variable refresh rate. - Disabling all kind of overlays such as nvidia ansel, nvidia app, discord, ea, steam, etc... - Changing screen modes. - Disabling and enabling G-Sync, Nvidia Reflex. - Updating OS, BIOS, drivers and Visual C++ Redistributable runtimes to latest ones. - Excluding the game from AV as a file, folder and process. - Excluding the game from Exploit Protection. - Disabling all kind of overclocking things in BIOS. - Changing Windows Power Plans. I am also sharing a screenshot of the detailed in-game graph, which shows what happens when the issue occurs. I would appreciate it if you could fix the issue as soon as possible. EA ERROR REPORTER REPORT ID OF MY DXDIAG FILE: b8859fd7-59bc-422a-987f-5cea18b00152 Best Regards, TR-drM00BGlitched out in pool
I was playing casual battle royale quads on Xbox series x and riding on the back of a teammates bike toward the mission. He drove into the pool and jumped off and the motorcycle fell over sideways and dumped me under the map and it glitched me out in the pool. The walls were made long and tall and I could see him riding the motorcycle over top of the pool but I could not climb out. I was able to move around, jump, throw grenades and shoot but was glitched out in the pool.UI Bugs STILL
Without fail, every session of Battlefield I either A. leave a game and become frozen on a black screen while trying to load the main menu and inevitably cannot do anything but alt+F4 out of the game and restart the whole game, or B. load into a new game and cannot select class or change class to begin the game and instead am stuck in spawn until I leave the match or close the game. This game has been out almost a year and these issues STILL CONTINUE TO OCCUR.
RedSec Second Chance Bug: I Won Without Existing
Issue Summary: I queued for Duos but did not get a teammate. When I died and should have gotten the Second Chance redeploy, the game bugged. My camera froze at the spot where I died. I could not move, respawn, or spectate. However, the match continued in the background. I could hear the announcer, the zone callouts, and my score increased while frozen. After a few minutes, I was awarded the win even though I was not actually alive in the final circle. This may be connected to matches where the final squad is “invisible” or not present in the circle but still wins. Steps to Reproduce: 1. Queue for Duos without receiving a teammate. 2. Play until first death. 3. Second Chance tries to activate. 4. Camera locks and character does not respawn. Impact: - Incorrect match outcomes - Final circles break - Potential free/unearned wins Screenshots: 1. Frozen camera where death occurred https://imgur.com/a/YaeoFYc 2. Score increasing while unable to respawn https://imgur.com/yJ3uprg https://imgur.com/a/z5l2WL9 3. Victory screen despite being stuck https://imgur.com/a/xIxgOpQ https://imgur.com/a/fLphcFV https://imgur.com/a/jowA3V5 I’m reporting this because I genuinely like the game and want RedSec to be solid. Thank you for looking into it.
