How to Fix KERNEL LOCKED PAGES IN MEMORY (0X00000016) BSOD on Windows 10 & 11
The KERNEL_LOCKED_PAGES_IN_MEMORY (0x00000016) Blue Screen of Death (BSOD) is a critical error that can suddenly crash your Windows system, often without warning. This error typically occurs when the operating system attempts to access memory pages that have been locked by a driver or security feature, leading to system instability. While frustrating, this issue is usually fixable with the right troubleshooting steps. Below, well explain what causes this BSOD and provide step-by-step solutions to resolve it.
What Causes the KERNEL_LOCKED_PAGES_IN MEMORY (0x00000016) Error?
The error can stem from several underlying issues, including:
- Corrupt or outdated drivers, especially graphics, network, or storage drivers.
- Faulty or incompatible hardware, such as RAM or a failing hard drive.
- Malware or security software interfering with system memory access.
- Windows updates or system file corruption.
- Overclocking or incorrect BIOS/UEFI settings (common in gaming PCs).
- Third-party antivirus or security software blocking legitimate system processes.
The error may appear during normal operation, while gaming, or after installing updates. If you see this BSOD, your PC will restart automatically, and an error log will be generated in the C:\Windows\Minidump folder (if enabled).
How to Fix KERNEL_LOCKED_PAGES_IN MEMORY (0x00000016)
Follow these methods in order, starting with the simplest and progressing to more advanced fixes.
Method 1: Update or Roll Back Drivers
Outdated or conflicting drivers are a common cause of this BSOD. Start by updating your system drivers:
- Press Win + X and select Device Manager.
- Expand categories like Display adapters, Network adapters, or Storage controllers.
- Right-click each device, choose Update driver, then select Search automatically for drivers.
- If the issue started after a recent update, right-click the driver and select Properties. Under the Driver tab, click Roll Back Driver if available.
Method 2: Run System File Checker (SFC) and DISM
Corrupted system files can trigger this error. Use Windows built-in tools to repair them:
- Open Command Prompt as Administrator (search for “cmd,” right-click, and choose Run as administrator).
- Paste the following commands one by one, pressing Enter after each:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
- Wait for both processes to complete (this may take 1030 minutes). Restart your PC afterward.
Method 3: Run CHKDSK to Check for Disk Errors
If the error is hardware-related, a failing disk could be the culprit. Run CHKDSK to scan for errors:
- Open Command Prompt as Administrator.
- Type the following command and press Enter:
chkdsk C: /f /r
- If prompted, confirm to run the scan on the next boot. Your PC will restart automatically.
- After scanning, check for any reported errors in the Event Viewer (Win + X > Event Viewer > Windows Logs > System).
Method 4: Disable or Reinstall Antivirus Software
Some security programs (e.g., third-party antivirus) may interfere with memory access. Temporarily disable them:
- Open your antivirus softwares settings and look for an option to Disable real-time protection or Pause updates.
- Restart your PC and check if the BSOD persists. If it doesnt, whitelist Windows system processes in your antivirus.
- If needed, uninstall the software via Settings > Apps > Installed apps, then reinstall a trusted alternative (e.g., Windows Defender).
Method 5: Check for Overclocking or BIOS Issues
If youve overclocked your CPU, GPU, or RAM, reset settings to default:
- Restart your PC and enter BIOS/UEFI (usually by pressing Del, F2, or Esc during boot).
- Look for options like Load Optimized Defaults or Reset to Defaults.
- Save changes and exit. Monitor stability after the change.
Method 6: Test RAM for Errors
Faulty RAM can cause this BSOD. Use Windows built-in tool:
- Open Task Manager (Ctrl + Shift + Esc), go to the Performance tab, and click Memory diagnostics.
- Select Restart now and check for problems. The tool will test your RAM on reboot.
- If errors are found, replace or reseat your RAM modules.
Method 7: Perform a Clean Boot to Identify Conflicts
A clean boot starts Windows with minimal drivers/services to isolate the issue:
- Press Win + R, type
msconfig, and press Enter. - Go to the Services tab, check Hide all Microsoft services, then click Disable all.
- Switch to the Startup tab and click Open Task Manager. Disable all startup items.
- Restart your PC. If no BSOD occurs, a third-party app or service is likely the cause. Re-enable items one by one to identify the culprit.
Method 8: Use System Restore (If Available)
If the error started after recent changes, restore your system to a previous stable state:
- Search for Create a restore point, click System Protection, and select System Restore.
- Choose a restore point from before the issue began (avoid choosing one marked as “Windows Update”).
- Follow the prompts to complete the process. Your PC will restart.
Method 9: Check for Windows Updates
Microsoft often releases patches for BSOD-related bugs:
- Go to Settings > Update & Security > Windows Update.
- Click Check for updates. Install any optional or important updates, then restart your PC.
Method 10: Reinstall Windows (Last Resort)
If all else fails, a clean install may be necessary. Back up your data first:
- Download the Windows Media Creation Tool.
- Create a bootable USB drive using another PC, then boot from it on your affected machine.
- Choose Repair your computer during setup to preserve files or perform a clean install.
FAQ About KERNEL_LOCKED_PAGES_IN_MEMORY (0x00000016)
Q: Is this error related to malware?
A: Rarely, but some malware can trigger memory-related BSODs. Run a scan with Windows Defender or a trusted antivirus.
Q: Will resetting BIOS fix this?
A: Yes, if overclocking or incorrect settings are the cause. Use the manufacturers default settings to rule out hardware issues.
Q: Can I prevent future BSODs?
A: Regularly update drivers, avoid overclocking, and use reliable antivirus software. Monitor system health with tools like Windows Memory Diagnostic.
Q: Why does this happen during gaming?
A: Graphics drivers or overloaded RAM are common culprits. Update your GPU driver and ensure sufficient cooling.
Final Notes
The KERNEL_LOCKED_PAGES_IN_MEMORY (0x00000016) BSOD is usually resolvable with patience and systematic troubleshooting. Start with driver updates, system file repairs, and hardware checks before considering more drastic steps like a clean install. If the issue persists after trying all methods, consult Microsoft Support or a local technician for further diagnosis.
Last Updated: December 13, 2025
Tested on: Windows 10 (22H2) & Windows 11 (23H2)