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 \u2014 inside Windows 11\u2019s Insider builds and a kernel-level conflict that only surfaces with Easy Anti-Cheat.<\/p>\n
If you\u2019re 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\u2019s reproducible. And the standard fixes won\u2019t stop it.<\/p>\n
Here is the exact sequence that worked for me and many others. Do these in order. Skip nothing.<\/p>\n
Right after a crash \u2014 before rebooting if you can \u2014 open Event Viewer (press Win+R, type The driver you\u2019re looking for is inputx64.sys<\/strong>. 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.<\/p>\n Check also for EasyAntiCheat.sys<\/strong> or ESET<\/strong> conflicts. But inputx64.sys is the most common culprit.<\/p>\n If you don\u2019t see that, look for any driver with a Open Command Prompt as Administrator. Run these three commands one after another:<\/p>\n “`<\/p>\n sc stop inputx64<\/p>\n sc config inputx64 start= disabled<\/p>\n sc query inputx64<\/p>\n “`<\/p>\n The third command should return STATE: STOPPED<\/strong>. If it says RUNNING, repeat the first two lines. Then restart your PC.<\/p>\n Once back on the desktop, launch WARDOGS. If it works, you\u2019ve isolated the problem. But stopping the driver is a bandage \u2014 the next step prevents the conflict permanently by removing the Windows update that started it.<\/p>\n This is the step that ends the cycle. Standard advice tells you to \u201cupdate Windows.\u201d For Insider users, that\u2019s the last thing you<\/a> want.<\/p>\n First, unenroll from the Insider program:<\/p>\n After reverting to the stable channel, uninstall KB5121003:<\/p>\n 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 \u2014 in the meantime, your system is still protected by every other update.<\/p>\n HAGS is another common conflict in Unreal Engine 5 games with Easy Anti-Cheat. After you\u2019ve stabilized the driver and Insider situation, turn off HAGS:<\/p>\n You can re-enable HAGS later once the game runs. Many UE5 titles perform fine without it, and WARDOGS doesn\u2019t gain much from it on Insider builds.<\/p>\n Memory Integrity (Core Isolation) can also block kernel-mode anti-cheat drivers. To test:<\/p>\n If WARDOGS launches, leave it off during your session. Re-enable it after you\u2019re done playing. This is a workaround, not a permanent solution \u2014 but given that your Insider build already breaks memory integrity guarantees, the risk is minimal for a gaming session.<\/p>\n Not every WARDOGS crash comes from the Insider conflict. Here\u2019s a quick-reference table for the<\/a> most common patterns and their effective fixes:<\/p>\n 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 \u201cperformance\u201d profiles disable it. If you\u2019ve tampered with BIOS settings \u2014 or you\u2019re running an older CPU that lets you toggle AES \u2014 check this:<\/p>\n This instruction set is used by Easy Anti-Cheat for encryption. If it\u2019s off, the game crashes at launch every time. No Event Viewer error will point directly to it \u2014 you just won\u2019t get past the loading screen<\/a>.<\/p>\n 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 The community also reports success with repairing the EAC service<\/strong> from the game folder (eventvwr.msc<\/code>codecodecodecode). Navigate to Windows Logs > System<\/strong>. Look for a red exclamation mark with source BugCheck<\/strong> or Error<\/strong>. The error code will be 0x7E<\/code>codecodecodecode or 0x3B<\/code>codecodecodecode, and the detail line will mention a driver file.<\/p>\n.sys<\/code>codecodecodecode name you don\u2019t recognize. The fix below works for most kernel-mode conflicts.<\/p>\nStep 2: Stop the Conflicting Driver Immediately<\/h2>\n
Step 3: Unenroll from Windows Insider and Uninstall KB5121003<\/h2>\n
\n
\n
Step 4: Disable Hardware-Accelerated GPU Scheduling<\/h2>\n
\n
Step 5: Temporarily Disable Memory Integrity<\/h2>\n
\n
When Standard Advice Still Fails: Three Crash Scenarios<\/h2>\n
\n\n
\n \nCrash Pattern<\/th>\n Event Viewer Clue<\/th>\n Real Fix<\/th>\n<\/tr>\n<\/thead>\n \n Game window opens, then closes without error<\/td>\n No bugcheck; may see WARDOGS.exe<\/code>codecodecodecode error in Application log<\/td>\nDelete local config folder: %LOCALAPPDATA%WARDOGSSavedConfig<\/code>codecodecodecode<\/td>\n<\/tr>\n\n Blue screen with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED<\/code>codecodecodecode<\/td>\nBugCheck 0x7E, driver name after the error<\/td>\n Stop conflict driver (sc stop inputx64), then uninstall KB5121003<\/td>\n<\/tr>\n \n Black screen then restart<\/td>\n BugCheck 0x3B or 0x1E<\/td>\n Disable memory integrity, then clean-install GPU driver (use DDU in Safe Mode)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Step 6: Enable AES-NI in BIOS (The Hidden Switch)<\/h2>\n
\n
Why Your Standard Startup Fixes Don\u2019t Touch This<\/h2>\n
-dx11<\/code>codecodecodecode launch flags or compatibility modes will bypass a kernel-mode failure.<\/p>\nsteamappscommonWARDOGSEasyAntiCheatEasyAntiCheat_EOS_Setup.exe > Repair<\/code>codecodecodecode). Do that after the Insider rollback. But without removing the KB, even a fresh EAC install will crash on the next restart.<\/p>\nOne More Thing: The Game\u2019s Future on Insider Builds<\/h2>\n