ASUS Z890-F + Intel Ultra 7 265k HYPERVISOR_ERROR (20001) - only when launching certain games

[SMOKE911]

I recently built a new PC, and I'm encountering a BSOD with the message "HYPERVISOR_ERROR" when launching games that use Easy Anti-Cheat (EAC), like Fortnite and Rust. I've also noticed that after restarting, Memory Integrity is disabled. Interestingly, all my other EAC games are running without any issues. Any suggestions on how to resolve this?

HYPERVISOR_ERROR (20001)
The hypervisor has encountered a fatal error.
Arguments:
Arg1: 0000000000000026
Arg2: 0000000000000000
Arg3: fffff8065466e5b5
Arg4: fffffa8864185c20

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 718

    Key  : Analysis.Elapsed.mSec
    Value: 859

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x20001

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x20001

    Key  : Bugcheck.Code.TargetModel
    Value: 0x20001

    Key  : Dump.Attributes.AsUlong
    Value: 1800

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.LastLine
    Value: Dumping physical memory to disk:  100% 

    Key  : Dump.Attributes.ProgressPercentage
    Value: 100

    Key  : Failure.Bucket
    Value: 0x20001_26_0_intelppm!HvRequestIdle

    Key  : Failure.Hash
    Value: {8639bf00-96ae-1045-b8f4-753091ea7e23}

    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  : SecureKernel.HalpHvciEnabled
    Value: 1

    Key  : Stack.Pointer
    Value: NMI

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  20001

BUGCHECK_P1: 26

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8065466e5b5

BUGCHECK_P4: fffffa8864185c20

FILE_IN_CAB:  MEMORY.DMP

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


DUMP_FILE_ATTRIBUTES: 0x1800

FAULTING_THREAD:  ffffc0055bd20080

PROCESS_NAME:  System

STACK_TEXT:  
ffffdf81`47747ca8 fffff806`54944ff1     : 00000000`00020001 00000000`00000026 00000000`00000000 fffff806`5466e5b5 : nt!KeBugCheckEx
ffffdf81`47747cb0 fffff806`548b7be8     : 00000000`00000100 fffff806`5471769c ffffdf81`475bf3d0 ffffdf81`47747d30 : nt!HvlSkCrashdumpCallbackRoutine+0x81
ffffdf81`47747cf0 fffff806`54822d82     : 00000000`00000100 ffffdf81`47747ef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0x1a0a28
ffffdf81`47747d30 fffff806`54822aee     : 00000000`00000100 ffffdf81`47747ef0 00000000`00000000 36646d61`7e353365 : nt!KxNmiInterrupt+0x82
ffffdf81`47747e70 fffff806`50800003     : fffff806`547c76c4 ffffdf81`47711180 fffff806`54635ca8 00000000`00000000 : nt!KiNmiInterrupt+0x26e
fffffa88`5ad7f408 fffff806`547c76c4     : ffffdf81`47711180 fffff806`54635ca8 00000000`00000000 fffff806`54639d0d : 0xfffff806`50800003
fffffa88`5ad7f410 fffff806`54944245     : ffffc005`6bbcb000 0f0f0f0f`0f0f0f00 ffffdf81`47711180 00000000`00000000 : nt!HvcallInitiateHypercall+0x54
fffffa88`5ad7f490 fffff806`6f023f8e     : 00000000`000100de ffffdf81`47711180 ffffc005`6bbcb158 fffff806`54736a83 : nt!HvlRequestProcessorHalt+0x35
fffffa88`5ad7f4c0 fffff806`6f0215c4     : 00000000`00000002 ffffdf81`47711180 00000000`00000000 00000000`00000000 : intelppm!HvRequestIdle+0x2e
fffffa88`5ad7f510 fffff806`54637e26     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffdf81`47711180 : intelppm!AcpiCStateIdleExecute+0x24
fffffa88`5ad7f540 fffff806`546377d1     : ffffc005`6bbcb860 00000000`00000000 00000000`ffffffff fffffa88`5ad7f9f0 : nt!PpmIdleExecuteTransition+0x426
fffffa88`5ad7f990 fffff806`54819d14     : 00000000`00000000 00000000`00000000 ffffc005`5bd20080 ffffc005`802020c0 : nt!PoIdle+0x361
fffffa88`5ad7fb80 00000000`00000000     : fffffa88`5ad80000 fffffa88`5ad79000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  intelppm!HvRequestIdle+2e

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

STACK_COMMAND:  .process /r /p 0xfffff80655148f40; .thread 0xffffc0055bd20080 ; kb

BUCKET_ID_FUNC_OFFSET:  2e

FAILURE_BUCKET_ID:  0x20001_26_0_intelppm!HvRequestIdle

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {8639bf00-96ae-1045-b8f4-753091ea7e23}

Followup:     MachineOwner
---------
OS Name	Microsoft Windows 11 Pro

Version	10.0.22631 Build 22631

Other OS Description 	Not Available

OS Manufacturer	Microsoft Corporation

System Name	SMOKE911

System Manufacturer	ASUS

System Model	System Product Name

System Type	x64-based PC

System SKU	SKU

Processor	Intel(R) Core(TM) Ultra 7 265K, 3878 Mhz, 20 Core(s), 20 Logical Processor(s)

BIOS Version/Date	American Megatrends Inc. 0806, 10/22/2024

SMBIOS Version	3.7

Embedded Controller Version	255.255

BIOS Mode	UEFI

BaseBoard Manufacturer	ASUSTeK COMPUTER INC.

BaseBoard Product	ROG STRIX Z890-F GAMING WIFI

BaseBoard Version	Rev 1.xx

Platform Role	Desktop

Secure Boot State	On

PCR7 Configuration	Elevation Required to View

Windows Directory	C:\WINDOWS

System Directory	C:\WINDOWS\system32

Boot Device	\Device\HarddiskVolume3

Locale	United States

Hardware Abstraction Layer	Version = "10.0.22621.2506"

User Name	SMOKE911

Time Zone	Pacific Daylight Time

Installed Physical Memory (RAM)	64.0 GB

Total Physical Memory	63.4 GB

Available Physical Memory	55.0 GB

Total Virtual Memory	72.9 GB

Available Virtual Memory	62.4 GB

Page File Space	9.50 GB

Page File	C:\pagefile.sys

Kernel DMA Protection	Off

Virtualization-based security	Running

Virtualization-based security Required Security Properties	

Virtualization-based security Available Security Properties	Base Virtualization Support, Secure Boot, UEFI Code Readonly, SMM Security Mitigations 1.0, Mode Based Execution Control, APIC Virtualization

Virtualization-based security Services Configured	

Virtualization-based security Services Running	Hypervisor enforced Code Integrity

Windows Defender Application Control policy	Enforced

Windows Defender Application Control user mode policy	Audit

Device Encryption Support	Elevation Required to View

A hypervisor has been detected. Features required for Hyper-V will not be displayed.	


Additional Notes:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\intelppm

Start = 1
I did Change it to 4 at one point, but then I get Processor driver error 32.

I also removed me XMP profile and disabled AI optimization.

[Raccoon647]

I found this on reddit regarding EAC but with Fortnite.. So it seems to be a Intel problem. I guess the only thing we can do is to wait for a driver update:

received your inquiry and I can see that you're having issues launching Fortnite on your PC with your new Intel Core Ultra 7 265K.

Upon further review, it would appear that the error your being prompted with is the B.S.O.D. with the Hypervisor_error windows error when launching Fortnite. These errors is mostly being prompted to you if your system detected flaws on your PC's modules. In your case, I can see that there are multiple crashing modules that is required to run Fortnite which results to the the issue you're currently experiencing.

Once of which is the lsass.exe module (which is responsible for Active Directory database lookups that is also needed to perform tasks necessary for rendering) is faulty and crashing. There are also other faulty modules on your PC that is necessary to perform tasks like to run Fortnite that needs to be taken a look into.

[SMOKE911]

This was me 😅. They know little. I would take it with a grain of salt to be honest. Still waiting for asus to respond.

[Raccoon647]

I have created a ticket to Intel about this issue. I'll you know what they respond with!

[Rocoyoyo]

I have the same problem with this processor and Fortnite. If you resolve the problem, send a message plz 🙂 

[MirceaForce]

keep pushing to Asus for an answer or they will have to contact Intel about this

[goran69]

New BIOS out today:

Versjon 0902

16.01 MB 2024/11/07

"1.Changed defaults: Intel(R) Innovation Platform Framework and VT-d to ‘Enabled’. Ensure the corresponding IPF or DTT drivers are also installed to ensure system stability.
2.Updated to microcode 0x112 and added ‘Microcode Options’ to allow users to select the preferred microcode settings based on their needs.
3.Improved memory compatibility and stability.
4.Enable support for WiFi 6GHz band with up to 320MHz bandwidth in Japan.

I am puzzled on point 2 there, why would we need to select which microcode version to use? What is the problem here? Can Someone at ASUS enlight please?

[SMOKE911]

That's great news. Should solve our issue. Will give it a shot tonight and report the results. If anyone has tried it already please let us now 😁

[MiLesAreS]

I updated the BIOS and no difference. Seems to be a problem with new Intel CPU and Z890.

[SMOKE911]

That is unfortunate. I have to fill out a complete spec sheet to asus so they can replicate my hardware when testing, so this might take some time.

[MirceaForce]

so Microsoft to blame and intel ?