| Previous | Next |
| BAD_OBJECT_HEADER | SECURE_KERNEL_ERROR |
SILO_CORRUPT
Kernel silo/container state corruption for SILO_CORRUPT
SILO_CORRUPT is bug check code 0x0000018A. Windows uses silo-style isolation for container and server-silo scenarios. This bug check points at corruption in that isolation state, such as inconsistent object namespace, job, token, or per-silo kernel data.
How to read it in a dump
- Identify the silo, container, or isolated service context in the dump.
- Object namespace, job object, token, and process lifetime evidence are important.
- The failing process may be a victim of corrupted per-silo state.
What to check
- Check container runtime, Host Compute Service, and recent isolation-related updates.
- Inspect the process and job hierarchy in WinDbg.
- Look for drivers or filters that do not correctly handle server silo contexts.
References
- Windows containers and silos
- Analyze a kernel-mode dump with WinDbg
- Microsoft Bug Check Code Reference
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 silo / corrupt.
- 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.
Looking for a different code? Search another status or error code.