Game crashing during Gauntlet (Xbox Series X)
As title says, my game has been crashing multiple times, specifically during Gauntlet games. It has happened twice during the last match of the Gauntlet games, and now 3 other times during other times of Gauntlet matches (first match or beyond). I do not have this issue with other game modes, even battle royale I have not experienced a crash. My game is up to date, my xbox is cleaned out, and internet does not seem to be playing a factor. Just wondering if anyone else has ran into this issue, it is incredibly infuriating completing challenges and then the game crashes and nothing counts. Trying to see if there is anything left to attempt to fix this issue.
Battlefield 6 doesn’t start after update!
Hi, is anyone have problem with launching the game after the latest update through steam? I just updated it, and now i can’t even launch the game. Whether i press on the desktop game icon, or on steam to “game”, nothing happens. I’m from Hungary, i have 50+ hours in the game and i played yesterday too but there was no issue like this. If anyone know what’s this, please help somehow! Thanks!
Stutters, hiccups , framedrops i found the cause!! Edit***
So after hours of testing today, I found the cause of stutters, frame drops, etc. It's the Javelin anti-cheat, which overloads one or two CPU cores when you press WASD, 1, 2, or 3, the enter button, or certain letters. The CPU core goes to 100%, and this results in stutters. It's affecting all Battlefield titles, so please fix this, Dice! Edit** I noticed that pressing certain keyboard keys (like number keys or arrow keys) causes noticeable micro-stutters in BF1, BFV, and BF6. FPS stays high, GPU load is fine, and CPU cores aren’t maxed. Mouse movement or clicks don’t trigger this. It seems to happen only with keys that change the game state (weapon switch, zeroing, gadgets). Rapidly pressing these keys makes spikes worse (dpc latency.) Shader cache warm-up reduces it slightly, and capping FPS also helps mask the spikes. From what I can tell, the cause is kernel-level anti-cheat checks (Javelin/EA AC) validating discrete input. These checks temporarily block the main game thread, which shows up as micro-stutter, even though CPU/GPU aren’t overloaded. This isn’t a hardware or driver issue—it’s a side effect of the anti-cheat + Frostbite engine. please fix this soon!EA SPORTS FC 25 freezes on startup on PC (EA App) – no official solution yet
Hello everyone, I’m posting this because I’ve run into a game-breaking startup issue with EA SPORTS FC 25 on PC, and it seems I’m far from the only one. Issue description When launching FC 25 via the EA App on PC, the game gets past the initial input prompt but then freezes immediately on the next screen (see attached screenshot). It never loads any further, making the game completely unplayable. What I’ve tried Restarting the game and PC Reinstalling the game Deleting personal settings and recreating them (community workaround) Unfortunately, while I can recreate the settings, the game still freezes on the exact same screen afterwards. So this workaround does not fix the issue for me. System specifications OS: Windows 11 Pro 64-bit (Build 22631) CPU: Intel® Core™ Ultra 9 285K GPU: Gigabyte GeForce RTX 5070 Ti 16GB RAM: 64 GB DDR5 (6000 MHz) Motherboard: Z890 GAMING X WIFI7 Storage: Samsung 990 PRO SSD 2TB So this is clearly not a hardware limitation. Concern There are multiple threads on this forum describing the same problem, yet there is still no official response or solution from EA. For a paid title, this really shouldn’t be acceptable. Request If anyone from EA or the community team is reading this: Is this issue acknowledged? Is a fix being worked on? Is there any official workaround that actually works? At this point, I simply want to be able to play the game I paid for. Thanks in advance to anyone who can help or share useful information.
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.
