| Previous | Next |
| SAVER_MTBFIOERROR | SAVER_RENDERMOBILEUIOOM |
SAVER_RENDERTHREADHANG
SAVER_RENDERTHREADHANG: recorded condition
SAVER_RENDERTHREADHANG has value 0x0000F200 and identifies render-thread hang. The SAVER family is used as a diagnostic classification; public parameter semantics are not available for this value, so the producer, dump type, and accompanying event payload define how it must be read.
Evidence that matters
Preserve render thread stack, compositor and GPU waits, present/fence state, scene update, driver events, and last completed frame. Establish whether the thread is blocked on the GPU, waiting for another application thread, deadlocked on a lock, or spinning in rendering code.
- Record the exact Windows build, process or package identity, module versions, capture timestamp, and component that requested the report.
- Determine whether the artifact is a live kernel dump, application dump, WER report, test-harness result, or a true system bug check before choosing debugger commands.
- Follow the stack and provider-specific fields back to the operation that stopped progressing; the symbolic bucket is a routing clue rather than a root-cause verdict.
What distinguishes the result
Compare with the mobile-UI OOM bucket only when memory telemetry shows allocation pressure preceding the stall. Compare neighboring SAVER values only after the evidence above identifies the same producer and lifecycle stage; similar-looking names can describe different capture triggers.
References
Looking for a different code? Search another status or error code.