Is This Game Down
Browse games
You can fix thisReported

Deadlock VK_ERROR_DEVICE_LOST: Vulkan unrecoverable error (fix)

Deadlock server status →Deadlock servers →

Written by

IsThisGameDown

Last checked

October 8, 2026

r/DeadlockTheGame and the Deadlock Community Discord ↗

Deadlock closes with "Fatal Error: Vulkan encountered unrecoverable error VK_ERROR_DEVICE_LOST", on launch or when leaving the title screen.

Also appears as: vk_error_device_lost, deadlock vk_error_device_lost, vulkan encountered unrecoverable error vk_error_device_lost, deadlock vulkan encountered unrecoverable error, deadlock vulkan crash, deadlock fatal error vulkan, deadlock vulkan error, deadlock vulkan fatal error

The Vulkan renderer lost contact with your graphics card, so the game shut down. It's a problem between the game and your PC, not Valve's servers. Reports go back to mid-September 2026 in the Deadlock Community Discord and kept arriving after the September 30 update, mostly from Intel Arc B580 owners: a 44-comment r/DeadlockTheGame thread and new Steam threads on October 6 and 7 say Vulkan worked before that update.

Switching to DirectX 11 gets most of them in, though two Arc owners say DX11 then crashed mid-match. A clean reinstall that removes the leftover game folder fixed it for one player, and verifying files for another. Valve hasn't acknowledged it.

Fix it, step by step

  1. Add -dx11 to Deadlock's launch options

    In Steam > Deadlock > Properties > Launch options, enter -dx11. This switches the game to DirectX 11 and stops it opening in Vulkan. Two Steam Discussions threads (September 30 and October 1, 2026) had Intel Arc B580 owners say it fixed the fatal error, and a third player said it fixed theirs on the same GPU. Two other Arc owners say the game then crashed mid-match on DirectX 11, one of them on every reconnect too, and others report much lower frame rates on DX11, so it may not hold for everyone. Remove the option once a driver or game update fixes Vulkan.

  2. Delete the -vulkan line from boot.vcfg (one report)

    If you can't reach the settings menu to switch back, go to Steam\steamapps\common\Deadlock\game\citadel\cfg, open boot.vcfg in a text editor and delete the line "DefaultRenderSystemOption" "-vulkan". A player in the Steam thread "Game crashes on start up" said this reverted the renderer without a reinstall after they'd switched to Vulkan. An Intel Arc owner on Valve's forum said editing boot.vcfg didn't work for them.

  3. Remove any FPS config or mods first

    If you've installed a community FPS or performance config or any mods, remove them. The player who posted the fix said the error mostly affects players using configs, and configs broke on a large scale after the September 2026 update (see the FATAL ERROR page).

  4. Verify Deadlock's game files in Steam (one report)

    In Steam, right-click Deadlock, open Properties > Installed Files and choose Verify integrity of game files. In an r/DeadlockTheGame thread about this exact error after the update, one reply suggested it and another player said "Yep that's what I had to do this morning". The original poster didn't confirm, and said the crash also happened on DirectX.

  5. Uninstall, delete the leftover game folder, then reinstall

    Uninstall Deadlock in Steam, then delete what's left of its folder (Steam\steamapps\common\Deadlock\game) before reinstalling. A player on the game's subreddit said this fixed it for them. A normal reinstall that leaves the folder behind didn't work for another reporter. You'll need to set up any mods or configs again afterwards.

  6. Update your graphics driver (unconfirmed)

    Install the latest driver from NVIDIA, AMD or Intel. Vulkan device-lost errors come from the driver, and it's the usual advice in the Discord's help channel, but no reporter confirmed it fixed this error in Deadlock.

  7. Note

    The original poster of the r/DeadlockTheGame Arc thread said running the game through DXVK let them finish a full match. DXVK replaces the game's DirectX DLLs with a third-party one, and Deadlock uses VAC, so we don't recommend it. Valve and Intel haven't commented on the Arc crashes.

    Unconfirmed

Hit this error? Leave a comment

Say where you are, what you see on screen, and whether any fix worked for you.

No links. Anonymous, no account. Keep it about the game.

What people are saying

Notes from players who've hit this one — no time limit, an answer from months ago is still an answer.

  • Nothing reported here yet.
← CRASH-ON-LAUNCHVAC-CHALLENGE-TIMED-OUT →

Other Deadlock error codes

Recently added