Deadlock Crashing: Causes, Checks and Fixes (2026)

Deadlock runs on Source 2, the same engine family as Dota 2 and Counter-Strike 2, and it inherits that engine’s crash personality. When Deadlock dies, it usually does so in one of three ways: a hard crash to desktop with no message during hero select or the first minute of a match, an “Engine Error” dialog that names a shader, texture or memory allocation, or a silent hang where the sound loops and Windows eventually reports that deadlock.exe stopped responding. Because the game is still in a rolling early-access state with frequent patches, some crashes are simply Valve’s bugs. But the majority we see in 2026 trace back to a handful of local issues: a stale shader cache after an update, an overlay hooking into the Vulkan or DirectX 11 renderer, a page file that is too small for Source 2’s texture streaming, or a GPU driver that has not caught up with the current build.

Likely Causes

Fix 1: Clear the Steam shader cache for Deadlock

How to check

Source 2 precompiles and caches shaders. After a patch that changes materials, an old cache can conflict with new assets and produce a crash at the loading screen or the first time a new effect appears. If your crash started right after a Steam update finished downloading, this is the first suspect.

What to do

Close Steam completely. Navigate to Steam\steamapps\shadercache\1422450 (1422450 is Deadlock’s app ID) and delete the folder. Optionally also delete the contents of %LOCALAPPDATA%\NVIDIA\DXCache and %LOCALAPPDATA%\NVIDIA\GLCache on NVIDIA cards, or %LOCALAPPDATA%\AMD\DxCache on AMD. Relaunch Steam and Deadlock. Expect longer load times and some hitching in the first match while the cache rebuilds.

How to undo it

There is nothing to undo. The cache regenerates automatically. If you want to avoid the rebuild hitching, simply do not delete it again.

Fix 2: Disable every overlay

How to check

Overlays hook into the graphics API. Discord’s in-game overlay, MSI Afterburner with RivaTuner Statistics Server, GeForce Experience, Xbox Game Bar and Medal are all known to cause instability with Source 2 titles. Test by launching Deadlock with all of them turned off; if you play two or three matches without a crash, you have found the cause.

What to do

In Discord, go to User Settings, Game Overlay, and toggle “Enable in-game overlay” off. In Steam, right-click Deadlock, choose Properties, and uncheck “Enable the Steam Overlay while in-game.” Exit RivaTuner Statistics Server from the system tray. In Windows Settings, Gaming, Xbox Game Bar, turn it off. Re-enable them one at a time later to identify the specific culprit.

How to undo it

Reverse each toggle. Nothing else changes on your system.

Fix 3: Switch between Vulkan and DirectX 11

How to check

Deadlock defaults to a renderer based on your hardware, but you can force either one. If the crash dialog mentions a Vulkan device lost error, or if the game hard-locks without any message, forcing the other API is a quick and telling experiment.

What to do

In Steam, right-click Deadlock, choose Properties, and in the Launch Options field enter -vulkan to force Vulkan or -dx11 to force DirectX 11. Only use one at a time. Launch the game and play a few matches. Vulkan often gives better frame pacing on AMD cards, while DirectX 11 is sometimes more stable on older NVIDIA drivers, but this is hardware dependent and not a rule.

How to undo it

Clear the Launch Options field and the game returns to its automatic renderer selection.

Fix 4: Verify game file integrity

How to check

Interrupted downloads, disk errors and aggressive antivirus quarantines can all damage files in Steam\steamapps\common\Deadlock\game\citadel. Crashes that reference a specific .vpk or a missing map are a strong hint.

What to do

In Steam, right-click Deadlock, choose Properties, Installed Files, then “Verify integrity of game files.” Let it finish. If it reports that files were reacquired, launch and test. If it keeps finding bad files on each run, check your drive health with the manufacturer’s tool or chkdsk.

How to undo it

Verification only replaces damaged files with correct copies; there is no state to revert.

Fix 5: Reset the video configuration

How to check

Source 2 stores your video settings in Steam\steamapps\common\Deadlock\game\citadel\cfg\video.txt. A setting that was valid before a patch, such as a resolution the game no longer supports or an experimental option, can crash on startup before you ever see the menu.

What to do

With the game closed, rename video.txt to video.txt.bak. If you have created an autoexec.cfg in the same folder, rename that too. Launch Deadlock; it will generate fresh defaults. If it now starts cleanly, reintroduce your preferred settings through the in-game menu rather than by restoring the old file. You can also add -autoconfig to Launch Options for one session to force default video settings.

How to undo it

Delete the newly created video.txt and rename your .bak file back to video.txt.

Fix 6: Update or clean-install the GPU driver

How to check

Open Event Viewer, Windows Logs, System, and look for warnings around the crash time. An entry from nvlddmkm (NVIDIA) or amdkmdag (AMD) reading “Display driver stopped responding and has recovered” points at the driver, not the game.

What to do

Download the current driver for your card directly from NVIDIA, AMD or Intel. During installation choose the clean or factory reset option, which removes old profiles. If the newest driver is itself the problem, which happens with early-access titles, roll back to the previous release. Reboot after installing.

How to undo it

Reinstall the driver version you had before. Both NVIDIA and AMD keep older releases available for download, and Device Manager offers a “Roll Back Driver” button if the previous version is still cached.

Fix 7: Increase the Windows page file

How to check

Source 2 streams a lot of texture data and commits generous virtual memory. On systems with 16 GB of RAM or less, or systems where the page file has been disabled or fixed at a small size, Deadlock can throw “Engine Error: Out of memory” or simply vanish when a match gets busy. Check Task Manager’s Performance tab for the committed memory figure while the game runs; if it sits near the limit, this fix applies.

What to do

Open System Properties, Advanced, Performance Settings, Advanced, Virtual Memory. Uncheck “Automatically manage paging file size,” select your system drive, choose Custom size, and set both initial and maximum to at least 16384 MB (more if you have 8 GB of RAM). Click Set, OK, and reboot.

How to undo it

Return to the same dialog and re-enable “Automatically manage paging file size for all drives,” then reboot.

Fix 8: Return memory and CPU to stock settings

How to check

Deadlock’s combination of high frame rates and heavy CPU-side simulation exposes marginal overclocks that other games tolerate. If you have XMP or EXPO enabled, a manual CPU overclock, or an undervolt, and you also see occasional crashes in other titles, instability is likely.

What to do

Enter your BIOS and disable XMP/EXPO, then load default CPU settings. Play several matches. If the crashes stop, re-enable XMP but raise DRAM voltage slightly or drop to a lower memory profile, and test again. Intel 13th and 14th generation owners should also confirm they are on a BIOS that applies the current Intel default power settings.

How to undo it

Re-enable your previous BIOS profile. Most boards let you save profiles before making changes; do that first.

If Nothing Works

Gather evidence before asking for help. Note the exact text of any Engine Error, the Windows Event Viewer application error (look for deadlock.exe with a faulting module name), and whether the crash is tied to a specific hero, map area or match phase. Try a fresh Windows user account to rule out per-user configuration. Test with a completely stock system: no overclocks, no RGB or peripheral software, no third-party antivirus. Finally, remember that Deadlock is unfinished. Check the game’s official Steam forum and the in-game news for known issues; if a crash appeared for many players with the latest patch, waiting a day or two for a hotfix is a legitimate fix.

FAQ

Why does Deadlock crash only during hero select or the first minute?

That window is when the game loads the largest amount of new shader and texture data. Stale shader caches, undersized page files and overlay hooks all tend to fail at exactly that moment, which is why the first three fixes above target it.

Is the Vulkan or DirectX 11 renderer more stable?

Neither is universally better. Vulkan generally performs well on AMD hardware and modern NVIDIA drivers, while DirectX 11 can be more forgiving on older drivers. Test both with the launch options and keep whichever survives longer.

Can I lower a setting to stop crashes rather than fixing the cause?

Sometimes. Reducing texture quality and disabling any experimental or beta rendering options lowers memory pressure and can hide an “Out of memory” crash. It is a workaround rather than a repair, but it is a reasonable test.

Does a crash always mean a problem on my PC?

No. Because Deadlock is in active development, some crashes are introduced by patches and fixed by the next one. If the issue appeared for everyone on the same day, the cause is almost certainly on Valve’s side.