Непредвиденное завершение игры Apex Legends
Обнаружено непредвиденное завершение игры. Перезапустите игру. Если ошибка повторится, свяжитесь со Справкой EA. (0xC0000409) Произошло буквально неожиданно, в 13:00 ещё нормально играл, всё работало, вышел из игры стандартно через кнопки выхода. Уже вечером увидел эту ошибку. При ZapretDiscorda работал всегда стабильно, отключив его всё равно выкидывает это окно. В игру не успевает зайти, АнтиЧит проверку, как я понял, проходит и на "Запуске игры" всплывает эта плашка. Игру запускаю через стим. На другом устройстве в мой Акк заходит, играю пока через него, но хочу через основной ПК всё таки. Помогите исправить эту ошибку!
не запускает игру ea fc 27
Повторно поднимаю тему, так как проблему решать надо, а это "Годная" и "беспроблемная" игра стоила немалых денег Приветствую, неделю назад столкнулся с проблемой , что вылетает при заходе в игру , через стим или еа, куплена игра в стиме. Убил вчера весь на поиски решение, ничего не помогло. Переустановку пробовал, даже на другой диск, целостность проверял, впн и прочее пробовал, secure boot включен, проверял, даже отключал его и потом включал, абсолютно все фоновые службы отключал, faceit и прочее ничего нет, ea античит удалял и устанавливал заново, делал восстановление, стим через администратора запускал, visual c++ переустанавливал и восстанавливал, настройки сети делал и сбрасывал днас и прочее, также пробовал использоваться lagoifast и gearup бесполезно, вот все, что в интернете есть уже перепробовал, в чем проблема непонятно. 2 недели играл нормально Железо: ryzen 7 5700x3d rtx 3070 32 gb
FC 27 (PC): match ping 33-42ms → 50+ms after October maintenance — evidence
Hi EA team and everyone reading this. I want to report a server-side routing problem that started right after the October server maintenance. Everything below is measured and verified data, not guesses. MY SETUP - Location: Ufa, Russia (Urals) - ISP: Ufanet, wired connection, stable, no issues on my side - Game: EA SPORTS FC 27, PC - Platform: PC (the same behavior in every match, not related to specific opponents) TIMELINE AND SYMPTOMS - FC 27 launched on September 17, 2026. From launch day until mid-October my in-game match ping was consistently 33-42 ms. Smooth, stable, no problems at all. - Immediately after the October server maintenance the situation changed overnight: ping is now 50 ms and above (very rarely dips to 48, rises higher when servers are loaded), with visible packet loss and connection instability. - In the worst cases the connection to the opponent drops completely mid-match. - These disconnections trigger unfair sanctions against me: reduced coin rewards and uncredited objectives. I am being penalized for something that is happening on the server side. EVIDENCE 1 — WHERE MY MATCH TRAFFIC ACTUALLY GOES I captured game traffic during live matches using pktmon (the built-in Windows packet monitoring tool — no third-party software, no risk of triggering anticheat). Match traffic (ports 3659 / 9999 / 52054 / 52055, over 600,000 packets total) goes to exactly two Google Cloud hosts: - 35.217.3.225 — 353,286 packets - 35.217.34.79 — 271,330 packets All other EA endpoints exchanged only about 112 packets each — those are clearly background services, not the match itself. Conclusion: my matches are served from two Google Cloud IPs. There is no way to influence which ones — they are assigned by EA's server infrastructure. EVIDENCE 2 — MY PATH TO THOSE SERVERS IS CLEAN Traceroute to both hosts, zero packet loss across all hops: - Hops 1-10 (inside my ISP network): 3-5 ms, no loss - Hop 12 (ISP border, 81.27.252.150): 29 ms - Hop 14 (first Google network node, 72.14.220.22): 42 ms - Beyond that Google does not respond to probes (normal for their internal network) This means my ISP delivers traffic to the Google network edge in 42 ms with zero loss. The path is excellent. Therefore the extra latency, the packet loss and the disconnections originate inside EA's hosting side — not on my connection. EVIDENCE 3 — THE TIMING MATCHES THE MAINTENANCE EXACTLY The change happened overnight, immediately after the October maintenance, with no changes on my side: same ISP, same router, same cables, same game version. If my connection was the problem, the ping would not jump from 33-42 ms to 50+ ms in one night. WHAT I BELIEVE HAPPENED The October maintenance changed the region-to-data-center mapping: accounts from my region (Russia, Ufa area) are now assigned to a farther data center instead of the closer one that served us from launch until the maintenance. This is consistent with reports from other players in Russia in this forum section describing the same symptoms after the same maintenance. WHAT I AM ASKING EA TO DO 1. Confirm which data center is currently assigned to my account for FC 27 matches. 2. Check whether the region-to-data-center mapping for Russia was changed during the October maintenance. 3. Restore the closer data center that served my region from launch until the maintenance. 4. Review the unfair sanctions (reduced coin rewards, uncredited objectives) I received because of disconnections that were not my fault. I can provide full packet captures and traceroutes at any time — just ask. P.S. Side note for the EA team: the help.ea.com portal does not create cases for my account — submitted reports never appear in "My Cases" and no confirmation email ever arrives (tried different browsers, private mode, English site version). Because of that I could not open a formal ticket, which is why I am reporting this here. I would appreciate it if a Community Manager could open a manual case for this issue. Thank you.
Ошибка подключения к серверам EA
FC 27 (Steam): стабильное отключение через 2–5 минуты в UT, ошибка «Ошибка подключения к серверам EA» При входе в Ultimate Team меня стабильно выкидывает примерно через 2–5 минут. Иногда даже из меню — то есть я вообще не успеваю начать матч. Ошибка: «Потеря соединения с серверами EA». Я перепробовал буквально всё, что находил в гайдах и на форумах: Проверял статус серверов EA — там всё нормально. Проверял пинг до ea — у меня стабильно 20–21 мс, потери 0% (тестировал на 30 пакетах). То есть интернет у меня не плавает, пакеты долетают. В Steam проверял целостность файлов — Steam нашёл и докачал 3 проблемных файла, но это не помогло. Полностью удалял папку Electronic Arts в %localappdata%, чистил временные файлы, сбрасывал Winsock и менял DNS на Google. Запускал Steam и игру строго от имени администратора. Скачал EA App, чтобы попробовать запустить через него, но и это не решило проблему. Сейчас уже не знаю, что делать. Соединение рвётся слишком быстро, будто сервер EA сбрасывает мою сессию. Платформа: Steam, Windows 10, подключение кабель. Последние попытки были 19:40-20:50 (МСК). 22.10.2026 Если вам нужны какие-то логи или файлы диагностики, скажите, где их взять, я пришлю.
Persistent "Unknown error 0:85009S" disconnect 6-7 minutes into every match PC
SUMMARY Battlefield 6 (Steam) disconnects me 6-7 minutes after launch, always in the middle of a match, with "GAME ENDED - You were disconnected from the game" and then "UNKNOWN ERROR - An unknown error occurred. ERROR CODE 0:85009S". It started about two weeks ago (mid-October 2026). I have documented 7 sessions; every single one died between 6:16 and 7:43 minutes. Before that the game worked normally for about a year. SYSTEM - Platform: PC, Steam (app id 2807960), Steam build 26003479, game updated 2026-10-30 22:14. - EAAntiCheat: 10.0, driver build 2026-10-21T02:37:35Z. - OS: Windows 10 Pro 22H2, build 19045.6456 (no Windows updates available - Windows 10 support ended). - CPU AMD Ryzen 5 5600, mainboard Gigabyte B550M AORUS ELITE, Secure Boot enabled, fTPM 2.0 enabled. SYMPTOMS Matchmaking and joining work fine. I play about 5 minutes, then the game returns to the menu with the two dialogs above. Sometimes it also kicks me while I am in the menu. WHAT I MEASURED ON MY SIDE I ran a local monitor that samples "netstat" every 2 seconds for the bf6.exe and EA AntiCheat processes. At the exact moment of every disconnect: - DNS resolution of accounts.ea.com answered in 1-2 ms and TCP 443 to it connected successfully; - there were no router-side events at all (no WAN flap, no tunnel restart, no routing/policy change); - the game's own sockets (UDP 9999 and TCP connections to AWS game servers, e.g. :10010, :15073) were closed by the server side, after which the client opened new ones 3-10 seconds later. So the session is being terminated server-side, not by a network failure on my end. WHAT I ALREADY TRIED (no effect) - Clean reinstall of EAAntiCheat: removed the EAAntiCheat folder inside the game directory and C:\ProgramData\EAAntiCheat, then Steam "verify integrity of game files". - Full reinstall of the game; verify integrity - no errors reported. - IPv6 disabled; DNS variations (ISP DNS, router DNS, 1.1.1.1); UPnP enabled and a static UDP 3659 port forward configured. - Five different network paths, all with exactly the same result: 1) fiber PPPoE connection directly (ISP "Real", no VPN), 2) Beeline Ethernet directly (no VPN), 3) router-level WireGuard tunnel to a Netherlands datacenter, 4) GearUP Booster, 5) PC-level VPN (Windscribe). - Account: no bans or restrictions on the account page, no other active sessions or devices, password changed and logged out/in everywhere. IMPORTANT CROSS-CHECK Another EA title that uses the same EAAntiCheat driver ran on the same PC, same EA account and same network for 57 minutes 30 seconds without a single disconnect. SESSION LOG (local time, UTC+4) 2026-10-31 00:04:15 - 00:10:59 (6:44) direct, Beeline 2026-10-31 00:23:59 - 00:30:40 (6:41) direct, fiber PPPoE 2026-10-31 00:45:47 - 00:52:52 (7:05) direct 2026-10-31 20:23:38 - 20:30:16 (6:38) direct, Beeline 2026-10-31 22:14:05 - 22:20:32 (6:27) router WireGuard tunnel 2026-10-31 23:47:42 - 23:55:25 (7:43) direct 2026-11-01 11:29:36 - 11:36:51 (7:15) PC-level VPN (Windscribe) Every entry ends with error 0:85009S. Exact drop moments: 00:52:33, 11:36:29 (and similar for the rest). MY REQUEST 1. Please check on your side the server-side reason why these sessions were terminated for this account (anti-cheat invalidation / region check / session token rejection), using the timestamps above - you can see the termination reason in your session logs. 2. Please confirm whether this is a known regression introduced with the 2026-10-21/22 update (EAAntiCheat build 2026-10-21T02:37:35Z), because the disconnects started right after it. 3. If you cannot reproduce it, please escalate to the Battlefield 6 live-services / anti-cheat team. I can provide the full 2-second-resolution monitor logs for any of the sessions above. Thank you.
Расисты
Канадские расисты специально увеличивают пинг и потерю пакетов для игроков из восточной Европы. в фк26 пинг был 4-6. в середине июля после обновления стал 14. фк27. Пинг 14-20 частое болото. 15 октября после очерченного обновления пинг 24-30 и вечные телепорты и Фризы. Проблема только у восточной Европы.
Постоянные зависание в Апексе
Hello!This crap wasn’t happening when I first started, but appeared later. Every time I launch, shaders keep compiling. If I minimize the game, the whole system can freeze (not just the game), forcing a reboot. Same freeze can hit right after entering the game. Sometimes it just starts lagging hard — revive an ally once and it interrupts, so I have to do it again. Camera snaps me back sharply like it’s pinging. Flying and jumping in place work fine (small plus — harder for enemies to hit me), but because of the bugs I still miss all my shots...Internet is good. GPU and CPU are fine, other games work normally. No system issues — only happens in Apex on launch or during play.
