| Debugging Tools for Windows |
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.
The four parameters listed in the message can have two possible meanings.
If a driver locked these pages, the parameters have the following meaning.
| Parameter | Description |
|---|---|
| 1 | Calling address in the driver that locked the pages |
| 2 | Caller of the calling address in driver that locked the pages |
| 3 | Address of the MDL containing the locked pages |
| 4 | Number of locked pages |
If the driver responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver.
If the I/O manager locked these pages, the parameters have the following meaning.
| Parameter | Description |
|---|---|
| 1 | Address of the dispatch routine of the top driver on the stack to which the IRP was sent |
| 2 | Address of the device object of the top driver on the stack to which the IRP was sent |
| 3 | Address of the MDL containing the locked pages |
| 4 | Number of locked pages |
This bug check is issued only if the registry value \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\TrackLockedPages is equal to DWORD 1. If this value is not set, the system will issue the less-informative bug check 0x76 (PROCESS_HAS_LOCKED_PAGES).
Starting with Windows Vista, this bug check can also be issued by Driver Verifier when the Pool Tracking option is enabled.