What does BSOD 61953 (SAVER_RENDERMOBILEUIOOM) mean?

 
Previous Next
SAVER_RENDERTHREADHANG SAVER_DEVICEUPDATEUNSPECIFIED

SAVER_RENDERMOBILEUIOOM

SAVER_RENDERMOBILEUIOOM: recorded condition

SAVER_RENDERMOBILEUIOOM has value 0x0000F201 and identifies mobile UI rendering failure under memory pressure. 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 commit and working-set data, graphics allocations, surface dimensions, texture lifetime, trim events, and the allocation that failed. Find whether memory pressure came from retained UI surfaces, oversized content, a graphics leak, or system-wide commitment exhaustion.

  • 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

Treat out-of-memory evidence as primary; a render-thread timeout can be secondary when allocation repeatedly fails. Compare neighboring SAVER values only after the evidence above identifies the same producer and lifecycle stage; similar-looking names can describe different capture triggers.

Recovery after evidence collection

Preserve the original dump and logs before restarting the affected process or machine. A restart may restore service, but durable recovery requires correcting the component, dependency, resource limit, firmware, or application state demonstrated by the captured evidence.

References

Looking for a different code? Search another status or error code.