Detailed analysis
Baldur's Gate 3 crashed with a "Vulkan device lost" error, probably mid-combat with no recent save. This means your GPU's Vulkan rendering context crashed. The fastest fix: switch to DirectX 11 in the BG3 launcher settings. That alone stops the crash for most people. If you want to keep using Vulkan (it does perform better), read on for the specific fixes.
What's actually happening
Baldur's Gate 3 defaults to the Vulkan graphics API for rendering. Vulkan is lower-level than DirectX, which means it can be faster but it's also less forgiving of driver issues, GPU instability, and memory problems. When the Vulkan driver loses communication with your GPU — due to a driver crash, timeout, VRAM exhaustion, or hardware instability — the entire rendering pipeline dies instantly. There's no graceful recovery. The game shows you a "Vulkan device lost" error and closes.
BG3 is particularly prone to this because of how graphically demanding it is, especially in Act 3 (Baldur's Gate city). The dense geometry, complex lighting, and particle effects during large combat encounters with multiple spell effects push both VRAM and GPU compute harder than most of the game's earlier acts. It's common for players to get through Act 1 and Act 2 with zero crashes, then start getting Vulkan device lost errors every 30 minutes in Act
3.
The most common causes (in order of likelihood)
Vulkan driver instability — Both NVIDIA and AMD have had Vulkan-specific bugs in various driver versions. A driver that works perfectly with DirectX 11 and 12 can still have Vulkan issues. This is the most common cause and a driver update (or switch to DX11) fixes it immediately.
VRAM exhaustion — BG3 at Ultra settings with high-resolution textures can use 8-10GB of VRAM in Act 3 scenes. If your GPU has 6GB or 8GB of VRAM, the game can silently exceed it during complex moments. Vulkan handles VRAM oversubscription poorly compared to DX11 — instead of gracefully lowering quality, it crashes.
GPU overheating — BG3 sustains heavy GPU load for long periods, especially during extended combat encounters. If your GPU is hitting 85-90C+, thermal throttling can trigger a Vulkan timeout where the driver thinks the GPU has stopped responding.
Unstable GPU overclock — Any overclock, including factory overclocks from MSI, ASUS, or Gigabyte, can become unstable under the specific workload BG3 puts on Vulkan. An overclock that's stable in other games might not be stable here because Vulkan exercises the GPU differently.
Corrupted shader cache — BG3 pre-compiles Vulkan shaders and caches them on disk. If these cached shaders become corrupted (from a crash, power outage, or driver update), the GPU tries to execute invalid shader programs and the Vulkan device is lost.
How to fix it
The fastest solution is switching from Vulkan to DirectX
- Open the BG3 launcher (the window that appears before the game starts), click the gear icon or settings button, and change the renderer from Vulkan to DirectX
- Launch the game and test. DX11 is more stable and handles driver issues, VRAM pressure, and GPU instability more gracefully than Vulkan. You might see a small FPS decrease (typically 5-10%), but you won't crash. For most players, this is the right trade-off.
If you want to keep using Vulkan for better performance, start by updating your GPU driver. Go to nvidia.com or amd.com and download the latest driver. For the best results, do a clean install: download DDU (Display Driver Uninstaller) from guru3d.com, boot into Safe Mode (hold Shift while clicking Restart > Troubleshoot > Startup Settings > Safe Mode), run DDU to completely remove your GPU driver, restart, and install the fresh driver immediately before Windows Update installs its own. NVIDIA drivers 551.x and later have significant Vulkan stability improvements relevant to BG3.
Delete the BG3 shader cache. Navigate to %localappdata%\Larian Studios\Baldur's Gate 3\ and look for folders named ShaderCache, PipelineCache, or similar. Delete them entirely. The game will recompile all shaders on next launch, which takes a few minutes during the loading screen but gives you a clean cache matched to your current driver version. Expect some brief stuttering during the first play session after clearing the cache as new shaders compile.
Lower graphics settings to reduce VRAM pressure. Open BG3's graphics settings and drop Texture Quality from Ultra to High — this single change can save 2-3GB of VRAM. Set Shadow Quality to Medium. Turn off Model Quality's highest setting. If you're using DLSS or FSR with Frame Generation enabled, disable Frame Generation — it adds to VRAM usage and has been linked to Vulkan instability in BG3 specifically.
Check your GPU temperature during gameplay. Download HWiNFO64 (free), run it in sensors-only mode, and leave it running while you play BG3. After a crash (or after 30+ minutes of stable play), check the GPU Temperature maximum. NVIDIA cards start throttling at 83C and some models shut down at 92C. AMD cards throttle at 90-110C junction temperature. If your GPU is consistently hitting throttle temperatures during BG3, clean your GPU fans, reapply thermal paste, or improve your case airflow.
Remove any GPU overclock. Open MSI Afterburner (or whatever overclocking utility you use) and reset all sliders to stock. If you don't have overclocking software installed but your GPU is a factory-overclocked model, you can try underclocking the core clock by -50MHz in Afterburner — this adds stability margin and the FPS impact is negligible.
Increase your Windows pagefile. Right-click This PC > Properties > Advanced system settings > Performance > Settings > Advanced > Virtual Memory > Change. Set it to at least 16GB on your fastest SSD. BG3's memory usage is aggressive, and an insufficient pagefile can compound Vulkan memory allocation failures.
Is this a hardware or software problem?
If switching to DX11 stops the crashing, it's a software/driver issue with Vulkan. Your GPU hardware is fine. If the game still crashes on DX11, you might have a deeper problem — GPU overheating, failing VRAM, or a power delivery issue. Test GPU hardware by running FurMark or Unigine Heaven at stock clocks for 30 minutes. If those crash or show artifacts, the GPU itself needs attention. Run OCCT's VRAM test to check for memory errors. If Vulkan crashes happen across multiple different games (not just BG3), that points more toward a driver or hardware issue rather than a BG3-specific problem. If you're not sure, Crashless can check your drivers, temps, VRAM, and 400+ known patterns automatically — just use the chat above.
Games commonly affected
Vulkan device lost errors also appear in other Vulkan-based games including Red Dead Redemption 2 (which also supports Vulkan), Doom Eternal, various emulators (RPCS3, Yuzu/Ryujinx), and Source 2 games like Dota 2 and Counter-Strike 2 when running in Vulkan mode. The driver update and shader cache fixes from this guide apply to all of them.
Frequently asked questions
Q: I switched to DX11 and the crash stopped, but my FPS is lower. Is there a way to make Vulkan stable?
A: Yes — clean driver install, fresh shader cache, and lowered VRAM-heavy settings (textures, shadows) often stabilize Vulkan. The performance difference between Vulkan and DX11 in BG3 is typically 5-10%, so it's worth trying to get Vulkan working if performance matters to you. But if Vulkan keeps crashing even after all the fixes, just use DX11 and enjoy a stable game.
Q: The crash only happens in Act
3. Acts 1 and 2 were fine on Vulkan. What changed?
A: Act 3 (Baldur's Gate city) is dramatically more GPU-intensive than earlier acts. The city has dense geometry, more NPCs, complex lighting, and frequent combat encounters with many spell effects. Your GPU was within safe margins in Acts 1-2 but Act 3 pushes it past the threshold. Lower your settings for Act 3 or switch to DX11 for that section.
Q: Does this crash corrupt my save files?
A: BG3 save files are generally safe from Vulkan crashes because the game writes saves to disk separately from the rendering pipeline. However, if the crash happens during an autosave or quicksave, that specific save could be corrupted. Always keep multiple save slots. BG3's quicksave (F5) is your best friend — use it before every fight and after every dialogue.