Black Screen when exiting match (report)
As the title says... I've been getting stuck on a black screen when exiting a match. This has been a persistent issue since early last month and by a quick Google search, it certainly appears this is a neglected problem considering how many people have reported or discussed this issue. I've tried reinstalling, repairing, changing various settings (lowering graphics, resolution, full screen to borderless and windowed), updating GPU drivers, and nothing has fixed it. This issue requires force closing (Alt-F4) BF6 and relaunching the game.
This game is literally unplayable now
Scoreboard bug happens multiple times a game, seems more likely when in a vehicle (worst possible time, especially in spawn since you just have to alt tab and quit) Chat doesn't work I have been unable to perform a crouch slide since launch using the keybinds on my mouseBF6 Fix: DXGI DEVICE HUNG on GTX 10-Series
POST: I want to share a fully tested fix for the “Hang Detected in waitForFrameFences,” “DXGI_ERROR_DEVICE_HUNG,” and fence-value GPU crashes that MANY players (especially GTX 10-series / Pascal cards) are experiencing in Battlefield 6. This issue is not caused by overheating, overclocking, bad RAM, or drivers. It is caused by DirectX 12 instability on GTX 10-series GPUs combined with the new Frostbite RenderCore2 pipeline. Who Is Affected GTX 1060 GTX 1070 GTX 1080 GTX 1080 Ti Titan X Pascal Pascal cards have poor DX12 memory management + limited Async Compute, causing: Fence queue stalls Shader compilation timeouts VRAM fragmentation Total driver hang → “GPU will not respond to more commands” This causes the exact error message: "DXGI_ERROR_DEVICE_HUNG: The GPU will not respond to more commands" “Hang Detected in waitForFrameFences” ROOT CAUSE DirectX 12 on Pascal GPUs crashes because Frostbite’s RenderCore2 renderer aggressively allocates VRAM and async compute tasks that Pascal cannot handle. Under DX12: VRAM spikes to max Driver stalls Fence values stop incrementing The GPU times out (TDR) Crash THE FIX (100% WORKING): FORCE DX11 1. Add this to Steam Launch Options: -renderer dx11 -dx11 2. Edit PROFSAVE_profile (Documents\Battlefield 6\settings\steam): Find and set: GstRender.Dx12Enabled 0 GstRender.Dx11Enabled 1 Save file → set it to Read-Only (This stops the game from switching back to DX12 automatically.) 3. Delete shader + cache folders: Documents\Battlefield 6\cache AppData\Local\Battlefield 6\cache ProgramData\NVIDIA\DXCache ProgramData\NVIDIA\GLCache ProgramData\NVIDIA Corporation\NV_Cache The game will rebuild shaders cleanly when you relaunch. 4. Optional but recommended (OBS users): Disable this in OBS: Settings → Advanced → Browser Source Hardware Acceleration → OFF (Prevents additional GPU stalls.) RESULT After switching to DX11: No more DXGI_DEVICE_HUNG No more "waitForFrameFences" hangs No more GPU timeout No more stutters from VRAM spikes Stable gameplay even for hours OBS streaming works VRAM usage stays consistent Performance is smoother overall DX11 is slightly slower than DX12, but it is far more stable on Pascal GPUs, and the difference is small with optimized settings. (Optional) Recommended Graphic Settings for GTX 1080 (DX11): Set HIGH/ULTRA for: Texture Quality → Ultra Texture Filtering → Ultra Mesh Quality → Ultra Lighting Quality → High Terrain Quality → High Set MEDIUM for: Volumetric Quality Effects Quality Set LOW/OFF for: Undergrowth Local Light & Shadow Sun Shadow Screen Space Reflections Screen Space AO & GI High Fidelity Objects Advanced: Fixed Resolution Scale → 100% Anti-Aliasing → TAA Future Frame Rendering → ON Upscaling → OFF Dynamic Resolution → OFF Reflex → Disabled (optional) This gives excellent visuals WITH stability. FINAL NOTE This is a game engine issue, not a driver defect or user hardware problem. Frostbite DX12 + Pascal = unstable. Frostbite DX11 + Pascal = 100% stable. Until EA/DICE patch the DX12 path, GTX 10-series users should run DX11. Hope this helps others who have been fighting these crashes. This fix has completely stabilized my game.
The cause of mouse stuttering when pressing keys has been 100% found
I'll try to be brief🙂 The bug itself is that when quickly pressing certain keys on the keyboard while simultaneously moving the mouse left and right, the image stutters. However, there's a catch: every time the game is restarted, there seems to be some kind of buffer that fills with the first 4-8 keys pressed on the keyboard. So, if, for example, I press the W,A,D,C,R,Q,S keys first, there's a 99% chance the bug won't affect them. However, the keys pressed after this (from about the ninth key and so on) will reproduce the bug. Moreover, this buffer can "fill" even by clicking the keyboard in the menu. And if the first keys pressed weren't the ones needed for comfortable, dynamic play with parallel mouse movement, then only a reboot and a new input will help. I tested this theory on almost 100 game restarts. And now the first thing I do before a game is enter training mode with my mouse, click the necessary W,A,D,C,R,S,Space,Shift and continue playing calmly. But it shouldn't work like that!🙄 My guide on this topic is on Steam - https://steamcommunity.com/sharedfiles/filedetails/?id=3626300845 UPD: An interesting observation from steam/ZongerX is that when pressing problematic keys, Javelin Anti-Cheat activity increases in Task Manager (in my case, by ~3%). However, the problem most likely isn't the extra CPU load itself, but rather that the anti-cheat starts some background checks at that moment on those keys that did not end up in the "safe" buffer and those that are not pressed together with "Alt".
Unable to exit scoreboard mid match!
Hi DICE, This bug keeps happening and requires a full restart of the game to reset. Whilst checking the scoreboard mid match, pressing right mouse button whilst looking at the scoreboard causes all inputs to not register, freezing the game in the scoreboard and forcing a full restart of the game. I've seen other complaints of this happening. Needs looking into! Many thanks 🙏
Black screen and game does not respond after leaving a redsec match
Happens 80% of the time when I die in a redsec match and I leave, screen goes black and I have to alt+F4 the game and relaunch the whole thing. The term "annoying" is weak to describe this problem. Also, is it possible to actually drop in the direction I'm already looking at when dropping from the chopper in redsec? There's always a weird swivel in camera angle when dropping. Thanks.
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.
Stuck in Scoreboard
Every day for weeks now, iam stuck on PC in the Scoreboard. Reported it already multiple times, its still there, it still happens to me and my friends on a daylie basis. You have to kill your game to get out of it, so there is no way of getting any crash report or anything. you can use your mouse, open all scoreboard menues and player profiles, but you cant get back in game. We cant recreate it, but its there, randomly while checking out scoreboard or report a cheater.
