DX11 feature level 10.0 is required to run the engine (BG3 fix)
Baldur's Gate 3 crashes on launch with this DX11 error. It means your GPU can't handle DirectX 11 properly — here's the real fix.
You hit Play in the Larian launcher, the screen goes black for a second, and then you're back at the desktop with a dialog box that says "DX11 feature level 10.0 is required to run the engine". This usually happens on PCs that ran the game fine a year ago, or on laptops with dual GPUs (Intel integrated + NVIDIA/AMD dedicated). The trigger is almost always a Windows update or a graphics driver update that resets the default graphics adapter.
What's actually happening here is that the game's engine—Baldur's Gate 3 uses DirectX 11 by default—checks what your GPU supports at launch. Feature level 10.0 means your GPU must support Shader Model 4.0 and a few other DX11-specific capabilities. Most GPUs from 2010 onward (NVIDIA GeForce 400 series, AMD Radeon HD 5000 series) support this. But if the game picks your Intel integrated graphics instead of your dedicated GPU, and that integrated chip is too old (say, Intel HD 3000 or older), you get this error. The game literally can't initialize a DX11 device on that adapter.
The real fix isn't reinstalling the game or updating DirectX — Windows Update already has that covered. It's forcing the game to use the right GPU.
Fix: Force Baldur's Gate 3 to use your dedicated GPU
Step 1 — Check your GPU in Windows
Open Device Manager (Win + X, then select it). Expand "Display adapters." You'll see two entries if you have a dual-GPU laptop: one Intel (or AMD integrated) and one NVIDIA or AMD Radeon. If you only see one, you're likely on a desktop with a single GPU, and the problem is different — skip to Step 4.
Step 2 — Set the high-performance GPU in Graphics Settings
Go to Settings > System > Display > Graphics (Windows 10) or Settings > System > Display > Graphics (Windows 11). Click Browse and navigate to your Baldur's Gate 3 install folder — typically C:\Program Files (x86)\Steam\steamapps\common\Baldurs Gate 3\bin. Select bg3.exe (not the launcher). Then click Options and pick High performance. This forces Windows to route DX11 calls to your dedicated GPU.
Step 3 — Do the same for the launcher (this matters)
Add bg3_dx11.exe the same way — it's in the same folder. And also add the Larian launcher itself: Launcher.exe. The reason step 2 alone sometimes fails is that the launcher starts first and picks the integrated GPU, then passes that device context to the game. Adding all three executables eliminates that chain.
Step 4 — If you still see the error or have a single GPU
Your graphics drivers may be corrupt or missing the DX11 runtime. Open a Command Prompt as Administrator and run:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Then restart and install the latest driver from NVIDIA or AMD's website — don't use Windows Update's generic driver. For NVIDIA, use the Studio driver if you're on a stable release; for AMD, grab the Adrenalin package.
Step 5 — Last-resort workaround: launch with Vulkan
Baldur's Gate 3 also supports Vulkan. The launcher has a dropdown that lets you pick Vulkan instead of DX11. Vulkan doesn't check for feature level 10.0 the same way — it's more forgiving on older hardware. If you can get in with Vulkan, you're golden. But note: Vulkan can have its own stuttering issues on some GPUs, so this is a band-aid, not the real fix.
What to check if it still fails
If you've done all that and still get the error, your GPU might genuinely be too old. Check your GPU model against Baldur's Gate 3's minimum requirements: NVIDIA GeForce GTX 780 or AMD Radeon RX 470. Anything older than that (like a GTX 560 or Radeon HD 7750) won't work. You'll need a hardware upgrade. But also check that you're not running the game as Windows 7 compatibility mode — that can break DX11 initialization on Windows 10/11. Disable any compatibility flags in the .exe properties.
One more thing: if you have third-party overlays (Discord, GeForce Experience, MSI Afterburner), disable them temporarily. I've seen Afterburner's RTSS hook cause DX11 device creation to fail on some systems. It's a long shot, but it's free to try.
Was this solution helpful?