| 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.
HYPERVISOR_ERROR Parameters
| Parameter | Description |
|---|---|
| 1 | Reserved |
| 2 | Reserved |
| 3 | Reserved |
| 4 | Reserved |
Resolution
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.
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 preceding the stop: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang.
- Keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
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.