What does BSOD 361 (CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP) mean?

 
Could be also:
ConstantTypeOS
ERROR_DAX_MAPPING_EXISTSWin32 errorWindows
Previous Next
CLUSTER_CSV_STATE_TRANSITION_TIMEOUT_LIVEDUMP CLUSTER_CSV_VOLUME_REMOVAL_LIVEDUMP

CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP

CSV volume-arrival live dump for CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP

CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP is bug check code 0x00000169. This code belongs to Cluster Shared Volumes. It points to a problematic volume-arrival or online transition path, where CSV, storage, mount, file-system, and filter state must converge correctly.

How to read it in a dump for CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP

  • The dump time should be compared with disk arrival, CSV online, resource ownership, and mount-manager events.
  • The issue can involve storage discovery, persistent reservations, volume filters, or cluster coordination.
  • It is not just a plug-and-play disk arrival message; it is a CSV live-dump condition.

What to check for CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP

  • Check cluster logs around volume arrival, ownership changes, and resource online events.
  • Inspect storage filters, MPIO, disk signatures, and mount manager state.
  • Correlate with SAN zoning, virtual disk attachment, or node reboot sequences.

References for CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP

Dump evidence for CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP

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

Analysis order for CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP

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

Dump evidence for CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP

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

Analysis order for CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP

  • Run WinDbg !analyze -v, then inspect the documented meaning of each CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP parameter instead of relying only on the probably-caused-by line.
  • For CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with cluster / csv / volume / arrival / livedump.
  • For CLUSTER_CSV_VOLUME_ARRIVAL_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 CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP before collecting the dump and event logs. For CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP, 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.