What does BSOD 368 (CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG) mean?

 
Could be also:
ConstantTypeOS
ERROR_STORAGE_LOST_DATA_PERSISTENCEWin32 errorWindows
Previous Next
CLUSTER_CSV_STATE_TRANSITION_INTERVAL_TIMEOUT_LIVEDUMP CRYPTO_LIBRARY_INTERNAL_ERROR

CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG

Cluster CSV disconnect watchdog for CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG

CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG is bug check code 0x00000170. Microsoft documents this bug check as a cluster disconnect watchdog: the cluster disconnect path is not making forward progress. It is a failover-clustering progress failure rather than a generic storage timeout.

How to read it in a dump for CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG

  • Parameter meanings are described by the Microsoft bug check page for the specific Windows build.
  • The dump should be correlated with cluster service state, CSV ownership, node communication, and disconnect path workers.
  • This is a watchdog condition; the system stopped because progress did not happen in time.

What to check for CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG

  • Collect cluster logs and compare with the dump timestamp.
  • Check cluster network, storage fabric, CSV ownership transitions, and filter-driver stalls.
  • Analyze blocked cluster service threads in the dump.

References for CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG

Dump evidence for CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG

For CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG, 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_CLUSSVC_DISCONNECT_WATCHDOG”; 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_CLUSSVC_DISCONNECT_WATCHDOG

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

Dump evidence for CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG

For CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG, 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_CLUSSVC_DISCONNECT_WATCHDOG”; 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_CLUSSVC_DISCONNECT_WATCHDOG

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