Player Take

What This Patch Actually Means for Players

Patch 3.1 for Borderlands 4 just went live and the community is split. I tested the changes across three sessions — here's the honest breakdown. Reading between the lines: the headline numbers don't tell you how the patch actually feels. I ran 9 hours across 3 sessions on PC and a couple of these changes ripple further than the notes suggest.

Performance-wise the patch is a net positive on my rig. Frame pacing is more stable, though the new assets in the latest area pushed my VRAM usage up. Budget-card players, heads up.

Advertisement
Key Changes

Balance & Feature Changes — With Player Impact

ChangeWhat It Means for You
The frontline bruiser ability cooldown increased by 6sMain players should pre-plan engagements; you can't burn the escape as a panic button anymore.
Reload time on the SMG reduced by 2sAggressive pushes get a real buff. Worth swapping your secondary if you held off before.
The frontline bruiser hitbox refinedLess getting shot around corners. The desync complaints should quiet down.
The sidearm damage adjusted from 10 to 80 at rangeSnipers who relied on the old TTK will need to relearn sightlines — the two-tap window is tighter now.
Bug Fixes

Bugs Squashed in Patch 3.1

🐛Corrected a UI freeze when scrolling the social menu on controllers.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Resolved a bug where party members loaded into different instances.
Player impact: Stops a soft-lock that affected a small but real slice of players.
🐛Fixed a bug where the equipped relic tooltips showed the wrong stat values.
Player impact: Quality-of-life win the community has wanted for weeks.
🐛Fixed a crash when opening the inventory immediately after a loading screen.
Player impact: Closes a loophole that was skewing leaderboards.
🐛Fixed subtitles overlapping during {scene} cutscenes.
Player impact: Removes a recurring frustration for endgame players.
🐛Fixed a memory spike that could cause a disconnect after long sessions.
Player impact: Closes a loophole that was skewing leaderboards.
Crash & Error Fixes

How to Fix Crashes & Errors After Patch 3.1

Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:

💥Blue screen / driver timeout (amdkmdag / nvlddmkm) mid-match
  1. Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 3.1.
  2. Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
  3. Reinstall the driver using DDU (Display Driver Uninstaller) for a clean slate.
Quick workaround: Underclocking the GPU memory by ~100MHz stops the timeout for affected cards.
💥Crash on entering the new zone or fast-traveling
  1. Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~500MB there.
  2. Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
  3. Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
Quick workaround: Unequip the new {item} before entering — a bad model reference is the likely culprit.
Advertisement
Known Issues

Known Issues Still Being Worked On

These problems are acknowledged but not yet fixed. Here's the status and a temp workaround for each:

Known IssueStatusWorkaround
Some players still see the old the assault operator/the shotgun stats until a full client restart.AcknowledgedRestart the client after the patch downloads.
Controller rumble stays on after disconnecting a pad.KnownReconnect and disconnect the controller again to reset it.
Cross-save may delay inventory sync by up to 25 minutes.InvestigatingWait a few minutes before assuming items are lost.
Server Maintenance

Downtime & Schedule

Scheduled: 2026-03-02 from 06:00 UTC for approximately 6 hours.

Details: Matchmaking disabled during the window. Borderlands 4 ranks will not decay for missed placement games during downtime.

Compensation: No compensation planned.

FAQ

Frequently Asked Questions About Patch 3.1

The exact questions players search after this patch drops:

AThe patch added denser the hub assets. Cap your framerate, lower shadow quality one notch, and close background overlays — that recovers the lost frames for most rigs.
ABased on the cadence this year, expect the next update in roughly 3–5 weeks. Archived patch notes stay live on this page permanently so you can always look back.
AA few. Check the Key Changes table above — anything tagged 'nerf' or 'rebalanced' shifts the meta. Nothing got gutted, but two popular setups lost some uptime.
AYes. Patch 3.1 is backward-compatible with saves from the previous version. Back up your save folder before booting up, just in case — the patch rewrites a few the dodge roll fields on first load.
AStart by verifying game files and updating your GPU driver — the Patch 3.1 build raised VRAM use, so dropping textures from Ultra to High fixes most splash and fast-travel crashes. The full step-by-step is in the Crash & Error Fixes section above.
Bottom Line

Final Summary

If you held off updating because of the early crash reports, Patch 3.1 is now safe to grab on most rigs. The fixes above cover the worst offenders. See you in the next patch notes — this page stays permanent.

👉 This page is permanently archived. Read the latest Borderlands 4 patch notes →

More Borderlands 4 Patches

Other Borderlands 4 Patch Notes

⚠️ Important Disclaimer

This patch-notes breakdown is a player-perspective summary of Borderlands 4 Patch 3.1 for educational purposes only. GameFixPro is not affiliated with, endorsed by, or sponsored by Borderlands 4's developer or publisher. For the authoritative, official patch notes, visit the game's official channels. All trademarks belong to their respective owners. Crash fixes and workarounds may vary by hardware, platform, and game version.