| Previous | Next |
| SAVER_WAITFORSHELLREADY | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M |
HYPERVISOR_ERROR
The result 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 it, The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause.
Dump evidence
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 “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each 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.
- 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 this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Distinctive failure boundary
This result 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 the result 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. 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.