| Previous | Next |
| STATUS_ACPI_INVALID_OPCODE | STATUS_ACPI_ASSERT_FAILED |
STATUS_ACPI_STACK_OVERFLOW
STATUS_ACPI_STACK_OVERFLOW identifies a limit reached inside AML evaluation. Control methods can call other methods, create temporary objects and evaluate namespace objects dynamically. A deep or cyclic evaluation path can exhaust interpreter state even when the platform has plenty of ordinary process stack or physical memory.
It is not interchangeable with a firmware table syntax error. A table can decode correctly and still produce excessive nesting only for a particular method, notification, device state or power transition. The decisive evidence is the active AML call chain and the trigger that caused it to be evaluated.
Nested AML evaluation exceeded its execution stack
- Capture the method path, trigger event and preceding ACPI diagnostic messages; the final status alone does not identify the recursive method.
- Compare the path with a known-good firmware revision and look for methods that re-enter themselves through another namespace object or notification.
- Avoid treating an application restart as remediation: the execution path belongs to the platform ACPI interpreter.
References
Looking for a different code? Search another status or error code.