| Previous | Next |
| SAVER_APPLISTUNREACHABLE | SAVER_UNEXPECTEDSHUTDOWN |
SAVER_REPORTNOTIFICATIONFAILURE
SAVER_REPORTNOTIFICATIONFAILURE: recorded condition
SAVER_REPORTNOTIFICATIONFAILURE has value 0x0000F011 and identifies failure while reporting or delivering a notification. For SAVER_REPORTNOTIFICATIONFAILURE, 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_REPORTNOTIFICATIONFAILURE
Preserve notification payload type, application identity, broker/service state, delivery result, network dependency, and platform event logs. Determine whether report creation, broker submission, transport, recipient lookup, or acknowledgment failed.
- For SAVER_REPORTNOTIFICATIONFAILURE, record the exact Windows build, process or package identity, module versions, capture timestamp, and component that requested the report.
- For SAVER_REPORTNOTIFICATIONFAILURE, 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_REPORTNOTIFICATIONFAILURE, 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_REPORTNOTIFICATIONFAILURE
This is distinct from dismissal: the relevant boundary is report delivery rather than removal of an existing notification. For SAVER_REPORTNOTIFICATIONFAILURE, 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_REPORTNOTIFICATIONFAILURE
Preserve the original dump and logs before restarting the affected process or machine. For SAVER_REPORTNOTIFICATIONFAILURE, 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_REPORTNOTIFICATIONFAILURE
- Microsoft: Windows Error Reporting
- Microsoft: Analyze a kernel-mode dump with WinDbg
- Microsoft: Bug check code reference
Looking for a different code? Search another status or error code.