| Previous | Next |
| UFX_LIVEDUMP | WORKER_THREAD_RETURNED_WHILE_ATTACHED_TO_SILO |
KERNEL_STORAGE_SLOT_IN_USE
The KERNEL_STORAGE_SLOT_IN_USE bug check has a value of 0x00000199. This indicates that the storage slot cannot be freed because there is an object using it.
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_STORAGE_SLOT_IN_USE Parameters
| Parameter | Description |
|---|---|
| 1 | The address of the storage array |
| 2 | Reserved |
| 3 | Reserved |
| 4 | Reserved |
Dump evidence for KERNEL_STORAGE_SLOT_IN_USE
For KERNEL_STORAGE_SLOT_IN_USE, 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 “KERNEL_STORAGE_SLOT_IN_USE”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for KERNEL_STORAGE_SLOT_IN_USE
- Run WinDbg
!analyze -v, then inspect the documented meaning of each KERNEL_STORAGE_SLOT_IN_USE 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 / storage / slot / in / use.
- For KERNEL_STORAGE_SLOT_IN_USE, 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 KERNEL_STORAGE_SLOT_IN_USE before collecting the dump and event logs. For KERNEL_STORAGE_SLOT_IN_USE, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.