| Previous | Next |
| INVALID_KERNEL_HANDLE | PNP_INTERNAL_ERROR |
KERNEL_STACK_LOCKED_AT_EXIT
The result bug check has a value of 0x00000094. This bug check indicates that a thread exited while its kernel stack was marked as not swappable
Important
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.
KERNEL_STACK_LOCKED_AT_EXIT Parameters
None
Dump evidence
Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with kernel / stack / locked / at / exit.
- keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Distinctive failure boundary
This result identifies kernel stack left locked during thread exit. Find who locked or attached to the terminating thread stack, inspect outstanding stack-swap or attach operations, and verify that every lock/attach path has a matching release/detach path.
Separating the result from neighboring bug checks
The key distinction is lifetime imbalance at thread teardown, not arbitrary corruption of a memory-manager region. Preserve the original dump and use the documented parameters and stack to verify this distinction before changing drivers or platform configuration.
Looking for a different code? Search another status or error code.