Asrdrv106.sys Error | Stop Memory Integrity Blocking It

What Is The Asrdrv106.sys Driver Issue?

On many modern Windows 10 and Windows 11 systems, this error shows up as a small notification saying that a driver cannot load on this device. The message usually points to security features, not to a broken installation. It is Windows telling you that the driver behind some ASRock utilities is on the vulnerable driver block list and is being held back to keep the system safer.

The file asrdrv106.sys belongs to low level motherboard tools from ASRock, such as RGB control apps or tuning utilities. These tools need deep access to hardware, so they ship a kernel driver. When Microsoft or security researchers later mark that driver as vulnerable, Windows Security, Memory Integrity, and the Microsoft vulnerable driver blocklist start to block it during boot. That is why the alert repeats even when the computer seems to run fine.

The good news is that this type of driver error is usually about compatibility and risk management, not about instant hardware failure. Your goal is to decide whether you really need the ASRock utility, try to update it if you do, and then cleanly remove or disable the old driver so that Windows Security stops warning you.

Asrdrv106.sys Error Fixes On Windows 10 And 11

Before diving into detailed steps, it helps to see the main ways you can deal with this driver warning on a Windows desktop or laptop. You can either update the driver, remove the software that installed it, or make a careful change to how strict Windows is about vulnerable drivers. Start with the least risky changes and only relax security if you fully understand the trade off.

Fix	Use It When	Risk Level
Update ASRock tools and drivers	You still want RGB, tuning, or monitoring features from ASRock.	Low
Uninstall ASRock utility that added the driver	You do not need the extra features and only want the warning gone.	Low
Turn off Memory Integrity or the vulnerable driver blocklist	You fully trust the driver and accept lower protection for that device.	Higher
Remove or rename asrdrv106.sys manually	Updates or uninstall attempts did not help and the alert keeps showing.	Medium

Each method below stays close to official Windows guidance while still giving you practical, step by step instructions. Start with updates and software removal before you touch any core isolation or driver blocklist settings.

Update Or Remove ASRock Utilities That Use Asrdrv106.sys

The cleanest way to clear this driver warning is to update or uninstall the ASRock utility that installed the driver in the first place. That way you stay aligned with Microsoft security rules and avoid weakening core isolation on your machine.

Check Which ASRock Apps Are Installed

Many systems include RGB lighting tools or motherboard tuning apps that quietly add the asrdrv106.sys driver. You need to identify these first so you know what to update or remove.

• Open Installed Apps — Press Win + I, select the settings gear, then open Apps and go to the installed apps list.
• Look For ASRock Entries — Search the list for names such as ASRock Polychrome RGB, ASRock A Tuning, or other ASRock utilities related to your motherboard.
• Confirm You Use Them — Ask yourself if you really adjust RGB, fan curves, or tuning profiles with these tools. If you never open them, they may not be worth the extra driver risk.

Update ASRock Tools From The Official Site

If you rely on the RGB or tuning features, your first step should be to update the tools so they include a newer, fixed driver that Windows no longer flags as vulnerable.

• Find Your Motherboard Support Page — Visit ASRock support in a browser, search for your exact board model, and open its support page.
• Download The Latest Utilities — Go to the downloads section and pull the newest versions of RGB, tuning, or monitoring tools that match your system.
• Install Over The Old Versions — Run each installer as an administrator and let it replace previous builds of the same utility.
• Restart And Watch For Alerts — After a reboot, watch Windows Security notifications to see if the warning still appears.

Uninstall ASRock Utilities You Do Not Need

If updates do not help or you simply do not care about the extra lighting and tuning features, uninstalling the utilities is often the fastest way to stop the warning on every startup.

• Open Settings Apps — Press Windows + I, open Apps, then choose the installed apps view.
• Remove RGB Or Tuning Tools — Select each ASRock utility you no longer use and choose Uninstall, then follow the prompts.
• Reboot The Computer — Restart to give Windows a chance to remove the asrdrv106.sys driver from active use.
• Check Windows Security Again — Open Windows Security, go to Device security, and confirm that the vulnerable driver warning for asrdrv106.sys no longer appears.

In many cases, removing a single RGB utility is enough to clear the driver cannot load warning without touching any advanced security settings.

Adjust Windows Security Settings Safely

Windows 10 and Windows 11 include security features such as Memory Integrity and the Microsoft vulnerable driver blocklist that stop risky kernel drivers from loading. These are the same features that flag the asrdrv106.sys driver as unsafe and show a driver cannot load on this device notices near the clock. You can change these settings, but any change needs to be thoughtful.

Review Memory Integrity Status

Memory Integrity is part of core isolation. It helps prevent attacks that try to run code in protected parts of memory. It can also block drivers like asrdrv106.sys if they do not meet current security standards.

• Open Windows Security — Click the shield icon in the taskbar or search for Windows Security from the Start menu.
• Go To Device Security — In the left menu, choose Device security, then select Core isolation details.
• Check Memory Integrity — Look at the Memory Integrity toggle. When it is on, Windows enforces stricter driver rules and may list asrdrv106.sys as blocked.

Turning off Memory Integrity can let a blocked driver load, but it also lowers protection against some attacks. For most people, it is better to update or remove the driver than to disable this feature long term.

Decide Whether To Change The Vulnerable Driver Blocklist

The vulnerable driver blocklist holds driver names and hashes that Microsoft and security partners have flagged as unsafe. On recent Windows builds it is enabled by default and closely tied to core isolation settings. When asrdrv106.sys is on this list, Windows stops it before it can run, even if the rest of the utility seems harmless.

• Stay With The Default Setting — For most home users, leaving the blocklist on gives a good balance between daily use and protection.
• Only Disable As A Last Resort — If you must run older software that still depends on asrdrv106.sys, and you fully trust the source, you can temporarily turn the blocklist off from the same core isolation screen, then restart.
• Turn Protection Back On Later — Once you finish the task that needed the older driver, return to Windows Security and enable the blocklist again to restore the normal safety level.

This type of change should be rare. Treat it like a short detour, not a permanent setup, because newer drivers and tools usually exist that work fine with Memory Integrity and the blocklist turned on.

Clean Up The Asrdrv106.sys Driver File If Needed

Sometimes the ASRock utilities are gone but Windows still reports this driver error during security checks. That can happen when the driver file remains in the system drivers folder or when an old service entry keeps trying to call it. In that case you may need a more direct clean up.

Create A Restore Point First

Driver changes touch low level parts of the operating system. A quick restore point makes it easier to reverse them later if something behaves oddly.

• Open System Protection — Search for Create a restore point from Start and open the matching control panel entry.
• Choose Your System Drive — Select the drive that shows System in the list and click Create.
• Name And Save The Point — Give the restore point a short name like Before driver cleanup and let Windows finish the snapshot.

Look For The Asrdrv106.sys File

With a restore point in place, you can search for the file and decide whether to rename or delete it. Renaming is safer because you can change it back if some tool still depends on it.

• Open A File Window — Press Windows + E to open a new file window.
• Browse To The Drivers Folder — Go to C:\Windows\System32\drivers and search within that folder for asrdrv106.sys.
• Rename The File — If you find it and no ASRock tools remain on the system, rename it to asrdrv106.old so that Windows no longer loads it.
• Restart And Watch For Errors — After a reboot, check whether the driver cannot load message still appears or whether any hardware feature is missing.

If something breaks or a feature you still need vanishes, you can rename the file back or restore the snapshot you created. If nothing changes aside from the warning going away, you have safely removed the leftover driver.

Prevent Future Driver Block Messages

Once the immediate driver warning is under control, it is worth taking a few small steps that make driver warnings less likely in the future. The same habits that help with this issue will also reduce surprise alerts for other vulnerable drivers.

• Keep Motherboard Drivers Current — Visit your board maker support page a few times a year to pull new chipset, storage, and utility updates that work well with recent Windows builds.
• Limit Extra Tuning Utilities — Install only the ASRock tools you truly use. The fewer third party kernel drivers you load, the fewer chances you give attackers and the fewer blocklist alerts you see.
• Use Windows Update Regularly — Let Windows install quality updates that refresh the vulnerable driver blocklist and core security features so you get better protection with less noise.
• Avoid Random Driver Packs — Skip driver bundles from unknown sites that promise quick fixes. Stick to Windows Update and the official support pages for your hardware.

Handling an asrdrv106.sys error is mostly about pruning older utilities and working with Windows Security instead of against it. Once your drivers and ASRock tools match what current versions of Windows expect, the system settles down and the driver cannot load on this device alerts stop repeating.