BSOD 61440 (SAVER_UNSPECIFIED): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: SAVER_UNSPECIFIED identifies a Windows bug check whose dump parameters and stack determine the failing component.

Previous	Next
SAVER_SICKAPPLICATION	SAVER_BLANKSCREEN

SAVER_UNSPECIFIED

SAVER_UNSPECIFIED diagnostic category

SAVER_UNSPECIFIED has value 0x0000F000. It records an unspecified SAVER capture reason. For SAVER_UNSPECIFIED, this SAVER value is an internal diagnostic category rather than a public stop-code contract with stable parameter meanings, so its name narrows the investigation but does not identify the defective component.

Evidence specific to SAVER_UNSPECIFIED

Preserve the WER bucket, dump type, producer, event payload, process, and surrounding diagnostic records. Because the bucket is generic, start with the producer and payload instead of inferring a subsystem from the symbolic name.

For SAVER_UNSPECIFIED, identify whether the artifact is a live dump, an application dump, a WER report, or a kernel stop, because the available context and commands differ.
For SAVER_UNSPECIFIED, keep the exact Windows build, process and package identity, module versions, event timestamps, and the component that requested diagnostic capture.
Correlate the capture with the relevant shell, app-model, input, graphics, service, or test-harness events instead of treating SAVER_UNSPECIFIED as a conventional blue-screen cause.

Recovery boundary for SAVER_UNSPECIFIED

Use the dump or WER stack to locate the stalled or unhealthy operation before restarting services or clearing diagnostic data. A reboot can restore availability, but it does not explain why an unspecified SAVER capture reason was detected and should not replace evidence collection.

Official and primary references for SAVER_UNSPECIFIED

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