WARDOGS runs kernel-level anti-cheat (the Elytra framework, launched before the game) on Unreal Engine, so the two things that crash it most are overlays injecting into the game and the anti-cheat service failing to start. Work down this list in order; most people are fixed by step 3.
1. Close every overlay first
Discord, Steam overlay, GeForce Experience / NVIDIA App, MSI Afterburner, RivaTuner, Medal, Overwolf and Xbox Game Bar all inject into the game process. Kernel anti-cheat plus injection is the single most common reason WARDOGS exits silently or never shows a window.
- Steam: right-click WARDOGS → Properties → General → untick Enable the Steam Overlay while in-game.
- Discord: Settings → Game Overlay → off.
- Afterburner/RivaTuner: close them fully, not just the tray icon.
- Xbox Game Bar: Windows Settings → Gaming → Game Bar → off.
Launch again. If it now opens, add overlays back one at a time.
2. Repair the anti-cheat framework (Elytra)
WARDOGS starts through the Elytra launcher (WardogsLauncher-Shipping.exe), which downloads three signed modules and connects to the Elytra.Service Windows service before the game opens. If that service can't start, the game exits with no window.
- Open
%LOCALAPPDATA%\Wardogs\ElytraLauncher.logand read the last line: it names the stage that failed. - Windows Settings → Apps → Elytra Anti-Cheat Framework → Repair. Reboot.
- If your antivirus quarantined anything from
C:\Program Files\Elytra, restore it and whitelist the folder. - Launch from Steam, not from the exe.
Stage-by-stage log reading is on the launcher page.
3. Verify the game files
Steam → WARDOGS → Properties → Installed Files → Verify integrity of game files. A 50 GB download in launch-week traffic often finishes with a few corrupt packs; this replaces them without redownloading everything.
4. Update, or roll back, the GPU driver
| GPU | Do this |
|---|---|
| NVIDIA | Install the launch-day Game Ready driver. If the crash started after a driver update, use DDU in safe mode and go back one version. |
| AMD | The same. The RX 7000 series has had "driver timeout" resets on some builds in 2026; if you get the AMD Bug Report Tool popup after a crash, roll back to the previous WHQL driver. |
| Intel Arc | Use the newest driver; Arc needs the shader cache rebuilt after each driver change (step 6). |
5. Turn off Hardware-Accelerated GPU Scheduling
Windows Settings → System → Display → Graphics → Change default graphics settings → Hardware-accelerated GPU scheduling → Off → reboot. This one cleared the repeatable crash during shader compilation for a lot of beta players. If it makes no difference, turn it back on.
6. Clear the shader cache
Delete %LOCALAPPDATA%\Wardogs\Saved\Wardogs_PCD3D_SM6.upipelinecache and the D3DDriverByteCodeBlob_*.ushaderprecache file next to it (real file names from the install), and clear the driver cache:
- NVIDIA:
%LOCALAPPDATA%\NVIDIA\DXCacheand%PROGRAMDATA%\NVIDIA Corporation\NV_Cache - AMD:
%LOCALAPPDATA%\AMD\DxCacheandGLCache
The first launch after this takes several minutes on the shader screen. Let it finish.
7. Crashes mid-match only
- VRAM. 8 GB cards at 1440p on High textures run out and the game dies without a message. Drop Textures to Medium.
- Memory. 16 GB is the minimum with nothing else open. Close browsers with many tabs; WARDOGS at 100 players sits at 10–13 GB.
- XMP/EXPO instability. If you also crash in other games, drop the RAM to JEDEC speed for one session and see.
- Intel 13th/14th gen. Crashes with "out of video memory" or decompression errors on i7-13700K / i9-13900K / 14th-gen parts are the known Raptor Lake degradation. Update the BIOS to the latest microcode and cap the P-core turbo until you can RMA.
What the game records when it crashes
WARDOGS ships with Sentry crash reporting (crashpad). After a fatal crash it writes a report under <install folder>\Wardogs\.sentry-native\ with your GPU, driver version, CPU, resolution and the last few events (map loads, settings changes, server login), and uploads it to BULKHEAD. So a crash you hit on launch night is already in their hands; the Steam forum post just needs the time it happened and what you were doing. Maps load as /Game/Maps/Frontend (the menu) and /Game/Maps/Worlds/... (the battlefield), which is what you'll see in the log around a crash.
8. Still crashing
Grab the log at %LOCALAPPDATA%\Wardogs\Saved\Logs\ (game) and %LOCALAPPDATA%\Wardogs\ElytraLauncher.log (launcher), search it for Fatal or Assertion, and post that line on the Steam forum. A crash that mentions D3D12 is the GPU driver; a launcher log that stops at "Connecting to the anti-cheat service" is step 2; one with OutOfMemory is step 7.
FAQ
Why does WARDOGS close with no error?
Almost always the anti-cheat. If the Elytra service didn't start or an overlay injected, the game exits before it opens a window. Repair the Elytra framework from Windows Apps and disable overlays.
Does WARDOGS work on Windows 10?
Yes. Minimum spec is Windows 10 64-bit; Windows 11 is recommended. Both need up-to-date GPU drivers.
Will disabling HAGS hurt my other games?
Rarely. Hardware-Accelerated GPU Scheduling helps some titles by a few percent. Turn it back on if WARDOGS runs fine without the crash.
Is it my hardware?
If the game crashes to desktop with a driver reset popup (AMD Bug Report Tool or an NVIDIA TDR), that's a GPU or driver-level hang. Roll the driver back a version before blaming the card.
Sick of full servers and queues?
Rent your own WARDOGS server from an approved host and play with your mates on your rules. UK/EU: QONZER (bare metal, no slot fees). Anywhere else: BisectHosting (21 locations). Casual group: xREALM (pay by the hour). Full comparison.