| Previous | Next |
| VIDEO_TDR_TIMEOUT_DETECTED | VIDEO_SCHEDULER_INTERNAL_ERROR |
NTHV_GUEST_ERROR
Hyper-V guest fatal error for NTHV_GUEST_ERROR
NTHV_GUEST_ERROR is bug check code 0x00000118. This bug check is tied to a Windows guest running with Hyper-V or enlightenment interfaces. It indicates a fatal condition in the guest/hypervisor contract rather than a generic application-level crash.
How to read it in a dump for NTHV_GUEST_ERROR
- Check whether the system is a VM or uses virtualization-based security.
- Hypervisor version, virtual hardware, synthetic devices, and integration components are key evidence.
- The dump should be correlated with host logs when available.
What to check for NTHV_GUEST_ERROR
- Review recent host, hypervisor, and guest integration updates.
- Check virtual hardware configuration and VBS/Hyper-V settings.
- Collect both guest dump and host event logs if the machine is virtualized.
References for NTHV_GUEST_ERROR
Dump evidence for NTHV_GUEST_ERROR
For NTHV_GUEST_ERROR, 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 “NTHV_GUEST_ERROR”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for NTHV_GUEST_ERROR
- Run WinDbg
!analyze -v, then inspect the documented meaning of each NTHV_GUEST_ERROR parameter instead of relying only on the probably-caused-by line. - For NTHV_GUEST_ERROR, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with nthv / guest.
- For NTHV_GUEST_ERROR, 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 NTHV_GUEST_ERROR before collecting the dump and event logs. For NTHV_GUEST_ERROR, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Dump evidence for NTHV_GUEST_ERROR
For NTHV_GUEST_ERROR, 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 “NTHV_GUEST_ERROR”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order for NTHV_GUEST_ERROR
- Run WinDbg
!analyze -v, then inspect the documented meaning of each NTHV_GUEST_ERROR parameter instead of relying only on the probably-caused-by line. - For NTHV_GUEST_ERROR, find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with nthv / guest.
- For NTHV_GUEST_ERROR, 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 NTHV_GUEST_ERROR before collecting the dump and event logs. For NTHV_GUEST_ERROR, 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.