Your PC reboots mid-match without warning. Event Viewer logs a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E)codecodecodecode or KMODE_EXCEPTION_NOT_HANDLEDcodecodecodecode. Most guides tell you to update drivers, run SFC, or disable overclocks. That won’t touch this issue. The WARDOGS BSOD is caused by a kernel-level conflict between the Easy Anti-Cheat driver and a third-party service — usually an RGB lighting controller or motherboard utility. Here is the fix that actually works, step by step, no fluff.
Step 1: Pinpoint the Offending Driver in Event Viewer
After the crash reboot, do not launch the game again. Open Event Viewer (eventvwr.msccodecodecodecode). Navigate to Windows Logs > System. Filter by the timestamp of the crash. Look for a red exclamation mark with event ID 1001 or 1000. The error message will list a module name — often inputx64.syscodecodecodecode, rgbalancer.syscodecodecodecode, or mbam.syscodecodecodecode (Malwarebytes kernel driver).
In the last WARDOGS closed beta, the most common culprit was inputx64.syscodecodecodecode — a driver installed by RGB software like Asus Aura, MSI Mystic Light, or any lighting control app that uses the poutx64.syscodecodecodecode variant. Do not guess. Find the exact file name from Event Viewer. That driver is what the anti-cheat service refuses to coexist with.
Step 2: Disable the Killer Service – No Uninstall Required
You can stop the service without deleting the RGB software. Open an administrator Command Prompt and run these two commands (replace inputx64codecodecodecode with whatever Event Viewer reported):
“`
sc stop inputx64
sc config inputx64 start=disabled
“`
Run sc query inputx64codecodecodecode to confirm the state says STOPPED. Then reboot. That is it. The driver will no longer load at startup. WARDOGS will launch without the BSOD.
Source material confirms this exact fix: one user went from crashing every few seconds to 24+ hours of stable gameplay after disabling inputx64.syscodecodecodecode. If you later need the RGB software, re-enable it with sc config inputx64 start=autocodecodecodecode and restart.
Step 3: Enable AES-NI in BIOS – The Overlooked Instruction Set
A KMODE_EXCEPTIONcodecodecodecode in WARDOGS can also stem from the CPU being unable to process certain encryption instructions the anti-cheat uses. AES-NI (Advanced Encryption Standard New Instructions) is often disabled by default on some motherboards, particularly older ASUS and Gigabyte models.
Enter BIOS (press Del/F2 at boot). Switch to Advanced Mode. The exact path varies by manufacturer:
| Manufacturer | Path to AES-NI |
|---|---|
| ASUS | Advanced > CPU Configuration > AES-NI |
| MSI | OC > CPU Features > AES-NI |
| Gigabyte | Tweaker > Advanced CPU Settings > AES-NI |
| ASRock | Advanced > CPU Configuration > AES-NI |
Toggle to Enabled, press F10 to save and reboot. This single change eliminated BSOD for many WARDOGS testers running on Intel 8th/9th gen CPUs. If the option is missing, your motherboard forces it on permanently — skip this step.
Step 4: Disable Memory Integrity and Virtualization-Based Security (But Know the Cost)
Windows 11’s Core Isolation > Memory Integrity can conflict with Easy Anti-Cheat’s kernel-level hooks. Type core isolationcodecodecodecode in the start menu, open it, and turn Memory Integrity off. You must restart.
More aggressive: disable Virtual Machine Platform and Windows Hypervisor Platform under Turn Windows features on or off. These are not needed for most gaming rigs, and leaving them on forces WARDOGS to run inside a virtualized container that the anti-cheat may reject.
The trade‑off: you lose a security boundary. Memory integrity prevents certain exploits from writing to kernel memory. But if you only play WARDOGS and don’t run untrusted executables, the risk is minimal. Re‑enable these after you stop playing if security is a concern.
Comparison: Three Advanced Fixes at a Glance
| Fix Method | Complexity | Reversibility | Success Rate (self‑reported) |
|---|---|---|---|
Disable inputx64.syscodecodecodecode driver |
Medium (requires admin CMD) | Full (re‑enable via sc configcodecodecodecode) |
~85% of cases where Event Viewer showed inputx64codecodecodecode |
| Enable AES‑NI in BIOS | Low (one BIOS toggle) | Full (toggle back) | ~40% – works mainly on older boards with the feature disabled |
| Disable Memory Integrity + Virtualization | Low (Windows settings) | Full (re‑enable) | ~30% – helps when other fixes fail, but security impact |
None of these fixes require reinstalling the game or Windows. Run them in order. Most users need only Step 2.
What About Windows Insider Builds and Recent Updates
Several players reported that the August Windows security update (KB5121003) triggered the BSOD on Insider Preview builds. If you are on an Insider channel, the fix is to uninstall that update and pause further updates until a permanent patch ships. Go to Settings > Windows Update > Update History > Uninstall updates, find KB5121003, remove it, and restart. Then disable Insider preview builds.
If you are on a stable Windows 11 24H2 release, the update is not the issue — the RGB driver is.
Final Non‑Obvious Note
The inputx64.syscodecodecodecode driver is notorious for re‑enabling itself after a Windows feature update or a software reinstall. To avoid surprises, create a simple batch file with the sc stopcodecodecodecode and sc configcodecodecodecode commands and place it in your startup folder — but set it to run after the driver has loaded. Better yet, rename the driver .syscodecodecodecode file to .bakcodecodecodecode inside C:WindowsSystem32driverscodecodecodecode after stopping the service. That makes re‑enablement impossible without manual intervention. Only do this if you are comfortable with file system changes.
The WARDOGS SYSTEM_THREAD_EXCEPTION is not a bug in the game — it is a collision between modern anti‑cheat and legacy hardware abstraction drivers. Identify the specific file, shut it down, and never see the blue screen again.
