Question Constantly getting BSODs related to amdppm.sys ?

Apr 1, 2022
12
0
10
Hi, could someone please help with this problem.
I purchased a new laptop last year and installed Windows 11 in February.
Every few minutes I keep getting a BSOD error on Windows 11.

Computer name: DESKTOP-GLPT35I
Windows version: Windows 11, 10.0, version 2009, build: 22000 (x64)
Windows dir: C:\WINDOWS
Hardware: HP ProBook 455 G7, HP, 8730
CPU: AuthenticAMD AMD Ryzen 5 4500U with Radeon Graphics 8664, level: 23
Processor count: 6 logical processors, active mask: 63
RAM: 15773.3MB


Here is some information from WhoCrashed:

Crash dump file: C:\WINDOWS\Minidump\040222-10515-01.dmp (Minidump)
Bugcheck code: 0x101(0x20, 0x0, 0xFFFFF80170C11180, 0x0)
Bugcheck name: CLOCK_WATCHDOG_TIMEOUT
Driver or module in which error occurred: amdppm.sys (amdppm+0x3a22)
File path: C:\WINDOWS\System32\drivers\amdppm.sys
Description: Processor Device Driver
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
Analysis: This is likely caused by a hardware problem, but there is a possibility that this is caused by a misbehaving driver.
This bugcheck indicates that a timeout has occurred. This may be caused by a hardware failure such as a thermal issue or a bug in a driver for a hardware device.

I have uploaded some minidump files here
Thanks.
 

gardenman

Splendid
Moderator
Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/g8fj70s6/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:033022-7562-01.dmp (Mar 30 2022 - 04:05:36)
Bugcheck:CLOCK_WATCHDOG_TIMEOUT (101)
Probably caused by:memory_corruption (Process running at time of crash: chrome.exe)
Uptime:0 Day(s), 3 Hour(s), 18 Min(s), and 12 Sec(s)

Comment: 3 of the dumps were full of null or space characters and are invalid.

System: HP ProBook 455 G7
Possible System Support page: https://support.hp.com/us-en/drivers/selfservice/hp-probook-455-g7-notebook-pc/32780046

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.
 

Colif

Win 11 Master
Moderator
Now this is odd, I read your dumps and they look like someone else I helped today

your 4th error, the only one that actually worked, is exactly the same as crash 2 here - https://jsfiddle.net/L4af5p0t/show
but your PC aren't the same. Only similarity is you both have AMD CPU and both on Win 11. It is the same BSOD in both cases, but pretty sure its stack text changes each time (Some BSOD are almost always the same)

Apart from certain error codes, I don't recall last time I seen 2 people with almost identical errors on 2 different PC. I wonder if its a windows 11 problem.
 
Apr 1, 2022
12
0
10
Apart from certain error codes, I don't recall last time I seen 2 people with almost identical errors on 2 different PC. I wonder if its a windows 11 problem.

Thank you. How do you think I could fix the problem? Do you think it could be anything to do with Chrome?
 

Colif

Win 11 Master
Moderator
I am starting to think its windows 11.

I wonder if it works with 11, if I go to the self service site it shows no drivers... sure, I don't have your laptop but normally there is a chance to search manually - https://support.hp.com/au-en/drivers/selfservice/hp-probook-455-g7-notebook-pc/32780046

Note: No drivers doesn't actually mean a lot, most win 10 drivers should work but some have changed.

if problems only started after you updated to 11, that could be the reason.

whatever cause is, it appears to be network related. But updating LAN drivers (in the other persons case) doesn't solve problem.


chrome was the victim. most of the time I would suggest updating LAN drivers so we can try
Apr 16 2020rt640x64.sysRealtek NICDRV 8169 PCIe GBE Family Controller driver https://www.realtek.com/en/
download Win11 Auto Installation Program (NetAdapterCx) from under windows header here - https://www.realtek.com/en/componen...0-1000m-gigabit-ethernet-pci-express-software

Jul 12 2021Netwtw10.sysIntel Wi-Fi driver
not sure if there is a newer version of that. download and run this and see if anything new - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html
 
For testing you can start by locking your cpu to a single frequency by turning off amdppm
this is the amd cpu primary processor module. disable it to give you time to work before the system crashes.

Click Start
Type: regedit
Right click regedit
Click Run as administrator

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\amdppm
Change Start to have a value of 4.
(you should note the old value since you will want to change it back after you fix the problem)

reboot and see if the system is more stable.
---------
to actually fix the problem, you would want to update the bios or reset it to defaults if it is the current version. (this sets cpu voltages and default settings)
Then you remove any overclocking tools you have installed. update the motherboard chipset drivers from the motherboard vendors website.

then go back and turn the AMDppm service back on and reboot

check to see if the system is stable without any overclock.
------------------
if you do not make progress on this then you will need to change the memory dump type to kernel and provide the kernel memory dump (memory.dmp) it will show more info than just the currently running process. this will be needed to find out why your processor hung. (assuming it is due to bad settings going amdppm driver, assuming your main power voltages from the PSU are within range) not likely overheating in 4 minutes.
 
Last edited:

Colif

Win 11 Master
Moderator
How to collect Kernel Memory Dumps
Can you follow option one on the following link - here - and then do this step below: Kernel Memory dumps.
this creates a dump in Memory.dmp after a BSOD

  1. Open Windows File Explore
  2. Navigate to C:\Windows\Memory.dmp
  3. Copy the dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

there is a new bios here dated 31 March 2022 - https://support.hp.com/us-en/drivers/selfservice/hp-probook-455-g7-notebook-pc/32780046
 
I tried these and I am still getting the BSOD all the time. Could someone please have a look at the dump files?
Thank you.
looks like cpu core 4 was running some filesystem driver and ended up telling all the cpus cores to flush their cache but cpu 0 did not respond. the system considered this a hung processor and bugchecked.

I will look and see if I can find a likely cause.
===========
machine info:
103C_5336AN HP ProBook
Product 8730
Version KBC Version 13.26.00
Product Name HP ProBook 455 G7
BIOS Version S79 Ver. 01.08.20
BIOS Release Date 03/15/2022
Processor Version AMD Ryzen 5 4500U with Radeon Graphics
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 4000MHz
Current Speed 2375MHz
0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2371
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 23 Model 96 Stepping 1
ProcessorNameString = REG_SZ AMD Ryzen 5 4500U with Radeon Graphics
Update Status = REG_DWORD 3
VendorIdentifier = REG_SZ AuthenticAMD
============
you have a bunch of audio devices and one realtek driver rt640x64.sys waiting for a wake signal. this is odd since the system up timer is only 1 minute 29 seconds.
you might want to go in and disable or update the various audio drivers.
rt640x64.sys is a network driver from 2020
----------------
debugger is flagging 3 core windows files as being modified
nt , pci.sys and ntfs.sys

basically the nt kernel, the pci system bus driver and the nt file system driver were all flagged as being modified.
 
Last edited:
all of the modifications in the 3 system files were in relation to guard_fids_table to prevent malware from running code. you might want to start cmd.exe as an admin and repair these files by running
dism.exe /online /cleanup-image /restorehealth

info on guard table:
CFG Improvements in Windows 10 Anniversary Update (trendmicro.com)

the initiial problem in the bugcheck started when ntfs driver requested a cache flush. This was one of the drivers that was modified.
--------------
from debugger only these three files were modified:
4: kd> !chkimg pci
6 errors : pci (fffff8072cc8c124-fffff8072cc8c43a)
4: kd> !chkimg -lo 50 -d pci
fffff8072cc8c124 - pci!_guard_fids_table <PERF> (pci+0x7c124)
[ 4c:51 ]
fffff8072cc8c12c - pci!_guard_fids_table <PERF> (pci+0x7c12c) (+0x08)
[ 4c:51 ]
fffff8072cc8c274 - pci!_guard_fids_table <PERF> (pci+0x7c274) (+0x148)
[ 38:39 ]
fffff8072cc8c276 - pci!_guard_fids_table <PERF> (pci+0x7c276) (+0x02)
[ 38:33 ]
fffff8072cc8c438 - pci!_guard_fids_table <PERF> (pci+0x7c438) (+0x1c2)
[ 38:39 ]
fffff8072cc8c43a - pci!_guard_fids_table <PERF> (pci+0x7c43a) (+0x02)
[ 38:33 ]
6 errors : pci (fffff8072cc8c124-fffff8072cc8c43a)
4: kd> !chkimg -lo 50 -d nt
fffff80727d3c628-fffff80727d3c62b 4 bytes - nt!_guard_check_icall_fptr
[ 20 26 fa 27:80 fd 01 28 ]
fffff80727d3c630-fffff80727d3c631 2 bytes - nt!_guard_dispatch_icall_fptr (+0x08)
[ 30 25:d0 fd ]
6 errors : nt (fffff80727d3c628-fffff80727d3c631)
4: kd> !chkimg -lo 50 -d ntfs
fffff8072d56d194 - Ntfs!_guard_fids_table <PERF> (Ntfs+0x2ad194)
[ 4c:51 ]
fffff8072d56d19c - Ntfs!_guard_fids_table <PERF> (Ntfs+0x2ad19c) (+0x08)
[ 4c:51 ]
fffff8072d56d2d0 - Ntfs!_guard_fids_table <PERF> (Ntfs+0x2ad2d0) (+0x134)
[ 38:39 ]
fffff8072d56d2d2 - Ntfs!_guard_fids_table <PERF> (Ntfs+0x2ad2d2) (+0x02)
[ 38:33 ]
fffff8072d56d49c - Ntfs!_guard_fids_table <PERF> (Ntfs+0x2ad49c) (+0x1ca)
[ 38:39 ]
fffff8072d56d49e - Ntfs!_guard_fids_table <PERF> (Ntfs+0x2ad49e) (+0x02)
[ 38:33 ]
6 errors : ntfs (fffff8072d56d194-fffff8072d56d49e)

================
you have a bunch of custom hp filter drivers installed.
you have epmvolfl.sys third party driver installed.
you should check to see what it is. google look like it is a disk performance driver. (if so I would remove it or update it from your version
EPMVolFl.sys Wed Oct 17 19:40:11 2018
(just looking for things that would mess up the nt file system)

most of these tools would not be needed for a solid state drive.
-----------
HpqKbFiltr.sys Tue Oct 26 19:26:42 2021
hp quick launch from the keyboard tool. these tend to have bugs, I would remove if you don't really use it.
same goes for
hpdskflt.sys
part of hp Mobile Data Protection System.
HP ProtectSmart Hard Drive Protection
(park mechanical drives heads when you drop the device?)
--------------
it is interesting that chkdsk.exe was running at the time of the crash. was it doing a automatic repair of a disk? or file system? at the time of the crash?
--------------
not sure what HP's "BridgeCommunication" Software. does, you might want to see if you need it. just trying to find out why you audio was waiting for a wake event. (confusing)
------------
another hp tool running, not sure what it does:
LanWlanWwanSwitchingServiceUWP.exe
-----------------
it does look like chkdsk that was running did request the file system to flush its cache. most likely it was doing some kind of repair operation that later failed after the file system told the cache manager to flush its cache, which told the memory manager to flush, which told all the cpu cores to flush its cache where one core did not respond and caused the bugcheck.

over all. I would guess the most likely cause is going to be that disk performance driver causing the problem. EPMVolFl.sys
I would look for a update or just remove it.
 
Last edited:
Apr 1, 2022
12
0
10
Hi, I followed your instructions and removed EPMVolFl.sys
Now my laptop won't even boot! Please help!
When booting a BSOD is displayed with the error INACCESSIBLE_BOOT_DEVICE
I tried startup repair, system restore and neither worked. Also it won't boot into safe mode.
 
Apr 1, 2022
12
0
10
Okay I performed another system restore to an earlier restore point and its now booting again.
Still getting BSOD errors though.
EPM is Ease Us Partition Master maybe? I tried uninstalling that program and can't.
Maybe I should reinstall Windows?
 
Last edited:
Apr 1, 2022
12
0
10
I tried reinstalling Windows 11 via USB and it kept freezing and a message said cannot configure Windows to run on this machine. I'm going to try Windows 10.
 
Apr 1, 2022
12
0
10
looks like cpu core 4 was running some filesystem driver and ended up telling all the cpus cores to flush their cache but cpu 0 did not respond. the system considered this a hung processor and bugchecked.

I will look and see if I can find a likely cause.
===========
machine info:
103C_5336AN HP ProBook
Product 8730
Version KBC Version 13.26.00
Product Name HP ProBook 455 G7
BIOS Version S79 Ver. 01.08.20
BIOS Release Date 03/15/2022
Processor Version AMD Ryzen 5 4500U with Radeon Graphics
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 4000MHz
Current Speed 2375MHz
0: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 2371
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ AMD64 Family 23 Model 96 Stepping 1
ProcessorNameString = REG_SZ AMD Ryzen 5 4500U with Radeon Graphics
Update Status = REG_DWORD 3
VendorIdentifier = REG_SZ AuthenticAMD
============
you have a bunch of audio devices and one realtek driver rt640x64.sys waiting for a wake signal. this is odd since the system up timer is only 1 minute 29 seconds.
you might want to go in and disable or update the various audio drivers.
rt640x64.sys is a network driver from 2020
----------------
debugger is flagging 3 core windows files as being modified
nt , pci.sys and ntfs.sys

basically the nt kernel, the pci system bus driver and the nt file system driver were all flagged as being modified.

I reinstalled Windows 10 and the BSOD is still present. I think it must be a hardware issue