Acer Predator PHN16-72 Continuous BSOD (Blue Screen of Death)

jihakkim

nt!KiIdleLoop+0x54

SYMBOL_NAME: intelppm!HvRequestIdle+2d

MODULE_NAME: intelppm

IMAGE_NAME: intelppm.sys

IMAGE_VERSION: 10.0.26100.5074

STACK_COMMAND: .process /r /p 0xfffff803ad7cef80; .thread 0xffffaf8dba575280 ; kb

BUCKET_ID_FUNC_OFFSET: 2dFAILURE_BUCKET_ID: 0x20001_11_2cde85_intelppm!HvRequestIdle

OSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {fd27776b-4c74-5c38-a160-7b1991a7e6f8}Followup: MachineOwner---------

HI!

I am Ji Hak Kim from S.Korea!
Your continuous PHN16-72BSOD (Blue Screen of Death)
I'm trying to fix the symptoms!

IMAGE_NAME: ntkrnlmp.exe

Or

ntoskrnl.exe

I know you're struggling with bsod!

That's why I brought a solution!

windows + r

regedit

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\안녕!
I am Ji Hak Kim from Korea!
Your continuous PHN16-72BSOD (Blue Screen of Death)
I'm trying to fix the symptoms!

IMAGE_NAME: ntkrnlmp.exe

Or

ntoskrnl.exe

I know you're struggling with bsod!

That's why I brought a solution!

windows + r

regedit

컴퓨터\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\intelppm

Give me the Start value of 4 and reboot

Thankful things will happen.

First of all, the CPU power management part is turned off from the window.

I think there's a conflict with the Predator sensor or there's a firmware problem. 1.17 Firmware

Just in case, I'll also upload the registry registration file!

If you have any questions, please send me an email at XXXXXXXXXXXX@naver.com

If you want to thank me, you can email me

I am a software developer in South Korea.

[Edited the content to hide personal information]
[Edited the thread to add issue detail]

Accepted answers

All comments

jihakkim

ppmstartno_.zip

Oh, the original value of that value is 3!!

jihakkim

I want this article to be the best

That way, more people will be able to deal with similar symptoms on Acer laptops.

Please press "Like" a lot.

jihakkim

????????????????????????????

Puraw

Hi jihakkim

Setting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\intelppm\Start to 4 does exactly one thing: it disables the Intel Processor Power Management driver so Windows never loads it.

That’s not a “fix” for the root cause — it’s a blunt bypass. You lose CPU power‑saving states, potentially increase heat and battery drain, and sidestep whatever firmware/driver conflict is actually causing the BSOD.

Also worth noting:

The original value (3) is “manual start” — Windows loads it when needed.
You can disable a service/driver via services.msc or sc config without touching the registry.
On Windows 11 23H2, registry edits to core services can be overwritten by updates or trigger integrity checks.

If you want to test whether intelppm is the culprit, disable it temporarily and see if the BSOD stops. If it does, the real fix is to address the firmware or Predator Sense conflict — not to leave CPU power management permanently off.

jihakkim

Two weeks test results
setting up, it was used without any problems.
In response, the firmware downgrad process is a step.
1.17 > 1.16 > 1.15 > 1.14
It is currently being tested.
The power charging option is limited to 80.
Windows PPM is enabled.
It started today.

There's a sensor program in the text.
He said there was a problem with the firmware.
Scheduleing of the power management core allocation operating system
The problem is likely.
At that time, the ME firmware and sensor program in Acer
It seems to be colliding.
If you analyze it, refer to the point null as a memo.
An error occurs by referring to the released memory.