| Previous | Next |
| STATUS_ACPI_INVALID_EVENTTYPE | STATUS_ACPI_INVALID_DATA |
STATUS_ACPI_HANDLER_COLLISION
STATUS_ACPI_HANDLER_COLLISION is a registration conflict: the target already has a handler where the attempted operation expects to install one. It should be diagnosed as a duplicate ownership or lifecycle issue, not as an indication that the underlying device necessarily malfunctioned.
The key comparison is between the existing registration and the new request: target, handler class, registration path and teardown history. A stale registration left after a partial initialization path can look similar to two independent components both claiming the same event or region target.
A second handler conflicted with an existing ACPI registration
- Identify the target object or event, current handler owner and attempted registrar.
- Trace initialization and teardown to find duplicate registration or a missing unregister path.
- Distinguish the collision from
STATUS_ACPI_REG_HANDLER_FAILED; the latter can fail for reasons other than an existing handler.
References
Looking for a different code? Search another status or error code.