AsIO3.sys error message Can't open AsIO3.sys!! IsASUSMB.exe
AsIO3.sys error message Can't open AsIO3.sys!! IsASUSMB.exe
I powered on my PC and encountered this error right away! I removed Armory Crate using the uninstaller from Asus' website and reinstalled it, but the problem persists during installation. Now, when installing Armory Crate, the error appears again. After completing the setup on Asus Armory Crate, it opens and then stops working. I've tried running sfc scannow and checkdsk, but nothing works. I also attempted to uninstall it in safe mode, yet the issue remains after installation. Any suggestions?
The issue appears to come from the AacAIOFanSetup in Roguelike II 360, but a solution hasn't been found yet.
You're facing the same issue repeatedly, unsure of the cause. Your PC started after a week off and you updated several drivers using Armoury Crate. After the updates, you kept seeing "can't open AsIO3.exe" errors. You've tried removing Armoury Crate with both the uninstaller and Revo Uninstaller, reinstalling it, but the problem persists, especially when accessing the AIO Fan Setup. It seems Armoury Crate is malfunctioning again, possibly needing a newer update.
Same problem again. Just like yesterday, when I turned on the PC, I got a warning about "can't open asio3.sys". In Armoury Create my left side was missing, some options disappeared. My hardware list showed the motherboard (b450f Gaming) but not my mouse (ROG Spatha X), keyboard (ROG Strix Flare), GPU (ROG 3060) and AIO (Ryujin 240). (List the parts if you need to track the issue) Usually Armoury Create causes trouble, so I used the uninstall tool and reinstalled, but now it’s getting worse. Either the same warning appears or I see a black screen with nothing, just the logo and no buttons. One user on Reddit mentioned disabling "asuscertservice.exe" but the service is still stopped and set to automatic start. When I right-click > start it shows a warning: "Windows can't start AsusCertService in the local machine. Error 2: The system can't find the specific file." All this happened before a full uninstall with the Armoury Create tool and a new install.
I discovered the issue behind our problems, unfortunately it’s not a good sign. Windows’ memory integrity and kernel-mode hardware protection are incorrectly marking something Armoury Crate calls an "attack." There’s no simple solution—either wait for a fix from Microsoft or ASUS, or you can disable memory integrity, which is not advised since it’s crucial for keeping your system virus-free. I hope this information helps everyone.