| Previous | Next |
| STATUS_PWD_TOO_LONG | STATUS_CONTEXT_STOWED_EXCEPTION |
STATUS_STOWED_EXCEPTION
The crash contains one or more WinRT stowed exceptions
WinRT can capture an HRESULT, stack trace or error text, thread identifier, and optional nested exception when an asynchronous operation fails. If that error later becomes fatal, Windows raises STATUS_STOWED_EXCEPTION. The current crash stack can be only the reporting path; the stowed records preserve the earlier point where the failure originated.
The exception parameters identify an array of pointers to stowed-exception structures and the number of entries. Decode each STOWED_EXCEPTION_INFORMATION header and version, then inspect ResultCode, ExceptionForm, stored stack, and NestedExceptionType. Debugging only the thread that finally raised the status can miss a worker thread that already completed or disappeared.
What to inspect
- Read the exception parameters to locate the stowed-exception pointer array and count.
- Validate each structure header before interpreting version-specific fields.
- Resolve stored stack addresses with the matching module versions and symbols.
- Inspect nested Win32, CLR, language, or additional stowed exceptions.
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.