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 fixThe shortest safe order for this issue:
- Remove overlays and GPU tuning utilities before testing the crash.
- Reduce texture quality to create VRAM headroom and disable frame generation for the baseline.
- 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.
[SystemSettings]
r.Streaming.PoolSize=6144
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.MaxTempMemoryAllowed=256
t.MaxFPS=120 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 completeKeep 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 answersWhy does Borderlands 4 crash only in co-op?
Does frame generation make crashes worse?
Crash & Startup
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.
Borderlands 4: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise Borderlands 4 on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Unreal Engine 5.
Borderlands 4: Shader Stutter, Frame Pacing & Unreal Engine 5 Config Tuning
A measured stutter-hunting routine for Borderlands 4: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Unreal Engine 5 settings file to edit.
Borderlands 4: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Borderlands 4 without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.