ERROR_CLUSTER_POISONED - 5907 (0x1713)
The cluster node has been poisoned.
Updated: Feb 21, 2026
Technical Meaning
ERROR_CLUSTER_POISONED is a specific error code indicating that a cluster node has been poisoned in the Windows file system. This condition typically arises when a node in a failover cluster becomes corrupt or is otherwise marked as unusable by the cluster management software.
Error Details
The term 'poisoned' in this context refers to a state where the node's metadata or data integrity has been compromised, making it unreliable for use within the cluster. This error code is typically generated during operations that require the cluster to be aware of such conditions, such as failover or maintenance activities.
Common Causes
- Corrupted Metadata: The node's metadata may have become corrupted due to hardware issues, software bugs, or other unforeseen circumstances.
- Incorrect Node State: The node might have been incorrectly marked as poisoned by the cluster management system, possibly due to a misconfiguration or a failure in the failover mechanism.
Real-World Context
In a Windows Failover Cluster environment, nodes are managed to ensure high availability and data integrity. When a node is identified as poisoned, it must be taken offline and repaired before being reintroduced into the cluster. This error code helps administrators identify such issues during routine maintenance or troubleshooting.
Is This Error Critical?
Yes, this error can have significant implications for the stability and reliability of the failover cluster. It indicates that a node is no longer trustworthy and must be addressed to maintain the integrity of the cluster.
How to Diagnose
- Review Operation Context: Examine the context in which the operation was performed, such as during a failover or maintenance activity.
- Validate Parameters: Ensure that all parameters passed to the operation are correct and valid.
- Confirm Object Types: Verify that the node being operated on is correctly identified and recognized by the cluster management software.
How to Resolve
- Correct Parameter Usage: Double-check the input parameters for any errors or inconsistencies.
- Adjust Operation Context: If the operation context is incorrect, adjust it to ensure proper handling of the cluster nodes.
- Restore Data: If data corruption is suspected, restore from a known good backup if available.
- Retry Operation with Valid Inputs: Attempt the operation again using valid inputs and parameters.
Developer Notes
Developers should be aware that this error code is specific to operations involving failover clusters in Windows environments. It is not applicable to non-clustered file systems or other types of storage management scenarios.
Related Errors
ERROR_CLUSTER_NODE_DOWN(507)ERROR_CLUSTER_NODE_NOT_FOUND(512)
FAQ
Q: What does the term 'poisoned' mean in this context?
A: In the context of Windows failover clusters, a node is considered poisoned when its metadata or data integrity has been compromised, making it unreliable for use within the cluster.
Q: How can I prevent this error from occurring?
A: Regularly maintain and monitor your cluster nodes to ensure that their hardware and software are up-to-date. Implement robust backup and recovery strategies to mitigate the risk of data corruption or node failure.
Q: Can this error occur in non-clustered environments?
A: No, ERROR_CLUSTER_POISONED is specific to failover clusters in Windows environments and does not apply to other types of file systems or storage management scenarios.
Summary
ERROR_CLUSTER_POISONED (5907) indicates that a node within a Windows failover cluster has been marked as poisoned, meaning its metadata or data integrity is compromised. This error requires immediate attention to ensure the stability and reliability of the cluster. Developers should be aware of this specific error code and take appropriate actions to diagnose and resolve issues related to poisoned nodes.