BSOD 389 (WVR_LIVEDUMP_STATE_FAILURE): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Windows captured a WVR live dump for replication state failure.

Could be also:
Constant	Type	OS
ERROR_CLOUD_FILE_UNSUCCESSFUL	Win32 error	Windows

Previous	Next
WVR_LIVEDUMP_MANUALLY_INITIATED	WVR_LIVEDUMP_CRITICAL_ERROR

WVR_LIVEDUMP_STATE_FAILURE

Windows Volume Replication state failure for WVR_LIVEDUMP_STATE_FAILURE

WVR_LIVEDUMP_STATE_FAILURE is bug check code 0x00000185. This WVR live dump indicates that the replication state machine reached a failure state. It is broader than a single I/O timeout and should be diagnosed through the exact transition, role, and resource status recorded in the dump.

How to read it in a dump

Find the failing state and transition in the WVR frames.
Look for partner disconnects, storage errors, cluster changes, or service restart.
A live dump may precede a later service recovery or failover.

What to check

Review Storage Replica health and cluster state.
Check resynchronization, log volume health, and replication partner connectivity.
Use the state-machine context in the dump rather than guessing from the symbolic name.

References

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 / state.
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.