BSOD 387 (WVR_LIVEDUMP_APP_IO_TIMEOUT): causes and diagnosis

Status / error code:		Category:

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

Could be also:
Constant	Type	OS
ERROR_CLOUD_FILE_INSUFFICIENT_RESOURCES	Win32 error	Windows

Previous	Next
WVR_LIVEDUMP_RECOVERY_IOCONTEXT_TIMEOUT	WVR_LIVEDUMP_MANUALLY_INITIATED

WVR_LIVEDUMP_APP_IO_TIMEOUT

Windows Volume Replication application I/O timeout for WVR_LIVEDUMP_APP_IO_TIMEOUT

WVR_LIVEDUMP_APP_IO_TIMEOUT is bug check code 0x00000183. This code indicates that application-visible I/O in a replicated volume context exceeded the expected wait. It should be analyzed through the storage replication layer and application I/O stack together.

How to read it in a dump

Separate the application request, file-system stack, replication layer, and physical storage path.
Look for whether the I/O is blocked by replica synchronization, network path, or storage latency.
The process issuing the I/O is not necessarily the root cause.

What to check

Check application logs together with Storage Replica and disk events.
Measure latency and queue depth on the replicated volumes.
Investigate storage filters and antivirus products that sit above the replication path.

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 / app / io / 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 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.