How to Fix: Battlefield 6 Crashing on Startup (PC)

Quick Fix

Most startup crashes are caused by Secure Boot being disabled, which the game's anti-cheat requires. Try this first:

1. Enable Secure Boot in BIOS/UEFI. Restart your PC, enter BIOS (usually Del, F2, or F12 at boot), find Secure Boot under Boot or Security, enable it, and save changes.
2. Repair the game. In the EA App, go to My Library, hover over Battlefield 6, click More Options, then Repair. On Steam, right-click Battlefield 6, choose Properties > Local Files > Verify Integrity of Game Files.
3. Restart your PC and launch the game again.

Step-by-Step Guide

What this error means

Battlefield 6 crashing on startup means the game closes to desktop shortly after launch, often at the splash screen, during 'compiling shaders', or right after the anti-cheat window appears. Some players on Windows PC have reported that they've been unable to launch the Battlefield 6 client, with it crashing to desktop shortly after being run initially. Frequently there's no visible error message at all — most of the time, there are no error messages, the game simply closes automatically, returning you to the desktop. This usually points to one of a handful of known culprits: Secure Boot/UEFI requirements not being met, corrupted install files, GPU driver or upscaling (FSR) conflicts, or in rarer cases a deeper anti-cheat service bug.

Cause 1: Secure Boot or UEFI not enabled

This is the single most commonly confirmed cause of BF6 failing to launch.

1. Check requirements first. Battlefield 6 officially requires Secure Boot to be enabled in order to launch and run properly on Windows PCs. If Secure Boot is disabled, or if your system is using the legacy MBR partition style, Battlefield 6 may fail to start, crash during initialization, or encounter repeated anti-cheat verification errors.
2. Confirm your system supports UEFI and GPT. Your system must support UEFI boot mode, since Secure Boot only works in UEFI, not Legacy BIOS mode, and your system disk should use the GPT partition style — if it's MBR, you'll need to convert it to GPT first.
3. Enable Secure Boot in BIOS. Reboot your PC and enter BIOS/UEFI (usually by pressing Del, F2, or F12), find Secure Boot under the Boot or Security section, enable it and save changes, then restart your PC and launch Battlefield 6 again.
4. Check manufacturer instructions if needed. The BIOS interface may vary by manufacturer (e.g., ASUS, MSI, Dell, HP) — if unsure, visit your brand's official support page for Secure Boot setup instructions.

Cause 2: Corrupted or missing game files

1. Verify files on Steam. Open the Steam Library on your PC, right-click Battlefield 6 > Properties > Local Files, then click Verify Integrity of Game Files.
2. Repair via the EA App. Open EA App, go to My Library, select Battlefield 6, click Manage > Repair — the client will automatically replace or repair any damaged files. This is worth doing even if you already verified files, since the Repair option performs a deeper integrity check and can resolve launch-related or crash-on-load issues.

Cause 3: Outdated or conflicting GPU drivers, especially FSR/DLSS

1. Update your GPU driver fully. An old, corrupted, or incompatible driver can be the single biggest reason for crashes, and the game's release has prompted specific driver updates from all major manufacturers, so it's crucial to make sure you have the right one.
2. Disable frame generation / upscaling if using NVIDIA. NVIDIA's Frame Generation settings may cause Battlefield 6 to crash during startup or when loading into matches. Turn this off in the in-game graphics settings.
3. Disable FSR manually if crashes reference FSR2. Some crash dumps point to an FSR2 null-pointer bug. Try explicitly disabling it in the config: go to Documents/Battlefield 6/settings/steam and open PROFSAVE_profile in notepad, set GstRender.AMDNvidiaUpscalingQuality to 0, and also try -nofsr as a launch parameter in Steam (right-click Battlefield 6 in your Steam library > Properties > Launch options).

Cause 4: Background apps, storage pools, or system conflicts

1. Close background/overlay software. Running too many applications in the background, especially resource-intensive ones like web browsers with dozens of tabs or overclocking utilities like MSI Afterburner, can compete with Battlefield 6 and cause it to crash, and a clean system environment also helps prevent conflicts with the game's anti-cheat service, which can be very sensitive. Press Ctrl + Shift + Esc, go to Processes, and end any non-essential tasks.
2. Remove Windows Storage Pools. Some users on EA's forums found that a Storage Pool was interfering with the launch. One user reported: go into Settings then Storage and Storage Spaces, click on Advanced Storage Settings, and if you have a storage pool there delete it, then try loading the game again.
3. Increase virtual memory (paging file) if you have limited RAM. The paging file should be a minimum of 1.5 times the size of your installed RAM, and a maximum of 3 times your RAM size. Set this via sysdm.cpl > Advanced > Performance Settings > Advanced > Change (under Virtual Memory).
4. Check CPU/RAM overclocks. Some players found instability tied to RAM speed. In one case a user found the game only ran reliably after decreasing memory clock from 5600 to 5200 with auto voltages. If you run XMP/EXPO or any overclock, try reverting to stock speeds/timings.

Cause 5: Antivirus or anti-cheat conflicts (harder to fix)

1. Add exceptions to your antivirus. EA has acknowledged this specifically for campaign crashes: EA has identified a possible contributing factor where some antivirus programs may be falsely detecting the single-player executable. Add Battlefield 6's install folder and executable as exceptions in your antivirus software.
2. Try running as administrator. Right-click the EA App or Steam and bf6.exe and choose Run as administrator, since one user noted the campaign closes the launcher and launches a separate campaign application but needs admin permission first.
3. Try installing on a different drive. One affected user found their crash was tied specifically to their main drive: after installing the game on their second SSD it worked, saying the game just randomly decided it hated their main NVMe C drive.

Cause 6: Deeper, unresolved anti-cheat bug (needs official support/patch)

1. Recognize the signs of this rarer case. Some players have exhausted every fix (BIOS, drivers, clean Windows profile, no overclocks) with no success. In one detailed report, a user concluded: since they'd tried everything from BIOS settings to creating a new Windows user, this wasn't a standard configuration issue but a more fundamental bug related to their specific hardware/software combination.
2. Watch for anti-cheat service registration failures. On the Steam version specifically, some crashes stem from the EA Javelin Anti-Cheat installer failing to detect the Steam version of the game on certain hardware configurations, leading to a broken service registration that cannot be fixed by the user, with the main game executable still crashing immediately after the anti-cheat driver loads.
3. Escalate to official support. If you've tried Secure Boot, driver updates, repairs, antivirus exceptions, and a clean reinstall with no luck, file a detailed ticket at the EA Help/EA Forums Battlefield 6 Technical Issues board, including your DxDiag, crash dump files, and exact crash signature (e.g., error codes like c0000005 or STATUS_HEAP_CORRUPTION). This is likely a bug that requires waiting for a patch from the developers.

Fallback: Full uninstall and reinstall

1. Uninstall via the EA App. Open the EA App, go to My Library, right-click Battlefield 6, select Manage, and choose Uninstall, then confirm and wait for the process to finish.
2. Remove leftovers via Control Panel too. Press Windows + R, type appwiz.cpl, and press Enter, find Battlefield 6 in the list, right-click it and select Uninstall, then follow the on-screen instructions.
3. Delete leftover folders in your game install directory and Documents/Battlefield 6 before reinstalling to clear any corrupted cache or settings files.

Note: these steps are all Windows PC-specific. If you're on console, Secure Boot/BIOS steps do not apply — focus instead on storage, software updates, and reinstalling the game.