How to Fix Baldur's Gate 3 Crashing After Hotfix 34

There is a specific kind of dread that hits when you see a “Hotfix” notification on Steam, click update, and then watch your game crash to desktop (CTD) during a critical cinematic or—worst of all—right as you’re loading an Honour Mode save. I’ve been there. You just want to get back to your camp and figure out how to deal with the Absolute, but instead, you’re staring at a frozen screen and a “Baldur’s Gate 3 has stopped working” dialogue box.

Hotfix 34 was designed to tighten things up, particularly for Xbox and Steam Deck players, but as with any major tweak to a game as complex as BG3, some of us found ourselves in a loop of instability. If you’re seeing crashes after the latest update, you aren’t alone.

The Culprits: What Hotfix 34 Actually Changed #

To fix a crash, you first have to understand what the game was doing when it broke. Hotfix 34 wasn’t just a “bug fix” update; it brought some architectural changes and very specific stability patches.

According to the official Larian Studios patch notes, the team targeted several high-impact crash points:

Combat Status Effects: Specifically, the “Slow” condition and the “Find Familiar” spell (especially when used on Scratch or Boo) were causing hard crashes.
Honour Mode Loading: There were significant issues with saves hanging at 33% or 83% loading or crashing entirely when returning to the main menu.
Steam Deck Architecture: The biggest shift was the introduction of a native Steam Deck build, moving away from purely relying on Proton.
Graphics Tech: The addition of Intel XeSS (Super Sampling) for DX11 and Vulkan.

If you’re still crashing in these specific areas, it means the fix didn’t “take” or something else in your system is conflicting with these new changes.

Step 1: The “Golden Rule” — Verify Integrity of Game Files #

I can’t stress this enough: if you update BG3 and it starts crashing, Verify your files first.

Larian’s updates often overwrite large chunks of data. If a single packet is dropped or a file is corrupted during the download, the game will crash the moment it tries to call that specific asset. I’ve seen this happen repeatedly where a “corrupt” file makes the game think it’s missing a texture or a script, leading to an instant CTD.

How to do it on Steam:

Right-click Baldur’s Gate 3 in your Library.
Select Properties > Installed Files.
Click Verify integrity of game files.

Wait for it to finish. Steam will likely find 1 or 2 files that need re-downloading. In my experience, this solves about 60% of post-patch crashes.

Step 2: The Mod Purge (and Update) #

If you use the BG3 Mod Manager or Nexus Mods, Hotfix 34 is a potential landmine. Most mods for Baldur’s Gate 3 hook into the game’s executable or specific script files. When Larian updates the game, those hooks often break.

Even if a mod “should” be compatible, a version mismatch can cause the game to crash during loading screens or when opening the inventory.

My recommended workflow for modded games after a hotfix:

Backup your saves. Always.
Disable all mods. Launch the game “vanilla” to see if the crash persists.
Check for updates. Go back to Nexus and check if your core mods (like ImprovedUI or Mod Fixer) have been updated for Hotfix 34.
Re-enable one by one. If the game is stable vanilla, enable your mods in small batches until you find the one causing the crash.

Step 3: Tackling the Graphics API (Vulkan vs. DX11) #

Hotfix 34 introduced Intel XeSS and tweaked how the game handles rendering. Sometimes, the update can leave your graphics settings in a “limbo” state where your current API is no longer the most stable for your hardware.

If you’re crashing during combat or cinematics:

Switch your API. If you’re using Vulkan, try launching with DX11, or vice versa. Vulkan generally offers better performance on some systems but can be more prone to crashes after an update.
Toggle XeSS. If you have an Intel card (or are using the new XeSS support on other cards), try disabling it in the options menu. New scaling tech is great, but it’s often the first thing to cause a crash in the first 48 hours of a patch.
Update GPU Drivers. This sounds like a cliché, but Larian’s updates often coincide with driver optimizations. Check NVIDIA GeForce Experience or AMD Software to ensure you’re on the latest version.

Step 4: Steam Deck Specifics — Native vs. Proton #

If you’re on a Steam Deck, Hotfix 34 is a game-changer because of the Native build. However, this transition is where most of the current Deck crashes are happening.

The game now defaults to native graphics settings. If you had a very specific Proton configuration (like GE-Proton) that worked for you, the switch to native might be causing conflicts.

If the native build is crashing:

Go to the game’s Properties in Steam.
Select Compatibility.
Check “Force the use of a specific Steam Play compatibility tool”.
Select Proton Experimental or your preferred GE-Proton version.

This forces the game back into the Proton layer, which can be a lifesaver if the native build isn’t playing nice with your specific save file.

When to Report vs. When to Wait #

Still crashing? Here is how to decide your next move.

Report it immediately if:

You are in an Honour Mode run and the game crashes during a save/load. This is a critical failure that can kill a run.
The game crashes on startup every single time, regardless of API or mod status.
You’ve verified files and updated drivers, but the crash happens at the exact same spot in the story.

Wait a few days if:

The crash is intermittent (happens once every 4 hours).
You are using a complex mod list (wait for mod authors to catch up).
You’re seeing “Performance Overlay” issues on Steam Deck (as Steam has already released Beta updates to address this).

To report a bug, use the Larian Support Portal. Be specific: tell them your GPU, whether you’re using mods, and exactly what was happening in-game (e.g., “Crashed while casting Find Familiar on Boo in Act 2”).

Getting back into Faerûn shouldn’t feel like a puzzle, but with a game this size, a little bit of manual troubleshooting is often the only way to clear the path. Now, go get that tadpole sorted.