| Previous | Next |
| WIN32K_CRITICAL_FAILURE | CLUSTER_RESOURCE_CALL_TIMEOUT_LIVEDUMP |
CLUSTER_CSV_STATUS_IO_TIMEOUT_LIVEDUMP
CSV I/O timeout live dump for CLUSTER_CSV_STATUS_IO_TIMEOUT_LIVEDUMP
CLUSTER_CSV_STATUS_IO_TIMEOUT_LIVEDUMP is bug check code 0x00000165. This is a Cluster Shared Volumes live-dump code. It indicates that the cluster storage path observed an I/O timeout and preserved kernel state for diagnosis rather than necessarily stopping the machine.
How to read it in a dump
- The important evidence is CSV ownership, redirected I/O, storage path latency, and cluster service state.
- The dump can identify whether the timeout is storage, network, filter-driver, or cluster coordination related.
- Live dumps should be treated as diagnostic captures even when the node remains up.
What to check
- Check cluster logs, CSV redirected I/O state, storage latency, MPIO paths, SMB/CSV network, and file-system filters.
- Correlate the dump time with storage array, SAN, or virtual disk events.
- Look for repeated timeouts before failover decisions.
References
- Microsoft clustering / DFS documentation
- Microsoft clustering / DFS documentation
- Microsoft Bug Check Code Reference
- Crash dump files and 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 cluster / csv / io / timeout / livedump.
- 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.