BSOD help - 0x20001 intelppm unknown_function

I am facing a weird issue which do not happen every time. I could not find any specific pattern to this but hoping that someone will see the error and help with further debugging the issue.

```

nt!KeBugCheckEx:
fffff802`c76a7ce0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffb600`f89cccb0=0000000000020001
14: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 984

    Key  : Analysis.Elapsed.mSec
    Value: 4405

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27793.1000

    Key  : Analysis.Version.Description
    Value: 10.2410.02.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2410.2.2

    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_7c60ac00008_intelppm!unknown_function

    Key  : Failure.Hash
    Value: {f3f0ac9b-dd47-7cbc-c760-93e577d7eef7}

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

BUGCHECK_P3: 1005

BUGCHECK_P4: ffffe700014059b0

FILE_IN_CAB:  032125-40156-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffa587896bf280

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffb600`f89ccca8 fffff802`c7736e4a     : 00000000`00020001 00000000`00000011 000007c6`0ac00008 00000000`00001005 : nt!KeBugCheckEx
ffffb600`f89cccb0 fffff802`c7765421     : ffffa587`894ddad0 fffff802`c777b056 ffffb600`f89dd3d0 ffffb600`f89ccd30 : nt!HvlSkCrashdumpCallbackRoutine+0x9a
ffffb600`f89cccf0 fffff802`c7874ec2     : 00000000`00000100 ffffb600`f89ccef0 00000000`00000000 00000000`00000000 : nt!KiProcessNMI+0xb1
ffffb600`f89ccd30 fffff802`c7874c2e     : 00000000`00000000 00000000`00000100 ffffb600`f89ccef0 00000000`00000000 : nt!KxNmiInterrupt+0x82
ffffb600`f89cce70 fffff802`585b0003     : fffff802`c7509798 00000000`00000046 00000000`00000000 00000000`0000000e : nt!KiNmiInterrupt+0x26e
ffffc686`bafef7d8 fffff802`c7509798     : 00000000`00000046 00000000`00000000 00000000`0000000e 00000000`00000000 : 0xfffff802`585b0003
ffffc686`bafef7e0 fffff802`c7735f26     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvcallInitiateHypercall+0x68
ffffc686`bafef870 fffff80f`6495d6ed     : 00000000`000100de fffff802`c768a7e0 00000000`00000001 ffffa587`9be0ab40 : nt!HvlRequestProcessorHalt+0x26
ffffc686`bafef8a0 fffff80f`64953c03     : 00000005`4ba50ebb ffffc686`bafefa20 ffffb8d6`caecf303 ffffa587`9be0ab40 : intelppm+0xd6ed
ffffc686`bafef8f0 fffff802`c75f4167     : 00000000`ffffffff ffffc686`bafefa20 ffffa587`ae788050 ffffb600`f8990180 : intelppm+0x3c03
ffffc686`bafef920 fffff802`c75f2ef7     : ffffa587`ae788050 ffffa587`ae788050 ffffc686`bafefb19 ffffb600`f8990180 : nt!PpmIdleExecuteTransition+0x5ab
ffffc686`bafefab0 fffff802`c7869eb4     : ffffb600`f8990180 ffffb600`f8990100 00000000`00000000 fffff802`c7766e00 : nt!PoIdle+0x187
ffffc686`bafefb80 00000000`00000000     : ffffc686`baff0000 ffffc686`bafe9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x54


SYMBOL_NAME:  intelppm+d6ed

MODULE_NAME: intelppm

IMAGE_NAME:  intelppm.sys

IMAGE_VERSION:  10.0.26100.3323

STACK_COMMAND:  .process /r /p 0xfffff802c81bdf80; .thread 0xffffa587896bf280 ; kb

BUCKET_ID_FUNC_OFFSET:  d6ed

FAILURE_BUCKET_ID:  0x20001_11_7c60ac00008_intelppm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f3f0ac9b-dd47-7cbc-c760-93e577d7eef7}

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

14: kd> lmvm intelppm
Browse full module list
start             end                 module name
fffff80f`64950000 fffff80f`649a0000   intelppm   (no symbols)           
    Loaded symbol image file: intelppm.sys
    Mapped memory image file: C:\ProgramData\Dbg\sym\intelppm.sys\5BB422C250000\intelppm.sys
    Image path: intelppm.sys
    Image name: intelppm.sys
    Browse all global symbols  functions  data  Symbol Reload
    Image was built with /Brepro flag.
    Timestamp:        5BB422C2 (This is a reproducible build file hash, not a timestamp)
    CheckSum:         0004C765
    ImageSize:        00050000
    File version:     10.0.26100.3323
    Product version:  10.0.26100.3323
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        3.7 Driver
    File date:        00000000.00000000
    Translations:     0409.04b0
    Information from resource tables:
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     intelppm.sys
        OriginalFilename: intelppm.sys
        ProductVersion:   10.0.26100.3323
        FileVersion:      10.0.26100.3323 (WinBuild.160101.0800)
        FileDescription:  Processor Device Driver
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
```

My system configuration is as follows:

Operating System: Windows 11 Pro 64-bit (10.0, Build 26100) (26100.ge_release.240331-1435)
Processor: Intel(R) Core(TM) i9-14900K (32 CPUs), ~3.2GHz
DirectX Version: DirectX 12
|
Hi, thanks for reaching out. My name is Bernard a Windows fan like you. I'll be happy to help you out today, my timezone is UTC +8.

I understand the issue you have, there is nothing to worry I am here to assist, as per checking and analyzing the DMP logs 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...

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.



Let me know how it goes and I hope that helps.

Bernard

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thanks Bernard for the detailed instructions.

I searched on the internet for `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm` setting of 4 and it appears (not 100% sure) that it disables CPU power management. Is that correct? If that is true then I just want to make sure that my system should not overheat despite this setting and throttling should be applied rather than abruptly shutting down when system is at max usage.

I have done then changes and will use the system for a bit to see if this solved the problem.

Thanks again.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yes, it disables CPU power management but it will repair the CPU frequency and it is likely disabling the overclock of the CPU, moreover, kindly observe the device and I hope it will be all good.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

 
 

Question Info


Last updated April 16, 2025 Views 29 Applies to: