| Previous | Next |
| SAVER_WATCHDOG | SAVER_NAVIGATIONMODEL |
SAVER_STARTNOTVISIBLE
SAVER_STARTNOTVISIBLE diagnostic category
SAVER_STARTNOTVISIBLE has value 0x0000F005. It records startup that did not become visible. For SAVER_STARTNOTVISIBLE, 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_STARTNOTVISIBLE
Preserve activation timestamps, window creation, visibility state, compositor events, and shell launch telemetry. Check whether the process launched but failed to create a window, created it off-screen, or was blocked before first presentation.
- For SAVER_STARTNOTVISIBLE, 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_STARTNOTVISIBLE, 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_STARTNOTVISIBLEas a conventional blue-screen cause.
Recovery boundary for SAVER_STARTNOTVISIBLE
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 startup that did not become visible was detected and should not replace evidence collection.
Official and primary references for SAVER_STARTNOTVISIBLE
- 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.