Windows BSOD 0x000000D9 — LOCKED_PAGES_TRACKER_CORRUPTION Fix

What Does This Error Mean?

Blue screen 0x000000D9 (LOCKED_PAGES_TRACKER_CORRUPTION) means the internal table Windows uses to track locked memory pages has become corrupted. Windows keeps a precise record of which memory pages are locked by which drivers. When that record is tampered with or corrupted, Windows cannot safely manage memory and must stop. This is almost always caused by a faulty driver or bad RAM.

Affected Models

Windows 10
Windows 11
Windows Server 2019
Windows Server 2022

Common Causes

A driver modified or corrupted the Windows locked pages tracking table directly
Faulty RAM causing data corruption in the kernel's memory management structures
A rootkit or malware that tampers with kernel memory tracking to hide its own locked pages
Driver Verifier is active and detected a locked pages accounting error in a specific driver
System file corruption in the Windows kernel after an interrupted update or disk error

How to Fix It

Run MemTest86 to thoroughly check your RAM. Download it free from memtest86.com, create a bootable USB, boot from it, and let it run at least two full passes. Any errors indicate bad RAM.

Windows Memory Diagnostic is quicker but MemTest86 is more thorough. For this specific BSOD, extended RAM testing is worth the extra time.
Run System File Checker. Open Command Prompt as Administrator and run: sfc /scannow — restart after it completes.

Corrupted kernel files can cause internal tracking tables to malfunction. SFC repairs these automatically.
Run DISM to restore Windows component integrity. In Administrator Command Prompt: DISM /Online /Cleanup-Image /RestoreHealth — wait for it to finish fully.

DISM repairs deeper system file issues that SFC alone cannot address.
Run a full malware scan with Windows Defender offline scan. Search 'Windows Security' in the Start menu, go to Virus and Threat Protection > Scan options, and choose Microsoft Defender Offline Scan.

Rootkits that modify kernel memory tracking tables specifically avoid regular antivirus scans. The offline scan runs before Windows loads and catches threats that hide during normal operation.
Update all drivers, especially storage, network, and chipset drivers. Check Device Manager and also visit your PC or motherboard manufacturer's support page for driver packages.

Storage and chipset drivers interact heavily with memory page locking during disk I/O. Outdated versions of these are a common cause of locked page tracking corruption.

When to Call a Professional

If memory diagnostics pass and drivers are updated, a technician should analyze the crash dump. Kernel memory corruption can sometimes point to failing hardware that standard memory tests miss. Extended memory testing tools like MemTest86 (run from a USB overnight) give more thorough results.

Frequently Asked Questions

How does Windows track locked pages?

Windows maintains an internal kernel structure that records every memory page currently locked by a driver, along with which driver locked it and why. This is similar to a check-out log at a library — every borrowed book is tracked so nothing goes missing. When a driver locks a page for a disk operation, an entry is added to this table. When the operation completes and the driver unlocks the page, the entry is removed. If anything modifies this table without following the rules, Windows detects the inconsistency and crashes.

Does this BSOD always mean my RAM is bad?

No — RAM failure is one cause but not the only one. A buggy driver is more commonly responsible. If MemTest86 finds no errors, focus your investigation on recently installed drivers or software. RAM failure as a cause is more likely if you also experience other stability issues like random freezes or file corruption across multiple applications.

What if I cannot boot into Windows to run these fixes?

If Windows BSODs before the desktop loads, boot from a Windows installation USB. Choose 'Repair your computer' instead of Install Now, then open Command Prompt from Advanced Options. You can run SFC from here with: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows — replacing C: with the drive letter where Windows is installed.