APPLICATION_HANG_KERNEL_LIVEDUMP
Bug check code: 0x000001f5 (501)
As HRESULT:- S: 0 (Success)
- C: 0 (Microsoft-defined)
- N: 0 (Not an NTSTATUS value)
- Facility: 0x000 (FACILITY_NULL: Default)
- Code: 0x01f5 (501)
- Sev: 0 (STATUS_SEVERITY_SUCCESS)
- C: 0 (Microsoft-defined)
- Facility: 0x000 (Default)
- Code: 0x01f5 (501)
Parameters
| Parameter | Description |
|---|---|
| 1 | Reserved |
| 2 | Reserved |
| 3 | Reserved |
| 4 | Reserved |
Description
The APPLICATION_HANG_KERNEL_LIVEDUMP has a value of 0x000001F5. This indicates that an application hung when attempting to be terminated.
(This code can never be used for a real BugCheck; it is used to identify live dumps.)
Cause
After an application hang report (such as that can be created with the WerReportHang function) was completed, TerminateProcess was called, but the target process failed to terminate, likely because a thread is hung in kernel mode.
This live kernel triage dump may contain the kernel thread states of the hung process. The kernel dump contains only the threads for the process which WER was unable to terminate, and only kernel, not user memory.
Resolution
The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.
See Also
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.