KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION
Code: 0x153 (339)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x0153 (339)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x0153 (339)
Parameters
| Parameter | Description |
|---|---|
| 1 | The address of the thread |
| 2 | The address of the entry that was not freed |
| 3 | A status code indicating the state of the entry 0x1 : Lock pointer was not NULL 0x2 : Thread pointer reserved bits were set 0x3 : Thread pointer was corrupted 0x4 : The entry had residual IO or CPU boosts left |
| 4 | Reserved |
Description
The KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION bug check has a value of 0x00000153. This indicates that a thread was terminated before it had freed all its AutoBoost lock entries.
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.
Cause
This is typically caused when a thread never released a lock it previously acquired (e.g. by relying on another thread to release it), or if the thread did not supply a consistent set of flags to lock package APIs.
See also
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
| Module | Code | Found in | Description |
|---|---|---|---|
| EventCreate.exe | 0x153 | 78.11011 | %1 |
| KernelBase.dll | 0x153 | 8.1 | One or more copies of data on this device may be out of sync. No writes may be performed until a data integrity scan is completed. |
| kernel32.dll | 0x153 | 8.11011 | One or more copies of data on this device may be out of sync. No writes may be performed until a data integrity scan is completed. |
| webservices.dll | 0x153 | 78.11011 | The character '\' or '"' was expected. |
| 4 entries | |||