Windows BSOD Error 0x00000076 — PROCESS_HAS_LOCKED_PAGES Fix

What Does This Error Mean?

The 0x00000076 blue screen means a process was terminated while it still had pages of memory locked. This is called PROCESS_HAS_LOCKED_PAGES. It is almost always caused by a buggy driver that did not properly release locked memory when it was supposed to.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows Server

Common Causes

A device driver locked memory pages for a transfer and then failed to unlock them before the process ended
A recently installed or updated driver has a memory management bug
An antivirus or security software driver is not handling memory allocation correctly
A USB or peripheral device driver is not cleaning up properly after the device is disconnected
Windows system files have become corrupted, affecting how the memory manager handles locked pages

How to Fix It

Identify the offending driver using a crash analyzer. Download the free tool WhoCrashed from resplendence.com/whoCrashed and run it. It reads your crash dump files and names the driver responsible.

Knowing the specific driver name makes every subsequent step much faster and more targeted.
Update all device drivers, especially recently installed ones. Open Device Manager (right-click Start > Device Manager) and check for yellow warning icons. Right-click drivers and choose Update driver.

Pay particular attention to drivers for USB devices, graphics cards, network adapters, and storage controllers.
Uninstall recently added hardware or software drivers. If the crashes started after installing a new device or program, uninstall it through Settings > Apps or Device Manager.

Peripheral devices like printers, drawing tablets, and webcams often install custom drivers that can cause this error.
Run the System File Checker. Open Command Prompt as Administrator and type: sfc /scannow — then press Enter. This repairs corrupted Windows memory management and driver support files.

Follow with DISM if SFC finds errors: DISM /Online /Cleanup-Image /RestoreHealth
Try disabling or replacing your antivirus software temporarily. Security programs run deep kernel-level drivers that must handle memory very carefully. A buggy security driver is a known cause of PROCESS_HAS_LOCKED_PAGES.

Switch to Windows Defender if a third-party antivirus is suspected. Windows Defender is well-tested and rarely causes this error.

When to Call a Professional

This error is almost always caused by a driver bug and can usually be resolved with software fixes. If the crash happens constantly and no specific driver can be identified as the cause, a technician can use advanced debugging tools to pinpoint the problem driver.

Frequently Asked Questions

What are locked memory pages?

Windows normally swaps memory between RAM and the hard drive as needed. Locked pages are sections of RAM that a driver has flagged as 'do not move this.' This is legitimate behavior during data transfers, but the driver must unlock those pages when it is done. If a process ends before unlocking them, Windows detects the orphaned locked pages and crashes.

How do I find my Windows crash dump files?

Windows saves crash information to C:\Windows\Minidump. These .dmp files can be read by tools like WhoCrashed or WinDbg. If this folder is empty, ensure crash dump creation is enabled: Control Panel > System > Advanced > Startup and Recovery > set Small memory dump.

Can this error be caused by a printer or scanner driver?

Yes. Printer and scanner drivers are common culprits for this specific error. They frequently lock memory during print jobs and must release it cleanly when the job finishes. Try uninstalling the printer software completely (not just the device) and reinstalling the latest version from the manufacturer's website.