BSOD 390 (WVR_LIVEDUMP_CRITICAL_ERROR): causes and diagnosis

Status / error code:		Category:

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

Could be also:
Constant	Type	OS
ERROR_CLOUD_FILE_NOT_UNDER_SYNC_ROOT	Win32 error	Windows

Previous	Next
WVR_LIVEDUMP_STATE_FAILURE	VIDEO_DWMINIT_TIMEOUT_FALLBACK_BDD

WVR_LIVEDUMP_CRITICAL_ERROR

Windows Volume Replication critical error for WVR_LIVEDUMP_CRITICAL_ERROR

WVR_LIVEDUMP_CRITICAL_ERROR is bug check code 0x00000186. This is the high-severity WVR diagnostic bucket. It indicates that the replication component considered the condition critical enough to capture detailed state.

How to read it in a dump

Use the parameters and WVR component data to distinguish corruption, timeout, service failure, and resource exhaustion.
Correlate with Storage Replica event IDs and cluster events.
The live dump should be treated as evidence, not as a complete explanation.

What to check

Collect both partner logs, cluster logs, and storage diagnostics.
Check whether the issue followed failover, firmware update, or network/storage outage.
Escalate with the live dump when WVR component data is needed.

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