0x00000016 KERNEL_LOCKED_PAGES_IN_MEMORY Blue Screen Fix Guide (Windows 10/11)

Understanding the 0x00000016 KERNEL_LOCKED_PAGES_IN_MEMORY Blue Screen

The KERNEL_LOCKED_PAGES_IN_MEMORY (0x00000016) blue screen error, also known as a BSOD or “blue screen of death,” occurs when Windows encounters a critical system failure. This specific stop code indicates that the operating system has attempted to lock pages in memory but failed due to insufficient privileges or other issues. When this happens, your computer will crash and display the error on a blue background.

This guide covers what the error means, its common causes, step-by-step fixes, and answers frequently asked questions to help you resolve it without technical jargon.

What Does 0x00000016 Mean?

The KERNEL_LOCKED_PAGES_IN_MEMORY error suggests that Windows is trying to secure certain memory pages for system use, but the process cannot proceed because of a lack of necessary permissions. This often happens when:

• Antivirus or security software interferes with memory management.
• Corrupted system files prevent proper memory locking.
• Outdated or incompatible drivers cause conflicts.
• Hardware issues, such as RAM errors, trigger the error.

The error can appear during normal operation, startup, or while running specific applications. It is typically accompanied by a dump file that records system details at the time of the crash, which can be useful for deeper analysis if needed.

Common Causes of 0x00000016

The KERNEL_LOCKED_PAGES_IN_MEMORY BSOD is usually linked to one or more of the following issues:

• Antivirus or Security Software Conflicts: Some security programs aggressively lock memory, which can interfere with Windows’ ability to manage it properly.
• Corrupted System Files: Damaged system files, such as those related to the kernel or drivers, may prevent proper memory operations.
• Outdated or Incompatible Drivers: Graphics card, chipset, or other hardware drivers that are not updated can cause this error.
• RAM Issues: Faulty RAM modules or incorrect settings in the BIOS can lead to memory-related crashes.
• Windows Updates or System Restore Problems: A failed update or restore process might leave your system in an unstable state, causing this error.
• Third-Party Software Conflicts: Programs like VPN clients, disk utilities, or other system tools may conflict with memory management.

Step-by-Step Fixes for KERNEL_LOCKED_PAGES_IN_MEMORY

Follow these methods in order to resolve the 0x00000016 BSOD. Start with the simplest steps and proceed if the issue persists.

Method 1: Disable Antivirus or Security Software Temporarily

The most common cause of this error is antivirus software that locks memory too aggressively. To test this:

• Open your antivirus program and look for settings related to “memory protection” or “locked pages.”
• Temporarily disable these features or set them to a less restrictive mode.
• Restart your computer and check if the error persists. If it does not, re-enable the antivirus with adjusted settings.
• If the issue is resolved, consider switching to a different antivirus program that does not lock memory as aggressively.

Method 2: Run System File Checker (SFC) and DISM

System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools scan for corrupted system files and repair them automatically. These are essential steps if the error is caused by file corruption.

• Open Command Prompt as Administrator:

  Win + X

  • Select “Command Prompt (Admin)” or “Windows Terminal (Admin).”

  Run the SFC scan:

  sfc /scannow

  Wait for the process to complete. If no issues are found, proceed to run DISM.

  Run the DISM scan in one of these two ways (choose only one):

  DISM /Online /Cleanup-Image /RestoreHealth

  DISM /Image:C:\ /Cleanup-Image /RestoreHealth

  Restart your computer after both scans finish.

  Method 3: Update or Reinstall Drivers

  Outdated drivers, especially for graphics cards or chipsets, can trigger this error. To update them:

  • Press Win + X and select “Device Manager.”
  • Expand the categories such as “Display adapters,” “System devices,” or “Other devices.”
  • Right-click on any device with a yellow exclamation mark (e.g., graphics card) and select “Update driver.”
  • Choose “Search automatically for drivers” and let Windows install the latest version.
  • If updating doesn’t resolve the issue, try reinstalling the driver by right-clicking it again and selecting “Uninstall device,” then restart your computer to force a reinstall.

  Method 4: Check for RAM Issues

  Faulty RAM can cause memory-related BSODs. To diagnose this:

  • Open Command Prompt as Administrator and run the following command:

    mdsched.exe

    • This opens the Windows Memory Diagnostic tool.
    • Select “Restart now and check for problems (recommended).”

    Follow the on-screen instructions to complete the memory test. If errors are found, replace or reseat your RAM modules.

    Method 5: Perform a Clean Boot

    A clean boot starts Windows with only essential drivers and services, helping identify if third-party software is causing the error.

    • Press Win + R, type msconfig, and press Enter.
    • Go to the “Services” tab and check “Hide all Microsoft services.”
    • Click “Disable all,” then go to the “Startup” tab and click “Open Task Manager.”
    • In Task Manager, disable all startup items by right-clicking them and selecting “Disable.”
    • Restart your computer in clean boot mode.
      • If the error doesn’t occur during a clean boot, gradually re-enable drivers and services one at a time to pinpoint the culprit.

      Method 6: Check BIOS Settings

      Incorrect BIOS settings can affect memory stability. Ensure your RAM is set correctly:

      • Restart your computer and enter BIOS (usually by pressing Del, F2, or Esc during startup).
      • Look for options like “Memory Voltage,” “Timing Settings,” or “XMP/DOCP.”
      • Set these to default values unless you have a specific reason to use custom settings.
      • Save changes and exit BIOS. Restart your computer to see if the error persists.

      Method 7: Roll Back Windows Updates or System Restore

      If the error started after a recent update or system restore, rolling back can help:

      • Press Win + R, type msconfig, and press Enter.
      • Go to the “Tools” tab and click “Uninstall updates.”
      • Select the most recent update and click “Uninstall.”
      • Restart your computer. If the error is resolved, check for new updates before installing them again.
      • If rolling back doesn’t work, use System Restore to revert to a stable state:

        rstrui
        
        
        
        Last Updated: December 07, 2025
        
        Tested on: Windows 10 (22H2) & Windows 11 (23H2)