The PROCESS_HAS_LOCKED_PAGES bug check has a value of 0x00000076. This bug check indicates that a driver failed to release locked pages after an I/O operation, or that it attempted to unlock pages that were already unlocked.
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
PROCESS_HAS_LOCKED_PAGES Parameters
Parameter 1
Parameter 2
Parameter 3
Parameter 4
Cause of error
The pointer to the process object
The number of locked pages
The pointer to driver stacks (if they are enabled). Otherwise, this parameter is zero.
The process being terminated has locked memory pages. The driver must unlock any memory that it might have locked in a process, before the process terminates.
MDL specified by the driver
Current number of locked memory pages in that process
A pointer to driver stacks for that process (if they are enabled). Otherwise, this parameter is zero.
The driver is attempting to unlock process memory pages that are not locked.
Cause
The driver either failed to unlock pages that it locked (parameter 1 value is 0x0), or the driver is attempting to unlock pages that have not been locked or that have already been unlocked (parameter 1 value is 0x1).
Resolution
The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.
If the parameter 1 value is 0x0
First use the !search extension on the current process pointer throughout all of physical memory. This extension might find at least one memory descriptor list (MDL) that points to the current process. Next, use !search on each MDL that you find to obtain the I/O request packet (IRP) that points to the current process. From this IRP, you can identify which driver is leaking the pages.
Otherwise, you can detect which driver caused the error by editing the registry:
In the \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management registry key, create or edit the TrackLockedPages value, and then set it equal to DWORD 1.
Restart the computer.
The system then saves stack traces, so you can easily identify the driver that caused the problem. If the driver causes the same error again, bug check 0xCB (DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS) is issued, and the name of the driver that causes this error is displayed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.
If the parameter 1 value is 0x1
Examine the driver source code that locks and unlocks memory, and try to locate an instance where memory is unlocked without first being locked.
PROCESS HAS LOCKED PAGES error in Windows 10 [FULL FIX]
If you wish your computer to be error-free and stable, be sure to update Windows 10 frequently. The updates bring improved security as well as new features , but most importantly, they also fix many hardware and software issues that can cause BSoD errors such as PROCESS HAS LOCKED PAGES.
Since drivers can be a cause for BSoD errors, we urge you to update your drivers as often as you can. Updating drivers on Windows 10 is simple, and you can do it directly from Device Manager .
BSoD can be pretty scary, but they are actually useful because they prevent hardware damage. Come to our BSoD troubleshooting Hub if you need any assistance with other BSoD errors.
Do you want to learn how to fix Windows 10 errors? Head over to our Windows 10 errors section and read out full guides.
There is a wide range of BSoD errors available, and what is common for all these errors is that they crash Windows 10 and restart your computer in order to prevent damage.
These types of errors can be troublesome, therefore today we’re going to show you how to fix PROCESS HAS LOCKED PAGES error.
How can I fix PROCESS HAS LOCKED PAGES BSoD error?
How do I fix PROCESS HAS LOCKED PAGES error?
Solution 1 – Make sure that Windows 10 and your drivers are up to date
Windows 10 isn’t a perfect operating system, and with certain hardware and software, some issues can appear. Fortunately, Microsoft usually fixes these issues through Windows updates.
These updates bring improved security as well as new features, but most importantly, these updates fix many hardware and software issues that can cause BSoD errors such as PROCESS HAS LOCKED PAGES.
If you wish your computer to be error-free and stable, be sure to update Windows 10 frequently.
Although Windows updates can fix many problems, it’s also important that you keep your drivers up to date.
If certain driver is out of date or corrupted, Windows 10 won’t be able to use that device, and you’ll get a BSoD error.
Since drivers can be a cause for BSoD errors, we urge you to update your drivers as often as you can.
Updating drivers on Windows 10 is simple, and you can do it directly from Device Manager. To update your drivers, do the following:
Press Windows Key + X to open Power User Menu. Select Device Manager from the list.
When Device Manager opens, find the driver you want to update, right-click it and choose Update Driver Software.
Select Search automatically for updated driver software. Windows 10 will now download and find the best driver for your device.
Repeat this step for all drivers that you want to update.
Update drivers automatically
Searching for drivers on your own can be time-consuming. So, we advise you to use a tool that will do this for you automatically.
Using an automatic driver updater will certainly save you from the hassle of searching for drivers manually, and it will always keep your system up to date with the latest drivers.
Tweakbit’s Driver Updater (approved by Microsoft and Norton Antivirus) will help you update drivers automatically and prevent PC damage caused by installing the wrong driver versions.
After several tests, our team concluded that this is the best-automatized solution.
Here is a quick guide on how to use it:
Download and install TweakBit Driver Updater
Once installed, the program will start scanning your PC for outdated drivers automatically. Driver Updater will check your installed driver versions against its cloud database of the latest versions and recommend proper updates. All you need to do is wait for the scan to complete.
Upon scan completion, you get a report on all problem drivers found on your PC. Review the list and see if you want to update each driver individually or all at once. To update one driver at a time, click the Update driver link next to the driver name. Or simply click the Update all button at the bottom to automatically install all recommended updates. Note:Some drivers need to be installed in multiple steps so you will have to hit the Update button several times until all of its components are installed.
Solution 2 – Run the BSOD Troubleshooter
If updating your drivers didn’t get the job done, we’re going to try Windows 10’s built-in troubleshooting tool.
This tool can be used for resolving all sorts of problems inside the system, including the BSOD errors.
Here’s how to run Windows 10’s troubleshooting tool:
Open the Settings app.
Head over to Update & Security section.
Select Troubleshoot from the menu on the left.
Select BSOD from the right pane and click Run the troubleshooter.
Follow further instructions to complete the troubleshooting process.
PROCESS_HAS_LOCKED_PAGES BSOD on Windows 10
Replies (7)
One possible cause of this issue are the changes you made to your drivers. For now, we recommend doing the wall-through steps in this article on how to troubleshoot blue screen errors.
Should you need further assistance, feel free to get back to us.
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
I have it a look, but it wasn’t helpful. I’d like to see if the source of the BSOD can be pinpointed using the crash dumps.
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Thank you for your response. To further isolate the cause of this issue, we highly appreciate providing your dump file by uploading it to your OneDrive.
We will be waiting for your response.
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
We can analyze the minidumps if you make them available from the OneDrive or other file sharing sites (such as MediaFire). If you have problems uploading the minidumps copy them to the Desktop or the Documents folder and upload them from there.
Zip or upload the contents of C:\Windows\minidump
Hope this helps. ——————————————————————————————— Rob Brown — Microsoft MVP Rob Brown — past Microsoft MVP — Windows Insider MVP 2016 — 2021 Microsoft MVP Windows and Devices for IT 2009 — 2020
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
I uploaded the minidump file here, please let me know if you need the full one:
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
I uploaded the minidump here. Hope this helps!
Was this reply helpful?
Sorry this didn’t help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Sorry, for some unknown reason I missed the notification you had replied.
Not a lot of help in the minidump. Even further analysis was inconclusive.
Probably caused by : memory_corruption ( nt!MmDeleteProcessAddressSpace+181467 )
1. Check HP Support, their online docs and drivers, and ask in their forums about any known issues. Update the BIOS, chipset drivers, and the major onboard and separate device drivers (see driver update methods below). Be sure to check to see if there are still issues with the HP Accelerometer.sys which may or may not be involved.
BiosVersion = F.10 BiosReleaseDate = 11/01/2017 SystemManufacturer = HP SystemProductName = OMEN by HP Laptop 15-ce0xx SystemFamily = 103C_5335KV HP OMEN SystemVersion = SystemSKU = 1GX62LA#AKH BaseBoardManufacturer = HP BaseBoardProduct = 838F BaseBoardVersion = 40.24 CPUID: «Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz» MaxSpeed: 2800 CurrentSpeed: 2808
2. Run the memory tests (see methods below).
3. As needed use ALL the methods in the troubleshooters below.
4. After ALL the above if needed run Driver Verifier to see if it can indicate a CAUSE (see Driver Verifier methods below).
Check this resource:
For Drivers check System Maker as fallbacks and Device Maker’s which are the most current. Right Click the Start Button — Device Manager — Display Adapter — write down the make and complete model of your video adapter — double click — Driver’s tab — write down the version info. Now click UPdate Driver (this may not do anything as MS is far behind certifying drivers) — then Right Click — Uninstall — REBOOT this will refresh the driver stack.
Repeat that for Network — Network Card (NIC), Wifi, Sound, Mouse and Keyboard if 3rd party with their own software and drivers and any other major device drivers you have.
Now go to System Maker’s site (Dell, HP, Toshiba as examples) (as rollback) and then Device Maker’s site (Realtek, Intel, Nvidia, ATI as examples) and get their latest versions. (Look for BIOS, Chipset, and software updates at System Maker’s site while there.)
Download — SAVE — go to where you put them — Right Click — RUN AD ADMIN — REBOOT after each installation.
Always check in Device Manager — Drivers tab to be sure the version you are installing actually shows up. This is because some drivers rollback before the latest is installed (sound drivers particularly do this) so install a driver — reboot — check to be sure it is installed and repeat as needed.
Repeat at Device Makers — BTW at Device Makers DO NOT RUN THEIR SCANNER — check manually by model.
Manually look at manufacturer’s sites for drivers — and Device Maker’s sites. http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm
Memory tests do not catch all errors such as mismatched memory (possible even for sticks that appear to be identical) and when faster memory is placed in the system behind slower memory. So it is best to also swap sticks in and out to check for those even if all memory tests fail to show a problem.
For the Windows Memory Diagnostic Tool.
Type in Cortana’s search box -> Windows Memory Diagnostics . find at top of the list — click it. in Windows 8/8.1/10 the name is «Windows Memory Diagnostic».
================================================
After doing ALL the updates you can, and if the issue continues, then run DriverVerifier.
Driver Verifier can help find some BSOD issues :
Using Driver Verifier to identify issues with Windows drivers for advanced users http://support.microsoft.com/kb/244617
How To Troubleshoot Driver Problems in Windows Vista or 7. (8/8.1 and 10 are essentially the same). http://www.winvistaclub.com/t79.html
WINKEY + X — RUN — type in -> verifier /reset hit enter to disable
If Driver Verifier creates a minidump upload it and post the link here so we can analyze it.
