| Previous | Next |
| CLUSTER_CSVFS_LIVEDUMP | SILO_CORRUPT |
BAD_OBJECT_HEADER
The BAD_OBJECT_HEADER bug check has a value of 0x00000189. This indicates that The OBJECT_HEADER has been corrupted.
BAD_OBJECT_HEADER Parameters
| Parameter | Description |
|---|---|
| 1 | Pointer to bad OBJECT_HEADER |
| 2 | Pointer to the resulting OBJECT_TYPE based on the TypeIndex in the OBJECT_HEADER |
| 3 | Type of corruption. 0x0 : The type index is corrupt 0x1 : The object security descriptor is invalid |
| 4 | Reserved |
What the bug check means
Windows detected corruption in the kernel OBJECT_HEADER metadata for an object. This is a kernel bookkeeping corruption condition, not an ordinary access-denied or invalid-handle result.
What to inspect
- Start with the crashing thread and the object operation that exposed the damaged header.
- Use the corruption type reported in parameter 1 to narrow the damaged OBJECT_HEADER field or invariant.
- Look for driver misuse of object references, handles or lifetime rules, including use-after-free and double dereference paths.
- Check nearby pool corruption and memory-corruption evidence; the component that detects the bad header may not be the component that damaged it.
Correction
Fix the driver or kernel component that corrupts object metadata rather than retrying the failed object operation. Driver Verifier and a kernel dump are useful when the corruption is intermittent because they can expose the earlier lifetime or pool violation closer to its source.
References
Looking for a different code? Search another status or error code.