CLUSTER_RESOURCE_CALL_TIMEOUT_LIVEDUMP
Code: 0x166 (358)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x0166 (358)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x0166 (358)
Parameters
| Parameter | Description |
|---|---|
| 1 | Resource Host Monitor PID. |
| 2 | TID of the thread that handles resource call. |
| 3 | Resource call type - listed below. |
| 4 | Subcode. When parameter 3 equals 8 then this parameter contains cluster resource control code. When parameter 3 equals 9 then this parameter contains cluster resource type control code. |
Description
The CLUSTER_RESOURCE_CALL_TIMEOUT_LIVEDUMP live dump has a value of 0x00000166. This indicates that a Cluster Resource call took longer than configured timeout.
Cause
A Cluster Resource call took longer than configured timeout. The system generated a live dump for analysis of the delay.
(This code can never be used for a real bug check; it is used to identify live dumps.)
Resolution
See Also
Troubleshooting Hangs Using Live Dump (Blog)
Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.
Associated Modules
| Module | Code | Found in | Description |
|---|---|---|---|
| EventCreate.exe | 0x166 | 78.11011 | %1 |
| kernel32.dll | 0x166 | 1011 | The cloud sync root metadata is corrupted. |
| webservices.dll | 0x166 | 78.11011 | The writer must be positioned on an element or attribute to write an xmlns attribute. |
| 3 entries | |||