{"id":81560,"date":"2026-09-22T09:00:00","date_gmt":"2026-09-22T13:00:00","guid":{"rendered":"https:\/\/overcentral.com\/en\/?p=81560"},"modified":"2026-09-13T19:55:07","modified_gmt":"2026-09-13T23:55:07","slug":"wardogs-blue-screen-fix-driver-conflict-resolution-guide-step-by-step-practical-fix-system-thread-exception-not-handled-blue-screen-of-death-easy-anti-cheat-inputx64-sys-rgb-software-kernel-level-conf","status":"publish","type":"post","link":"https:\/\/overcentral.com\/en\/wardogs-blue-screen-fix-driver-conflict-resolution-guide-step-by-step-practical-fix-system-thread-exception-not-handled-blue-screen-of-death-easy-anti-cheat-inputx64-sys-rgb-software-kernel-level-conf\/","title":{"rendered":"WARDOGS Blue Screen Fix: SYSTEMTHREADEXCEPTION"},"content":{"rendered":"

Your PC reboots mid-match without warning. Event Viewer logs a SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E)<\/code>codecodecodecode or KMODE_EXCEPTION_NOT_HANDLED<\/code>codecodecodecode. 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 \u2014 usually an RGB lighting controller or motherboard utility. Here is the fix that actually works<\/a>, step by step, no fluff.<\/p>\n

Step 1: Pinpoint the Offending Driver in Event Viewer<\/h2>\n

After the crash reboot, do not launch the game again. Open Event Viewer (eventvwr.msc<\/code>codecodecodecode). Navigate to Windows<\/a> Logs > System<\/strong>. Filter by the timestamp of the crash. Look for a red exclamation mark<\/strong> with event ID 1001 or 1000. The error message will list a module name \u2014 often inputx64.sys<\/code>codecodecodecode, rgbalancer.sys<\/code>codecodecodecode, or mbam.sys<\/code>codecodecodecode (Malwarebytes kernel driver).<\/p>\n

In the last WARDOGS closed beta<\/a>, the most common culprit was inputx64.sys<\/code>codecodecodecode \u2014 a driver installed by RGB software like Asus Aura, MSI Mystic Light, or any lighting control app that uses the poutx64.sys<\/code>codecodecodecode variant. Do not guess. Find the exact file name from Event Viewer. That driver is what the anti-cheat service refuses to coexist with.<\/p>\n

Step 2: Disable the Killer Service \u2013 No Uninstall Required<\/h2>\n

You can stop the service without deleting the RGB software. Open an administrator Command Prompt<\/strong> and run these two commands (replace inputx64<\/code>codecodecodecode with whatever Event Viewer reported):<\/p>\n

“`<\/p>\n

sc stop inputx64<\/p>\n

sc config inputx64 start=disabled<\/p>\n

“`<\/p>\n

Run sc query inputx64<\/code>codecodecodecode to confirm the state says STOPPED<\/strong>. Then reboot. That is it. The driver will no longer load at startup. WARDOGS will launch without the BSOD.<\/p>\n

Source material confirms this exact fix: one user went from crashing every few seconds to 24+ hours of stable gameplay after disabling inputx64.sys<\/code>codecodecodecode. If you later need the RGB software, re-enable it with sc config inputx64 start=auto<\/code>codecodecodecode and restart.<\/p>\n

Step 3: Enable AES-NI in BIOS \u2013 The Overlooked Instruction Set<\/h2>\n

A KMODE_EXCEPTION<\/code>codecodecodecode 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.<\/p>\n

Enter BIOS (press Del\/F2 at boot). Switch to Advanced Mode<\/strong>. The exact path varies by manufacturer:<\/p>\n\n\n\n\n\n\n\n\n
Manufacturer<\/th>\nPath to AES-NI<\/th>\n<\/tr>\n<\/thead>\n
ASUS<\/td>\nAdvanced > CPU Configuration > AES-NI<\/td>\n<\/tr>\n
MSI<\/td>\nOC > CPU Features > AES-NI<\/td>\n<\/tr>\n
Gigabyte<\/td>\nTweaker > Advanced CPU Settings > AES-NI<\/td>\n<\/tr>\n
ASRock<\/td>\nAdvanced > CPU Configuration > AES-NI<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Toggle to Enabled<\/strong>, press F10 to save and reboot. This single change eliminated BSOD for many WARDOGS testers running on Intel<\/a> 8th\/9th gen CPUs. If the option is missing, your motherboard forces it on permanently \u2014 skip this step.<\/p>\n

Step 4: Disable Memory Integrity and Virtualization-Based Security (But Know the Cost)<\/h2>\n

Windows 11\u2019s Core Isolation > Memory Integrity<\/strong> can conflict with Easy Anti-Cheat\u2019s kernel-level hooks. Type core isolation<\/code>codecodecodecode in the start menu, open it, and turn Memory Integrity<\/strong> off. You must restart.<\/p>\n

More aggressive: disable Virtual Machine Platform<\/strong> and Windows Hypervisor Platform<\/strong> under Turn Windows features on or off<\/strong>. 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.<\/p>\n

The trade\u2011off: you lose a security boundary. Memory integrity prevents certain exploits from writing to kernel memory. But if you only play WARDOGS and don\u2019t run untrusted executables, the risk is minimal. Re\u2011enable these after you stop playing if security is a concern.<\/p>\n

Comparison: Three Advanced Fixes at a Glance<\/h2>\n\n\n\n\n\n\n\n
Fix Method<\/th>\nComplexity<\/th>\nReversibility<\/th>\nSuccess Rate (self\u2011reported)<\/th>\n<\/tr>\n<\/thead>\n
Disable inputx64.sys<\/code>codecodecodecode driver<\/td>\nMedium (requires admin CMD)<\/td>\nFull (re\u2011enable via sc config<\/code>codecodecodecode)<\/td>\n~85% of cases where Event Viewer showed inputx64<\/code>codecodecodecode<\/td>\n<\/tr>\n
Enable AES\u2011NI in BIOS<\/td>\nLow (one BIOS toggle)<\/td>\nFull (toggle back)<\/td>\n~40% \u2013 works mainly on older boards with the feature disabled<\/td>\n<\/tr>\n
Disable Memory Integrity + Virtualization<\/td>\nLow (Windows settings)<\/td>\nFull (re\u2011enable)<\/td>\n~30% \u2013 helps when other fixes fail, but security impact<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

None of these fixes require reinstalling the game or Windows. Run them in order. Most users need only Step 2.<\/p>\n

What About Windows Insider Builds and Recent Updates<\/h2>\n

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<\/strong> and pause further updates until a permanent patch ships. Go to Settings > Windows Update > Update History > Uninstall updates<\/strong>, find KB5121003, remove it, and restart. Then disable Insider preview builds.<\/p>\n

If you are on a stable Windows 11 24H2 release, the update is not the issue \u2014 the RGB driver is.<\/p>\n

Final Non\u2011Obvious Note<\/h2>\n

The inputx64.sys<\/code>codecodecodecode driver is notorious for re\u2011enabling itself after a Windows feature update or a software reinstall. To avoid surprises, create a simple batch file with the sc stop<\/code>codecodecodecode and sc config<\/code>codecodecodecode commands and place it in your startup folder \u2014 but set it to run after<\/strong> the driver has loaded. Better yet, rename the driver .sys<\/code>codecodecodecode file to .bak<\/code>codecodecodecode inside C:WindowsSystem32drivers<\/code>codecodecodecode after<\/strong> stopping the service. That makes re\u2011enablement impossible without manual intervention. Only do this if you are comfortable with file system changes.<\/p>\n

The WARDOGS SYSTEM_THREAD_EXCEPTION is not a bug in the game \u2014 it is a collision between modern anti\u2011cheat and legacy hardware abstraction drivers. Identify the specific file, shut it down, and never see the blue screen again.<\/p>\n","protected":false},"excerpt":{"rendered":"

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 \u2014 usually an RGB lighting controller […]<\/p>\n","protected":false},"author":7,"featured_media":81696,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"fifu_image_url":"https:\/\/encrypted-tbn0.gstatic.com\/images?q=tbn:ANd9GcQubtoE7szJY7hdnzWwxi1NN4z0UvbQMm9-0spr8tvsGPf4L-NQe-j7A2w&s=10","fifu_image_alt":"","footnotes":""},"categories":[2],"tags":[],"class_list":["post-81560","post","type-post","status-publish","format-standard","has-post-thumbnail","category-videogames"],"fifu_image_url":"https:\/\/encrypted-tbn0.gstatic.com\/images?q=tbn:ANd9GcQubtoE7szJY7hdnzWwxi1NN4z0UvbQMm9-0spr8tvsGPf4L-NQe-j7A2w&s=10","_links":{"self":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/81560","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/comments?post=81560"}],"version-history":[{"count":1,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/81560\/revisions"}],"predecessor-version":[{"id":88993,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/posts\/81560\/revisions\/88993"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media\/81696"}],"wp:attachment":[{"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/media?parent=81560"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/categories?post=81560"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/overcentral.com\/en\/wp-json\/wp\/v2\/tags?post=81560"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}