KERNEL_SECURITY_CHECK_FAILURE

Possible solutions

Choose the method that matches your situation. Start with the simplest suitable option and check the result. If the problem is fixed, you do not need to continue with the other methods.

1. Checking the driver or security program

   If the error occurs after the change, roll it back or use a compatible update.

   Steps to follow

   1. Remember what you installed or updated before the first failure. Write down the name of the app or device.
   2. If it's an app, go to Settings > Apps > Installed apps and find just that app. Save her documents first.
   3. Use its official update or "Remove". If it's a driver, in Device Manager, select its Properties > Driver > Roll back driver if allowed.
   4. Reboot and check if the same error occurs again. If you don't know the change, don't uninstall random programs or drivers.

2. RAM test

   If the origin of the error is unclear, check the memory in standard modes.

   Steps to follow

   1. Save open documents; the test will reboot the computer.
   2. Press the Windows key and R together, type mdsched.exe and press Enter.
   3. Select reboot and check for problems now. Let the test finish, do not turn off the computer.
   4. When you return to Windows, note whether any errors are displayed. If so, don't try to change the modules at random - pass the result to the master. A successful short test does not rule out all failures.

3. Restoring system files

   In a running Windows with a stable disk, use DISM and then SFC as administrator.

   Steps to follow

   1. Click on Start and type "cmd" in the search.
   2. Select "Run as administrator" and confirm if prompted.
   3. Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter.
   4. Wait for the completion and success message; do not close the window.
   5. In the same window, type sfc /scannow and press Enter.
   6. When the check is complete, write down the result, reboot and repeat the problem. If the first command returns an error, pass its text to the master; do not apply bootloader to Windows in the /Online recovery environment.