BSOD Hypervisor Error (20001)

Question

Hello,

My PC crashed a third time in a month, I'm unsure of the cause. I've run a dump check using the windows debugger, the results are below. Need help to interpret?

Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\053124-11859-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 22621 MP (32 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Edition build lab: 22621.1.amd64fre.ni_release.220506-1250

Kernel base = 0xfffff8071c000000 PsLoadedModuleList = 0xfffff8071cc13080

Debug session time: Fri May 31 16:18:21.134 2024 (UTC + 10:00)

System Uptime: 0 days 2:20:54.771

Loading Kernel Symbols

...............................................................

................................................................

................................................................

...........................................

Loading User Symbols

Loading unloaded module list

...........

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff8071c419fe0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd28071947cb0=0000000000020001

6: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

HYPERVISOR_ERROR (20001)

The hypervisor has encountered a fatal error.

Arguments:

Arg1: 0000000000000011

Arg2: 000000000020f24f

Arg3: 0000000000001005

Arg4: ffffe70001205530

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec 

Value: 296 

Key  : Analysis.Elapsed.mSec 

Value: 4110 

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: 62 

Key  : Analysis.Init.Elapsed.mSec 

Value: 7995 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 99 

Key  : Bugcheck.Code.LegacyAPI 

Value: 0x20001 

Key  : Bugcheck.Code.TargetModel 

Value: 0x20001 

Key  : Failure.Bucket 

Value: 0x20001\_11\_20f24f\_nt!HvlSkCrashdumpCallbackRoutine 

Key  : Failure.Hash 

Value: {20447b65-5cae-fdd0-a1bf-ed6d6c2d50db} 

Key  : Hypervisor.Enlightenments.ValueHex 

Value: 1417df84 

Key  : Hypervisor.Flags.AnyHypervisorPresent 

Value: 1 

Key  : Hypervisor.Flags.ApicEnlightened 

Value: 0 

Key  : Hypervisor.Flags.ApicVirtualizationAvailable 

Value: 1 

Key  : Hypervisor.Flags.AsyncMemoryHint 

Value: 0 

Key  : Hypervisor.Flags.CoreSchedulerRequested 

Value: 0 

Key  : Hypervisor.Flags.CpuManager 

Value: 1 

Key  : Hypervisor.Flags.DeprecateAutoEoi 

Value: 1 

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: 21631230 

Key  : Hypervisor.Flags.ValueHex 

Value: 14a10fe 

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: 20f24f

BUGCHECK_P3: 1005

BUGCHECK_P4: ffffe70001205530

FILE_IN_CAB: 053124-11859-01.dmp

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

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:

ffffd28071947ca8 fffff8071c5458c1 : 0000000000020001 0000000000000011 000000000020f24f 0000000000001005 : nt!KeBugCheckEx

ffffd28071947cb0 fffff8071c46da84 : 0000000000000100 fffff8071c206f2c ffffd280719553d0 ffffd28071947d30 : nt!HvlSkCrashdumpCallbackRoutine+0x81

ffffd28071947cf0 fffff8071c428082 : 0000000000000100 ffffd28071947ef0 0000000000000000 0000000000000000 : nt!KiProcessNMI+0x2670d4

ffffd28071947d30 fffff8071c427dee : 0000000000000100 ffffd28071947ef0 0000000000000000 0000000000000000 : nt!KxNmiInterrupt+0x82

ffffd28071947e70 fffff807192d0003 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiNmiInterrupt+0x26e

ffffcf070c0bf408 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0xfffff807`192d0003

SYMBOL_NAME: nt!HvlSkCrashdumpCallbackRoutine+81

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.3672

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 81

FAILURE_BUCKET_ID: 0x20001_11_20f24f_nt!HvlSkCrashdumpCallbackRoutine

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {20447b65-5cae-fdd0-a1bf-ed6d6c2d50db}

Followup: MachineOwner

---

Answer 1

Hi, Harland

Welcome to Microsoft Community.

We understand that you are experiencing blue screen issues, and judging by the contents of the file you posted, the program that is causing your blue screen is ntkrnlmp.exe , which is the

system kernel, which is usually related to drivers or hardware. There is a higher chance that this blue screen is caused by an incompatible driver installed in your device.

We suggest that you try to download the main driver BIOS, discrete graphics card, core graphics card, wired network card and wireless network card driver installation package for the corresponding device model through the official website of the device brand, overlay and install it into the device, restart the device after installation, and continue to use the device for a period of time according to your usual usage habits, and then see if there will still be a blue screen. (Note: Please do not use a third-party program to download).

Then try to repair the system

1. Search for CMD, find the Command Prompt, and choose to run in administrator mode.
2. Enter the following commands one by one, and be sure to execute the next command after the previous one is completed. DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /RestoreHealth SFC /Scannow
3. After the scan is complete, you can check the scan information to see if the problem has been detected and fixed.

Sincerely

Nicholas.Z | Microsoft Community Support Specialist

Answer 2

Thanks Nicolas,

I'll let you know of the results.