Hypervisor error, how to solve?

Anonymous
2024-03-28T00:19:36+00:00

On the last couple days I have been experiencing blue screens with the Hypervisor Error. Here is the latest analysis from the minidump. Can someone help me figure out what's the cause please? Already did the MemTest86 ram scan and it was all good!

******************************************************************************* * * * Bugcheck Analysis * * * *******************************************************************************

HYPERVISOR_ERROR (20001) The hypervisor has encountered a fatal error. Arguments: Arg1: 0000000000000011 Arg2: 000000000023271c Arg3: 0000000000001005 Arg4: ffffe70000c05c80

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2265

Key  : Analysis.Elapsed.mSec
Value: 5025

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

Key  : Analysis.Init.CPU.mSec
Value: 311

Key  : Analysis.Init.Elapsed.mSec
Value: 2793

Key  : Analysis.Memory.CommitPeak.Mb
Value: 100

Key  : Bugcheck.Code.LegacyAPI
Value: 0x20001

Key  : Bugcheck.Code.TargetModel
Value: 0x20001

Key  : Failure.Bucket
Value: 0x20001\_11\_23271c\_nt!HvlSkCrashdumpCallbackRoutine

Key  : Failure.Hash
Value: {f54431b0-ab71-a061-a7b7-43fb065d576a}

Key  : Hypervisor.Enlightenments.ValueHex
Value: 1497cf94

Key  : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key  : Hypervisor.Flags.ApicEnlightened
Value: 1

Key  : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 0

Key  : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key  : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key  : Hypervisor.Flags.CpuManager
Value: 1

Key  : Hypervisor.Flags.DeprecateAutoEoi
Value: 0

Key  : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key  : Hypervisor.Flags.Epf
Value: 0

Key  : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key  : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key  : Hypervisor.Flags.MaxBankNumber
Value: 0

Key  : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key  : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key  : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key  : Hypervisor.Flags.Phase0InitDone
Value: 1

Key  : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key  : Hypervisor.Flags.RootScheduler
Value: 0

Key  : Hypervisor.Flags.SynicAvailable
Value: 1

Key  : Hypervisor.Flags.UseQpcBias
Value: 0

Key  : Hypervisor.Flags.Value
Value: 4853999

Key  : Hypervisor.Flags.ValueHex
Value: 4a10ef

Key  : Hypervisor.Flags.VpAssistPage
Value: 1

Key  : Hypervisor.Flags.VsmAvailable
Value: 1

Key  : Hypervisor.RootFlags.AccessStats
Value: 1

Key  : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key  : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key  : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key  : Hypervisor.RootFlags.IsHyperV
Value: 1

Key  : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key  : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key  : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key  : Hypervisor.RootFlags.Nested
Value: 0

Key  : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key  : Hypervisor.RootFlags.Value
Value: 1015

Key  : Hypervisor.RootFlags.ValueHex
Value: 3f7

Key  : WER.OS.Branch
Value: ni\_release

Key  : WER.OS.Version
Value: 10.0.22621.1

BUGCHECK_CODE: 20001

BUGCHECK_P1: 11

BUGCHECK_P2: 23271c

BUGCHECK_P3: 1005

BUGCHECK_P4: ffffe70000c05c80

FILE_IN_CAB: 032724-13578-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffff8b00fb74dca8 fffff80614545311 : 0000000000020001 0000000000000011 000000000023271c 0000000000001005 : nt!KeBugCheckEx ffff8b00fb74dcb0 fffff8061449a390 : 0000000000000100 fffff806142b2d7c ffff8b00fb756340 ffff8b00fb74dd30 : nt!HvlSkCrashdumpCallbackRoutine+0x81 ffff8b00fb74dcf0 fffff80614425742 : 0000000000000100 ffff8b00fb74def0 0000000000000000 0000000000000000 : nt!KiProcessNMI+0x1e7830 ffff8b00fb74dd30 fffff806144254ae : 0000000000000100 ffff8b00fb74def0 0000000000000000 69f1e9cd7ffe1b0e : nt!KxNmiInterrupt+0x82 ffff8b00fb74de70 fffff806143d1ec3 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiNmiInterrupt+0x26e ffffbb0032092548 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!HalpHvTimerStop+0x23

SYMBOL_NAME: nt!HvlSkCrashdumpCallbackRoutine+81

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.3296

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 81

FAILURE_BUCKET_ID: 0x20001_11_23271c_nt!HvlSkCrashdumpCallbackRoutine

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f54431b0-ab71-a061-a7b7-43fb065d576a}

Followup: MachineOwner

***moved from Windows / Windows 11 / Performance and system failures***

Windows for business | Windows Client for IT Pros | Performance | System performance

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} vote
Accepted answer
  1. Anonymous
    2024-04-01T05:37:36+00:00

    Hello,

    Thank you for posting in Microsoft Community forum.

    Based on the description, I understand your question is related to BSOD HYPERVISOR_ERROR.

    The HYPERVISOR_ERROR bug check has a value of 0x00020001. This indicates that the hypervisor has encountered a fatal error.

    Bug Check 0x20001 HYPERVISOR_ERROR - Windows drivers | Microsoft Learn

    1. Try boot machine into safe mode, start Windows by using a minimal set of drivers and startup programs: Start your PC in safe mode in Windows - Microsoft Support
    2. Perform clean boot to avoid any third party software conflict.

    How to perform a clean boot in Windows

    1. This may cause by a driver, try run driver verifier:

    Start a Command Prompt window by selecting Run as administrator, and type verifier to open Driver Verifier Manager.

    Driver Verifier - Windows drivers | Microsoft Learn

    Have a nice day. 

    Best Regards,

    Molly

    0 comments No comments

0 additional answers

Sort by: Most helpful