Deadlock VK_ERROR_DEVICE_LOST: Vulkan unrecoverable error (fix)
Written by
Last checked
September 30, 2026
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
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. Players in the Deadlock Community Discord have reported it since mid-September 2026, and one Intel Arc B580 owner said Vulkan crashed for them on leaving the title screen right after the September 30 update. The fix that worked, from a player on the game's subreddit who posted it the day of the update, is a clean reinstall that removes the leftover game folder. A plain reinstall didn't help an earlier Discord reporter. The same post says it hits players running community FPS configs in particular.
Fix it, step by step
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).
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.
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.
Sorted. Glad that worked.
Nothing worked. Here's what to do next.
You've ruled out every step on this page, which is useful. Send this to support or drop it in the community Discord so nobody makes you repeat yourself.
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.
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""
From isthisgamedownMatched on ""