| Previous | Next |
| STATUS_VERIFIER_STOP | STATUS_INCOMPATIBLE_DRIVER_BLOCKED |
STATUS_CALLBACK_POP_STACK
Callback return processing must discard the callback stack frame
This status is an internal control signal used when an exception or unwind crosses a user-mode callback boundary. Kernel callback-return code recognizes it and restores state differently, removing or replacing the callback frame instead of following the ordinary successful-return path. It should not be interpreted as a standalone application business error.
When it becomes visible in a crash, search backward for the exception that initiated the callback unwind and identify the callback transition. Windows Research Kernel and ReactOS sources both show special handling of this exact value during callback return. Changing it to STATUS_SUCCESS or catching it outside the callback machinery can leave the user stack and exception chain inconsistent.
What to inspect
- Record the original exception and callback entry before this control status appeared.
- Inspect the saved user stack, trap frame, and callback frame relationship.
- Identify hooks or runtimes that intercept NtCallbackReturn-style transitions.
- Do not translate the status away inside low-level callback plumbing.
References
- Windows Research Kernel source: user callback return handling
- ReactOS source: AMD64 user callback handling
- Microsoft Open Specifications: NTSTATUS values
- Microsoft Windows SDK metadata: ntstatus.h
Looking for a different code? Search another status or error code.