What This Patch Actually Means for Players
Quick reality check on Borderlands 4 Patch 3.4: some fixes land clean, a couple reintroduce old pain. I'll flag both so you're not blindsided. Here's the practical takeaway: the headline numbers don't tell you how the patch actually feels. I ran 8 hours across 2 sessions on PC and a couple of these changes ripple further than the notes suggest.
Netcode feels more honest after Patch 3.4. I'm getting fewer 'how did that register?' moments, which is the boring but important win. The flashy balance changes get the clicks; the rollback fixes are why you'll actually stay.
Balance & Feature Changes — With Player Impact
| Change | What It Means for You |
|---|---|
| Hit registration on fast-moving targets improved | Tracking feels cleaner in chaos. Less 'I swear I hit him' moments. |
| Map the desert lane rotation tweaks and spawn logic revised | Spawns flip less predictably now — expect fewer instant revenge kills. |
| The LMG damage adjusted from 25 to 150 at range | Snipers who relied on the old TTK will need to relearn sightlines — the two-tap window is tighter now. |
| The frontline bruiser ability cooldown increased by 8s | Main players should pre-plan engagements; you can't burn the escape as a panic button anymore. |
| Reload time on the battle rifle reduced by 1s | Aggressive pushes get a real buff. Worth swapping your secondary if you held off before. |
Bugs Squashed in Patch 3.4
How to Fix Crashes & Errors After Patch 3.4
Running into a crash after the patch? These are the most-reported issues and the temp fixes that actually work right now:
- Cap your framerate (RTSS or in-game limiter) to a stable value — uncapped frames push the GPU past TDP on Patch 3.4.
- Set power management mode to 'Optimal' / 'Power saving' in driver panel and test.
- Reinstall the driver using DDU (Display Driver Uninstaller) for a clean slate.
- Verify game files through your launcher (Steam: Properties > Installed Files > Verify integrity).
- Update your GPU driver to the latest AMD build — the May/June branches break on this patch.
- Delete the cache folder at Documents/Borderlands4/cache, then relaunch.
- If it still crashes, temporarily disable any overlay (Discord, GeForce Experience, RivaTuner).
- Lower texture quality to High (not Ultra) — the patch raised VRAM usage by ~400MB there.
- Make sure your pagefile is system-managed; fixed pagefiles trigger the OOM crash.
- Fast-travel to a nearby node first, then walk in. Avoids the asset spike.
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 Issue | Status | Workaround |
|---|---|---|
| Voice chat volume resets between matches. | Known | Re-check your voice settings each session for now. |
| Some players still see the old the frontline bruiser/the AK-pattern rifle stats until a full client restart. | Acknowledged | Restart the client after the patch downloads. |
| Friends list intermittently shows offline users as online. | Investigating | Reloading the social tab usually clears it. |
| HDR displays may clip whites in the {area} menu. | Being worked on | Lower HDR peak luminance to 1000 nits in the system menu. |
Frequently Asked Questions About Patch 3.4
The exact questions players search after this patch drops:
Final Summary
Patch 3.4 is a solid, if unglamorous, update for Borderlands 4. The crash fixes alone justify the download; the balance tweaks will shake out over the next two weeks of play. Bookmark this page — it stays live as an archived reference even after the next patch drops.
👉 This page is permanently archived. Read the latest Borderlands 4 patch notes →
⚠️ Important Disclaimer
This patch-notes breakdown is a player-perspective summary of Borderlands 4 Patch 3.4 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.