| Previous | Next |
| SAVER_WAITFORSHELLREADY | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M |
HYPERVISOR_ERROR
The HYPERVISOR_ERROR bug check has a value of 0x00020001. This indicates that the hypervisor has encountered a fatal error.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
HYPERVISOR_ERROR Parameters
| Parameter | Description |
|---|---|
| 1 | Reserved |
| 2 | Reserved |
| 3 | Reserved |
| 4 | Reserved |
Resolution for HYPERVISOR_ERROR
For HYPERVISOR_ERROR, The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.
Dump evidence for HYPERVISOR_ERROR
For HYPERVISOR_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 “HYPERVISOR_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 HYPERVISOR_ERROR
- Run WinDbg
!analyze -v, then inspect the documented meaning of each HYPERVISOR_ERROR parameter instead of relying only on the probably-caused-by line. - Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with hypervisor.
- For HYPERVISOR_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 HYPERVISOR_ERROR before collecting the dump and event logs. For HYPERVISOR_ERROR, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Distinctive failure boundary for HYPERVISOR_ERROR
HYPERVISOR_ERROR identifies unrecoverable hypervisor condition. Collect hypervisor enlightenment data, virtualization platform events, firmware and microcode revisions, processor topology, nested-virtualization state, and the hypervisor-specific dump fields.
Separating HYPERVISOR_ERROR from neighboring bug checks
Separate a hypervisor failure from a guest driver stack error: the decisive evidence is in the hypervisor context and platform logs. For HYPERVISOR_ERROR, preserve the original dump and use the documented parameters and stack to verify this distinction before changing drivers or platform configuration.
Looking for a different code? Search another status or error code.