Question BSOD help, please

[Drewb628]

Been getting a lot of BSoD lately. Seems to be happening during high load periods like gaming and video exporting from premier pro. Sometimes I will get stuck in a BSoD loop on startup which is concerning that one of these times I won't get back to windows.

I have ran CPU checks using intel and RAM checks using Windows. Here are my system specs and the bugcheck report (which sadly I have no idea how to read). Any help would be greatly appreciated.

OS Name: Microsoft Windows 11 Home - Version 10.0.26100 Build 26100
Processor: 13th Gen Intel(R) Core(TM) i9-13900K, 3000 Mhz, 24 Core(s), 32 Logical Processor(s)
BaseBoard Product: ROG MAXIMUS Z790 HERO
Installed Physical Memory (RAM): 64.0 GB
Graphics Card - Nvidia GeForce 4090
Power Supply: Corsair HX Series, HX1200, 1200 Watt, Fully Modular Power Supply, 80+ Platinum Certified, Model Number: CP-9020140-NA (2.5 years old, new when installed)
Disk Drives: qty 1 SAMSUNG 980 PRO SSD 2TB PCIe NVMe Gen 4, qty 2 Samsung 970 EVO Plus SSD 1TB NVMe M.2 Internal Solid State Hard Drive, (all around 1/3 capacity used)
Connected Peripherals: 3 monitors, GoXLR, elgato webcam, mouse and keyboard.
Network - Wired

Event Log:

https://imgur.com/a/TU1U5Vk

View: https://imgur.com/a/TU1U5Vk



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

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1046

Key : Analysis.Elapsed.mSec
Value: 2154

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27829.1001

Key : Analysis.Version.Description
Value: 10.2503.24.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2503.24.1

Key : Bugcheck.Code.LegacyAPI
Value: 0x20001

Key : Bugcheck.Code.TargetModel
Value: 0x20001

Key : Dump.Attributes.AsUlong
Value: 0x1808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x20001_11_ffffef872b564000_intelppm!HvRequestIdle

Key : Failure.Hash
Value: {48dead97-3611-2012-0f28-6e212f402a1d}

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84

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

Key : Hypervisor.Flags.ValueHex
Value: 0x34a10fe

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: 0x3f7

Key : Stack.Pointer
Value: NMI


BUGCHECK_CODE: 20001

BUGCHECK_P1: 11

BUGCHECK_P2: ffffef872b564000

BUGCHECK_P3: 1005

BUGCHECK_P4: ffffe70001005cd0

FILE_IN_CAB: 060325-13562-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffbf838861c280

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffa901`d6bf5ca8 fffff803`bfb8e72a : 00000000`00020001 00000000`00000011 ffffef87`2b564000 00000000`00001005 : nt!KeBugCheckEx
ffffa901`d6bf5cb0 fffff803`bfbbae81 : ffffbf83`8849df40 fffff803`bfbcd0d6 ffffa901`d6f7c3d0 ffffa901`d6bf5d30 : nt!HvlSkCrashdumpCallbackRoutine+0x8a
ffffa901`d6bf5cf0 fffff803`bfcb15c2 : 00000000`00000100 ffffa901`d6bf5ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xb1
ffffa901`d6bf5d30 fffff803`bfcb132e : 7b2fb1a7`24e504a6 00000000`00000100 ffffa901`d6bf5ef0 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffa901`d6bf5e70 fffff803`4e100003 : fffff803`bf9e8a88 00000000`00000047 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x26e
ffff9404`49b6f7d8 fffff803`bf9e8a88 : 00000000`00000047 00000000`00000000 00000000`00000000 00000000`0000000a : 0xfffff803`4e100003
ffff9404`49b6f7e0 fffff803`bfb8d7d6 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvcallInitiateHypercall+0x68
ffff9404`49b6f870 fffff803`6d27d59d : 00000000`000100de fffff803`bfaeb80c 00000000`00000001 ffffbf83`98eb09d0 : nt!HvlRequestProcessorHalt+0x26
ffff9404`49b6f8a0 fffff803`6d273c03 : 000000b9`793c85c2 ffff9404`49b6fa20 ffff1d48`22ea87af ffffbf83`98eb09d0 : intelppm!HvRequestIdle+0x2d
ffff9404`49b6f8f0 fffff803`bf9fd30b : 00000000`ffffffff ffff9404`49b6fa20 ffffbf83`99c0b000 ffffa901`d6fd1180 : intelppm!AcpiCStateIdleExecute+0x23
ffff9404`49b6f920 fffff803`bf9fc097 : ffffbf83`99c0b000 ffffbf83`99c0b000 ffff9404`49b6fb19 ffffa901`d6fd1180 : nt!PpmIdleExecuteTransition+0x5ab
ffff9404`49b6fab0 fffff803`bfca65e4 : ffffa901`d6fd1180 ffffa901`d6fd1100 00000000`00000000 fffff803`bfbbc200 : nt!PoIdle+0x187
ffff9404`49b6fb80 00000000`00000000 : ffff9404`49b70000 ffff9404`49b69000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME: intelppm!HvRequestIdle+2d

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

IMAGE_VERSION: 10.0.26100.4202

STACK_COMMAND: .process /r /p 0xfffff803c05cef80; .thread 0xffffbf838861c280 ; kb

BUCKET_ID_FUNC_OFFSET: 2d

FAILURE_BUCKET_ID: 0x20001_11_ffffef872b564000_intelppm!HvRequestIdle

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {48dead97-3611-2012-0f28-6e212f402a1d}

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

 

[Ralston18]

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

List of all connected peripherals.

Wired or wireless network?

= = = =

BSODs: Look in Reliability History/Monitor and Event Viewer. Either one or both tools may be capturing some error codes, warnings, or informational events just before or at the time of the BSODs.

 

[Teknoman2]

You may be victim of the 13900K degradation problem.

 

[Drewb628]

Updated with additional

You may be victim of the 13900K degradation problem.

That is my concern. I jumped through hoops with them about 6 months ago, and their update at the time stopped the issues I was having.

 

[Drewb628]

Update your post to include full system hardware specs and OS information.

Include PSU: make, model, wattage, age, condition (original to build, new, refurbished, used)?

Disk drive(s): make, model, capacity, how full?

List of all connected peripherals.

Wired or wireless network?

= = = =

BSODs: Look in Reliability History/Monitor and Event Viewer. Either one or both tools may be capturing some error codes, warnings, or informational events just before or at the time of the BSODs.

Added all the additional information.

 

[Teknoman2]

If degradation had begun before you got the BIOS update, the update can slow down further damage but once the crack appears, it can't be fixed, just delay the complete break down.