Fix Memory Integrity BSOD in Windows 11

If you are getting a Blue Screen of Death (BSOD) after enabling Memory Integrity in Windows 11, the fix is usually to update incompatible drivers, disable the feature temporarily, or run a clean driver install. This article explains why the conflict happens and walks you through the most reliable solutions, from quick checks to more thorough driver cleanups.

What Is Memory Integrity and Why Does It Cause BSOD?

Memory Integrity is a Windows 11 security feature that is part of Core Isolation. It uses hardware virtualization to run kernel-mode processes in an isolated environment, preventing malicious code from injecting into high-integrity processes. When enabled, the system checks that all drivers are compatible with this virtualization-based security. If a driver is not designed to work with Memory Integrity, the system may fail to load it, and in some cases, the conflict triggers a BSOD with a stop code like MEMORY_INTEGRITY_VIOLATION or DRIVER_VERIFIER_DMA_VIOLATION.

The feature is off by default on most Windows 11 installations, but some PCs ship with it enabled, or users turn it on manually. The BSOD usually appears during boot or shortly after signing in, making the system unstable or unusable.

Before You Start: Quick Checks

• Update Windows: Go to Settings > Windows Update and install all pending updates. Microsoft regularly fixes compatibility issues with driver and security updates.
• Update your drivers: Use the manufacturer’s update utility (e.g., Intel Driver & Support Assistant, AMD Software, or the PC maker’s update app) to get the latest versions of chipset, GPU, network, and storage drivers.
• Check for known issues: If your PC model has a known issue with Memory Integrity, the manufacturer’s support page will usually mention it. Search for your model plus “Memory Integrity BSOD”.

How to Temporarily Disable Memory Integrity

If you need to get back into Windows immediately, disabling the feature is the fastest fix. This is a temporary measure; you should re-enable it after resolving the driver conflict.

1. Boot into Windows. If the BSOD happens before you can sign in, boot into Safe Mode: restart your PC, and at the sign-in screen, hold Shift while clicking the Power icon > Restart. Then go to Troubleshoot > Advanced options > Startup Settings > Restart, and press 4 or F4 to enter Safe Mode.
2. Open Windows Security (shield icon in the system tray).
3. Go to Device security > Core isolation details.
4. Toggle Memory integrity to Off.
5. Restart your PC. The BSOD should be gone.

Note: If the toggle is greyed out, it may be controlled by your organization or by the PC manufacturer. In that case, you may need to check with your IT admin or consult the manufacturer’s documentation.

Find the Incompatible Driver

Disabling Memory Integrity is a workaround, not a fix. To keep the security feature on, you need to identify which driver is causing the conflict. Here are the most reliable ways:

• Check the event log: Open Event Viewer (Win + R, type eventvwr). Go to Windows Logs > System and look for errors with source “Kernel-PnP” or “Microsoft-Windows-CoreIsolation”. The error details often mention the offending driver file (e.g., xxx.sys).
• Use Driver Verifier (advanced): This built-in tool can stress-test drivers and pinpoint the faulty one. Run verifier as administrator, choose “Create custom settings”, then select all checks except “Low resource simulation”. Next, select “Select driver names from a list” and choose all non-Microsoft drivers. Restart and let the system run; the BSOD that appears will usually name the driver. Afterward, turn off Driver Verifier by running verifier /reset in an admin command prompt.
• Check the minidump files: Use a tool like BlueScreenView (free) to read the .dmp files in C:\Windows\Minidump. The dump will often list the crashing driver.

Fix the Incompatible Driver

Once you know which driver is at fault, you have several options:

• Update the driver: Download the latest version from the manufacturer’s website, not from Windows Update if the latest is not offered there. Uninstall the old driver first (Device Manager > right-click the device > Uninstall device, check “Delete the driver software for this device”) and then install the new one.
• Roll back the driver: If the BSOD started after a driver update, roll back to the previous version: Device Manager > right-click the device > Properties > Driver > Roll Back Driver.
• Remove the driver entirely: If the device is optional (e.g., an old sound card or a third-party virtual adapter), uninstall it and see if the system is stable.
• Check for a firmware update: Sometimes the issue is with the device firmware, not the driver. Visit the manufacturer’s support page for a BIOS/UEFI or firmware update.

If the BSOD Persists: Clean Boot and Driver Cleanup

If you cannot identify the driver, or the BSOD continues even with Memory Integrity off, a clean boot can help isolate the problem. This starts Windows with a minimal set of drivers and startup programs.

1. Press Win + R, type msconfig, and press Enter.
2. Go to the Services tab, check “Hide all Microsoft services”, then click “Disable all”.
3. Go to the Startup tab and click “Open Task Manager”. Disable all startup items.
4. Restart. If the BSOD is gone, re-enable services and startup items one by one until you find the culprit.

For stubborn driver conflicts, use a driver cleaner tool (like Display Driver Uninstaller for graphics drivers) to completely remove leftover files and registry entries, then reinstall the latest driver. Always back up your data before doing a clean driver removal.

Re-enable Memory Integrity After the Fix

Once you have updated or removed the problematic driver, you can turn Memory Integrity back on:

1. Open Windows Security > Device security > Core isolation details.
2. Toggle Memory integrity to On.
3. Restart your PC. If the BSOD does not reappear, the fix was successful.

If the BSOD returns, you may need to repeat the driver identification process, or consider that the driver is fundamentally incompatible with Memory Integrity. In that case, you have to choose between keeping the driver (and leaving Memory Integrity off) or removing the device/driver to keep the security feature enabled.

Common Misconceptions and Tips

• “Memory Integrity is not worth it.” It adds a meaningful layer of protection against kernel-level attacks, but it is not mandatory. If you cannot resolve driver conflicts, it is acceptable to leave it off, especially if your PC is up to date and you practice safe browsing.
• “All drivers are compatible.” Not true. Older or poorly coded drivers, especially those for legacy hardware or some anti-cheat software, may not support virtualization-based security.
• “Windows Update will fix it.” Not always. Driver updates from Windows Update may be older than the ones from the manufacturer. Always check the manufacturer’s site for the latest version.
• “Safe Mode is the only way to fix it.” If you can reach the sign-in screen, you can often access Settings without Safe Mode. Safe Mode is only needed if the BSOD occurs before you can interact with the desktop.

Frequently Asked Questions

Will disabling Memory Integrity make my PC less secure?

Yes, it reduces protection against certain kernel-level attacks, but it does not leave your system defenseless. Windows Defender and other security features remain active. If you must disable it, keep your system and drivers updated to mitigate the risk.

Can I fix the BSOD without disabling Memory Integrity?

Yes, if you can identify and update the incompatible driver, you can keep Memory Integrity on. The steps above focus on finding and fixing the driver. If you cannot find it, temporarily disabling the feature is the only reliable way to stop the BSOD.

Why does Memory Integrity cause BSOD even with updated drivers?

Some drivers are not designed to work with virtualization-based security, and updating them may not change that. The manufacturer must release a specific version that is compatible. If no such version exists, the driver will always cause a conflict.

What is the stop code MEMORY_INTEGRITY_VIOLATION?

It is a specific BSOD error that occurs when a driver attempts to load into a protected memory region that is reserved for virtualization-based security. It indicates that the driver is not compatible with Memory Integrity.

Can I use System Restore to fix the BSOD?

Yes, if you have a restore point from before the BSOD started, you can use System Restore to revert your system to that state. This can undo driver changes that caused the conflict. Access it via Advanced startup options if you cannot boot normally.

Is there a way to prevent this from happening in the future?

Always install drivers from the manufacturer’s official website, keep Windows updated, and check the compatibility of drivers before enabling Memory Integrity. If you are using older hardware, verify that the manufacturer provides Memory Integrity-compatible drivers.

Related

• Set Personal Ringtones on Samsung Galaxy J5
• How to Remap the Copilot Key on Windows 11
• How to Add 3D Photos on iOS 26