Connection problems
Subject: Battlefield 6 PC – Persistent Hit Registration, Latency Warnings, and Respawn Stuttering Hello EA Support, I am requesting technical assistance with a persistent problem in Battlefield 6 on my PC. My bullets sometimes appear not to register correctly, and I experience stuttering or delayed responsiveness, especially after respawning. The in-game network performance indicator also reports latency problems. My ping is usually stable during each match, but it varies between servers. Some matches start around 38–40 ms, while others start around 68–70 ms. The latency warning can appear even when the ping remains stable throughout the match. My PC specifications: - CPU: AMD Ryzen 9 9950X3D - GPU: AMD Radeon RX 9070 XT 16 GB - RAM: 64 GB - Motherboard: MSI MPG X870E Carbon WiFi - Operating system: Windows 11 Pro - Monitor: LG, 165 Hz - Game platform: Steam - AMD Software: Adrenalin Edition 26.10.1 Troubleshooting already performed: - Tested the PC connected directly to my Xfinity XB10 gateway via Ethernet. - Ran extended ping tests to my local router and to 8.8.8.8. - Updated and checked my AMD graphics driver. - Enabled Windows Game Mode and hardware-accelerated GPU scheduling. - Disabled AMD Fluid Motion Frames and AMD FSR Frame Generation. - Tested TAA antialiasing. - Limited in-game frame rate to 160 FPS. Limiting the frame rate improved responsiveness and hit registration somewhat, but the network latency warnings and other problems persist. I have also experienced similar issues in other games. I would like EA to investigate whether this could be related to Battlefield 6 server performance, client-server synchronization, hit registration, or another technical issue. Please provide a case number and any advanced diagnostic steps that can help identify the root cause. I can provide screenshots and additional evidence from the in-game network performance graph. Thank you for your assistance.
Battlefield 6 Error 14:130003S:-7A (PC/Steam)
I’m still experiencing error code 14:130003S:-7A in Battlefield 6. I have tried the following: Restarted my PC and router. Verified game files through Steam. Tested both my home internet and mobile hotspot. Confirmed that other online games work normally. Unfortunately, none of these steps resolved the issue. I also found reports from PS5 Pro and PC/Steam players experiencing the same error. The game was working perfectly before October 28, but now it gets stuck connecting to online services and eventually displays “Couldn’t Load.” Could an EA representative please investigate whether this is related to the game servers, account authentication, or a recent update? Thank you.Subject: Battlefield 6 on Steam — 0:85009S after approximately 5 min
Subject: Battlefield 6 on Steam — recurring error 0:85009S after approximately 5 minutes; reconnecting only provides brief relief Hello EA Support, I need help investigating a reproducible online connection issue in Battlefield 6 on PC, launched through Steam and the EA app. The error in the BF6 scenario described below is consistently 0:85009S. SYMPTOMS AND REPRODUCTION STEPS 1. I launch Battlefield 6 through Steam and remain in the main menu without joining a match. 2. After approximately five minutes, error 0:85009S appears. 3. The game does not close or crash to the desktop. I click Reconnect and return to the main menu. 4. After reconnecting, the same error returns much sooner and repeats frequently. I have not measured the exact intervals between these subsequent errors. 5. Leaving the game open on the error screen for six minutes before reconnecting does not help: the error still returns quickly. 6. Completely closing only BF6 and launching it again through Steam restores the initial interval of approximately five minutes before the first error. Steam and the EA app remain running throughout these game restarts. Important clarification: this is an online-session disconnection while the game process remains running, not a confirmed process crash. Earlier troubleshooting notes used the term "crash," but that does not accurately describe the observed behavior. Connection problems have also occurred in EA SPORTS FC 26 and skate. The precise reproduction steps and error code above refer to BF6. Previous testing also reproduced the problem with different EA accounts on this PC. SYSTEM INFORMATION - Windows 11; the build recorded in my earlier notes is 26200. I can provide the full build number and update channel if needed. The build number alone does not establish whether this is an Insider installation. - Motherboard: Gigabyte B650M GAMING WIFI. - Network adapter: Realtek Gaming 2.5GbE; - Secure Boot and TPM 2.0 enabled. TROUBLESHOOTING ALREADY COMPLETED Network: - Ping tests to the router and 1.1.1.1 showed no packet loss during those tests. - Tested a commercial VPN and a mobile 4G connection. Previous tests did not resolve the problem when changing the network/IP address. A separate VPN scenario could produce a different error; this request concerns the reproducible 0:85009S scenario. - Tested Google/Cloudflare DNS, cleaned the hosts file, and tested port forwarding, UPnP, and temporarily placing the PC in the router's DMZ, without resolving the issue. - Tested zapret traffic-manipulation strategies, without resolving the issue. - Cloudflare WARP could not be used as a successful alternative-connection test because it returned CF_HAPPY_EYEBALLS_MITM_FAILURE. - A curl connection error for gosredirector.ea.com also occurred on a friend's PC where the game works, so that result was not treated as evidence of ISP blocking. Software, drivers, and anti-cheat: - Removed Gigabyte Control Center and GbtCloudMatrix.exe. - Removed the gdrv3 driver. - Disabled VirtualMachinePlatform, WSL, and the vmcompute and hns services during testing. - Removed/disabled the TAP-Windows Adapter V9 and tun0 (sing-box) virtual adapters. - Reinstalled EA Javelin Anti-Cheat, including cleanup of related folders and registry entries. - Checked that CryptoPro CSP was not installed. - Performed a Windows clean boot using msconfig. - Tested with Memory Integrity disabled. Windows and user profile: - Ran sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. The problem remained; earlier notes mention a repair involving bthmodem.sys. - Created a new local Windows user profile; the problem remained. - Checked the Application and System event logs. The previous review did not find Application Error events indicating a BF6 crash at the time of disconnection. EAAntiCheat unload events (FilterManager Event ID 1) were noted, but no causal connection to the disconnections has been established. This list describes tests already performed. It does not mean that every modified setting is still in that state now. NETWORK CAPTURE AND MONITORING FINDINGS The available files are ea-connections.txt, ea-service-monitor.txt, ea-socket-monitor.txt, ea-full.etl, and ea-full.pcapng. They cover different observation intervals and should not be treated as one synchronized recording. 1. In ea-full.pcapng: - At 303.161 seconds after capture start, the PC sends the first FIN in the connection to 98.85.38.9:8095. - At 303.370 seconds, the PC sends a FIN in the connection to 98.85.38.9:9000. - The server responds; packet exchange is still occurring at this point. - The capture continues until 322.295 seconds. New connections to 100.50.20.250 on ports 9000 and 8095 appear at approximately 317–319 seconds. Their owning process has not been established from this capture. - These timings are relative to capture start, not a verified game-process start time. 2. In ea-connections.txt: - At 23:50:37, a connection to remote port 9000 enters TimeWait with PID 0. - Other bf6 connections with PID 16380 remain in the log until 23:50:47. - Therefore, PID 0 for the closed connection is not evidence that the game process was terminated. 3. In a separate pair of before/after snapshots: - bf6 retains PID 11668 and the same start time, 2 November 2026 at 00:21:09. - Before the disconnection, the connections to 100.50.20.250:8095 and :9000 belong to bf6. - After the disconnection, those connections are absent from the Established list, but bf6 and its other connections remain present. 4. In ea-service-monitor.txt: - All 789 entries show EABackgroundService as Running with PID 3780. - No restart of that service was observed. This file does not monitor the anti-cheat service. 5. Limitation of ea-socket-monitor.txt: - The script used hard-coded process IDs, including an old game PID of 11668. - The resulting file contains EADesktop and EABackgroundService entries but no bf6 entries. It cannot establish that a newly launched BF6 process with a different PID had no connections. These findings do not establish anti-cheat termination, ISP blocking, token expiration, or a server-forced disconnect as the cause. A TCP FIN shows connection closure, but does not explain why the application closed it.
Battlefield 6 freezes the entire Windows system
Hello Battlefield Support, Battlefield 6 repeatedly causes a severe full-system freeze on my MSI Vector 16 HX AI A2XWIG. This is not a normal crash to desktop: the game first drops to only a few (2-6) FPS, then the entire Windows interface becomes unresponsive. The computer may remain in this state for several minutes before recovering, or it has to be restarted. System configuration: Laptop: MSI Vector 16 HX AI A2XWIG CPU: Intel Core Ultra 9 275HX GPU: NVIDIA GeForce RTX 5080 Laptop GPU, 16 GB Operating system: Windows 11 NVIDIA Game Ready Driver: 621.01 WHQL BIOS: E15M3IMS.118 Platform: Steam Graphics settings: Overkill preset (Any) Resolution: 2560 × 1440 Frame Generation: Off Ray Tracing: Off Incident: The problem occurs only in Battlefield 6. I have not observed the same behavior in other demanding games. HWiNFO evidence from the Battlefield 6 session (LOG1.CSV): Immediately before the freeze, at 21:57:06, the GPU was running at approximately 2377 MHz and consuming 146 W. At 21:57:10, the GPU clock suddenly dropped to approximately 180 MHz and power fell to 35.7 W. HWiNFO then stopped recording normally for 108.4 seconds. This was followed by additional logging gaps of approximately 71.1 and 62.6 seconds, confirming that the entire Windows system was unresponsive rather than only the game. The PCIe Recovery Count increased from 188 before the freeze to 191 during the incident. Maximum recorded temperatures were: CPU: 104°C GPU: 87.6°C GPU hotspot: 92.7°C GPU memory: 87°C Comparison test: I tested the latest Call of Duty: Modern Warfare 4 (Or Any Other game) using the same 2560 × 1440 resolution, Ultra graphics preset, Frame Generation disabled and Ray Tracing disabled (LOG2.CSV). Call of Duty remained completely stable for more than 16 minutes (Several Hours) despite placing an equal or greater load on the laptop: Average GPU load: approximately 95% Peak GPU power: approximately 197 W Maximum GPU temperature: 87.8°C Maximum CPU temperature: 104°C Maximum HWiNFO logging interval: approximately 1.25 seconds PCIe Recovery Count remained unchanged throughout the test Battlefield 6 therefore freezes even though the comparison game remains stable at practically identical temperatures and higher GPU load and peak power. This makes a general thermal or power limitation less likely. The sudden loss of GPU clock and power, long system-wide logging interruptions, and increase in the PCIe Recovery Count suggest a possible Battlefield 6/Frostbite/DirectX 12 interaction with the NVIDIA driver, leading to a GPU timeout or recovery event. Windows also recorded a LiveKernelEvent 141 on the same day, although I cannot confirm that the available entry corresponds to the exact 21:57 incident. I did not capture a normal Battlefield 6 APPCRASH or AppHang entry because Windows itself became unresponsive. Please escalate this as a full-system GPU hang rather than a standard application crash. Thank you.gun jammed
why is it when i shoot at certain players my gun fires 1 bullet and stops, or during sustained fire it'll stop firing halfway through the mag? i've tested it on all of the other modes and it hasn't happened once. it ONLY happens in the battle royale modes. i've built up a reflex of flicking my reticle off target and back on because it's the only thing that fixes the issue. also, it only happens in close range fights(10meteres or less) unless i'm using a sniper rifles. with sniper rifles it fires normally but will not zoom in if my reticle is on the players model. i have to again flick my reticle away from the player model and then zoom in and flick back on, so i don't use snipers anymore. from everything i've learned and experienced, it's tied to the reticle being on the player model and the only thing to reset it is to move your reticle off of the player model and back on. yes i have reinstalled and multiple times now have reset my settings because that is the only info i've been able to find. no i'm not forgetting to reload and no i'm not accidentally putting the rifle into semi. there's a reload bug too. it might look reloaded, you didn't swap and the animation played all the way through, but it isn't.
Unable to get Ranked matches going in asia
In asia it has been hard to get ranked matches as people are not queueing at the same time . the easiest way to fix this is by adding a queue counter like apex or put us in the plane like regular br . in asia the player base dropped a lot as players were unable to get game. until a few weeks ago there were 2 active lobbies atleast but getting the first game popping is the issue as people leave after few minutes of waiting as they do not know how many players are in the queue or how long it might take . to bring back asian players and ranked lobbies back we need a Queue counter feature . EA_LunardustCat