You updated your graphics drivers. You verified game files. You disabled the Steam overlay. And WARDOGS still crashes before the title screen loads. The typical three-step script doesn’t cut it here because the root cause lives deeper — inside Windows 11’s Insider builds and a kernel-level conflict that only surfaces with Easy Anti-Cheat.
If you’re running a Windows 11 Insider Preview build (especially 26220.9223 or similar from the Beta or Dev channel), your game will crash. Repeatedly. The crash might restart your PC or simply return you to the desktop with no error. This is not random. It’s reproducible. And the standard fixes won’t stop it.
Here is the exact sequence that worked for me and many others. Do these in order. Skip nothing.
Step 1: Find the Culprit in Event Viewer
Right after a crash — before rebooting if you can — open Event Viewer (press Win+R, type eventvwr.msccodecodecodecode). Navigate to Windows Logs > System. Look for a red exclamation mark with source BugCheck or Error. The error code will be 0x7Ecodecodecodecode or 0x3Bcodecodecodecode, and the detail line will mention a driver file.
The driver you’re looking for is inputx64.sys. This belongs to certain RGB control software (like Razer, Corsair, Logitech) or motherboard utility suites. It conflicts with Easy Anti-Cheat under Windows 11 Insider builds after the August 12th security patch.
Check also for EasyAntiCheat.sys or ESET conflicts. But inputx64.sys is the most common culprit.
If you don’t see that, look for any driver with a .syscodecodecodecode name you don’t recognize. The fix below works for most kernel-mode conflicts.
Step 2: Stop the Conflicting Driver Immediately
Open Command Prompt as Administrator. Run these three commands one after another:
“`
sc stop inputx64
sc config inputx64 start= disabled
sc query inputx64
“`
The third command should return STATE: STOPPED. If it says RUNNING, repeat the first two lines. Then restart your PC.
Once back on the desktop, launch WARDOGS. If it works, you’ve isolated the problem. But stopping the driver is a bandage — the next step prevents the conflict permanently by removing the Windows update that started it.
Step 3: Unenroll from Windows Insider and Uninstall KB5121003
This is the step that ends the cycle. Standard advice tells you to “update Windows.” For Insider users, that’s the last thing you want.
First, unenroll from the Insider program:
- Go to Settings > Windows Update > Windows Insider Program.
- Click Stop getting preview builds.
- If you’re on a build newer than stable (25H2), you cannot simply unenroll. You must revert using Settings > System > Recovery > Go back. This option only works if fewer than 10 days have passed since the upgrade. If that window has closed, you need to clean-install the public release of Windows 11 25H2.
After reverting to the stable channel, uninstall KB5121003:
- Go to Settings > Windows Update > Update History > Uninstall updates.
- Find KB5121003 (dated around August 12, 2026). Select it and uninstall.
- Restart your PC.
This security update is the trigger. Without it, Easy Anti-Cheat can initialize properly. I know removing a security update feels risky. But the alternative is a game that never launches. Microsoft will patch the underlying issue eventually — in the meantime, your system is still protected by every other update.
Step 4: Disable Hardware-Accelerated GPU Scheduling
HAGS is another common conflict in Unreal Engine 5 games with Easy Anti-Cheat. After you’ve stabilized the driver and Insider situation, turn off HAGS:
- Settings > System > Display > Graphics > Default graphics settings.
- Toggle Hardware-accelerated GPU scheduling to Off.
- Restart.
You can re-enable HAGS later once the game runs. Many UE5 titles perform fine without it, and WARDOGS doesn’t gain much from it on Insider builds.
Step 5: Temporarily Disable Memory Integrity
Memory Integrity (Core Isolation) can also block kernel-mode anti-cheat drivers. To test:
- Search for Core Isolation in Windows.
- Turn off Memory Integrity.
- Restart and test the game.
If WARDOGS launches, leave it off during your session. Re-enable it after you’re done playing. This is a workaround, not a permanent solution — but given that your Insider build already breaks memory integrity guarantees, the risk is minimal for a gaming session.
When Standard Advice Still Fails: Three Crash Scenarios
Not every WARDOGS crash comes from the Insider conflict. Here’s a quick-reference table for the most common patterns and their effective fixes:
| Crash Pattern | Event Viewer Clue | Real Fix |
|---|---|---|
| Game window opens, then closes without error | No bugcheck; may see WARDOGS.execodecodecodecode error in Application log |
Delete local config folder: %LOCALAPPDATA%WARDOGSSavedConfigcodecodecodecode |
Blue screen with SYSTEM_THREAD_EXCEPTION_NOT_HANDLEDcodecodecodecode |
BugCheck 0x7E, driver name after the error | Stop conflict driver (sc stop inputx64), then uninstall KB5121003 |
| Black screen then restart | BugCheck 0x3B or 0x1E | Disable memory integrity, then clean-install GPU driver (use DDU in Safe Mode) |
Step 6: Enable AES-NI in BIOS (The Hidden Switch)
One more fix that caught me off-guard: WARDOGS requires the AES-NI instruction set to be enabled in the BIOS. Most modern motherboards have it on by default. But some overclocking presets or “performance” profiles disable it. If you’ve tampered with BIOS settings — or you’re running an older CPU that lets you toggle AES — check this:
- Enter BIOS (tap Del or F2 during boot).
- Look for CPU AES Instructions or AES-NI under Advanced > CPU Configuration.
- Set to Enabled.
- Save and exit.
This instruction set is used by Easy Anti-Cheat for encryption. If it’s off, the game crashes at launch every time. No Event Viewer error will point directly to it — you just won’t get past the loading screen.
Why Your Standard Startup Fixes Don’t Touch This
You already know the basics: update drivers, verify files, disable overlays. Those fix ordinary corruption and hook conflicts. But WARDOGS (like many modern UE5 titles) uses Easy Anti-Cheat, which operates at the kernel level alongside drivers like inputx64.sys. When a Windows security update tightens memory access restrictions, these drivers can cause exceptions that crash the entire system. No amount of -dx11codecodecodecode launch flags or compatibility modes will bypass a kernel-mode failure.
The community also reports success with repairing the EAC service from the game folder (steamappscommonWARDOGSEasyAntiCheatEasyAntiCheat_EOS_Setup.exe > Repaircodecodecodecode). Do that after the Insider rollback. But without removing the KB, even a fresh EAC install will crash on the next restart.
One More Thing: The Game’s Future on Insider Builds
Bulkhead Interactive has stated that WARDOGS is not officially tested on Windows Insider Preview builds. They expect players to run production releases. If you depend on Insider for your work or hardware compatibility, you’ll face recurring crashes after every new flight from Microsoft. The only sustainable fix is to run the game on the stable channel and use a dual-boot setup for Insider testing. That’s ugly — but it’s honest. The game’s anti-cheat is not going to chase Microsoft’s kernel changes every month.
For now, unenroll, remove KB5121003, stop inputx64.sys, and disable memory integrity. Then verify EAC once. You’ll be back in the hot zone within an hour.
