11-03-2024 01:51 AM
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.
Solved! Go to Solution.
a month ago - last edited a month ago
Came here for the same issue, mine was when I tried to run fortnite on a new 265k on an msi board, win 11 pro.
This is what I did and now it works.
Confirm virtualisatuon is on in bios
Install hyper V thru "turn windows features on or off" (mine was not installed on a clean pro)
Go into device manager and confirm "system Devices/Microsoft Hyper*** " drivers are up to date
Open Task Manager , go to processes and confirm in lower right that virtualisation is enabled.
Open an elevated cmd and run
"sfc/scannow" then
"DISM /Online /Cleanup-image /ScanHealth" then
"DISM /Online /Cleanup-image /RestoreHealth"
Then
"bcdedit /set hypervisorlaunchtype auto"
I uninstalled fortnite from Epic
I used Revo Uninstaller to remove Epic and Epic Online, also allow it to remove all files and registry entries
Then I went here
https://www.microsoft.com/en-us/software-download/windows11
And installed windows 24H2 using the windows auto updater/installer
Then i reinstalled Epic
And reinstalled fortnight.
Now... it works, NO BSOD.
11-03-2024 01:11 PM - edited 11-03-2024 01:14 PM
Hi
I have the same issue with New World in Steam. BSOD when easy anti cheat starts. I solved it by enabling core isolation. I don't want that on beacuse it slowes the computer down, but until this is fixed i have it on. It must be bug somwhere though.
I have 265K with strix-e z890 64gb ram
11-03-2024 02:33 PM
Thank you for your response! Unfortunately, I do have it enabled. When I launch the game through the game launcher and it initializes with EAC, I experience the BSOD. After restarting, it disables itself, and I have to re-enable it.
11-04-2024 02:48 AM
I have the same issue with my new PC. Have not yet tried this "enabling core isolation", will try it when I get home from work and get back if it works or not.
11-04-2024 08:46 AM
Didn't work me either im afraid...
11-06-2024 12:41 AM
Did you try to also enable memory integrity? I put both on for now.
I believe this is bug and not anything to do with bad RAM sticks. It could be that EAC needs an update, CPU microcode update or new bios. EAC needs to reqognize the new socket/CPU somehow.
11-06-2024 09:51 AM
Yeah I tried that. Didn't work 😕
11-04-2024 04:24 AM - edited 11-04-2024 04:26 AM
have you tried with the latest bios after update & Intel ME updates ?
1.load defaults in bios F10 save
2.update via usb stick
3.load again defaults in bios F10 save
4.shut down pc unplug power supply cord or switch off power..wait 30 sec or 1min and reset bios (io panel back of the case.press 5sec)
5.enter bios(load bios defaults again) make settings again as you wanted F10 save
6.make settings again as you wanted F10
maybe this will help solve the issues if not also contact customer support via Asus support
Also your Ram is QVL from here?
https://rog.asus.com/motherboards/rog-strix/rog-strix-z890-f-gaming-wifi/helpdesk_qvl_memory/
https://rog.asus.com/motherboards/rog-strix/rog-strix-z890-f-gaming-wifi/helpdesk_bios/
11-04-2024 09:15 AM
Thank you for the response. Everything has been updated, but I didn't unplug the computer and fully reset to default to be honest. That said, I did purchase QVL kinda. I went with 64GB over 48GB though. CMK64GX5M2B6400C32
11-04-2024 09:34 AM
I have the exact same kit from Corsair, Smoke911 and same reasoning. They are not QVL but they have passed 4 hours of memtest86+ so to blame memory for bsod in easy anti cheat is just wrong. It is something else that causing this issue. I am also fully updated with latest bios/windows/drivers.