Why Does Borderlands 3 Keep Crashing? | Stop The Loop

When Borderlands 3 drops to desktop, freezes at launch, or throws an OakGame error, the cause is usually local: the PC, console cache, launcher files, or one setting that doesn’t like your hardware. The cleanest fix is to change one thing, test for ten minutes, then move to the next suspect.

Start with the crash pattern. A crash before the main menu points to DirectX, launcher files, overlays, or permissions. A crash after loading a character points to graphics load, corrupted local data, mods, or a save sync conflict. A crash after long play usually points to heat, RAM pressure, or an unstable overclock.

Borderlands 3 Crashing Fixes That Match Each Symptom

Don’t reinstall the game as the first move. Reinstalling can help, but it takes longer than the checks that fix most cases. Use this order instead:

• Restart the device fully, not sleep or resume.
• Turn off overlays from Steam, Epic, Discord, Xbox Game Bar, and GPU apps.
• Verify the game files in the launcher.
• Switch from DirectX 12 to DirectX 11 if the game crashes on launch.
• Update GPU drivers, then restart again.
• Lower texture streaming, volumetric fog, and screen-space reflections.
• Disable overclocks or undervolts while testing.
• Back up saves before deleting config files or turning off cloud sync.

Why DirectX 12 Causes Trouble

Borderlands 3 can run in DirectX 11 or DirectX 12 on PC. DirectX 12 may load slowly, stutter, or crash on some systems, even when the hardware is good enough. If the game won’t open, edit the graphics config file and set the preferred graphics API to DirectX 11.

On Windows, the usual file path is Documents\My Games\Borderlands 3\Saved\Config\WindowsNoEditor\GameUserSettings.ini. Open it with Notepad, find PreferredGraphicsAPI=DX12, change it to PreferredGraphicsAPI=DX11, save, then relaunch.

Check The Launcher Before Reinstalling

Corrupted local files can make Borderlands 3 crash after an update, a forced shutdown, or a failed download. Steam says its file check can repair missing or damaged content, so use Steam file verification before wiping the whole install.

If you own the game through Epic, the same idea applies. Epic says its verify feature checks local files and replaces files that don’t match, while saved data remains untouched. Run Epic Games file verification, restart the launcher, then test the same crash point again.

What The OakGame Error Usually Means

OakGame is the internal Unreal Engine project name used by Borderlands 3, so an OakGame crash does not name one exact culprit. Treat it as a crash wrapper. Read what happened right before it: launch, map load, firefight, co-op join, or exit to desktop. That timing narrows the test list.

If the error mentions “fatal error,” start with GPU driver, DirectX, overlays, and config reset. If it mentions access violation, test RAM stability, background apps, mods, and corrupted files. The wording is less useful than the repeatable trigger, so write the trigger down before changing more settings.

Run tests from the same save, same map, and same launcher each time. Mixed test conditions can hide the real cause and make a clean fix look random.

Crash Pattern	Likely Cause	Best First Fix
Crash before menu	DirectX 12, overlay, bad config	Set DirectX 11, disable overlays, reset config
Crash on character load	Save sync conflict or damaged local data	Back up saves, test with cloud sync off
Crash after update	Missing or mismatched game files	Verify files in Steam or Epic
Crash during fights	GPU load spike or driver fault	Update drivers, cap frames, lower effects
Crash after long sessions	Heat, RAM pressure, unstable overclock	Check temperatures, remove overclocks
Crash with mods	Broken mod, outdated script, file mismatch	Remove mods, verify files, test clean
Crash on console resume	Stale cache or suspended game state	Fully power down, then relaunch
Crash in co-op	Network hiccup, crossplay, host mismatch	Test solo, then test with a different host

Clean Up The PC Without Breaking Saves

2K’s own 2K PC troubleshooting steps point to the basics for crashes and freezes: system requirements, cache, reinstalling, graphics drivers, background programs, Windows updates, and diagnostic files. That order is sensible because each step removes a common failure point.

Before deleting anything, copy your save folder to a safe place. Borderlands 3 saves often sit in Documents\My Games\Borderlands 3\Saved\SaveGames. Copy the whole folder, then change settings or cloud sync. If a save conflict caused the crash, you’ll want a clean backup before the launcher tries to overwrite it.

Reset Settings The Safe Way

If the game opens, use the menu and change one graphics setting at a time. If it won’t open, rename the config folder instead of deleting it. Windows will build fresh settings at the next launch, and you can restore the old folder if needed.

A safe test looks like this: rename WindowsNoEditor to WindowsNoEditor-old, start the game, and let new files generate. If the crash stops, the old settings were part of the problem. Move only needed binds or settings back later.

Setting	Why It Can Crash	Safer Test Value
Graphics API	DirectX 12 can fail at boot	DirectX 11
Frame rate	Uncapped frames raise heat and load spikes	60, 90, or 120 FPS cap
Texture streaming	High VRAM use can overflow weaker cards	Medium
Volumetric fog	Heavy GPU effect during fights	Low or off
Screen-space reflections	Extra GPU load in busy areas	Low
Overlays	Hooks can clash with the game window	Off during testing

Console Crashes Need A Different Reset

On PlayStation or Xbox, you can’t edit DirectX files, so the fix list changes. Start with a full power cycle. Close the game, shut the console down fully, unplug it for a short wait, then start again. This clears stale session data better than suspend mode.

Next, check storage. Borderlands 3 is large, and weak free space can make updates messy. Leave extra room, run the game from internal storage when possible, and avoid playing while another large download is writing to the same drive.

When Co-Op Is The Trigger

If crashes only happen in co-op, test solo in the same map with the same character. If solo works, try a new host, turn crossplay off for one test, and remove network-heavy downloads from the house while playing. This separates a game crash from a connection drop that feels like one.

What To Do If Nothing Works

If every basic fix fails, collect clean proof before sending a report. Write down the platform, launcher, GPU, driver version, crash message, map, character, and the exact action that causes the crash. A short video of the crash point helps too.

For a last local test, remove mods, restore stock files, verify again, and launch with no overlays. Then test a new character for a few minutes. If the new character works but the old one crashes, your save or build state is the lead suspect. If both crash, the system or install is still the better target.

Crash-Fix Order To Save Time

1. Restart the device fully.
2. Disable overlays and recording tools.
3. Verify files in the launcher.
4. Switch to DirectX 11 on PC.
5. Update GPU drivers and Windows.
6. Reset config files after backing up saves.
7. Lower GPU-heavy settings and cap frames.
8. Test without mods, cloud sync, or overclocks.

Most Borderlands 3 crashing comes down to a small set of repeat offenders. Treat the crash like a pattern, not a mystery. Match the symptom, test one fix, and keep the change only if the game stays stable.