Need help tracking down Hypervisor Error

Question

Hello

My son's laptop keeps blue screening. I thought it was a RAM problem but after replacing the memory, the problem exists. We can seem to recreate on demand though. Here is the mini dump file.

HYPERVISOR_ERROR (20001) The hypervisor has encountered a fatal error.Arguments:Arg1: 0000000000000011Arg2: 000000000023272cArg3: 0000000000001005Arg4: ffffe70001c05c80Debugging Details:------------------KEY_VALUES_STRING: 1Key  : Analysis.CPU.mSecValue: 2718Key  : Analysis.Elapsed.mSecValue: 6363Key  : Analysis.IO.Other.MbValue: 1Key  : Analysis.IO.Read.MbValue: 0Key  : Analysis.IO.Write.MbValue: 32Key  : Analysis.Init.CPU.mSecValue: 389Key  : Analysis.Init.Elapsed.mSecValue: 38606Key  : Analysis.Memory.CommitPeak.MbValue: 105Key  : Bugcheck.Code.LegacyAPIValue: 0x20001Key  : Bugcheck.Code.TargetModelValue: 0x20001Key  : Dump.Attributes.AsUlongValue: 808Key  : Dump.Attributes.KernelGeneratedTriageDumpValue: 1Key  : Failure.BucketValue: 0x20001_11_23272c_amdppm!HvRequestIdleKey  : Failure.HashValue: {4d98ffa3-8a44-5713-1aed-008b8f6757bc}Key  : Hypervisor.Enlightenments.ValueHexValue: 1497cf94Key  : Hypervisor.Flags.AnyHypervisorPresentValue: 1Key  : Hypervisor.Flags.ApicEnlightenedValue: 1Key  : Hypervisor.Flags.ApicVirtualizationAvailableValue: 0Key  : Hypervisor.Flags.AsyncMemoryHintValue: 0Key  : Hypervisor.Flags.CoreSchedulerRequestedValue: 0Key  : Hypervisor.Flags.CpuManagerValue: 1Key  : Hypervisor.Flags.DeprecateAutoEoiValue: 0Key  : Hypervisor.Flags.DynamicCpuDisabledValue: 1Key  : Hypervisor.Flags.EpfValue: 0Key  : Hypervisor.Flags.ExtendedProcessorMasksValue: 1Key  : Hypervisor.Flags.HardwareMbecAvailableValue: 1Key  : Hypervisor.Flags.MaxBankNumberValue: 0Key  : Hypervisor.Flags.MemoryZeroingControlValue: 0Key  : Hypervisor.Flags.NoExtendedRangeFlushValue: 0Key  : Hypervisor.Flags.NoNonArchCoreSharingValue: 1Key  : Hypervisor.Flags.Phase0InitDoneValue: 1Key  : Hypervisor.Flags.PowerSchedulerQosValue: 0Key  : Hypervisor.Flags.RootSchedulerValue: 0Key  : Hypervisor.Flags.SynicAvailableValue: 1Key  : Hypervisor.Flags.UseQpcBiasValue: 0Key  : Hypervisor.Flags.ValueValue: 4853999Key  : Hypervisor.Flags.ValueHexValue: 4a10efKey  : Hypervisor.Flags.VpAssistPageValue: 1Key  : Hypervisor.Flags.VsmAvailableValue: 1Key  : Hypervisor.RootFlags.AccessStatsValue: 1Key  : Hypervisor.RootFlags.CrashdumpEnlightenedValue: 1Key  : Hypervisor.RootFlags.CreateVirtualProcessorValue: 1Key  : Hypervisor.RootFlags.DisableHyperthreadingValue: 0Key  : Hypervisor.RootFlags.HostTimelineSyncValue: 1Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabledValue: 0Key  : Hypervisor.RootFlags.IsHyperVValue: 1Key  : Hypervisor.RootFlags.LivedumpEnlightenedValue: 1Key  : Hypervisor.RootFlags.MapDeviceInterruptValue: 1Key  : Hypervisor.RootFlags.MceEnlightenedValue: 1Key  : Hypervisor.RootFlags.NestedValue: 0Key  : Hypervisor.RootFlags.StartLogicalProcessorValue: 1Key  : Hypervisor.RootFlags.ValueValue: 1015Key  : Hypervisor.RootFlags.ValueHexValue: 3f7BUGCHECK_CODE:  20001BUGCHECK_P1: 11BUGCHECK_P2: 23272cBUGCHECK_P3: 1005BUGCHECK_P4: ffffe70001c05c80FILE_IN_CAB:  062524-20500-01.dmpTAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202bDUMP_FILE_ATTRIBUTES: 0x808Kernel Generated Triage DumpCUSTOMER_CRASH_COUNT:  1PROCESS_NAME:  SystemSTACK_TEXT:ffffd880895deca8 fffff80485545a81     : 0000000000020001 0000000000000011 000000000023272c 0000000000001005 : nt!KeBugCheckExffffd880895decb0 fffff8048546dc84     : 0000000000000100 fffff80485206f2c ffffd880895ed340 ffffd880895ded30 : nt!HvlSkCrashdumpCallbackRoutine+0x81ffffd880895decf0 fffff80485428282     : 0000000000000100 ffffd880895deef0 0000000000000000 0000000000000000 : nt!KiProcessNMI+0x2672d4ffffd880895ded30 fffff80485427fee     : 0000000000000100 ffffd880895deef0 0000000000000000 0000000000000000 : nt!KxNmiInterrupt+0x82ffffd880895dee70 fffff80480a10003     : fffff804853cc987 00000022ae233dab 0000000000989680 0000000000000004 : nt!KiNmiInterrupt+0x26effffec82e4e924a8 fffff804853cc987     : 00000022ae233dab 0000000000989680 0000000000000004 0000000000000000 : 0xfffff80480a10003ffffec82e4e924b0 fffff80485544cd5     : fffff804853d42c0 fffff8048534f007 ffffc308d25b5ba0 fffff8049ab79d30 : nt!HvcallInitiateHypercall+0x57ffffec82e4e92530 fffff8049ab79d5d     : 00000000000100de 0000000000989680 000000d181e93b00 ffffd88089517180 : nt!HvlRequestProcessorHalt+0x35ffffec82e4e92560 fffff8049ab7c265     : ffffc308d2593000 0000000000000000 ffffc308ca0ff640 fffff8049ab715d1 : amdppm!HvRequestIdle+0x2dffffec82e4e925b0 fffff80485276e96     : 0000000000000000 ffffd88089517180 0000000000000000 ffffd88089517180 : amdppm!LpiIdleExecute+0xb5ffffec82e4e92600 fffff80485276a0b     : ffffd88089517180 0000000000000000 0000000000000000 0000000000000000 : nt!PpmIdleExecuteTransition+0x426ffffec82e4e92a50 fffff8048541f204     : 0000000000000000 ffffc308c8f5f040 ffffc308e20ea080 ffffc308df449080 : nt!PoIdle+0x68bffffec82e4e92c40 0000000000000000     : ffffec82e4e93000 ffffec82e4e8d000 0000000000000000 00000000`00000000 : nt!KiIdleLoop+0x54SYMBOL_NAME:  amdppm!HvRequestIdle+2dMODULE_NAME: amdppmIMAGE_NAME:  amdppm.sysIMAGE_VERSION:  10.0.22621.3790STACK_COMMAND:  .cxr; .ecxr ; kbBUCKET_ID_FUNC_OFFSET:  2dFAILURE_BUCKET_ID:  0x20001_11_23272c_amdppm!HvRequestIdleOSPLATFORM_TYPE:  x64OSNAME:  Windows 10FAILURE_ID_HASH:  {4d98ffa3-8a44-5713-1aed-008b8f6757bc}Followup:     MachineOwner---------