WARDOGS Crashing: Every Known Fix From the Closed Beta

Preferred Source Add TposeGaming on Google

on

WARDOGS crashing is annoying everyone, and this trending game isn’t even out yet! The Closed Beta wrapped up on August 23, and Early Access doesn’t launch until September 10, so every crash report right now comes from a build that’s about to change. Here’s every fix that’s worked, organized by what’s actually causing it. So jump to yours first to save time.

Disclaimer: This guide is written for the game’s beta release and is subject to change. Check again later.

Check This First: Is It Actually a Crash

Before you assume your PC is the problem: on beta day, community trackers logged about 1,000 crash reports in 24 hours. Only 6% of those were actual crashes or freezing. Server connection issues made up 41%, signing in took another 32%, and matchmaking or queue problems accounted for 17%.

That tracks with what BULKHEAD said themselves. The login queue got crowded on beta day, and they were seeing a new backend issue tied to login volume that didn’t exist in the Alpha. If you’re stuck at a loading screen or bounced from the queue, that’s probably not a crash. Keep reading if your game is actually freezing or crashing.

The Windows Update Causing Most WARDOGS Crashes

Microsoft’s KB5121003 update, released August 11, is under formal investigation for crashing games. Confirmed symptoms: apps closing unexpectedly, freezing, EXCEPTION_ACCESS_VIOLATION errors, and full device restarts. Embark Studios traced it to inpoutx64.sys, a kernel-level driver bundled with tools like Razer Synapse and various RGB software. The update broke compatibility with it, and closing an invalid handle now triggers a BSOD instead of being ignored.

WARDOGS uses kernel-level Easy Anti-Cheat, and its shader-compilation crashes throw the exact same EXCEPTION_ACCESS_VIOLATION error. Two WARDOGS players independently confirmed that removing KB5121003 fixed their crashes completely.

Two ways to fix it:

• Safer: delete the inpoutx64.sys driver and its service. Keeps your security patches intact.
• Blunt: uninstall KB5121003 entirely (Settings → Windows Update → Update history → Uninstall updates). This worked for WARDOGS players, but it strips 400+ security fixes, and Windows will try to reinstall them.

Crash on Shader Compilation (0xC0000005)

This is the most reported crash on the Steam board. Symptom: WARDOGS crashes right after shader compilation finishes, throwing an “Unexpected Error” popup. Dump files consistently show 0xC0000005 EXCEPTION_ACCESS_VIOLATION, faulting at platformcore.dll, which is the same signature Microsoft flagged in KB5121003. Try the Windows fix above first.

If that doesn’t fix it, disable Hardware-Accelerated GPU Scheduling: Settings → System → Display → Graphics → Advanced graphics settings → toggle off HAGS → restart your PC. It’s a known fix for identical shader crashes in other Unreal Engine games like Hogwarts Legacy. One catch: HAGS is required for DLSS Frame Generation, so RTX 40/50 owners using frame gen will need to choose between the two.

Error 0xc0000142 at Launch

This one fires the moment anti-cheat initializes, and it’s one of the most reported beta-day errors. It’s a Windows DLL initialization failure, which fits with something injecting into the process before Easy Anti-Cheat finishes loading.

For a lot of players, it cleared up on its own with no fix needed, which points to a server-side or build-side cause rather than anything on your end. If it doesn’t self-resolve, try a clean boot: msconfig → Services → check “Hide all Microsoft services” → disable the rest → Startup tab → disable everything → restart.

BSODs and Full PC Freezes

A normal game can’t blue-screen your PC. Only a kernel driver messing with another kernel driver can, and that’s what’s happening here. WARDOGS runs kernel-level Easy Anti-Cheat, and it’s clashing with KB5121003 the same way it does in other anti-cheat games. Uninstalling KB5121003 fixes this completely.

Can’t uninstall the update yet? Try this instead: clear the NVIDIA cache folders under %LOCALAPPDATA%\NVIDIA (DXCache and GLCache), clear the DirectX Shader Cache (Settings → System → Storage → Temporary Files), reboot twice, and disable the Steam overlay.

The Full Crash Reset Sequence

If nothing above worked, this is the most complete fix sequence around:

1. Delete the EasyAntiCheat folder inside your WARDOGS install directory.
2. Delete %LOCALAPPDATA%\Wardogs.
3. Reboot your PC. This is the step most people skip, and the one most often credited with actually fixing it.
4. Verify game files through Steam.
5. Launch and let shaders finish compiling before assuming it’s hung.

Still crashing? Check %LOCALAPPDATA%\Temp for dump files starting with “PACKER.” If you find one showing an access violation (0xC0000005), that’s a client-side bug. Reinstalling won’t fix it, so hold off until BULKHEAD patches it.

Quick Fixes Worth Trying

A handful of smaller fixes worth running through if you’re still stuck:

• Whitelist WARDOGS and the EAC service in your antivirus. Kernel anti-cheat drivers often look like malware to heuristics.
• Disable overlays: Discord, Steam, GeForce Experience, MSI Afterburner, RivaTuner. Injection plus kernel anti-cheat is a known launch-failure combo.
• Enable Secure Boot. Kernel-level EAC expects it to be on, and at least one crash cleared up once you switched it on.
• Update your GPU drivers and run WARDOGS as administrator once, so the anti-cheat driver can install properly if permissions blocked it before.
• Using Sogou Input Method? It injects a DLL into every process, which collides with anti-cheat. Switch to Microsoft Pinyin or kill the Sogou process before launching.

That’s every fix available for Wardogs crashing on PC. Did I miss one? Write them to me in the comments.

FAQ

WARDOGS

Action-Adventure Indie Multi-player Simulation

Release Date

September 10, 2026

Developer(s)

BULKHEAD

Publisher(s)

Team17

Official Site Steam

4 Images