hvservice.sys
Associated Error Codes
Below lists error codes and symbolic names found for this module.
| Code | Found in | Description |
|---|---|---|
| 0x1 | 10 | Hypervisor successfully started. |
| 0x2 | 10 | Hypervisor scheduler type is %1. |
| 0x3 | 10 | Hypervisor Eventlog for global system events could not be created! |
| 0x5 | 10 | Hypervisor launch has been disabled through the hypervisorlaunchtype bcdedit setting. |
| 0xd | 10 | Hypervisor fails to start ETW tracing session. |
| 0x14 | 10 | Hypervisor launch failed; sleep and hibernate could not be disabled (status %1). |
| 0x1a | 10 | Hypervisor launch failed; the hypervisor boot loader's internal logic failed (BalStatus %1, sub-status %2). |
| 0x1b | 10 | Hypervisor launch failed; the hypervisor boot loader was unable to allocate sufficient resources to perform the launch. |
| 0x1c | 10 | Hypervisor launch failed; the hypervisor boot loader does not support the vendor of at least one of the processors in the system. |
| 0x1f | 10 | Hyper-V launch failed; the system does not appear to have a sufficient level of ACPI support to launch the hypervisor. |
| 0x20 | 10 | Hypervisor launch failed; at least one of the processors in the system does not appear to provide a virtualization platform supported by the hypervisor. |
| 0x22 | 10 | Hyper-V launch failed; the image %1 could not be loaded (status %2). |
| 0x24 | 10 | Hypervisor launch failed; the image %1 failed code integrity checks, and cannot be used. |
| 0x25 | 10 | Hypervisor launch failed; the image %1 does not contain the image description datastructures, and cannot be used. |
| 0x26 | 10 | Hyper-V launch failed; at least one of the processors in the system was unable to launch the hypervisor (status %1). |
| 0x28 | 10 | Hypervisor launch failed; the hypervisor image is revision %1, but the currently installed virtualization software only supports launching revision %2 hypervisor images. |
| 0x29 | 10 | Hypervisor launch failed; Either VMX not present or not enabled in BIOS. |
| 0x2a | 10 | Hypervisor launch failed; Either SVM not present or not enabled in BIOS. |
| 0x2c | 10 | Hypervisor launch failed; Either No Execute feature (NX) not present or not enabled in BIOS. |
| 0x2e | 10 | Hypervisor launch failed; Processor does not support the minimum features required to run the hypervisor (MSR index %1, allowed bits %2, required bits %3). |
| 0x30 | 10 | Hypervisor launch failed; Processor does not provide the features necessary to run the hypervisor (leaf %1, register %2: features needed %3, features supported %4). |
| 0x36 | 10 | Hypervisor launch failed; Hypervisor image does not match the platform being run on. |
| 0x37 | 10 | Hypervisor launch failed; Required firmware table not found. |
| 0x38 | 10 | Hypervisor launch failed; Encountered invalid firmware information. |
| 0x3b | 10 | Hypervisor launch failed; Second Level Address Translation is required to launch the hypervisor. |
| 0x3c | 10 | Hypervisor launch failed; Secure Mode Extensions have been enabled by the BIOS. Please disable Secure Mode Extensions in the BIOS to launch Hyper-V. |
| 0x3d | 10 | Hypervisor launch failed; Minimum CPUID leaves required by the hypervisor are not supported on the system. |
| 0x3e | 10 | Hypervisor launch failed; The physical address limit supported has been exceeded. |
| 0x3f | 10 | Hypervisor launch failed; The hypervisor was unable to initialize successfully (phase %1), and was not started. This initialization failure may be the result of a platform configuration or firmware issue. Contact your system vendor for more information or updated firmware. |
| 0x40 | 10 | Hypervisor launch failed; Too many runtime services memory ranges described by firmware. |
| 0x50 | 10 | Hypervisor launch failed; The operating systems boot loader failed with error %1. |
| 0x51 | 10 | Hypervisor launch failed; The operating system boot loader was unable to locate a required resource. |
| 0x52 | 10 | Hypervisor launch failed; The operating system boot loader detected a persistent memory failure. |
| 0x53 | 10 | Hypervisor launch failed; The operating system boot loader was unable to allocate sufficient memory to complete the operation. |
| 0x54 | 10 | Hypervisor launch failed; The operating system boot loader was unable to allocate sufficient resources to complete the operation. |
| 0x55 | 10 | Hypervisor launch failed; The operating system boot loader detected a memory map conflict. |
| 0x56 | 10 | Hypervisor launch failed; the version of the microcode update dll does not match the current operating system. |
| 0x60 | 10 | Hypervisor processor startup failed (APIC ID %1, status %2). Further processors in the system were not started. |
| 0x61 | 10 | Hypervisor processor startup failed (APIC ID %1) due to CPUID feature validation error. Further processors in the system were not started. Leaf %2, register %3 feature mismatch: BSP has features %5; AP has features %4 |
| 0x81 | 10 | Hypervisor initialized I/O remapping. Hardware present: %1 Hardware enabled: %2 Policy: %3 Enabled features: %4 Internal information: %5 Problems: %6 Additional information: %7 |
| 0x82 | 10 | Hypervisor I/O remapping is forcibly enabled by policy (the hypervisoriommupolicy BCD option is set to enable). If the system exhibits instability or reduced performance, consider restoring the default policy. |
| 0x90 | 10 | A device is operating with reduced performance because of a problem with the system BIOS. The device is not reported under the scope of a unique I/O remapping unit. Device ID: %1 Partition ID: %2 |
| 0x91 | 10 | A device will not work correctly because of a problem with the system BIOS. The Requester IDs reported for the device overlap with those reported for another device. Device ID: %1 Partition ID: %2 |
| 0x92 | 10 | A device will not work correctly because the hypervisor does not have enough resources. Device ID: %1 Partition ID: %2 |
| 0x93 | 10 | A device will not work correctly because of a problem with the system BIOS. An IOAPIC is not correctly reported. IOAPIC ID: %1 |
| 0x94 | 10 | A device could not be used by a child partition because of a limitation of the system hardware and BIOS. The I/O remapping unit that controls the device does not have sufficient capabilities. Device ID: %1 I/O remapping unit base address: %2 Partition ID: %3 |
| 0x95 | 10 | A device could not be used by a child partition because of a limitation of the system hardware and BIOS. The device cannot be securely used by a child partition. Device ID: %1 Partition ID: %2 |
| 0x98 | 10 | The image %1 could not be read (status %2). |
| 0x99 | 10 | The image %1 failed code integrity checks, and cannot be used. |
| 0x9a | 10 | Hypervisor failed to properly synchronize TSC across logical processors (Max delta: %1, Min delta: %2). |
| 0x9d | 10 | The hypervisor did not enable mitigations for CVE-2018-3646 for virtual machines because HyperThreading is enabled and the hypervisor core scheduler is not enabled. To enable mitigations for CVE-2018-3646 for virtual machines, enable the core scheduler by running "bcdedit /set hypervisorschedulertype core" from an elevated command prompt and reboot. |
| 0x9e | 10 | The queried interface version %1 is not supported (Min : %2, Max : %3). |
| 0x9f | 10 | The queried interface is incomplete. |
| 0xa0 | 10 | Partition persistence services will be unavailable. |
| 0xa1 | 10 | The configured Minroot settings are not compatible with the hypervisor core scheduler and have been overriden. This may expose a different number of logical processors to the root partition. |
| 0xa2 | 10 | Failed to unregister the remote hypercall interface (status %1). |
| 0xa5 | 10 | Hypervisor configured mitigations for CVE-2019-11091, CVE-2018-12126, CVE-2018-12127, CVE-2018-12130 for virtual machines. Processor not affected: %1 Processor family not affected: %2 Processor supports microarchitectural buffer flush: %3 Buffer flush needed: %4 |
| 0x30000000 | 10 | Info |
| 0x50000002 | 10 | Error |
| 0x50000003 | 10 | Warning |
| 0x50000004 | 10 | Information |
| 0x90000001 | 10 | Microsoft-Windows-Hyper-V-Hypervisor |
| 0x90000002 | 10 | System |
| 0xb000000a | 10 | Hypervisor Eventlog creation failed! |
| 0xb000000b | 10 | Hypervisor Eventlog deletion failed! |
| 0xb0000027 | 10 | Hypervisor Load Options - %1. |
| 0xb000009b | 10 | Host processor features mask: %1 Host xsave features mask: %2 Host cache line flush size: %3 bytes |
| 0xb000009c | 10 | Hypervisor configured mitigations for CVE-2018-3646 for virtual machines. Processor not affected: %1 Processor family not affected: %2 Processor supports cache flush: %3 HyperThreading enabled: %4 Parent hypervisor applies mitigations: %5 Mitigations disabled by bcdedit: %6 Mitigations enabled: %7 Cache flush needed: %8 |
| 0xb00000a3 | 10 | The hypervisor encountered an internal error: nested NMI (processor %1). |
| 0xb00000a4 | 10 | The hypervisor encountered an internal error: IPI timeout (processor %1). |
| 0xb0002103 | 10 | Hyper-V failed creating a new partition (status %1)! |
| 0xb0003106 | 10 | Hyper-V detected access to a restricted MSR (Msr: %1, IsWrite: %2, MsrValue: %3, AccessStatus: %4, Pc: %5, ImageBase: %6, ImageChecksum: %7, ImageTimestamp: %8, ImageName: %9). |
| 0xb0004101 | 10 | Hyper-V successfully created a new partition (partition %1). |
| 0xb0004102 | 10 | Hyper-V successfully deleted a partition (partition %1). |
| 0xb001009b | 10 | Host processor features mask: %2 Host xsave features mask: %3 Host cache line flush size: %4 bytes |
| 0xb001009c | 10 | Hypervisor initial page allocation NUMA policy: %1 |
| 0xd0000001 | 10 | Connect IOCTL failed when registering interface. |
| 0xd0000002 | 10 | Registering remote hypercall interface failed. |
| 0xd0000003 | 10 | Library initialization failed when registering interface. |
| 0xd0000004 | 10 | NUMA distribution disabled |
| 0xd0000005 | 10 | Even NUMA distribution |
| 0xd0000006 | 10 | Proportional NUMA distribution |
| 82 entries | ||