| Previous | Next |
| STATUS_ACPI_INVALID_MUTEX_LEVEL | STATUS_ACPI_MUTEX_NOT_OWNER |
STATUS_ACPI_MUTEX_NOT_OWNED
STATUS_ACPI_MUTEX_NOT_OWNED describes a release-side state error: the mutex being released is not currently acquired. This is not a contention result and it is not necessarily a cross-thread ownership mismatch. The interpreter sees no active ownership state for the release to undo.
Typical analysis focuses on unbalanced control flow: an error path, conditional branch or earlier release can make a later release execute without the matching acquire. The relevant trace is the acquire/release history for that exact mutex within the same AML evaluation path.
AML attempted to release a mutex with no current owner
- Record the mutex name, method path and every preceding acquire or release operation for that invocation.
- Inspect conditional exits and exception-like branches that can bypass an acquire but still reach a release.
- Differentiate from
STATUS_ACPI_MUTEX_NOT_OWNER: no current ownership and ownership by someone else are distinct states.
References
Looking for a different code? Search another status or error code.