I cannot enable Memory Integrity

Question

Every time I enable memory core isolation and restart my pc I get the bluescreen of death.

stop code:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

what failed:ACPI.sys

what could I do to fix this?

https://www.mediafire.com/file/gje45irc6xoablh/060926-11703-01.dmp/file

I went on event viewer and deleted everything that was giving me issues but im still having issues.

I have the Tuf Gaming B550M- Plus (wifi) motherboard and on BIOS 1401 would I need to upgrade for it to work

Answer 1

Hi ,

Search for msinfo32.exe in the search bar, take a screenshot, and post it here so we can see the correct laptop model or desktop configuration.

Thanks

Answer 2

Enabling Memory integrity (HVCI) can expose incompatibilities in device drivers, firmware, or hardware. When those components are not fully compatible, Windows can crash with a blue screen during or after enabling Memory integrity.

From the provided context, the supported remediation paths for Memory integrity–related crashes are:

1. Update all relevant drivers and firmware
   • Update display/video drivers and other device drivers using Windows Update or from the device/motherboard/computer manufacturer.
   • If updating from Windows Update does not help, check the motherboard or PC vendor support site for newer chipset, storage, and other drivers.
   • In similar cases, updating BIOS/UEFI firmware has resolved blue screen issues after enabling security features.
2. Check for drivers blocked or affected by Memory integrity
   • Open Event Viewer and go to: Applications and Service Logs > Microsoft > Windows > CodeIntegrity > Operational
   • Look for events with Event ID 3087 or other Code Integrity events that indicate drivers blocked by Memory integrity. These can point to the specific driver causing instability.
3. If the system becomes unstable or fails to boot after enabling Memory integrity
   • Use the Windows Recovery Environment (Windows RE) to turn Memory integrity off at the registry level:
     1. Boot into Windows RE on the affected PC (for example, by interrupting normal boot several times until Recovery appears).
     2. Disable any policies that were used to enable VBS/Memory integrity (for example, Group Policy) if applicable.
     3. In Windows RE, open Command Prompt and run:

                reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v "Enabled" /t REG_DWORD /d 0 /f
        

     4. Restart the device.
4. Verify Memory integrity state and compatibility
   • Memory integrity status can be checked in:
     • Windows Security → Device Security → Core isolation → Core isolation details (Memory integrity toggle).
     • msinfo32 under Virtualization-based Security Services Running.
   • If Memory integrity cannot be enabled due to incompatible drivers, Windows Security will typically indicate that an incompatible driver is installed. In that case, check with the device or driver manufacturer for an updated, compatible driver, or remove the device/software that uses that driver.
5. If no compatible drivers/firmware are available
   • Some devices or drivers may not yet support Memory integrity. In that case, the supported options are:
     • Leave Memory integrity Off to maintain system stability, or
     • Remove or replace the incompatible hardware/software if Memory integrity must be kept On.

Because the context does not include specific guidance for ACPI.sys on a particular motherboard or BIOS version, the general supported approach is: update BIOS/UEFI and all drivers from the manufacturer, check Code Integrity logs for blocked drivers, and if crashes persist with Memory integrity enabled, keep Memory integrity disabled until compatible updates are available.

---

References:

• Enable virtualization-based protection of code integrity
• Memory integrity and VBS enablement
• Device Security in the Windows Security App
• A driver can't load on this device
• Troubleshooting Windows unexpected restarts and stop code errors
• Updating to Windows 10, version 2004 on devices with Hypervisor-protected code integrity (HVCI) enabled