Old Account Stuck: No Match Allocation, Even Firing Range Fails
Dear EA Support, My old S2 Apex account cannot enter any match. It was created on Origin and later linked to Steam; I now launch via Steam. Standard matchmaking searches forever, Ranked is locked by required matches, and even Firing Range will not load. Firing Range is single-player, so this is not population—my account cannot get a match allocation. Another account on same PC/network/region works normally, including Firing Range. No ban notice; no violations. This suggests a backend matchmaking or Origin-to-Steam linkage issue on this account. Account: [edit: email address removed], IGN 一枕明月, Steam (originally Origin), level 4, last played S2. Tried: EA re-login, language-switch update, Tokyo/Singapore, cross-play on, Ranked cancel + Firing Range, verify files. Request: Please check/reset this account’s stuck matchmaking allocation state, and verify the Origin-to-Steam linkage is not causing the block. I can provide screenshots/videos. Thanks, yizhenyue[PC/Steam] Stuck on Infinite Loading Screen After EA Javelin Anticheat Update
Platform: PC / Steam OS: Windows 11, fully updated GPU: AMD Radeon RX 9070 XT GPU Driver: AMD Software: Adrenalin Edition 26.8.1 Secure Boot: Enabled Issue: Since the migration from Easy Anti-Cheat to EA Javelin Anticheat, Apex Legends gets stuck indefinitely on the initial loading screen (spinning loading indicator) and never reaches the lobby. The game itself launches normally, and Javelin appears to start successfully, but Apex never gets past the loading screen. Troubleshooting already performed: Completely reinstalled Apex Legends Verified Steam game files multiple times Restarted Windows Reinstalled EA Javelin Anticheat Confirmed Secure Boot is enabled Fully updated Windows 11 Tested different AMD GPU driver versions Checked Windows Firewall Changed DNS to Cloudflare (1.1.1.1 / 1.0.0.1) and flushed the DNS cache Ran Steam/Apex with administrator privileges None of these steps resolved the issue. Javelin service test: Before launching Apex: sc query EAAntiCheat shows: STATE : 1 STOPPED While Apex is running and stuck on the loading screen, the same command shows: STATE : 4 RUNNING WIN32_EXIT_CODE : 0 SERVICE_EXIT_CODE : 0 So the EAAntiCheat driver appears to load successfully when Apex starts. Steam file verification behavior: After launching Apex, Steam consistently reports exactly 3 files as failing verification: EAAntiCheat.GameServiceLauncher.dll EAAntiCheat.GameServiceLauncher.exe preloader_l.dll Steam's content_log.txt reports: Validation: full scan ... found 3/10329 mismatching files (73.06 MB/88.12 GB) The verification repairs these files successfully. I also tested the following: Verify files → Steam repairs the 3 files. Verify again WITHOUT launching Apex → all files verify successfully. Launch Apex → game gets stuck on loading screen. Close Apex and verify again → the same 3 EA Anti-Cheat files fail verification again. Therefore, these files are being modified when Apex/Javelin is launched. I do not know whether this is expected Javelin behavior or related to the loading issue. Additional observation: C:\Program Files\EA\AC\EAAntiCheat.Installer.exe does not list Apex Legends in its game selection list. However, unlike some other reports, the EAAntiCheat driver IS registered on my system and changes to RUNNING while Apex is running. The issue started after the EA Javelin Anticheat migration. Apex was previously able to reach the lobby normally. Could this be an issue with the Javelin migration or authentication/initialization process? I can provide the full Steam content_log.txt or additional diagnostic information if needed.
The Razer V3 Pro (8kHz version) conflicts with Battlefield 6 and Apex's Javelin.
Update: This issue also occurs in Apex Legends—appearing to stem from a conflict between EA’s Javelin anti-cheat system and Razer’s 8 kHz polling rate implementation. I am documenting my case here in hopes of helping narrow down the root cause. Hardware configuration: Razer Huntsman V3 Pro (8 kHz variant). Upon launching affected titles, the keyboard exhibits identical symptoms: immediate disconnect/reconnect cycles; automatic switching from the active user profile to a different onboard profile; and continued cycling until the device resets to factory defaults—all while Razer Synapse freezes or crashes in the background. Two critical new observations: 1. The issue now reproduces consistently in Apex Legends. Following Apex Legends’ transition from Easy Anti-Cheat (EAC) to EA’s proprietary Javelin anti-cheat framework (completed in late September), the same behavioral pattern emerges. In contrast, non-Javelin titles—including Call of Duty, DOOM, and others—operate without incident. This strongly implicates Javelin as the common denominator, shifting focus away from a game- or engine-specific (e.g., Battlefield/Frostbite-only) explanation. 2. The problem persists even with Synapse fully closed or uninstalled, occurring approximately every 15 minutes during gameplay. This regular interval suggests a time-based or timeout-driven mechanism—such as Javelin’s periodic kernel-level input scanning or handshake routine interfering with the 8000 Hz HID report stream—or potentially a USB power management timeout on the peripheral side. To support deeper analysis, I am collecting Windows Event Viewer logs (Kernel-PnP events 1010 and 20001) alongside timestamped logs from C:\Program Files\EA\AC\. Troubleshooting steps already attempted (without permanent resolution): • Reducing keyboard polling rate to 1000 Hz (reduces occurrence frequency but does not eliminate it); • Connecting directly to a rear motherboard USB-A port; • Testing alternate USB-C cables; • Disabling USB selective suspend; • Updating firmware and performing a device-level factory reset via Synapse; • Removing all third-party tools flagged on EA’s denylist (e.g., OpenRGB, HWiNFO, MSI Afterburner, reWASD, AutoHotkey); • Running the EA App with administrator privileges; • Verifying integrity of game files. Request: We respectfully urge engineering teams at EA, DICE, and Razer to jointly investigate this interoperability issue. If Javelin’s kernel-mode input handling is incompatible with high-frequency HID reporting (e.g., 8000 Hz) or Rapid Trigger–enabled peripherals, such limitations should be formally documented. Users should not be forced to compromise between advertised hardware capabilities and access to EA-published titles. A targeted solution—such as a driver/firmware-level compatibility patch, an official allowlist for Razer’s certified HID interface, or even a documented workaround—would significantly improve user experience and reduce widespread diagnostic effort.[PC] Stutter: Threads Freeze 46-47ms Every 10-20s (Firing Range Too)
Hi Apex team, I want to report a very frustrating micro-stutter issue that has been happening recently. It happens in both live matches and the Firing Range. The physical feeling is that when I pan my camera quickly, the screen "jitters" or pauses for a split second. This happens very frequently, about every 10 to 20 seconds. I spent a few hours troubleshooting my PC and running data sampling, and I finally caught the exact cause. When the stutter happens, the game client's threads undergo a precise freeze lasting exactly 46-47ms. This specific "freeze" fingerprint remains exactly the same no matter what settings I change. Because it happens in the Firing Range (which doesn't need much network or complex loading), it clearly points to an engine-level issue. I have already done a lot of testing to make sure this is not a problem on my end. I tested and ruled out all Windows October updates, GameDVR, Steam Overlay, audio drivers, display path/MPO, shader cache, CPU downclocking, and GPU modes. I even completely reinstalled the game, but it didn't help. I also tested other highly demanding games (like Wuthering Waves), and they run perfectly with zero micro-stutters on my current setup (i7-13700HX + NVIDIA GPU). My conclusion is that this is an internal behavior conflict between the Apex client (v3.0.3.65) and certain hardware configurations. My best guess is that after the server/content switch around October 21st, some periodic internal system in the game is blocking the main thread. Since it's a thread freeze, I can't fix it locally. I really hope the dev team can look into the periodic thread blocking issues in this engine version using backend logs. Thanks! Please see the attached screenshot for the detailed diagnostic conclusion generated by the ZCode profiling tool.[PC] Micro-Stutter: Game Threads Freeze 46-47ms Every 10-20s (Firing Range)
■ System & Version Info Platform: PC (Steam/EA App) Hardware: Mechrevo Yaoshi 15 Pro 2024 (Intel i7-13700HX + NVIDIA GPU) Game Version: v3.0.3.65 ■ Issue Description During gameplay (both in live matches and the Firing Range), the game frequently experiences very brief micro-stutters. The physical sensation is that when panning the camera quickly, the screen "jitters" or "pauses" for a split second. The frequency is very high, occurring approximately every 10 to 20 seconds. ■ Technical Evidence & Fact Chain After over 4 hours of deep-level troubleshooting and dozens of data sampling sessions, we have identified the root cause: When the stutter occurs, all threads of the game process undergo a precise freeze lasting exactly 46-47ms. This specific "fingerprint" remains completely unchanged regardless of any system configuration adjustments. Notably, this periodic freeze still occurs in the "Firing Range," which requires no network interaction or complex resource loading. ■ Locally Ruled-Out Factors To prove this is not a local PC, system, or network issue, we have tested and ruled out the following items one by one: All Windows October updates (verified by uninstalling them individually). GameDVR, Steam Overlay, Nahimic, and the entire audio device chain (headphones/speakers). Display path/MPO, shader cache, VRAM limitations, and memory paging. CPU downclocking, Dedicated/Hybrid GPU modes. Third-party game accelerators, Easy Anti-Cheat (EAC) launcher activities. Complete game reinstallation (did not work). Other highly demanding games (e.g., Wuthering Waves) run perfectly on the same setup with zero micro-stutters. ■ Conclusion & Suspected Direction Based on the above, the issue points 100% to the internal behavior between the Apex game client (v3.0.3.65) and specific hardware configurations. Primary suspicion: Following the server/content switch around October 21st, a periodic internal system in the game (present even in the Firing Range) is blocking the main thread. This type of periodic thread freeze cannot be resolved locally and requires an official fix or driver adaptation. We hope the dev team can investigate the periodic thread blocking issues in this engine version via backend logs. Please see the attached screenshot for the original diagnostic conclusion.Server issues
I have been grinding hard this season and this has happened enough times that I’m about to put my controller through my screen. I have clips of this happening and I think it’s ridiculous that anyone should have to put up with this. My internet has been running on 40-60ms of ping while gaming so I know that the issue isn’t on my end. Fix your freaking servers I mean how many more seasons are players going to have to deal Dollar store service from a professional gaming company.
