Skip to content
← All errors

Please unload X.sys

WARDOGS asks you to unload a driver, or blue-screens naming a .sys file

Published Data as of Season 1 · 10 Sept 2026

This one is on your machine

The anti-cheat will not run alongside a third-party kernel driver, and the one it names is almost always RGB, motherboard or hardware-monitoring software rather than anything you installed on purpose.

What you see

A message asking you to unload a named driver, or a crash dump or blue screen that names a .sys file. Common ones are miso64.sys, AsUpIO, CmUpx.sys and ssgdio64.sys.

Also reported as: please unload · miso64.sys · CmUpx.sys · ssgdio64.sys · AsUpIO

Fixes, in the order worth trying

Work top to bottom and stop when the game launches. Each step is labelled with how much evidence sits behind it, so you can skip the guesses if the first ones work.

  1. 01 Read the exact driver name off the message or the dump first

    Confirmed

    Everything below depends on knowing which file it is. Write it down exactly, including the .sys, before you change anything.

  2. 02 Close ASUS Aura Sync if the name is miso64.sys

    Confirmed

    Closing it is enough — the driver stops with the application. Armoury Crate installs the same component, so check for both.

  3. 03 Stop AsUpIO from an elevated prompt

    Confirmed

    Another ASUS component. Run sc stop AsUpIO as administrator. Same family of problem as inpoutx64.sys, which has its own page.

  4. 04 Uninstall Novabench and its drivers if you have it

    Confirmed

    It leaves a kernel driver behind that the anti-cheat rejects. Removing the application alone is not always enough — take the drivers with it.

  5. 05 Leave the AMD Adrenalin overlay closed

    Confirmed

    Do not open it while the game is running. Turn its hotkeys and overlay off and use the AMD app directly instead.

  6. 06 Rename the driver only if you have positively identified it

    Confirmed

    For CmUpx.sys: rename C:\Windows\System32\drivers\CmUpx.sys to .old and reboot. Others such as ssgdio64.sys work the same way, some need Safe Mode, and C:\Windows\SysWOW64\drivers is worth checking too. If you are not certain which file it is, stop here — renaming the wrong driver can leave Windows unbootable.

Did this fix it for you?

Notes from other players who hit this code. Say what worked, what did not, and which region you are in — a fix that only works in one place is worth knowing about. Best-rated first, and there is no time limit: an answer from the first beta is still an answer.

No comments yet. Be the first to say whether this worked.

This is one fault with many faces. Easy Anti-Cheat runs at kernel level and refuses to share the machine with a set of third-party kernel drivers it does not trust, so the file it names depends entirely on what you happen to have installed. RGB suites, motherboard utilities and hardware-monitoring tools are the overwhelming majority.

The last step is the one to be careful with. Renaming a driver is a real change to Windows, and the mods maintaining this list say plainly that you should only do it to a file you have positively identified — if you are guessing, you are not ready to do it. Closing the offending application is usually enough and always reversible, so work down the list rather than starting at the bottom.

If the file named is inpoutx64.sys specifically, go to that page instead — it has its own procedure. If the machine blue-screens with INVALID_KERNEL_HANDLE rather than a driver name, stop playing and read this before anything else.

Source

WARDOGS Discord, #beta-fixes ↗

If that did not do it