| Previous | Next |
| WVR_LIVEDUMP_APP_IO_TIMEOUT | WVR_LIVEDUMP_STATE_FAILURE |
WVR_LIVEDUMP_MANUALLY_INITIATED
Manually initiated Windows Volume Replication live dump for WVR_LIVEDUMP_MANUALLY_INITIATED
WVR_LIVEDUMP_MANUALLY_INITIATED is bug check code 0x00000184. This value marks a WVR diagnostic capture that was explicitly requested rather than automatically triggered by a timeout or state failure. It is evidence collection, not by itself a root cause.
How to read it in a dump
- Confirm who or what requested the live dump.
- The surrounding WVR state still matters; this code only identifies the trigger style.
- Do not treat it as spontaneous replication failure unless logs show a correlated problem.
What to check
- Preserve the manual live dump with matching event logs.
- Record the operator action, script, or support tool that requested capture.
- Use the dump to inspect replication state at the moment of collection.
References
- Storage Replica overview
- Crash dump files and live dump context
- 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 wvr / livedump / manually / initiated.
- 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.