BSOD 386 (WVR_LIVEDUMP_RECOVERY_IOCONTEXT

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Windows captured a WVR live dump for recovery I/O context timeout.

Could be also:
Constant	Type	OS
ERROR_CLOUD_FILE_AUTHENTICATION_FAILED	Win32 error	Windows

Previous	Next
WVR_LIVEDUMP_STATE_TRANSITION_TIMEOUT	WVR_LIVEDUMP_APP_IO_TIMEOUT

WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT

Windows Volume Replication recovery I/O timeout for WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT

WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT is bug check code 0x00000182. This WVR code is focused on recovery I/O rather than steady-state replication. It suggests that recovery processing could not complete an I/O context in time after interruption, failover, resync, or replica state repair.

How to read it in a dump for WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT

Distinguish recovery I/O from ordinary application I/O.
Check whether the system was resynchronizing, recovering after outage, or changing replica roles.
Storage error records and replication service logs are central.

What to check for WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT

Inspect Storage Replica recovery and resync events.
Check disk health, network stability, and cluster role transitions.
Preserve the live dump before retrying recovery operations.

References for WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT

Dump evidence for WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT

For WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT, 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 “WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT

Run WinDbg !analyze -v, then inspect the documented meaning of each WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT parameter instead of relying only on the probably-caused-by line.
For WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with wvr / livedump / recovery / iocontext / timeout.
For WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT, 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 WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT before collecting the dump and event logs. For WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.

Dump evidence for WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT

Analysis order for WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT

Run WinDbg !analyze -v, then inspect the documented meaning of each WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT parameter instead of relying only on the probably-caused-by line.
For WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with wvr / livedump / recovery / iocontext / timeout.
For WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Looking for a different code? Search another status or error code.