REDSEC Ranked Matchmaking Takes 15–20+ Minutes in Iraq
Hello Battlefield / EA Support Team, I am experiencing a serious matchmaking issue in Battlefield 6 – REDSEC Ranked. I am playing from Iraq, on Xbox Series X, and Crossplay is enabled. The problem occurs specifically when searching for a Ranked REDSEC match. Problem details: Game mode: REDSEC Ranked Platform: Xbox Series X Location: Iraq Crossplay: Enabled Issue: Extremely long matchmaking times Typical queue time: 15–20+ minutes Sometimes the game continues searching without finding a match for a very long time. Casual/non-Ranked matchmaking appears to find games much faster. Restarting the matchmaking search does not consistently solve the problem. I am concerned that the matchmaking system may be having difficulty finding enough Ranked players in or near the Middle East region, or that players from Iraq are being routed to distant regions such as Europe or other regions because of limited server availability. This may be causing two related problems: Very long Ranked matchmaking queues Potentially high latency/ping after finally finding a match Since Crossplay is already enabled, the available player pool should be as large as possible, so disabling Crossplay does not appear to be a practical solution. Could you please investigate whether: REDSEC Ranked currently has sufficient Middle East server capacity. Players from Iraq are being correctly routed to the closest available server. There are currently any matchmaking or server-routing issues affecting Iraq and the Middle East. Ranked matchmaking is unnecessarily restricting the available player pool. There is a known issue causing players in the Middle East to be placed into European or other distant regions. Additional Middle East servers or improved regional matchmaking are planned. I would appreciate it if you could confirm whether this is a known issue and whether there is currently any recommended workaround for players in Iraq. Thank you.
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.
BF6 Crashes After Launch - Javelin ExitType 0xD9F6F9654DD8A675
I am experiencing what appears to be a reproducible EA Javelin AntiCheat crash with Battlefield 6 on Steam. Battlefield 6 launches normally, completes the shader-loading process, reaches the Portal/home screen, and then abruptly exits to the desktop after approximately a minute. There is no Battlefield error message displayed. Windows Event Viewer records the following at the time of every crash: Application Log Provider: EA Javelin Anticheat Event ID: 1000 ExitType: 0xD9F6F9654DD8A675 (0xE7726BD6414F02C6) System Log The EAAntiCheatService service terminated with the following error: %%4294944373 Immediately before that, Windows shows the EA AntiCheat filesystem filter successfully unloading. Troubleshooting already performed: - Steam Battlefield 6 file verification now reports no corrupt files. - Completely uninstalled and reinstalled EA Javelin AntiCheat. - Rebooted after reinstalling Javelin. - More than 150 GB of free space on the system drive. - Tested with OneDrive completely shut down. - Tested with Claude/Cowork VM service shut down. - Tested with WSL completely shut down. - Checked installed filesystem filter drivers; no unusual third-party filters were present. - Checked network adapters; no third-party VPN/TAP/TUN/virtual network adapters are installed. The EA AntiCheat filesystem filter reports: Version 10.0 Timestamp: 2026-09-04T21:39:46Z Battlefield itself appears healthy. Javelin loads successfully when the game starts, but shortly afterward Javelin terminates and Battlefield exits with it. I have found other users reporting both the identical ExitType 0xD9F6F9654DD8A675 and the identical service termination code %%4294944373. This appears potentially related to the current EA Javelin build rather than corrupted Battlefield game files. Please let me know if there are additional Javelin logs, session IDs, dumps, or diagnostics I can provide to help identify the cause.
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
[BUG] Battlefield 6 causes PAGE_FAULT_IN_NONPAGED_AREA (0x50) in eaanticheat.sys
Summary Battlefield 6 causes a Windows kernel-level BSOD during gameplay. The crash is consistently attributed to eaanticheat.sys. System Game: Battlefield 6 Process: bf6.exe OS: Windows 10 x64 EA Anti-Cheat driver timestamp: September 5, 2026 Driver image: eaanticheat.sys WinDbg Analysis Bugcheck: PAGE_FAULT_IN_NONPAGED_AREA (50) Parameters: Arg1: ffffe300e7e26000 Arg2: 0000000000000000 Arg3: fffff80137ff21f6 Arg4: 0000000000000000 WinDbg reports: AV.PTE: Invalid AV.Type: Read Faulting module: MODULE_NAME: eaanticheat IMAGE_NAME: eaanticheat.sys SYMBOL_NAME: eaanticheat+18521f6 FAILURE_BUCKET_ID: AV_eaanticheat!unknown_function Failure ID: {d544cf09-4735-e698-77c3-5df5924e5448} The faulting instruction is: fffff801`37ff21ef 4c8b0403 mov r8,qword ptr [rbx+rax] fffff801`37ff21f3 4931c8 xor r8,rcx fffff801`37ff21f6 448b4c0308 mov r9d,dword ptr [rbx+rax+8] fffff801`37ff21fb 4131d1 xor r9d,edx fffff801`37ff21fe 4d09c1 or r9,r8 The referenced address was: ffffe300`e7e26000 !pte reports: PTE ... not valid Page has been freed The preceding 8-byte read appears to access the end of the previous page: ffffe300`e7e25ff8 while the failing 4-byte read starts at: ffffe300`e7e26000 This suggests that the anti-cheat driver may be accessing a memory region whose next page has already become invalid or freed. Reproduction The crash occurs while Battlefield 6 is running. The system does not simply crash to desktop; Windows bugchecks at kernel level. Additional information A previous Battlefield 6 report appears to have the same failure ID: {d544cf09-4735-e698-77c3-5df5924e5448} This makes me suspect that the crash may be related to a recurring issue in EA Anti-Cheat rather than an isolated hardware failure. A complete kernel dump/minidump can be provided for further investigation. Please investigate whether this is a known issue in the current EA Anti-Cheat build and whether the affected memory access path has been fixed in a newer driver version The Failure ID Hash is identical to other Battlefield 6 crashes reported with eaanticheat.sys: {d544cf09-4735-e698-77c3-5df5924e5448}.
Critical Bug Report: Weapon Disappearance and Ghost Model Glitch After Revive.
Dear Battlefield 6 Development and QA Teams, I am reporting a severe, recurring technical bug that critically impacts gameplay performance during combat situations. * The Glitch: Upon being revived by a teammate or during specific respawn triggers, the player's weapon completely disappears from the hands, leaving the character model in a bugged, invisible-weapon state. * Combat Impact: This glitch renders the player entirely defenseless, as it blocks all shooting and attack mechanics until a new respawn or weapon switch occurs. * Frequency: This issue happens repeatedly during matches, disrupting competitive play. Please log this bug for an urgent fix to ensure match stability. Thank you for your support.Glitched 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.
Anti-cheat system kills Internet connection when using PPPOE
When I'm launching bf6 with PPPOE Internet connection, the ea javeling anti-cheat system mistakenly shut down my Internet connection. Also, I can't reconnect to the Internet when I closed the game process until I restart my PC This is not a casual problem, I tried on different platforms and the problems happened identically
