| Previous | Next |
| STATUS_ACPI_STACK_OVERFLOW | STATUS_ACPI_INVALID_INDEX |
STATUS_ACPI_ASSERT_FAILED
STATUS_ACPI_ASSERT_FAILED reports that ACPI processing reached an internal state the implementation considers inconsistent. It does not name a particular AML opcode, device or power resource. The status is therefore different from a bad method argument or an unsupported region: it points to an invariant check in the ACPI implementation or in the state assembled from firmware data.
Preserve the surrounding evidence before attempting changes. The most useful correlation is the exact ACPI table set, platform firmware revision, driver stack and transition in progress, such as boot, resume, docking or device power management.
An ACPI implementation invariant failed
- Collect kernel, ACPI and device-power events around the first assertion, including whether the system was resuming or changing device state.
- Record DSDT/SSDT identifiers and firmware revision so that the same table set can be examined or compared.
- Separate this status from
STATUS_ACPI_FATAL: an assertion is an inconsistency report; a fatal ACPI condition carries its own escalation semantics.
References
Looking for a different code? Search another status or error code.