What does BSOD 61456 (SAVER_APPLISTUNREACHABLE) mean?

 
Previous Next
SAVER_RILADAPTATIONCRASH SAVER_REPORTNOTIFICATIONFAILURE

SAVER_APPLISTUNREACHABLE

SAVER app-list unreachable bucket for SAVER_APPLISTUNREACHABLE

SAVER_APPLISTUNREACHABLE is bug check code 0x0000F010. This bucket suggests that a shell or app-model component could not reach the app list or app inventory service path. It should be diagnosed through shell, package, profile, and app repository state.

How to read it in a dump for SAVER_APPLISTUNREACHABLE

  • 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_APPLISTUNREACHABLE, the useful evidence is the dump type, WER bucket, triggering process, provider-specific data, and event-log context around the capture.
  • For SAVER_APPLISTUNREACHABLE, 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_APPLISTUNREACHABLE

  • Check app repository, Start/app-list, profile, and shell events.
  • Look for package registration, profile corruption, or service-host failures around the capture time.
  • Avoid interpreting the name as a low-level disk error unless storage events also exist.

References for SAVER_APPLISTUNREACHABLE

Dump evidence for SAVER_APPLISTUNREACHABLE

For SAVER_APPLISTUNREACHABLE, 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_APPLISTUNREACHABLE”; 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_APPLISTUNREACHABLE

  • Run WinDbg !analyze -v, then inspect the documented meaning of each SAVER_APPLISTUNREACHABLE parameter instead of relying only on the probably-caused-by line.
  • For SAVER_APPLISTUNREACHABLE, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with saver / applistunreachable.
  • For SAVER_APPLISTUNREACHABLE, 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_APPLISTUNREACHABLE before collecting the dump and event logs. For SAVER_APPLISTUNREACHABLE, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for SAVER_APPLISTUNREACHABLE

For SAVER_APPLISTUNREACHABLE, 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_APPLISTUNREACHABLE”; 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_APPLISTUNREACHABLE

  • Run WinDbg !analyze -v, then inspect the documented meaning of each SAVER_APPLISTUNREACHABLE parameter instead of relying only on the probably-caused-by line.
  • For SAVER_APPLISTUNREACHABLE, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with saver / applistunreachable.
  • For SAVER_APPLISTUNREACHABLE, 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_APPLISTUNREACHABLE before collecting the dump and event logs. For SAVER_APPLISTUNREACHABLE, 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.