Deadlock Crashing Fix: Vulkan, boot.vcfg and Launch Crashes

Most Deadlock crashes on PC come from its experimental Vulkan renderer: delete the "DefaultRenderSystemOption" "-vulkan" line from boot.vcfg (or add -dx11 to the launch options) to put the game back on DirectX 11. That one change fixes the three crash patterns players report most on Valve’s own Deadlock forum — closing right after the Valve logo, closing when a match loads, and the VK_ERROR_DEVICE_LOST fatal error. If you’re already on DirectX 11, work through verified files, a clean GPU driver, overlays and overclocks below.

Match your Deadlock crash to the fix

When Deadlock crashes	Most likely cause	Fix first
Right after the Valve logo, no error	Vulkan set as the boot renderer	Fix 1 (boot.vcfg)
“Vulkan encountered unrecoverable error VK_ERROR_DEVICE_LOST”	Vulkan renderer losing the GPU (often Intel integrated graphics)	Fix 2 (-dx11)
Closes when joining a match, replay or bot match; sandbox works	Vulkan render setting	Fix 1 (boot.vcfg)
Started crashing right after a big patch	Damaged or partly updated game files	Fix 3 (verify files)
Random crash to desktop mid-match on DirectX 11	Driver, overlay or unstable overclock	Fixes 4 and 5
GPU hang / device removed message	Driver or GPU stability	DXGI_ERROR_DEVICE_HUNG fix

Fix 1: Remove Vulkan from boot.vcfg

Deadlock runs on DirectX 11 or an experimental Vulkan renderer. When you switch to Vulkan, Deadlock writes that choice into a startup file called boot.vcfg — so if Vulkan crashes before you can reach the settings menu, you’re locked out of switching back in-game. Edit the file instead:

1. Close Deadlock completely.
2. Open this folder (default Steam library shown — use your own library drive if you installed elsewhere): C:\Program Files (x86)\Steam\steamapps\common\Deadlock\game\citadel\cfg
3. Open boot.vcfg in Notepad.
4. Delete the line "DefaultRenderSystemOption" "-vulkan" and save the file.
5. Restart Steam, then launch Deadlock.

Deleting boot.vcfg outright also works — it only resets Deadlock’s startup configuration to the default. Some players find the file empty or missing; in that case use Fix 2.

One trade-off reported by a player whose match crashes this fixed: DirectX 11 ran with more stutter and the odd freeze on their PC. A stable game with some hitching beats one that closes — then work through the Deadlock stuttering fix to smooth DirectX 11 out.

Fix 2: Force DirectX 11 with the -dx11 launch option

The -dx11 launch option forces DirectX 11 on every launch, regardless of what boot.vcfg says. It’s the workaround posted on Valve’s Deadlock forum for FATAL ERROR: Vulkan encountered unrecoverable error VK_ERROR_DEVICE_LOST, a startup crash reported on 12th Gen Intel laptops with integrated Intel UHD Graphics as recently as October 2026.

1. In Steam, right-click Deadlock → Properties → General.
2. In Launch Options, type -dx11.
3. Close the window and launch the game.

Leave -dx11 in place until Valve’s Vulkan renderer stops crashing on your hardware. Remove it later if you want to test Vulkan again.

On a gaming laptop, also make sure Deadlock isn’t running on integrated graphics: open Windows Settings → System → Display → Graphics, add or select Deadlock, and set it to High performance (your NVIDIA or AMD GPU). See MUX switch and Advanced Optimus explained for how laptops pick a GPU.

Fix 3: Verify the game files after an update

Deadlock gets large updates — the late-September 2026 “City Never Sleeps” update reworked the map and added new heroes — and an interrupted or partial download leaves files that crash on load. Steam can repair them without a reinstall:

1. Right-click Deadlock → Properties → Installed Files.
2. Click Verify integrity of game files and wait for it to finish.
3. Restart Steam before launching again.

If Deadlock closes silently at launch with no crash dialog, fully exit Steam from the system tray and reopen it too — Deadlock starts through the Steam client, and a stale Steam session is a common reason a game closes before the menu.

Fix 4: Clean-install your GPU driver

An outdated or corrupted GPU driver is the next most common cause of mid-match crashes on DirectX 11. Update to the latest NVIDIA, AMD or Intel driver; if Deadlock started crashing right after a driver update, do a clean install with DDU so no leftovers from the old driver remain. Laptop users on integrated Intel graphics should get the current driver from Intel rather than relying on an old OEM package.

Fix 5: Turn off overlays and undo overclocks

• Overlays: turn off the Steam overlay for Deadlock (Properties → General → Enable the Steam Overlay while in-game), plus Discord, the NVIDIA app or AMD overlay, and MSI Afterburner/RivaTuner for a test session. If the crashes stop, re-enable them one at a time to find the culprit.
• GPU overclock: reset any MSI Afterburner or driver-level overclock and undervolt to stock. A clock that passes benchmarks can still crash in a long match.
• CPU and RAM: if you run a manual CPU overclock or an aggressive memory profile, test a few matches at stock settings. If crashes stop, the overclock was the problem, not Deadlock.
• Motherboard BIOS: one player whose launch crashes survived every software fix reported that a BIOS update solved it. It isn’t a guaranteed fix, but it’s worth doing if you’ve exhausted the steps above — especially on Intel 13th/14th Gen desktops.

If Deadlock still crashes

• GPU hang or “device removed” messages point at the driver or GPU stability: see DXGI_ERROR_DEVICE_HUNG fix and DXGI_ERROR_DEVICE_REMOVED fix.
• “Access violation” or 0xc0000005 errors across several games suggest memory or system instability: see the 0xc0000005 access violation fix.
• The game runs but hitches rather than crashing — that’s a different problem: see the Deadlock stuttering fix.

Once Deadlock is stable, tune it: the best Deadlock settings for FPS and Deadlock lowest input lag settings cover the rest.

Related guides

• Deadlock Stuttering Fix
• Best Deadlock Settings for FPS
• Deadlock Lowest Input Lag Settings
• DXGI_ERROR_DEVICE_HUNG Fix
• 0xc0000005 Access Violation Crash Fix
• Marvel Rivals Crashing Fix