Baldur's Gate 3: Crash on Launch - Resolution Diagnosis

⚠️ SAFETY WARNING. Opening the PC and handling internal components (such as GPUs and motherboards) exposes you to the risk of electrostatic discharge (ESD) which can permanently damage printed circuit boards (PCBs). Never attempt to open or repair the inside of the power supply unit (PSU) due to the presence of high-voltage residual capacitors. ReeFix provides this diagnostic report EXCLUSIVELY for educational, informational, or study purposes.

REAL CASE

During the analysis of a medium-to-high-end desktop system, the game Baldur's Gate 3 systematically crashed on launch. With the Vulkan API, the crash was immediate (Crash to Desktop), while with DirectX 11, a total freeze occurred followed by a video driver recovery (TDR event).

The diagnosis revealed a dual concomitant cause: the corruption of Pipeline State Objects (PSO) in the shader cache and an active conflict with the Discord overlay, which was attempting to inject code into an unprotected low-level graphics pipeline.

GENERAL PATTERN

The crash on launch of Baldur's Gate 3 (based on Divinity Engine 4.0) is almost always attributable to an initialization conflict between the graphics libraries (DirectX 11 or Vulkan) and the operating system.

| Graphics API | Main Symptom | Underlying Cause | Error Tolerance | | :--- | :--- | :--- | :--- | | Vulkan | Immediate crash to desktop (CTD) | Shader corruption or memory allocation violation | Very low (no protective buffer) | | DirectX 11 | Temporary total freeze or TDR event | GPU timeout (>2 seconds) or electrical instability | Medium (managed by the Windows driver) |

Vulkan, operating at a low level, lacks the protective "buffers" of the driver: if it detects a memory allocation error or a corrupted shader file, it instantly terminates the process (bg3.exe). DirectX 11 is more tolerant but is subject to TDR (Timeout Detection and Recovery) events if the GPU does not respond within 2 seconds due to overloads or electrical instability.

Analysis of Causes and Probability

1. Shader Cache Corruption or Driver Conflict — 43% (High)
   • Indicators: The crash occurs during initial loading (0% - 100%) or immediately after selecting the API in the launcher.
2. Interference from Third-Party Overlays (Hooking Conflict) — 27% (Medium)
   • Indicators: The game starts for an instant in the background but closes as soon as the window becomes active.
3. Electrical or Thermal Instability of the GPU (Transient Spikes) — 18% (Low)
   • Indicators: The PC completely restarts or shows a black screen with fans at maximum speed when 3D rendering starts.
4. Configuration File Corruption or Write Permissions — 12% (Residual)
   • Indicators: The Larian launcher reports synchronization errors or fails to write to the user profile folder.

WHAT TO DO NOW

Quick Checks (DIY)

• Bypass the Launcher: Access the game's installation folder, enter bin, and run directly as administrator either bg3_dx11.exe (for DirectX 11) or bg3.exe (for Vulkan).
• Clear Graphics Cache: Clear the DirectX shader cache using the Windows Disk Cleanup tool and remove temporary GPU files in AppData\Local\NVIDIA or AppData\Local\AMD.
• Disable Overlays: Completely close GeForce Experience, Discord, MSI Afterburner, and Steam Overlay before launching the game.

Common Mistakes to Avoid

Uninstalling and reinstalling the entire game (over 120 GB) is often useless: corrupted configuration files and the shader cache reside in the user profile (AppData) and are not removed with a standard uninstallation.

Tools and Spare Parts for Hardware Diagnostics

If crashes persist and show symptoms of electrical or thermal instability under load, physical component intervention may be required:

• Samsung 990 Pro NVMe SSD: Recommended to eliminate bottlenecks and micro-stutters during asset loading and shader compilation.
• Corsair RM850x Power Supply: Necessary if the current power supply cannot tolerate the GPU's transient load spikes when the graphics engine starts.

If you experience a sudden PC shutdown under load with this model, it could be the activation of internal protection due to transient spikes from the video card. Many users resolve this simply by balancing dedicated PCIe cables instead of using daisy-chained split connectors.

• Arctic MX-6 Thermal Paste: Essential to restore operating temperatures if the GPU enters instant thermal protection.
• Can of compressed air: For quick cleaning of the video card's radiators and fans.

Handoff Report for the Technician

"The system exhibits Crash to Desktop (CTD) on launch of Baldur's Gate 3. Under Vulkan, an immediate process termination is recorded (potential memory access violation or failure to allocate descriptors). Under DX11, a TDR event (Event ID 4101, display driver source) occurs during initial loading. A deep driver clean with DDU in Safe Mode, shader cache purge, and verification of the power supply's +12V rail stability during GPU load transients is requested."

Operational decision: If bypassing the launcher and clearing the shader cache resolves the crash -> software issue resolved at zero cost; if the PC continues to restart or shuts down -> contact a technician to test the power supply or replace the GPU thermal paste.