HYPERVISOR_ERROR (20001)

Marcel Fürst 10 Reputation points
2025-10-24T00:34:39.0766667+00:00

My computer keeps crashing from a blue screen with this error: HYPERVISOR_ERROR (20001) The hypervisor has encountered a fatal error. I have tried a bunch of things to troubleshoot but it is still crashing and driving me crazy. If anyone can help it would be great! Thanks a lot in advance

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

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 828

    Key  : Analysis.Elapsed.mSec
    Value: 2580

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29457.1000

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.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_2c32ce_intelppm!HvRequestIdle

    Key  : Failure.Hash
    Value: {09a0a00b-c19d-e539-4a32-45ebd384c2be}

    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

    Key  : WER.System.BIOSRevision
    Value: 20.1.0.0


BUGCHECK_CODE:  20001

BUGCHECK_P1: 11

BUGCHECK_P2: 2c32ce

BUGCHECK_P3: 1005

BUGCHECK_P4: ffffe70001005c70

FILE_IN_CAB:  102425-15937-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffd70c6e732280

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffab00`f2cceca8 fffff807`a29849ea     : 00000000`00020001 00000000`00000011 00000000`002c32ce 00000000`00001005 : nt!KeBugCheckEx
ffffab00`f2ccecb0 fffff807`a29b1301     : ffffd70c`6e4c0c10 fffff807`a29c3c26 ffffab00`f2cdf3d0 ffffab00`f2cced30 : nt!HvlSkCrashdumpCallbackRoutine+0x8a
ffffab00`f2ccecf0 fffff807`a2aa9dc2     : 00000000`00000100 ffffab00`f2cceef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xb1
ffffab00`f2cced30 fffff807`a2aa9b2e     : 8b493424`4489f08b 00000000`00000100 ffffab00`f2cceef0 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffab00`f2ccee70 fffff807`30ba0003     : fffff807`a2752a58 00000000`00000047 00000000`00000000 00000000`00000000 : nt!KiNmiInterrupt+0x26e
ffffe808`19daf7d8 fffff807`a2752a58     : 00000000`00000047 00000000`00000000 00000000`00000000 00000000`0000000c : 0xfffff807`30ba0003
ffffe808`19daf7e0 fffff807`a2983a96     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvcallInitiateHypercall+0x68
ffffe808`19daf870 fffff807`5332a18d     : 00000000`000100de fffff807`a28cadbc 00000000`00000001 ffffd70c`91ad1ce0 : nt!HvlRequestProcessorHalt+0x26
ffffe808`19daf8a0 fffff807`53323bb3     : 00000004`22900f74 00000000`00000000 ffff179d`4890e1d5 ffffd70c`91ad1ce0 : intelppm!HvRequestIdle+0x2d
ffffe808`19daf8f0 fffff807`a28e4481     : 00000000`ffffffff ffffe808`00000000 ffffd70c`95682000 ffffab00`f2ca2180 : intelppm!AcpiCStateIdleExecute+0x23
ffffe808`19daf920 fffff807`a2842180     : ffffab00`f2ca2180 ffffab00`f2ca2180 ffffe808`19dafb19 ffffab00`f2caa9c0 : nt!PpmIdleExecuteTransition+0x5a9
ffffe808`19dafab0 fffff807`a2a9ee14     : ffffab00`f2ca2180 ffffab00`f2ca2100 ffffd70c`00000000 ffffd70c`b9cca000 : nt!PoIdle+0x1c0
ffffe808`19dafb80 00000000`00000000     : ffffe808`19db0000 ffffe808`19da9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  intelppm!HvRequestIdle+2d

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

IMAGE_VERSION:  10.0.26100.6725

STACK_COMMAND: .process /r /p 0xfffff807a33cef00; .thread 0xffffd70c6e732280 ; kb

BUCKET_ID_FUNC_OFFSET:  2d

FAILURE_BUCKET_ID:  0x20001_11_2c32ce_intelppm!HvRequestIdle

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {09a0a00b-c19d-e539-4a32-45ebd384c2be}

Followup:     MachineOwner
---------
Windows for home | Windows 11 | Performance and system failures
0 comments

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Marcel Fürst 10 Reputation points
    2025-10-24T02:41:45.3066667+00:00

    I tried your solution, and end up on different error. However, I just run "Windows memory diagnostic tool" and it end up on detecting hardware problems. So, you have been right, I will try to resolve the issue via warranty. Thanks a lot for your help!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Lester Bernard Reyes 82,970 Reputation points Independent Advisor
    2025-10-24T20:57:24.5766667+00:00

    Hi, you are always welcome. Yes, it is better to maximize your warranty.

    Was this answer helpful?

    0 comments
  3. Lester Bernard Reyes 82,970 Reputation points Independent Advisor
    2025-10-24T02:08:45.66+00:00

    Hi, thank you for that information. After checking and analyzing the new DMP file, there is an error Ntfs.sys. This error occurs when there is an issue with the file system or there is a hardware-related problem which is on your hard drive. To sort out the issue, kindly follow the steps below:

     

    Method 1. Run a full check disk.

     

    Open Terminal (Admin) or Windows PowerShell(Admin) (Press Windows key + X then click Terminal(Admin))

     

    Copy, paste, and enter the command below:

     

    chkdsk c: /f

     

    Follow the prompt and restart the PC if needed.

    Note: If the issue persists, I suggest contacting a local technician to physically check the device for any hardware-related issues.

    Was this answer helpful?

  4. Marcel Fürst 10 Reputation points
    2025-10-24T01:12:28.3766667+00:00

    I disabled the Hyper V in the BIOS as well in the windows features and now the dump is about something else. 

    SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c000001d, Exception code that caused the BugCheck
Arg2: fffff8050f09c4b3, Address of the instruction which caused the BugCheck
Arg3: ffffa109ea1fe510, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1125

    Key  : Analysis.Elapsed.mSec
    Value: 17122

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29457.1000

    Key  : Analysis.Version.Description
    Value: 10.2506.23.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2506.23.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Bugcheck.Code.TargetModel
    Value: 0x3b

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    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: 0x3B_C000001D_Ntfs!NtfsFsdCreate

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff8050f09c4b3

    Key  : Failure.Exception.IP.Module
    Value: Ntfs

    Key  : Failure.Exception.IP.Offset
    Value: 0x2bc4b3

    Key  : Failure.Hash
    Value: {b9b8eed4-eda6-dc0c-1062-05a92fca4e61}

    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  : WER.System.BIOSRevision
    Value: 20.1.0.0


BUGCHECK_CODE:  3b

BUGCHECK_P1: c000001d

BUGCHECK_P2: fffff8050f09c4b3

BUGCHECK_P3: ffffa109ea1fe510

BUGCHECK_P4: 0

FILE_IN_CAB:  102425-15453-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa48f6fe16080

CONTEXT:  ffffa109ea1fe510 -- (.cxr 0xffffa109ea1fe510)
rax=ffffa48f7ae9e0c8 rbx=ffffa48f7ae9e010 rcx=0000000000000000
rdx=ffffa48f7ae9e3f8 rsi=ffffa48f56e1b030 rdi=0000000000000000
rip=fffff8050f09c4b3 rsp=ffffa109ea1fef40 rbp=ffffa109ea1ff2e9
 r8=ffffa48f6fe16080  r9=0000000000000001 r10=fffff8057b8e9740
r11=ffffa109ea1febc8 r12=0000000000000001 r13=ffffa48f7b37caa8
r14=ffffa48f7ae9e000 r15=ffffa109ea1ff180
iopl=0         nv up ei pl nz ac po cy
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050217
Ntfs!NtfsFsdCreate+0x14b1d3:
fffff805`0f09c4b3 4533e4          xor     r12d,r12d
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MSI.CentralSer

STACK_TEXT:  
ffffa109`ea1fef40 fffff805`7b9ab63d     : ffffa48f`56e1b030 ffffa48f`7ae9e010 ffffa48f`00000000 ffffa109`00000001 : Ntfs!NtfsFsdCreate+0x14b1d3
ffffa109`ea1ff1f0 fffff805`0d328d8d     : 00000000`000000fd ffffa48f`7b3b3010 00000000`00000000 ffffa109`ea1ff2e9 : nt!IofCallDriver+0xcd
ffffa109`ea1ff230 fffff805`0d397d16     : ffffa109`ea1ff2e0 ffffa109`00000000 00000000`00000000 00000000`00000000 : FLTMGR!FltpLegacyProcessingAfterPreCallbacksCompleted+0x12d
ffffa109`ea1ff2a0 fffff805`7b9ab63d     : ffffa48f`7b5cd800 ffffa48f`56ccdd20 00000000`00000000 00000000`00000000 : FLTMGR!FltpCreate+0x706
ffffa109`ea1ff350 fffff805`7be4f995     : ffffba04`e0260c05 ffffa109`ea1ff640 ffffa48f`56ccdd20 ffffa48f`56ba08f0 : nt!IofCallDriver+0xcd
ffffa109`ea1ff390 fffff805`7be4d8c0     : ffffa109`ea1ff800 ffffba04`e0260cf0 ffffa109`ea1f0000 ffffa109`ea1ff788 : nt!IopParseDevice+0x6e5
ffffa109`ea1ff540 fffff805`7be4b6f1     : ffffa48f`73826a01 ffffa109`ea1ff788 ffffa48f`00000040 ffffa48f`3553bc90 : nt!ObpLookupObjectName+0xc90
ffffa109`ea1ff700 fffff805`7bf802f8     : ffffffff`00000000 ffffa48f`3553bc90 ffffa48f`7614b8a0 00000000`00000001 : nt!ObOpenObjectByNameEx+0x201
ffffa109`ea1ff850 fffff805`7bf7f2a9     : 00000000`0686e600 00700074`80100080 00000000`0686eee0 00000000`0686e618 : nt!IopCreateFile+0x1038
ffffa109`ea1ff920 fffff805`7bcb1455     : 00000000`0696ed08 00000000`01084498 00000000`0686fc00 00000000`01083000 : nt!NtCreateFile+0x79
ffffa109`ea1ff9b0 00007ffd`ad142694     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0686e588 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`ad142694


SYMBOL_NAME:  Ntfs!NtfsFsdCreate+14b1d3

MODULE_NAME: Ntfs

IMAGE_NAME:  Ntfs.sys

IMAGE_VERSION:  10.0.26100.6899

STACK_COMMAND: .cxr 0xffffa109ea1fe510 ; kb

BUCKET_ID_FUNC_OFFSET:  14b1d3

FAILURE_BUCKET_ID:  0x3B_C000001D_Ntfs!NtfsFsdCreate

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b9b8eed4-eda6-dc0c-1062-05a92fca4e61}

Followup:     MachineOwner

    Was this answer helpful?

    0 comments
  5. Lester Bernard Reyes 82,970 Reputation points Independent Advisor
    2025-10-24T01:10:21.9333333+00:00

    Hi, I'm Bernard, a fellow Windows user. I'm happy to help!

    Upon analyzing the DMP logs you have, there is an error intelppm.sys, this is the Intel Processor Power Management, which is used to check the performance and cooling of the processor, and for us to sort out the issue, kindly follow the steps below:

     

    Change IntelPPM Registry value:

     

    Press the Windows key + R, then type in:

     

    Regedit

     

    Then hit OK

     

    Navigate:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

    Double-click on "Start" and change the Value data to 4

     

    Click OK, close the registry, and restart the PC.

     

    If the issue persists, you may also follow the steps from this link:

     

    https://www.thewindowsclub.com/fix-intelppm-sys-blue-screen-error-on-windows-10

     

    Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

     

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.