| Previous | Next |
| STATUS_STOWED_EXCEPTION | STATUS_REPARSE_POINT_NOT_RESOLVED |
STATUS_CONTEXT_STOWED_EXCEPTION
The original WinRT failure context was preserved separately
This status is associated with the point-of-failure evolution of WinRT stowed exceptions. Its purpose is to retain context nearer the originating failure instead of relying only on the later thread that reports the fatal error. The current instruction pointer can therefore represent error propagation rather than the code that first failed.
Treat the attached context and nested error information as primary evidence. Decode the stowed structures, HRESULTs, stored traces, and nested exception type before analyzing the reporter’s stack. If symbols or module versions no longer match the stored addresses, preserve the exact application package and binaries from the failing deployment; symbolizing against a later build can produce a plausible but incorrect call path.
What to inspect
- Locate and validate every attached stowed-context structure.
- Prioritize stored point-of-failure traces over the final reporting stack.
- Correlate ResultCode and nested exception data with the failed async operation.
- Use symbols from the exact package and binary versions recorded in the dump.
References
- Microsoft Learn: STOWED_EXCEPTION_INFORMATION_V2
- Microsoft Inside: Stowed Exception C000027B
- Microsoft Learn: RoFailFastWithErrorContextInternal2
- Microsoft Learn: EXCEPTION_RECORD
Looking for a different code? Search another status or error code.