Crash and Black Screen Fixes#

Over the three years since release, Baldur’s Gate 3 has received multiple rounds of fixes from Hotfix #12 through the small update on September 29, 2026, and most known crashes are covered by a corresponding hotfix. Based on official and community records verified through October 15, 2026, this page separates crashes and black screens by the point at which they occur: identify the matching case first, then follow the relevant section step by step. Only three verified error codes are included; consult the official support page for all other errors. On PC, the game runs through Steam or GOG with Larian Studios’ own launcher, which offers a choice of Vulkan or DirectX rendering mode at startup. That choice determines the entry point for many fixes. The Xbox edition uses the Microsoft Store and Xbox App, and consoles do not offer this rendering-mode choice.

First, Identify Your Type of Crash#

Before troubleshooting, identify the stage at which the crash occurs and jump to the corresponding section. This is faster than trying every general fix in sequence; the table covers eight common situations.

The startup chain determines where to troubleshoot: Steam players configure launch options in the Steam client and change rendering mode in the Larian Launcher; GOG players enter through an offline installer or the Galaxy client; console players mainly depend on version updates and official troubleshooting advice. The sections below cover each case.

Crashes at Startup: Switch to DirectX and Clear Background Software#

Most startup crashes come from the rendering mode or background software. Launching in DirectX (DX11) mode and disabling graphics overlays and antivirus software are the two fixes with the highest success rates.

Step 1: Switch the Rendering Mode from Vulkan to DirectX#

Crashes when starting in Vulkan mode, frequent crashes to desktop, and freezes on the Larian logo are the most commonly recorded startup issues in the community. Both community and official guidance recommend switching to DirectX first:

1. Open the Larian Launcher and change the rendering mode from Vulkan to DirectX (DX11).
2. Steam players can also skip the launcher by setting the game’s Steam launch option to -d3d11, forcing DirectX.
3. NVIDIA graphics-card users can open the Control Panel and set the game’s Vulkan/OpenGL present method to Prefer native.
4. After applying these settings, run the launcher or the game executable as administrator and test again.

There is another community workaround for users still on Win7: find the game’s main executable and hold Shift while running bd3direct11.exe, the DirectX 11 executable, as administrator. If the game crashes after entering gameplay, prioritize DirectX rather than Vulkan here as well. This is a community record from November 2025, included for users of older systems.

Step 2: Remove Overlays and Security Software from the Background#

For the “crash on startup” issue, the official support page recommends closing unnecessary background programs before launch, including antivirus software, firewalls, graphics monitoring tools, and tuning-tool overlays. For this game, they mainly fall into three categories:

How to Fix the “Device Hung” Error (DXGI_ERROR_DEVICE_HUNG)#

These two error codes are usually triggered by outdated graphics drivers. Fully uninstall the old driver with Display Driver Uninstaller (DDU), perform a clean installation of the latest version, and reduce graphics load.

A troubleshooting record published by a community technical site in September 2023 and updated that December, consistent with Steam Community player reports, provides these three steps:

A note on error-code coverage: the official support page does not publish an error-code reference table. This page includes only three verified cases: device hung (DXGI_ERROR_DEVICE_HUNG), device removed (DXGI_ERROR_DEVICE_REMOVED), and the Failed to initialize Vulkan error covered in the next section. For other errors, troubleshoot by the issue categories on the official support page, such as startup crashes and in-game crashes.

How to Fix “Failed to initialize Vulkan”#

This error means the graphics card does not support Vulkan 1.3 or the runtime is missing. Check the minimum GPU threshold first, then update the driver and install the Vulkan runtime. If it still fails, switch to DirectX.

Follow this troubleshooting order compiled by the player community:

1. Check the GPU threshold: GTX 970, RX 480, or Arc A380 and above, with Vulkan 1.3 support required. If the hardware does not meet the threshold, launch directly in DirectX mode.
2. Update the driver: player Q&A recommendations specify NVIDIA 535 or later and AMD Adrenalin 23.5.1 or later.
3. Install the runtime: install or repair the Vulkan runtime, restart the system, and try again.

Scope note: the association between this error and version 4.1.1.689 comes from a player-community Q&A record rather than an official conclusion and is included only for reference. Official fix status is determined by hotfix announcements.

Frame-Rate Drop and Crash When Loading a Save: The March 2026 Issue#

The save-corruption issue seen on all platforms in March 2026, including frame-rate degradation until a crash and loading stuck at 83%, was fixed on all platforms by Hotfix #36 on March 26, 2026. Update first, then test again.

Two reminders: first, official channels do not directly record the hotfix number between the corrupted-save repair update and Hotfix #36, so this page makes no inference. Second, community video platforms compiled demonstrations for handling corrupted saves and loading stuck at 83%, which can serve as procedural references. If loading a save still causes frame-rate loss after updating to the latest version, go to the random-crashes section and check your mods.

Crashes in Specific Scenarios: Dialogue, Controllers, and Xbox Multiplayer#

Crashes when starting dialogue with Cazador and when a second controller activated split-screen were fixed by Hotfix #12. Crashes on Xbox when two clients joined simultaneously and when pressing trigger buttons were fixed by Hotfix #21.

Players still on an older version can remove all four scenario-specific crashes by updating to the current version. The Hotfix #21 announcement also includes a requirement relevant to every case on this page: uninstall all mods and reproduce the issue before reporting it to official support.

Random Crashes During Play: Check Mods, Then AMD Driver Timeouts#

The official support checklist for in-game crashes matches the startup-crash checklist, and hotfix announcements repeatedly emphasize uninstalling all mods before reproducing an issue. When AMD graphics cards repeatedly time out, switching to DirectX is recommended.

Mod Troubleshooting: The First Step Repeatedly Emphasized by Larian#

1. Disable all mods before launch and verify whether the unmodified game still crashes.
2. If the base game works normally, add mods back one at a time and test after each addition to identify the conflict.
3. When reporting an issue to Larian, state whether mods are in use; hotfix announcements repeatedly require testing again without mods before filing a report.
4. In multiplayer, every player must have the same mod list and load order to start. Mismatched mods can also cause crashes during a session.

AMD Graphics-Driver Timeouts and Freezes#

Player-community reports from August 2023, including a case of a 7900XTX driver timeout roughly once per day, indicate that Vulkan mode crashed more often than DirectX mode. For severe driver timeouts, switch to DirectX and test first; if the issue remains, troubleshoot hardware and power delivery. This is player-community guidance and is included only for reference.

Crash After Infinite Loading During the Prologue Cutscene#

An infinite loading screen followed by a crash during the cutscene is usually caused by insufficient memory. With 8GB of RAM, high graphics settings can easily exhaust memory during the cutscene. Lower quality and resolution beforehand, then restore the settings after the prologue.

The community-compiled diagnosis and fix are as follows:

1. Diagnosis: if infinite loading followed by a crash happens only during the prologue cutscene while the rest of the game works normally, memory pressure is the likely cause. The cutscene is most likely to exhaust memory with 8GB of RAM and high settings.
2. Fix: lower the graphics preset and resolution before the cutscene, get through the prologue, then restore your usual settings.
3. Retest: if it still crashes at lower settings, move to the five-step general black screen checklist and close background programs that consume memory.

These are general fixes; rely on official announcements for issues specific to Baldur’s Gate 3.

Five-Step Checklist for a Black Screen Stuck on the Logo or Loading Screen#

For a black screen stuck on the logo or loading screen, follow five steps: verify game files, update the graphics driver, switch to borderless windowed mode, back up and clear the configuration cache, then uninstall and re-add mods one at a time.

1. Verify game files: on Steam, open Properties and run “Verify integrity of game files.”
2. Update the graphics driver: old drivers commonly trigger both black screens and crashes, so update to the latest version first.
3. Change the display mode: switch from fullscreen to borderless windowed mode before entering the game; this often improves cases stuck on the logo.
4. Clear the configuration cache: back up and clear the configuration cache in the Larian Studios folder under the user directory. The full path is %LocalAppData%\Larian Studios\Baldur's Gate 3. Copy the entire folder before making changes, and be sure to preserve your saves.
5. Re-add mods one at a time: after uninstalling every mod and confirming that the game starts normally, add them back individually to identify the problematic mod.

These are general fixes; rely on official announcements for issues specific to Baldur’s Gate 3.

Check the Hotfix Timeline: Does the Issue Still Exist?#

Larian explicitly stated that Patch 8 in April 2025 was the final major patch and that only small hotfixes would follow. The latest version is the September 29, 2026 update; compare your issue with the table below to see whether a fix already exists.

How to use this table: confirm your current version on the main menu or platform page, then compare it with the entries above. If your symptom appears in a hotfix’s fix list, update and test again. If there is no matching entry, follow the relevant sections above. If the problem remains, report it through the official news page, Larian forums, or official Discord, including your version number, platform, and whether you use mods. Larian does not provide an error-code reference table, so error-related troubleshooting is limited to the three verified cases above and the fixes recorded in this table.

Related Guides#

• Updates — patch-cadence criteria and before-and-after update checks to use with this page’s hotfix timeline
• Frequently Asked Questions — questions about mechanics and rules; check here first for issues unrelated to crashes
• Controls and Settings — display modes and keybind settings, including the borderless-window option used in black screen troubleshooting
• Beginner’s Guide — a starting guide that helps new players avoid common early mistakes
• Tips and Tricks — practical tips to continue with after fixing the crash