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.
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.
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 |
Kernel object handles are process specific. That is, a process must either create the object or open an existing object to obtain a kernel object handle. The per-process limit on kernel handles is 2^24. However, handles are stored in the paged pool, so the actual number of handles you can create is based on available memory. The number of handles that you can create on 32-bit Windows is significantly lower than 2^24.
Any process can create a new handle to an existing kernel object (even one created by another process), provided that the process knows the name of the object and has security access to the object. Kernel object handles include access rights that indicate the actions that can be granted or denied to a process. An application specifies access rights when it creates an object or obtains an existing object handle. Each type of kernel object supports its own set of access rights. For example, event handles can have set or wait access (or both), file handles can have read or write access (or both), and so on. For more information, see Securable Objects.
The Windows kernel-mode object manager component manages objects. Files, devices, synchronization mechanisms, registry keys, and so on, are all represented as objects in kernel mode. Each object has a header (containing information about the object such as its name, type, and location), and a body (containing data in a format determined by each type of object).
Windows has more than 25 types of objects. A few of the types are:
Files
Devices
Threads
Processes
Events
Mutexes
Semaphores
Registry keys
Jobs
Sections
Access tokens
Symbolic links
The object manager manages the objects in Windows by performing the following major tasks:
Managing the creation and destruction of objects.
Keeping an object namespace database for tracking object information.
Keeping track of resources assigned to each process.
Tracking access rights for specific objects to provide security.
Managing the lifetime of an object and determining when an object will be automatically destroyed to recycle resource space.