Startup crashes, random freezes mid-wave, black screens and the access-violation crash - an ordered fix list, cheapest step first.
Deadlock Crashing on Startup: An Ordered Fix Ladder
Most Deadlock startup crashes are not a broken install. They are a renderer setting that went stale, or Steam and the game running under two different Windows accounts, or an overlay injected into the Source 2 renderer. Walk this ladder in order and stop at the first step that changes the symptom.
Official source: Deadlock on Steam — early development build, access limited to friend invites
The fix ladder, cheapest first
| Step | What you change | Where the claim comes from |
|---|---|---|
| 1 | Steam "Verify integrity of game files" | Community walkthrough, echoed on the Steam and official forums |
| 2 | boot.vcfg renderer value, or the launch option |
Community walkthrough, not Valve guidance |
| 3 | Steam and game on the same Windows account | Player answer on the official Deadlock forum |
| 4 | Every overlay off | Community walkthrough |
| 5 | Graphics driver, scheduler, background apps | Community reports plus the official bug forum |
Read that last column before you start. Only step 3 comes with a maintainer-shaped explanation, and Valve has never published a troubleshooting document for this game.
Step 1: verify the Steam client files
Right-click Deadlock in your library, Properties, Installed Files, Verify integrity of game files. It takes a few minutes because there is a lot of game to check.
This is first because it is free, and because "deadlock game file corrupted" brings people here who already tried it and were told it did nothing. That happens. On the official forum's crashes-at-launch thread a player verifies files, gets "everything is in order", and crashes immediately afterward. "Steam said the files were fine" is real information, not a brush-off.
If you do verify, close Steam completely afterward: exit from the menu, confirm in Task Manager that no Steam processes are still running, then restart the client. That costs nothing and it is the step people skip.
Step 2: reset the renderer the game boots with
Deadlock runs on either DirectX 11 or Vulkan, and which one it picks is stored in a config file. The fix reported on this Steam discussion thread is to open your Deadlock install directory, find the citadel folder, go into cfg, open boot.vcfg, and change DefaultRenderSystemOption from -vulkan to -dx11. Others on the same thread report that editing the file did nothing but adding DefaultRenderSystemOption=-dx11 to the Steam launch options box did, and that deleting the config file outright fixed it.
The same switch has a third home: the in-game video settings have a rendering API selector, and guides from mid-2026 point players at it. The change can be made in the file, in the launch options, or in the game's own video menu. Try the file first because it survives a launch-option reset.
The boot.vcfg edit, the launch-option variant and deleting the config file all come from player posts and video walkthroughs. Valve has published no statement endorsing them. They are cheap, reversible and the most-repeated answer in the community, so they belong at step 2 — but do not expect a forum reply to confirm them.
Step 3: make sure Steam and Deadlock run as the same account
This is the step the popular videos get backwards. Several widely-copied Deadlock fix videos tell you to launch Steam as administrator. The most substantive answer on the official Deadlock forum says the opposite and gives a mechanism: the game's SteamAPI_Init call fails when it cannot reach the Steam client libraries, one cause being that Steam and Deadlock run in different Windows contexts.
Check which Windows user each running process belongs to. If they differ, install Steam as a non-administrator and Deadlock through that client, then confirm "Run as administrator" is unchecked on both executables' Properties pages. Two simpler checks come first in the same post: launch from the Steam client rather than a shortcut or the .exe directly, and confirm the library copy genuinely belongs to your account.
Do this before you reinstall anything. It costs two minutes and it explains a crash that reinstalling will never fix.
Step 4: turn off every overlay
Overlays hook into the game's renderer and survive file verification and config resets. The community list is consistent across sources: the Steam overlay, the Discord overlay, the NVIDIA overlay, and MSI Afterburner with Rivatuner running. Turn them all off, relaunch, then re-enable them one at a time.
Step 5: driver, scheduler and background apps
Driver problems have a shape: the game was fine, then an update landed and now it is not. The official forum has a thread titled crashes GPU specifically since 4/30 update, and another reports an RTX 5090 owner who validated files, did a full reinstall, and tried a spread of drivers from December 2025 through May 2026 with no result. On that hardware the move is rolling the driver back one version, not more reinstalling.
Two settings advice contradicts itself on, so test rather than trust:
- Hardware-accelerated GPU scheduling. One optimization guide recommends HAGS on for RTX 30-series and RX 6000-series and newer; general Windows troubleshooting advice for random crashes says turn it off. It lives in Settings, System, Display, Graphics. Try off first.
- Background Vulkan shader pre-caching. Steam has a setting for it, and the same guide that recommends turning it on also says the first launch after an update stutters hard and one match clears it. A bad first launch after a patch is not evidence of a broken install.
Freezing in Street Brawl or hero practice but not a Standard match points at a load or network problem, not a renderer problem. Four minutes of testing, not thirty.
Freezes mid-wave are a different bug from crashes
A crash ends the process. A freeze does not: frames stop, the game keeps believing it is connected, and nothing gets written to a log that says why. The official forum thread titled stutter and freezing since recent patch describes exactly that, random stuttering or full freezes that do not cause a disconnect, mostly frozen frames.
If the pattern is freezing every few seconds or locking up during a wave, no amount of file verification will touch it. Check overlays, the renderer switch from step 2, and the display mode. One unverified player report is worth a single test because it costs nothing: a user on r/DeadlockTheGame reported their stutter and freezes stopped entirely after turning Bluetooth off. That is one machine, not a diagnosis.
If the game runs but runs badly, that is a different page. A teamfight frame-rate collapse in Deadlock is usually a CPU-side problem rather than a settings problem, and the fix list is on our performance settings page.
The access-violation crash and the dump file
Access-violation reports in Deadlock come with a file. A player on r/DeadlockTheGame opened the Deadlock folder and found a DeadlockAccessViolation.mdmp dump written every time the game crashed. The official Crash Reports thread has a poster on AMD Radeon hardware describing the game crashing to desktop "due to an invalid memory access".
Do not delete those dumps while you are still reproducing the crash. The dump is the only artefact that separates an access violation from a driver timeout. Two threads on the Bug Reports board are worth reading first: an Xid 109 context-switch timeout on an RTX 5060 Ti running Linux, and a blue screen that happens only in Deadlock on both the DX11 and Vulkan renderers.
When none of this works, and why that is not your fault
Valve moved the game to the latest Source 2 engine code as part of City Never Sleeps on September 29, 2026, alongside "Rendering performance improvements", "Network prediction improvements", audio performance improvements and improved anti-cheat. That is a lot of engine churn landing at once on a build whose Steam system requirements still read TBD for CPU, GPU, OS and sound card.
Official source: City Never Sleeps — Valve's patch page
The store page still labels Deadlock an early development build, and GamingOnLinux's October 2026 coverage was still framing it as a long way from a public release. An Intel Arc A580 owner filing on the Intel GPU issue tracker reports trying the latest driver, a clean DDU install, an older driver branch and every combination of display mode and renderer without a definitive result.
The honest ending: a playtest build will crash on some drivers, on some GPUs, on some Windows installs, and no configuration change is guaranteed to fix it. The ladder gets most people to "runs most sessions". Past that the only real fix is a patch, and the useful thing you can do is keep the dump file and post it.
FAQ
Does deleting boot.vcfg delete my progress? No published answer. The file holds a renderer option, and the reported fixes are either editing one value in it or deleting it so the game regenerates it. Back it up first.
Will verifying game files delete my unlocked heroes or items? Nobody has ever reported this and no source addresses it. Valve publishes no statement on what a full re-download does to a playtest account. The invite page explains how access actually works, and Deadlock is invite-only on Windows, so a fresh install is not something you can simply download on a new machine.
Is it worth playing while it is this unstable? Depends on your tolerance. The honest answer is in what Deadlock actually is, and if you get it running the first three matches guide is where the real learning starts.
Does City Never Sleeps fix any of this? The September 29, 2026 patch lists rendering and network prediction improvements, so some of it may already be fixed for you. It does not include a hardware requirement list or a stability guarantee. The full breakdown is on the City Never Sleeps page.
Related Guides
More Deadlock Guides
Three lanes, four new Districts between them, and the Haunts that spawn in each. What City Never Sleeps changed about where you fight.
Every tier list is stale within a patch. How to judge strength from mobility, damage and role fit instead of copying a chart.
Stamina, dash into slide, slide hop, mantle and wall jump - the movement tech that decides fights, explained as mechanics.
Rat King landed Oct 2. The next five City Never Sleeps heroes drop Tuesdays and Fridays at 2pm PT through Oct 20, in the order players vote.
Destroy Guardians, then Walkers, expose the Patron, and burn it down. Why the Archmother pit punishes grouped pokes.
Deadlock is CPU-bound on Source 2. Shader cache, launch options, and the graphics settings that actually move teamfight frames.
Ranked landed in July 2026. How the badge tracks hidden MMR, what placements cost you, and why a 45% winrate still climbs.
Rat King is live since Oct 2, 2026. What Scrap Grenade, Swarm of Rats, Royal Pestments and Banner of Rattania actually do, and where he fits.