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 done
Fut Draft Bug/Cheat
Hey, i played a Draft Game (Round 3) and i got kicked 1 sec after kickoff. Your "Tool" to get a token when connection has been lost doesnt say im eligable. You might want to check if my Opponent Won by 3 Disconnects already as im thinking that the Fut Draft Hack Tool might be back. If this isnt the Case then Nice Netcode. (wasnt issue on my End :) )
Stutters, hiccups , framedrops i found the cause!! Edit***
So after hours of testing today, I found the cause of stutters, frame drops, etc. It's the Javelin anti-cheat, which overloads one or two CPU cores when you press WASD, 1, 2, or 3, the enter button, or certain letters. The CPU core goes to 100%, and this results in stutters. It's affecting all Battlefield titles, so please fix this, Dice! Edit** I noticed that pressing certain keyboard keys (like number keys or arrow keys) causes noticeable micro-stutters in BF1, BFV, and BF6. FPS stays high, GPU load is fine, and CPU cores aren’t maxed. Mouse movement or clicks don’t trigger this. It seems to happen only with keys that change the game state (weapon switch, zeroing, gadgets). Rapidly pressing these keys makes spikes worse (dpc latency.) Shader cache warm-up reduces it slightly, and capping FPS also helps mask the spikes. From what I can tell, the cause is kernel-level anti-cheat checks (Javelin/EA AC) validating discrete input. These checks temporarily block the main game thread, which shows up as micro-stutter, even though CPU/GPU aren’t overloaded. This isn’t a hardware or driver issue—it’s a side effect of the anti-cheat + Frostbite engine. please fix this soon!
Unable to connect to EA Servers (Code Anti-cheat authentication timeout).
I kept receiving the following error when trying to connect to apex legends: "Unable to connect to EA Servers (Code Anti-cheat authentication timeout). Please check your Internet connection and try again. See ea.com/unable-to-connect for more information." I've tried the following: Switch off router for >30s and switch on Run apex legends and "EasyAntiCheat_EOS_Setup.exe" as administrator Verify file integrity via steam Re-installed Apex legends Nothing seems to work. I can access occasionally but most of the times i will receive this error. Could you please advice?
Mouse Look Stutters / Jitters When Pressing Keyboard Buttons | Potential Fix
Potential Fix: One of the causes for this problem relates to having MSI Afterburner or Rivertuner Statistics Server running while the game is up. Just close the program and it might end up helping you out like it did me. If it doesn't, maybe try other similar software that might be running on top of Battlefield 6 like these applications did. Link to Reddit post talking about the same problem and providing the potential fix: https://www.reddit.com/r/Battlefield/comments/1pk5e2g/weird_bug_tapping_keyboard_keys_while_moving/ ~~~ A lot of other people have pointed out that the problem is tied to EA’s anticheat, and that it’s happening in other games even outside of the franchise. Some people have commented their own solutions like “Launching the game from the install folder and EAAntiCheat.GameServiceLauncher” or “going offline on every platform you use to run the game” or “pressing the 4 - 7 most used buttons on launch” to make the button presses not trigger the stuttering issue. Honestly I wouldn’t be surprised if a whole lot of unique things are causing this issue across a bunch of different setups. If you still need help, try poking around the comments section and take a look at other people’s suggestion's. For me, turning RTSS off completely fixes both the mouse stutter and text box issues, but not everyone having this issue has MSI Afterburner or RTSS installed. Someone mentioned the Jayztwocents “Stuttering in Games FIXED… This might fix yours too!” video but that issue isn’t dependent on keyboard inputs like the issue we’re having with Battlefield 6. I think it was related to Wi-Fi and Bluetooth wireless drivers but I’m going to be real, this video came out a couple months ago, there’s no chapters integrated into the video separating problem, demonstration, and solution, no one linked a timestamp to the solution in the top comments, and I’m not going to sit around watching the rest of a video about someone claiming they solved an issue but not talk about the solution after I’ve watched half of the video. https://youtu.be/YWTZkB9rVU0?si=UL6zAZhRzuZnkJj_ Solution may start at 7:40, YouTube mobile doesn’t allow you to send time stamped links anymore. ~~~ The Issue: Mouse stutters alternate depending on game launch between the three: Pressing action buttons such as sprint, reload, or interact. Pressing movement buttons. Pressing weapon swap buttons. When this bug happens, either one or the other affects mouse look. They don't occur at the same time. Spamming a bunch of buttons at the same time results with severely increased stutter. Seems like the mouse movement isn't tracked until the button register code has been run, then the mouse movement jumps to the position it should be once the register code is complete. Only happening in Battlefield 6, doesn't happen in other games such as Call of Duty: Black Ops 1. Happens with different mice such as the Logitech G502 Hero and Razer Deathadder Essential. Only one mouse has been plugged in while this bug occurs. There are no duplicate peripherals plugged in. Restarting computer doesn't change anything. No control or peripheral changes have been made since last played with no issues. There is no way for the user to fix this bug unless they know how. (I didn't know how and would've never been able to figure it out on my own). The issue persists even after resetting controls and reinstalling the game. Attachment MP4 example is bug occurring when movement keys are pressed. Footage is captured at 125 frames per second in-game and 60 frames per second video export. ~~~ While this bug is active, you can't type into the text chat. Opening the text chat for the first time instantly closes it after a few frames, letters don't register when you re-open and sequentially try to type, the cursor appears on the screen, and clicking automatically closes the menu and fires the equipped weapon. ~~~ Other bug reports on the same issue: Mouse feels a bit off after new update and chat not working | EA Forums - 13015957 Keyboard button presses lead to stuttering even AFTER hotfix | EA Forums - 13015746 When this report was first made back when barely anyone else had posted about the issue online, I kept an eye out for similar threads that might’ve been buried in the Battlefield 6 bug reports page, but now it looks like new threads with potential button buffering solutions are popping up on the trending page thanks to a LOT LOT more people recognising there’s an issue. ~~~ I appreciate all the help and awareness that everyone’s provided over this issue. I understand that not everyone is having the exact same issue I had, but it’s obvious that the issue is a whole lot worse than any one of us could’ve imagined. I just wish a developer would acknowledge the fact we’re experiencing this large of an issue with a reply in one of these threads. Didn’t developers respond to threads back when they first advertised the bug report forum? What happened to that?
