The borderlands 4 crash on startup symptom hits hardest in the first 10 seconds: you double-click, the splash flickers, and the game silently dies before the Gearbox logo. We rechecked this guide against the Version 1.8 baseline, and the cause is still almost always one of five things — Easy Anti-Cheat handshake failure, a missing redist, a DX12 swapchain conflict, an overlay hook, or a corrupt Saved folder. None of these need a reinstall. Work through the list in order and you will catch it.

First 90-second triage

Before changing files, split the crash into the right bucket:

  • Splash appears, then closes: start with Easy Anti-Cheat repair, then runtimes.
  • Nothing visible happens: check Steam launch state, overlays, and Windows Event Viewer.
  • Black screen before menu: treat it as a DX12 or GPU selection problem.
  • Crash after changing graphics settings: reset the Saved\Config folder and let settings regenerate.

Keep one clean test after each change. Launch once, wait until the main menu or failure, then write down what changed. Changing three things at once makes the crash harder to isolate.

Why this happens

Borderlands 4 uses Unreal Engine 5.4 in DX12-only mode plus Easy Anti-Cheat for matchmaking. At startup the launcher chains four processes: Steam handshake, EAC service init, UE5 PreInit, then the DX12 swapchain. Any one of those failing produces a silent borderlands 4 crash on startup with no visible error.

The most common culprits we see in WinEvent logs are EAC service stuck in a half-installed state from previous Gearbox titles, missing or mismatched VC++ runtimes (UE5 needs 14.40 or newer), and overlay DLLs hooking into D3D12 too early. On laptops with hybrid GPUs the swapchain can also try to bind to the iGPU, which the DX12-only renderer rejects.

5 fixes ranked by likely effectiveness

1. Repair Easy Anti-Cheat from the install folder

This rebuilds the EAC service and re-registers the kernel driver. We see this clear about 40 percent of all reports.

cd "C:\Program Files (x86)\Steam\steamapps\common\Borderlands 4\EasyAntiCheat"
.\EasyAntiCheat_EOS_Setup.exe

Click “Repair Service” and accept the UAC prompt. Reboot. Skip this fix if you have never installed any other EAC game — fix 2 is more likely.

2. Install the current VC++ and DirectX runtimes

UE5.4 builds against MSVC 14.40 and require the matching runtime.

winget install Microsoft.VCRedist.2015+.x64
winget install Microsoft.DirectX

If winget is missing, grab the redists directly from Microsoft’s download center. Reboot after install. Skip if your machine is fresh from a Windows 11 24H2 update — those ship recent runtimes.

3. Kill every overlay before launch

Overlays inject DLLs into the game process and any one of them can crash the DX12 swapchain. Disable them all, confirm a clean launch, then re-enable one at a time.

Steam: Settings -> In-Game -> Disable Steam Overlay
Discord: Settings -> Game Overlay -> Disable
NVIDIA: GeForce Experience -> Settings -> Disable In-Game Overlay
RTSS / MSI Afterburner: Quit from system tray

If you use third-party FPS counters or capture tools (OBS Game Capture hook, ReShade), exit those too. Skip this only if you have already tested with overlays off.

4. Force the discrete GPU on a laptop

If you have a hybrid laptop and BL4 dies before the logo, Windows is binding to the iGPU.

NVIDIA Optimus:

NVIDIA Control Panel -> Manage 3D Settings -> Program Settings
  Add Borderlands 4 -> Preferred graphics processor: High-performance NVIDIA processor

AMD SmartShift / hybrid:

Adrenalin -> Gaming -> Borderlands 4 -> Graphics -> GPU Workload: Graphics
Windows Settings -> Display -> Graphics -> Borderlands 4 -> High performance

Skip if you are on a desktop — there is only one GPU to pick.

5. Delete the Saved\Config folder

A corrupt GameUserSettings.ini from a beta or earlier patch can crash the engine before the menu. This is safe — the game regenerates it on next launch.

Rename-Item "$env:LOCALAPPDATA\Oak2\Saved\Config" "Config_backup"

Launch the game. If it loads, your old settings were the cause and you can delete the backup. Skip this if you have never opened BL4 before — there is nothing to corrupt yet.

If all five fixes fail

At that point you need evidence rather than more random changes:

  1. Open %LOCALAPPDATA%\Oak2\Saved\Logs\ and copy the last 30 lines of the newest log.
  2. Open Event Viewer -> Windows Logs -> Application and look for the failed module name.
  3. If the failed module is nvwgf2umx.dll or amdxx64.dll, update or clean-install the GPU driver.
  4. If the failed module is EasyAntiCheat_EOS.sys, rerun fix 1 and reboot before testing again.
  5. If the log ends during shader setup, switch to the compiling shaders fix instead.

Did this guide fix your issue?

FAQ

  • Why does Borderlands 4 crash with no error message? UE5 fatal errors before PreInit do not write a CrashReportClient dialog. Check %LOCALAPPDATA%\Oak2\Saved\Logs\ for the latest .log file — the last 30 lines almost always name the failed module.
  • Do I need to verify Steam files first? Only if %LOCALAPPDATA%\Oak2\Saved\Logs\ shows missing assets. Otherwise the borderlands 4 crash on startup is environmental, not file-related.
  • Will reinstalling Windows fix it? It will, but it is overkill. Fix 1 plus fix 2 resolves over 70 percent of reports we have seen.
  • Is the Steam beta client safer? No. The 2026-04 stable client is the one BL4 is tested against. Opt out of beta if you are still crashing.
  • Should I delete the whole Oak2 folder? No. Rename only Saved\Config first so you keep logs, shader cache evidence, screenshots, and save-adjacent data intact.