
Battlefield 6 Crash to Desktop with No Error Code Fix
Fix Battlefield 6 crashing to desktop with no error message. Javelin anti-cheat PCIe fix, Frame Generation crash, memory leak workaround, and overlay conflicts.
What is the Battlefield 6 Crash to Desktop with No Error?
Battlefield 6 (released October 10, 2025) suffers from a widespread issue where the game silently closes to desktop with no error dialog, no crash code, and no Windows Event Log entry. This makes diagnosis extremely difficult. The crashes are seemingly random but often correlate with specific maps (Cairo, Badlands, Eastwood), anti-cheat conflicts, or GPU driver timeouts.
A December 2025 hotfix made the issue significantly worse for many players, with crashes occurring every 10-15 minutes. A February 2, 2026 update introduced a variant where the game gets past the Javelin anti-cheat splash screen, shows nothing, and silently closes.
When does it occur?
- At startup, after the Javelin Anti-Cheat splash screen (game shows nothing then closes)
- During map loading, especially Cairo, Badlands, and Eastwood maps
- Mid-match after 10-15 minutes of gameplay (memory leak related)
- When Frame Generation (FSR) is enabled on NVIDIA hardware
- When overlays (Steam, Discord, GeForce Experience) are active
- After the December 2025 hotfix or February 2026 update
Common causes
- Javelin Anti-Cheat PCIe conflict — Javelin trips Windows' PCIe Runtime D3 (RTD3) power management, causing the GPU to momentarily power down
- Secure Boot disabled — Javelin requires Secure Boot enabled in BIOS and a GPT partition disk
- FSR Frame Generation on NVIDIA GPUs — a null pointer crash occurs when FSR is set as Frame Generation on non-AMD hardware
- VRAM memory leak — VRAM consumption climbs from 8GB to 14-15GB during extended sessions
- Overlay conflicts — Steam Overlay, Discord, and NVIDIA overlays interfere with DX12 rendering
- Corrupted shader cache — stale shader cache from previous driver versions causes startup crashes
- GPU driver timeout (TDR) — Windows kills the GPU driver when it stalls for more than 2 seconds
Step-by-step fixes
- Disable PCIe Link State Power Management — Open Control Panel > Hardware and Sound > Power Options > Change plan settings > Change advanced power settings > PCI Express > Link State Power Management > set to Off. Reboot. This is the most impactful fix for silent crashes caused by Javelin anti-cheat.
- Enable Secure Boot — Restart PC, enter BIOS/UEFI, navigate to Security > Secure Boot > Enabled. Your disk must use GPT partitioning (use Microsoft's
mbr2gpttool to convert from MBR if needed). Without Secure Boot, the game will not launch at all.
- Disable Frame Generation — If the game crashes on startup, edit the config file at
Documents\Battlefield 6\settings\PROFSAVE_profile(orDocuments\Battlefield 6\settings\steam\PROFSAVE_profilefor Steam) and manually set Frame Generation to off. If using a controller via Steam Input, disconnect it before launching — it forces FSR options instead of DLSS, causing crashes on NVIDIA hardware.
- Disable all overlays — Disable Steam Overlay (Steam > Settings > In-Game > uncheck "Enable Steam Overlay while in-game"). Also disable Discord Overlay (Settings > Game Overlay), NVIDIA GeForce Experience overlay, and MSI Afterburner overlay.
- Clear all shader caches — Delete shader cache files at these locations:
%LOCALAPPDATA%\Battlefield 6\cache,%LOCALAPPDATA%\D3DSCache,%LOCALAPPDATA%\NVIDIA\DXCache,%LOCALAPPDATA%\NVIDIA\GLCache(orAMD\DxCacheandAMD\GLCachefor AMD GPUs). Then verify game files through Steam or EA App.
- Increase the TDR timeout — Open Registry Editor as Admin > navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers> create a new DWORD value namedTdrDelay> set to10(decimal). Reboot. This gives the GPU 10 seconds to recover instead of 2.
- Increase virtual memory (pagefile) — Open System Properties > Advanced > Performance Settings > Advanced > Virtual Memory > Change > set a custom size of 16384-32768 MB on your SSD. The game has a known VRAM memory leak — restart the game every few matches to force the engine to release cached shaders.
- Switch to DirectX 11 — Add
-dx11to launch options (Steam: right-click > Properties > Launch Options; EA App: Game Properties > Advanced Launch Options). DX11 mode sacrifices some visual features but resolves DX12-specific crashes, especially on AMD GPUs.
If it still doesn't work
For map-specific crashes (Cairo, Badlands, Eastwood), navigate to <install directory>\Data\Win32\game\glaciermp\levels\, delete all files, then repair the game through the EA App or verify files on Steam. Install the latest Microsoft Visual C++ Redistributable to fix Javelin error codes 7 and 1053. Clean-install GPU drivers using DDU (Display Driver Uninstaller) in Safe Mode — do not rely on the standard installer. For the VRAM memory leak, toggle Texture Quality to Low > Apply > back to High — this resets VRAM allocations mid-session. Report persistent crashes on the [EA Battlefield Forums](https://forums.ea.com/categories/battlefield-6-technical-issues-en) with your system specs and the exact crash scenario (menu, loading, or mid-match).
Related errors
Fix Battlefield 6 DXGI_ERROR_DEVICE_HUNG and DEVICE_REMOVED GPU crashes. Resolve DirectX errors, driver timeouts, and game freezes on Nvidia and AMD GPUs.
Fix NVIDIA RTX 5090 and 5080 driver crashes with VIDEO_ENGINE_TIMEOUT_DETECTED error. Resolve black screens, game crashes, and DLSS instability on RTX 50 series GPUs.
Resolve Windows KERNEL_MODE_HEAP_CORRUPTION blue screen error. Fix memory corruption, driver heap violations, and pool corruption causing kernel mode heap BSOD in Windows 10/11.