What does BSOD 61460 (SAVER_AUXILIARYFULLDUMP) mean?

 
Previous Next
SAVER_RPCFAILURE SAVER_ACCOUNTPROVSVCINITFAILURE

SAVER_AUXILIARYFULLDUMP

SAVER auxiliary full-dump bucket for SAVER_AUXILIARYFULLDUMP

SAVER_AUXILIARYFULLDUMP is bug check code 0x0000F014. This bucket indicates that an auxiliary full dump was involved in the SAVER diagnostic path. It mainly describes the capture style and evidence set, not the underlying root cause.

How to read it in a dump for SAVER_AUXILIARYFULLDUMP

  • Treat this value as an internal diagnostic bucket from the Windows SAVER family, not as a classic blue-screen stop code with public parameter semantics.
  • For SAVER_AUXILIARYFULLDUMP, the useful evidence is the dump type, WER bucket, triggering process, provider-specific data, and event-log context around the capture.
  • For SAVER_AUXILIARYFULLDUMP, the symbolic name narrows the subsystem that requested capture; it does not by itself identify a defective driver or application.

What to check for SAVER_AUXILIARYFULLDUMP

  • Preserve the auxiliary full dump together with any minidump or live dump.
  • Check who requested the dump and whether it was triggered by WER, shell, or support tooling.
  • Use the full dump to inspect process state, memory pressure, and provider-specific objects.

References for SAVER_AUXILIARYFULLDUMP

Dump evidence for SAVER_AUXILIARYFULLDUMP

For SAVER_AUXILIARYFULLDUMP, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “SAVER_AUXILIARYFULLDUMP”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for SAVER_AUXILIARYFULLDUMP

  • Run WinDbg !analyze -v, then inspect the documented meaning of each SAVER_AUXILIARYFULLDUMP parameter instead of relying only on the probably-caused-by line.
  • For SAVER_AUXILIARYFULLDUMP, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with saver / auxiliaryfulldump.
  • For SAVER_AUXILIARYFULLDUMP, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by SAVER_AUXILIARYFULLDUMP before collecting the dump and event logs. For SAVER_AUXILIARYFULLDUMP, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for SAVER_AUXILIARYFULLDUMP

For SAVER_AUXILIARYFULLDUMP, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “SAVER_AUXILIARYFULLDUMP”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for SAVER_AUXILIARYFULLDUMP

  • Run WinDbg !analyze -v, then inspect the documented meaning of each SAVER_AUXILIARYFULLDUMP parameter instead of relying only on the probably-caused-by line.
  • For SAVER_AUXILIARYFULLDUMP, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with saver / auxiliaryfulldump.
  • For SAVER_AUXILIARYFULLDUMP, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by SAVER_AUXILIARYFULLDUMP before collecting the dump and event logs. For SAVER_AUXILIARYFULLDUMP, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

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