What does BSOD 61697 (SAVER_MTBFCOMMANDHANG) mean?

 
Previous Next
SAVER_ACCOUNTPROVSVCINITFAILURE SAVER_MTBFPASSBUGCHECK

SAVER_MTBFCOMMANDHANG

SAVER_MTBFCOMMANDHANG: recorded condition

SAVER_MTBFCOMMANDHANG has value 0x0000F101 and identifies reliability-test command 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 MTBF harness command id, target component, issue timestamp, last progress marker, wait chain, and cancellation state. Determine whether the command entered the target, which completion signal was expected, and which owner retained the request.

  • 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

A hang differs from a timeout bucket when the command is known to be stuck rather than merely exceeding an external deadline. 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.