HYPERVISOR_ERROR (20001)

Question

minidump: https://1drv.ms/u/s!App9OdKe1fsvhYJJStUbmwbHJ7G06Q?e=c6B0Mr

could those memeory dump able to identiy which hardware failed? memory test passed on the machine by win11 built-in tool.
https://answers.microsoft.com/en-us/windows/forum/windows_11-performance/bosd-failurebucketid-ipmisaligned/35c2fe47-3a09-4645-9863-19e353a29768?messageId=ae652f9e-4201-42d0-8a6f-c317e46a1af7

Microsoft (R) Windows Debugger Version 10.0.25111.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\060722-20703-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 22000 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff801`0c600000 PsLoadedModuleList = 0xfffff801`0d229b90
Debug session time: Mon Jun  6 17:28:33.704 2022 (UTC + 8:00)
System Uptime: 6 days 3:09:36.684
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
..................................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`0ca16b40 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8000`1c0fecb0=0000000000020001
11: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000011
Arg2: 00000000002c6309
Arg3: 0000000000001003
Arg4: ffffe80001a0e9f0

Debugging Details:
------------------

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 6609

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 19725

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

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

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

    Key  : WER.OS.Branch
    Value: co_release

    Key  : WER.OS.Timestamp
    Value: 2021-06-04T16:28:00Z

    Key  : WER.OS.Version
    Value: 10.0.22000.1

FILE_IN_CAB:  060722-20703-01.dmp

BUGCHECK_CODE:  20001

BUGCHECK_P1: 11

BUGCHECK_P2: 2c6309

BUGCHECK_P3: 1003

BUGCHECK_P4: ffffe80001a0e9f0

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffff8000`1c0feca8 fffff801`0cb46e9b     : 00000000`00020001 00000000`00000011 00000000`002c6309 00000000`00001003 : nt!KeBugCheckEx
ffff8000`1c0fecb0 fffff801`0ca62c8e     : 00000000`00000000 fffff801`0c82484c ffff8000`1c0ff340 ffff8000`1c0fed30 : nt!HvlSkCrashdumpCallbackRoutine+0x6b
ffff8000`1c0fecf0 fffff801`0ca22b82     : 00000000`00000000 ffff8000`1c0feef0 00000000`00000000 ffffb582`8fcb52f0 : nt!KiProcessNMI+0x23eece
ffff8000`1c0fed30 fffff801`0ca22903     : 00000000`00000000 00000000`00000000 61502d64`65726975 31343065`67616b63 : nt!KxNmiInterrupt+0x82
ffff8000`1c0fee70 fffff801`0c88d224     : 00000001`ffffffff 000000e0`00000001 00000000`00000000 ffffffff`ffffffff : nt!KiNmiInterrupt+0x243
ffffb582`8fcb5250 fffff801`0c88cd25     : ffff8000`1c0c0180 000004d1`7b82f0b0 00000000`00000000 ffffb582`8fcb52f0 : nt!KiFindNextTimerDueTime+0x244
ffffb582`8fcb52d0 fffff801`0cb68923     : 00000000`00000000 ffff8000`1c0c0180 000004d1`7b82f0b0 fffff801`0c998ce5 : nt!KiGetNextTimerExpirationDueTime+0x75
ffffb582`8fcb5340 fffff801`0cbc3382     : fffff801`00000002 ffffffff`ffffffff 00000000`0000434a 00000000`00000000 : nt!KeEstimateClockTickDuration+0xb3
ffffb582`8fcb53a0 fffff801`0caae8bb     : fffff801`0d2f8b40 ffff8000`1c0c0180 00000000`00000000 00000000`00000001 : nt!PpmEstimateIdleDuration+0xde
ffffb582`8fcb5570 fffff801`0c8886f6     : 00000000`00000000 fffff801`0c82a32a 00000000`cc000000 00000000`00000000 : nt!PpmIdleSelectStates+0x111bdb
ffffb582`8fcb5a70 fffff801`0ca1aa44     : 00000000`00000000 00000000`00000000 ffff8000`1c0cc440 00000000`000016e2 : nt!PoIdle+0x226
ffffb582`8fcb5c40 00000000`00000000     : ffffb582`8fcb6000 ffffb582`8fcb0000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME:  nt!HvlSkCrashdumpCallbackRoutine+6b

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.675

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  6b

FAILURE_BUCKET_ID:  0x20001_11_2c6309_nt!HvlSkCrashdumpCallbackRoutine

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {55fecba1-1eb0-ea8f-a250-9902d6ba898e}

Followup:     MachineOwner
---------

Answer 1

This is indeed a driver component of AMD, but it is not necessarily cpu-related, and this may also be a problem with AMD's GPU or chipset.

Answer 2

Does following message indicated CPU failure?

SYMBOL_NAME:  nt!KiSystemServiceExit+11a

STACK_COMMAND:  .cxr; .ecxr ; kb

MODULE_NAME: AuthenticAMD

IMAGE_NAME:  AuthenticAMD.sys

FAILURE_BUCKET_ID:  IP_MISALIGNED_AuthenticAMD.sys

OS_VERSION:  10.0.22000.1

BUILDLAB_STR:  co_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {716d112a-8330-4bbb-160c-ec98297019d2}

Followup:     MachineOwner

Answer 3

Hello, I'm A&K, here to help.

Your dump file shows a problem with the system kernel, which is a very common error that may be caused by the driver, but the dump file does not record the specific driver name. It is recommended to try to uninstall all major device drivers (GPU, chipset, etc.) first, and then go to the device manufacturer's official website to download the latest version and reinstall it.