Hypervisor Error, how to fix?

Question

My PC keeps crashing randomly, sometimes getting BSOD sometimes not. It happens most often while playing certain games, some games seem to be immune to it.

I've tried updating all the drivers, using different USB ports, removing SSD, lowering settings on the games that causes crashing.

Hypervisor error is the most common message I get when the crash occurs, but I have no clue what to do anymore.

Here's a debug results I got from the dumpfile if they're any help:

HYPERVISOR_ERROR (20001) The hypervisor has encountered a fatal error. Arguments: Arg1: 0000000000000011 Arg2: 00000000002b2595 Arg3: 0000000000001005 Arg4: ffffe70001c05a30

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 2421

Key  : Analysis.Elapsed.mSec
Value: 10414

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

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

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

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

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

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

Key  : Bugcheck.Code.LegacyAPI
Value: 0x20001

Key  : Dump.Attributes.AsUlong
Value: 808

Key  : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

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

Key  : Failure.Hash
Value: {7249ae88-7af6-1ec9-5c28-847186b6bdf7}

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

BUGCHECK_CODE: 20001

BUGCHECK_P1: 11

BUGCHECK_P2: 2b2595

BUGCHECK_P3: 1005

BUGCHECK_P4: ffffe70001c05a30

FILE_IN_CAB: 050323-13156-01.dmp

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

DUMP_FILE_ATTRIBUTES: 0x808 Kernel Generated Triage Dump

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd580247e2ca8 fffff80516d38ad1 : 0000000000020001 0000000000000011 00000000002b2595 0000000000001005 : nt!KeBugCheckEx ffffd580247e2cb0 fffff80516c76a76 : 0000000000000100 fffff80516a0770c ffffd580247eb340 ffffd580247e2d30 : nt!HvlSkCrashdumpCallbackRoutine+0x81 ffffd580247e2cf0 fffff80516c39542 : 0000000000000100 ffffd580247e2ef0 0000000000000000 0000000000000000 : nt!KiProcessNMI+0x26fa96 ffffd580247e2d30 fffff80516c392ae : 0000000000000100 ffffd580247e2ef0 0000000000000000 0000000000000000 : nt!KxNmiInterrupt+0x82 ffffd580247e2e70 fffff80516abc7ef : ffffffffffffffff fffff78000000340 0000000000000000 0000000000001388 : nt!KiNmiInterrupt+0x26e fffff5856a03e050 fffff80516a18d97 : ffffd580247a6180 ffffffffffffffff fffff5856a03e338 0000000000000000 : nt!KiSetNextClockTickDueTime+0x6ff fffff5856a03e290 fffff80516ac0ed9 : 000000838a3d5f69 fffff5856a03e3d0 000000838a3d5a96 000000838ab9d7f3 : nt!KiRestoreClockTickRate+0x77 fffff5856a03e2d0 fffff80516abf3c9 : fffff7e50001fca8 0000000000989680 0000000000000000 0000000000000000 : nt!KeResumeClockTimerFromIdle+0x11a9 fffff5856a03e590 fffff80516abda1b : 0000000000000000 0000000000000000 0000000000000000 fffff80516c27a10 : nt!PpmIdleExecuteTransition+0x1949 fffff5856a03ea50 fffff80516c306a4 : 0000000000000000 ffffe588ba894040 ffffe588d0255080 ffffe588d1b20380 : nt!PoIdle+0x67b fffff5856a03ec40 0000000000000000 : fffff5856a03f000 fffff5856a039000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME: nt!HvlSkCrashdumpCallbackRoutine+81

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.1635

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 81

FAILURE_BUCKET_ID: 0x20001_11_2b2595_nt!HvlSkCrashdumpCallbackRoutine

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7249ae88-7af6-1ec9-5c28-847186b6bdf7}

Followup: MachineOwner

Let me know if I can provide more info that'll help solve this problem, please and thank you.

Answer 1

Hi Funamitan,

Thanks for sharing the minidump files.

The minidump files indicate amdppm.sys as a cause of the BSOD which is related to the AMD processor device driver.

To troubleshoot this issue, kindly download and install the latest BIOS & Chipset drivers from the manufacturer's website.

If you are overclocking your PC, try running everything (CPU, GPU, system memory) at their stock speeds. See if the issue is still reproducible. Or, turn off XMP profile or set it to Auto.

Please do not hesitate to ask if you need further assistance.

Stay safe

Answer 2

Hi Funamitan,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

Kindly check C:\Windows\Minidump and copy available minidump files to the desktop then share them via One Drive or Google Drive in order to be analyzed and indicate which file is causing the crash.

https://answers.microsoft.com/en-us/windows/for...

Also, check C:\Windows and share the MEMORY.DMP file.

If the folder is empty or the MEMORY.DMP is not available, kindly share the Event viewer logs:

https://www.yourwindowsguide.com/2017/12/how-to...

Regards,

____________________________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

Answer 3

Here are the minidump files: Minidump

and here is the Event viewer logs: Event viewer log.evtxThere was no MEMORY.DMP in my Windows folder.