sodcalculator

10 Tech How-To

Windows Crashing: Memory Integrity Fixes

Guide 10-57164 · Updated · Step by step

If Windows is crashing with a blue screen after you enable Memory Integrity (Core Isolation), the feature is conflicting with an incompatible driver or app. The fix is to identify the culprit, update or remove it, and then re-enable Memory Integrity safely.

What Memory Integrity Does

Memory Integrity is a Windows security feature that runs kernel-mode code integrity checks inside a hardware-isolated environment using Virtualization-Based Security (VBS). It prevents untrusted drivers and malware from injecting code into the Windows kernel. When enabled, it creates a memory sandbox that only allows signed, validated code to run at the highest privilege level. This significantly reduces the attack surface for exploits that target kernel vulnerabilities.

However, because the feature enforces strict code signing and integrity rules, any driver or application that uses unsupported or outdated kernel hooks can trigger a system crash (BSOD) when Memory Integrity is on. This is a known trade-off: stronger security can break compatibility with older or poorly written software.

Why It Causes Crashes

The most common cause of a crash after enabling Memory Integrity is an incompatible driver. Drivers that are not WHQL-signed, use obsolete kernel APIs, or rely on techniques like kernel patching will be blocked. When Windows detects a violation, it may halt the system to prevent further damage, resulting in a blue screen with an error like MEMORY_INTEGRITY_VIOLATION or KERNEL_SECURITY_CHECK_FAILURE.

Other triggers include:

  • Outdated graphics or audio drivers that use legacy kernel interfaces.
  • Third-party antivirus or security software that installs kernel filters.
  • Virtual machine tools (like VirtualBox or VMware) that load kernel modules.
  • Game anti-cheat systems that modify kernel memory.

Even if a driver was fine before, a Windows update or a driver update can change its behavior, making it incompatible with Memory Integrity.

How to Fix the Crash

If you are stuck in a boot loop or the system crashes immediately after enabling Memory Integrity, you need to disable it first to regain access. Here are the steps:

  1. Boot into Safe Mode: Restart your PC, and at the lock screen, hold Shift while clicking Power > Restart. Then navigate to Troubleshoot > Advanced options > Startup Settings > Restart, and press 4 or F4 to enter Safe Mode.
  2. Open Windows Security > Device security > Core isolation details.
  3. Toggle Memory Integrity to Off and restart normally.

Once you are back in Windows, update all your drivers, especially the ones for your chipset, GPU, and network adapter. You can also use Windows Update to get the latest drivers automatically. After updating, re-enable Memory Integrity and see if the crash returns.

Finding the Problem Driver

If updating drivers doesn’t help, you need to identify which driver is causing the conflict. Windows Event Viewer logs the crash details. To find the culprit:

  1. Open Event Viewer (search for it in the Start menu).
  2. Go to Windows Logs > System.
  3. Look for errors with source BugCheck or Kernel-Power around the time of the crash.
  4. Note the bug check code and the parameter that includes the driver name (often in the fourth parameter).

You can also use the Memory Integrity page in Windows Security: it lists incompatible drivers under Review incompatible drivers when they are detected. If you see a driver listed, update or uninstall it from Device Manager.

For a more thorough analysis, use WinDbg to open the minidump file in C:\Windows\Minidump. The !analyze -v command will often reveal the offending driver.

Prevention and Best Practices

To avoid crashes in the future, keep your system and drivers up to date. Enable Memory Integrity only after ensuring all critical drivers are current. If you rely on older hardware or specialized software, check the manufacturer’s website for compatibility notes.

  • Always install Windows updates, as they often include driver fixes.
  • Use the Optional updates section in Windows Update to get driver updates.
  • If you use virtualization software, update it to the latest version that supports VBS.
  • Consider removing unused drivers or devices that are no longer needed.

Should You Keep It On or Off?

Memory Integrity is a valuable security feature, but it is not mandatory. If you cannot resolve the crashes, you may choose to keep it off. However, this leaves your system more vulnerable to kernel-level attacks. Weigh the risk: if you are a typical home user with up-to-date drivers, enabling it is worth the effort. If you are a gamer using anti-cheat software that conflicts, you might need to wait for the game or driver vendor to release a compatible version.

You can also enable Core Isolation (the parent feature) without Memory Integrity, but that provides less protection. The best approach is to fix the driver issue rather than permanently disabling the feature.

Frequently Asked Questions

Q: Will disabling Memory Integrity void my Windows warranty?
No, it is a user-configurable setting. It does not void any warranty, but it reduces security.

Q: Can I enable Memory Integrity after a crash without losing data?
Yes, you can re-enable it after fixing the driver. Your files are not affected by toggling the feature.

Q: Why does my PC crash only when playing a specific game?
That game’s anti-cheat software may use kernel drivers that are incompatible with Memory Integrity. Check the game’s support site for updates or workarounds.

Q: How do I check if my drivers are compatible before enabling?
Windows Security will show a warning if it detects incompatible drivers. You can also run msinfo32 and look at Virtualization-based Security to see if the feature is running properly.

Q: Is there a way to enable Memory Integrity without a restart?
No, the change requires a restart to take effect.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →