| Previous | Next |
| SAVER_NOTIFICATIONDISMISSAL | SAVER_CALLDISMISSAL |
SAVER_SPEECHDISMISSAL
SAVER speech-dismissal bucket for SAVER_SPEECHDISMISSAL
SAVER_SPEECHDISMISSAL is bug check code 0x0000F00C. This bucket indicates diagnostic capture around speech UI or speech-session dismissal. It is most useful when correlated with shell, audio, microphone, and speech-platform logs.
How to read it in a dump
- 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.
- the useful evidence is the dump type, WER bucket, triggering process, provider-specific data, and event-log context around the capture.
- the symbolic name narrows the subsystem that requested capture; it does not by itself identify a defective driver or application.
What to check
- Check speech runtime, audio endpoint, microphone privacy, and shell event logs.
- Identify whether dismissal followed a timeout, user action, or service crash.
- Keep the dump and WER data; the bucket name alone does not identify the failing module.
References
- Windows SDK bugcodes.h
- Windows Bug Check Codes research index
- Windows Error Reporting
- Windows audio architecture
- Microsoft Bug Check Code Reference
- Analyze a kernel-mode dump with WinDbg
Dump evidence
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 “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with saver / speechdismissal.
- 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 this result before collecting the dump and event logs. 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.