Crash & Startup / Borderlands 4 / Unreal Engine 5

Borderlands 4: Fixing UE5 GPU Crashes and Co-op Desync

A practical UE5 crash and co-op stability path for Borderlands 4, from VRAM pressure to render-thread hooks.

Official Steam Store header artwork for Borderlands 4.

Borderlands 4 splits its problems into two broad types: a local UE5 GPU crash, and a co-op session that desyncs because one client is falling behind. The evidence is different.

Fixing UE5 GPU Crashes and Co-op Desync

Verified field fix

The shortest safe order for this issue:

  1. Remove overlays and GPU tuning utilities before testing the crash.
  2. Reduce texture quality to create VRAM headroom and disable frame generation for the baseline.
  3. Verify game files and test solo before diagnosing co-op desync.

Stabilise the local client first

A device-removal crash is not repaired by a co-op relaunch. Remove render hooks, reset the graphics profile, and test solo at a lower VRAM budget. If the client survives, restore one quality setting at a time and watch memory pressure rather than average FPS.

%USERPROFILE%/Documents/My Games/Borderlands 4/Saved/Config/Windows/Engine.ini
[SystemSettings]
r.Streaming.PoolSize=6144
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.MaxTempMemoryAllowed=256
t.MaxFPS=120
Back up the original file. In-game settings may override these values; verify before claiming a win.

Co-op needs headroom

A client that is already at its VRAM or CPU limit has less room for network updates and ability effects. Cap frame rate below the busiest combat average and avoid running two capture tools. If the desync persists only on one host, treat it as a networking issue rather than a graphics issue.

Field notes before you change the build

A crash report for Borderlands 4 is only useful if it can be repeated. Record the last visible frame, the exact game build, the GPU driver, and whether the failure happens before or after the anti-cheat splash. “It crashed” is a category, not a reproduction.

If the client fails again after a clean launch, test a second save or a fresh profile before changing the Unreal Engine 5 configuration. That separates a local game-state problem from a client, driver, or protected-launch problem.

  • Do not delete the entire config, save, or game folder before making a backup.
  • Do not reinstall Windows for a single-title startup failure.
  • Do not stack launcher flags and driver rollbacks in the same test run.

Check it before you keep it

Test a solo session and a co-op session separately

0 / 5 complete

Keep the rollback boring

A known-good local profile and one current log are more valuable than another speculative repair pack. If the fix works, save the exact steps with the patch number.

The line to keep

Solo stability first, co-op second. Keep the graphics baseline conservative and let the network evidence stay separate.

Did this fix work on Patch 1.0.6 — co-op stability and shader fixes?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against 1.0.6 — co-op stability and shader fixes. Votes are local-only telemetry.

Borderlands 4: bench questions

2 answers
Why does Borderlands 4 crash only in co-op?
Co-op adds network state, more ability effects, and another player’s build to the scene. It raises load; it does not automatically identify the faulty component.
Does frame generation make crashes worse?
It increases the working set and the complexity of the display path. Disable it for the baseline, then reintroduce it only after the client is stable.
Filed under

Crash & Startup

Patch tested: 1.0.6 — co-op stability and shader fixes

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.