Windows 10: Turn On or Off Core Isolation Memory Integrity in Windows 10

I have posted my experience with switching core isolation memory "on" in the Insider thread, but those threads get buried away real quick, so think maybe I post it here, too.

After manually switching the setting to "on", everything looked OK for a while, just "off" switch was greyed of. During the night, when system went to sleep, it froze. After wake (start up really) system resources went crazy (CPU up to 100%) mostly taken by system and diagnostic services.





Symptoms: GSOD (or BSOD - light blue really *Confused) at restart with reference to ACPI.SYS crash dump shows:
Code: Crash dump directories: C:\WINDOWS C:\WINDOWS\Minidump On Sun 15. 04. 2018 00:55:19 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\Minidump\041518-23796-01.dmp This was probably caused by the following module: ntoskrnl.exe (nt+0x112253) Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8030BA2E57A, 0xFFFF8089609776C8, 0xFFFF808960976F10) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M file path: C:\WINDOWS\system32\ntoskrnl.exe product: Microsoft® Windows® Operating System company: Microsoft Corporation description: NT Kernel & System Bug check description: This indicates that a system thread generated an exception which the error handler did not catch. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. On Sun 15. 04. 2018 00:55:19 your computer crashed or a problem was reported crash dump file: C:\WINDOWS\MEMORY.DMP This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x5055) Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8030BA2E57A, 0xFFFF8089609776C8, 0xFFFF808960976F10) Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch. The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time. -------------------------------------------------------------------------------- Conclusion -------------------------------------------------------------------------------- 2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.[/quote] Manually switched the setting to "off" by changing the registry key (same as option 2 in this tutorial) and system resources became a bit more available, but still up to 60% CPU, taken by diagnostic and system alone - after couple of restarts that is.

Resource monitor showed, that sleepstudy log was filled and taken resources, so I manually disabled diagnostic (services...), but it came up after some time. This was going on for hours.

Problem resolved after manually triggering sleepstudy with
Code: powercfg /sleepstudy[/quote] *Arrow Generate Sleep Study Report in Windows 10 Windows 10 Tutorials

and put system to sleep, then wake it up.

All fine after that

 

Click to enlarge

 

At least we have the .reg file to use. *Smile

 

*Thumbs

 

I just got this update:




Then rebooted, and after the reboot Core Isolation was turned OFF.
So I turned it back on, rebooted, again, hoping maybe the switch will let you turn it off, meaning the bug or feature, was fixed.

No chance*Sad