DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS

Code: 0xcb (203)

As HRESULT:As NTSTATUS:

Parameters

ParameterDescription
1The address of the internal lock tracking structure.
20 (Reserved)
3Address of the MDL containing the locked pages.
4Number of locked pages

Description

The DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS bug check has a value of 0x000000CB. This indicates that a driver or the I/O manager failed to release locked pages after an I/O operation.

Important

This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Remarks

This bug check is issued only if the registry value is equal to DWORD 1.

\\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackLockedPages

If this value is not set, the system will issue the less-informative bug check 0x76 (PROCESS_HAS_LOCKED_PAGES).

This bug check can also be issued by Driver Verifier when the Pool Tracking option is enabled. For more information, see Pool Tracking.

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

ModuleCodeFound inDescription
ESENT.dll0xcb8.11011%1 (%2) %3The database engine has stopped the backup with error %4.
EventCreate.exe0xcb78.11011%1
KernelBase.dll0xcb78.1The system could not find the environment option that was entered.
SCardSvr.dll0xcb78.11011Server Control has no memory for reader reference object
aeevts.dll0xcb7The Program Compatibility Assistant service failed to start.
appmgmts.dll0xcb78.11011Application %1 from policy %2 was configured to remove any unmanaged install before being assigned. An unmanaged install was found and will be removed.
dsreg.dll0xcb1011All attempts to get WAM token for MDM auto-enrollment failed.
kernel32.dll0xcb78.11011The system could not find the environment option that was entered.
nslookup.exe0xcb78.11011Non-authoritative answer:
webservices.dll0xcb78.11011The size of the socket address was not correct.
win32k.sys0xcb78.1ActiveWndTrkTimeout
win32kbase.sys0xcb1011ActiveWndTrkTimeout
12 entries