What does BSOD 61443 (SAVER_INPUT) mean?

 
Previous Next
SAVER_BLANKSCREEN SAVER_WATCHDOG

SAVER_INPUT

SAVER_INPUT: recorded condition

SAVER_INPUT has value 0x0000F003 and identifies input-path diagnostic capture. For SAVER_INPUT, 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 for SAVER_INPUT

Preserve keyboard, pointer, touch, controller, focus, input queue, and shell routing telemetry. Check whether the event reached the expected queue, whether focus or capture changed, and whether the receiving UI thread was pumping messages.

  • For SAVER_INPUT, record the exact Windows build, process or package identity, module versions, capture timestamp, and component that requested the report.
  • For SAVER_INPUT, 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.
  • For SAVER_INPUT, 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 SAVER_INPUT

Distinguish missing input delivery from an application that received input but could not respond. For SAVER_INPUT, 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 for SAVER_INPUT

Preserve the original dump and logs before restarting the affected process or machine. For SAVER_INPUT, 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 for SAVER_INPUT

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