BF6 Not Launching: EA Javelin Anticheat error code (7) (1053)
Hi there, BF6 is not launching for me in Steam, when I try to open the game I get this error message: I have tried several things: restarting my computer reinstalling EA Javelin Anticheat reinstalling the game running the game as well as the Anticheat as an administrator running the game in compatibility mode allowed the game in Windows anti-virus verified integrity of game files in Steam installed/repaired Visual C++ files Has anyone else encountered this? Can anyone help? I have an AMD Ryzen 7 1700X Eight-Core Processor and an NVIDIA GeForce GTX 1070 Ti.
EA SPORTS FC 26 PC FIX – COMMUNITY GUIDE
if your game keeps crashing after kickoff loading or in drop in follow this full reset fix 1 open EA App and uninstall the game completely 2 go to this path C:\Users\gamer\AppData\Local delete the folders EA SPORTS FC 26 and EADesktop 3 then go to C:\Users\gamer\AppData\Roaming delete the folders EA and Electronic Arts 4 restart your PC 5 open EA App again and reinstall the game normally 6 after install launch the game it will rebuild all cache and config files fresh this method clears all broken data that causes the common PC bug where the game crashes during cutscenes goals or kickoff it basically forces EA App and FC 26 to create new clean files I didn’t touch any graphic settings after doing this I went straight into the game in rush mode i am now on my 10 game before i was chrashing every game for past 2 days i needed to take it on my own hands maybe ea can me a job from now on because this been tested and its working for all my friends too
Battlefield 6 DirectX crashes can only be a problem with the game engine.
Battlefield 6 is crashing with DirectX errors on a wide range of systems. This has been happening since release and appears related to the game engine under heavy load. It needs an official fix. Many players are reporting the same behavior across different hardware and drivers. Some players say that the problem appears to have existed since Battlefield 2042. I can't confirm that myself, as I haven't played BF2042 for very long. My system: - CPU: [I7 14700K] - GPU: [RTX 3090] - RAM: [DDR5/ 64gb / 6400mhz] - Storage: [M.2 SDD/NVme] - Motherboard and BIOS: [MSI Z790 Carbon WiFi/latest] - OS: Windows 11 [24H2] fully updated - Display: [1440P/ultrawide] - Driver: NVIDIA [latest] clean installed with DDU Error codes: - DXGI_ERROR_DEVICE_HUNG - DXGI_ERROR_DEVICE_REMOVED What happens: - Crashes occur sporadically - Sometimes only the game and open Steam processes die (most in my Case) - Sometimes the entire PC reboots (for some players) - there is no consistent pattern by map or time into the match But there are repeated DirectX related crashes that are not fixed by normal maintenance or driver changes. Steps to reproduce: 1. Launch the game normally from Steam or EA App 2. Join RedSec or Conquest mode 3. Played it through heavy action for a few minutes to tens of minutes or Sometimes over one hours 4. Crash with one of the codes above Impact: - Progress and match results are broken - Time is wasted on failed troubleshooting - This affects many players, not isolated edge cases What I have already tried: (None of the following resolved the issue) - Drivers and OS: - Clean driver installs with DDU for multiple versions - Switching between Game Ready and Studio drivers - Windows updates and optional cumulative updates - Removing all overlays and capture tools - Graphics API and launch options: - Launching with -d3d11 - Disabling or enabling the different Anti-lag and upscaling ingame options. - Forcing different shader cache settings in the driver - BIOS and firmware: - Enabling and disabling Resizable BAR - Updating GPU VBIOS - Updating motherboard BIOS and chipset drivers - Power and stability: - Returning CPU and GPU to stock clocks - Disabling XMP or EXPO - Raising power limits or lowering them to stock - Checking PSU capacity and Performance - disable PCI-Express - Link State Power Management on Windows - set Windows PWR-Management to ultimate Performance - Game files and cache: - Verifying files via Steam - Reinstalling the game on a different drive - Deleting DX shader caches - switching Graphics settings - Dropping all settings Low - Disabling Anti-lag and upscalers - Reducing resolution to well below native - Frame cap on and off (ingame and rtss) - Vsync on and off - disable Freesync/gsync - Workarounds that are not solutions: - Artificially throttling performance to keep GPU load very low (this seems to be working) - Running windowed or borderless - (Not tested long enough yet) - Disabling all background apps and services - (Not tested long enough yet) Community signal: Multiple reports show the same DirectX crash codes and the same failure of the usual fixes. The scope appears broad across GPUs from different vendors, multiple driver lines, and fully updated Windows systems. -- All this points to an engine side stability issue under specific render or memory pressure conditions.-- What we need from EA and the dev team: Official acknowledgement that this is being tracked as a top priority and a targeted hotfix or a detailed workaround that does not **bleep** performance. If a driver side change is needed, coordinated guidance with NVIDIA and AMD. Optional: a temporary toggle to disable the specific feature set that triggers the crash. Clear communication on progress and an estimated timeline for a fix. This is blocking normal play for many of us. A stable fix would go a long way for the community. Thank you.
Game crashes upon death
Bug Report: Battlefield 2042 Crash on Death Animation So earlier today I started back playing Battlefield 2042 after not playing for about a year due to the new Dead Space collab with the new Outbreak mode. However, I'm having a serious issue where every time I die, right as the death animation starts to play, the game freezes and crashes immediately with no error message. This happens in all modes. I've looked online and seen others with similar issues. Some reported that deleting the cache folder for the game helped, but it was only a temporary fix — the issue returned within 30–45 minutes. Since deleting the folder didn’t help, I decided to reinstall the game, even though it’s large. Unfortunately, the problem got slightly worse: it started freezing even faster, sometimes before the death animation even starts. I then consulted ChatGPT, which recommended analyzing the crash dump file using a program called WinDbg. I did so, and shared the analysis with ChatGPT to interpret the results. ChatGPT Response Summary: Root Cause Summary: The crash was due to an Access Violation (0xC0000005) — specifically a read from a null or invalid pointer (0x0000000000000008). Crash Details: Module: amdxc64.dll (likely part of AMD graphics drivers) Function: Boost Serialization (boost::archive::detail::iserializer::load_object_data) Crash Reason: Attempted to read from RCX + 8, but RCX was NULL (0x0), leading to a crash. Contextual Clues: Crash occurred while BF2042.exe was running. Involves amdxc64.dll — a common AMD GPU driver library. Occurred during Boost serialization and DirectX 12 GPU pipeline operations. Likely Cause: A pointer used by the AMD graphics driver during deserialization or pipeline setup was NULL, causing the game to crash. So at this point, having done nearly every troubleshooting step and even running diagnostics with the help of ChatGPT, this is the closest I’ve gotten to an explanation. Hopefully someone from the developer team can help investigate further. And yes, before anyone asks — I did try switching the game to run in DirectX 11. The same issue persists. System Specs: CPU: AMD Ryzen 7 5800X GPU: AMD Radeon RX 6750 XT RAM: 32 GB DDR4 OS: Windows 11 Home, 64-bit Driver Version: AMD Adrenalin – latest version as of May 2025 Troubleshooting Performed: Verified game files via Steam Reinstalled the game Updated GPU drivers to the latest AMD version Set game to run as administrator Disabled all overlays (Discord, Steam, Radeon) Disabled all background apps No overclocking is done on this system
Controller switches to keyboard/mouse. Settings randomly change all the time
I’m playing FC 26 on PC using a PS5 DualSense controller. The pad works fine in menus and team selection, but when I load into an online match (FUT, Rivals etc.), the game randomly switches to keyboard/mouse input. Movement stops working, and I lose full control—even though the controller was active before kickoff. This happens even with Steam Input enabled, launched via Big Picture Mode, and with overlays disabled. It’s not a one-off—it’s consistent and game-breaking. On top of that, FC 26 constantly resets my settings: Every time I launch the game, some settings revert (camera, controller config, UI layout) Even after fixing them, they can randomly reset again when loading into a match This includes controller mappings, which makes the input bug even worse Here’s what I’ve already tried: Steam Input enabled (to support DualSense) and launched via Big Picture Mode Disabled EA Overlay, Steam Overlay, and NVIDIA Overlay Turned off EA Cloud Saves and deleted config folders under Documents/FC 26 Plugged in controller first, launched game cleanly, and avoided touching KBM during load Tested in Kick-Off mode first—controller works fine there, but bug still happens online This issue makes online play unreliable and borderline unplayable. I paid £90 for this game and have never had a PC title with so many input and config issues. Please escalate this—it's not an isolated case, and players across forums are reporting the same bug. This is quite frankly appalling and I will be asking for a refund if not sorted ASAP. Many thanks
