Share via

BSOD when idling - amdppm.sys

Anonymous
2020-10-19T03:12:37+00:00

I have a new build running Windows 10 build 19041.572 which has the following specs:

MB: Gigabyte GA-A320M-S2H

CPU: AMD Ryzen 5 3400G

RAM: 16 GB ADATA Premier 2666 MHz DDR4

SSD: Kingston SSD 500gb

Patch level is upto date, BIOS and firmwares are updated as per manufacturer standards. 

The PC is working correctly, but it's getting several BSODs a day when idling. When the processor is working, nothing happens, but after a random time idling, it will crash with amdppm.sys as the main culprit. A memory.dmp is created after each crash, and a debug looks like this:

************* Path validation summary **************

Response                         Time (ms)     Location

Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

Windows 10 Kernel Version 19041 MP (8 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 19041.1.amd64fre.vb_release.191206-1406

Machine Name:

Kernel base = 0xfffff8060aa00000 PsLoadedModuleList = 0xfffff8060b62a310

Debug session time: Sun Oct 18 23:50:25.110 2020 (UTC - 3:00)

System Uptime: 1 days 4:34:04.758

Loading Kernel Symbols

...............................................................

................................................................

................................................................

......

Loading User Symbols

Loading unloaded module list

...........................................

For analysis of this file, run !analyze -v

6: kd> !analyze -v

*******************************************************************************

*                                                                             *

*                        Bugcheck Analysis                                    *

*                                                                             *

*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)

This is a very common bugcheck.  Usually the exception address pinpoints

the driver/function that caused the problem.  Always note this address

as well as the link date of the driver/image that contains this address.

Arguments:

Arg1: ffffffffc0000005, The exception code that was not handled

Arg2: fffff80627752d2d, The address that the exception occurred at

Arg3: 0000000000000000, Parameter 0 of the exception

Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:

------------------

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.Sec

Value: 3

Key  : Analysis.DebugAnalysisProvider.CPP

Value: Create: 8007007e on DESKTOP-OKGMTJN

Key  : Analysis.DebugData

Value: CreateObject

Key  : Analysis.DebugModel

Value: CreateObject

Key  : Analysis.Elapsed.Sec

Value: 3

Key  : Analysis.Memory.CommitPeak.Mb

Value: 69

Key  : Analysis.System

Value: CreateObject

BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80627752d2d

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

READ_ADDRESS:  ffffffffffffffff

EXCEPTION_PARAMETER2:  ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

TRAP_FRAME:  c48348c0950fc984 -- (.trap 0xc48348c0950fc984)

Unable to read trap frame at c48348c0`950fc984

BAD_STACK_POINTER:  ffff89803a099158

STACK_TEXT:

ffff89803a099158 fffff8060aef465e : 000000000000001e ffffffffc0000005 fffff80627752d2d 0000000000000000 : nt!KeBugCheckEx

ffff89803a099160 fffff8060adfd462 : fffff8060aef463c 0000000000000000 0000000000000000 0000000000000000 : nt!HvlpVtlCallExceptionHandler+0x22

ffff89803a0991a0 fffff8060ac52d97 : ffff89803a099710 0000000000000000 ffffdd080326fc60 fffff8060adf80c4 : nt!RtlpExecuteHandlerForException+0x12

ffff89803a0991d0 fffff8060ac519a6 : ffffdd080326f478 ffff89803a099e20 ffffdd080326f478 ffffc68d8ad88de8 : nt!RtlDispatchException+0x297

ffff89803a0998f0 fffff8060adf5432 : 880000023288b60f c0337f4db60f7f4d c48348c0950fc984 83485540ccc35d30 : nt!KiDispatchException+0x186

ffff89803a099fb0 fffff8060adf5400 : fffff8060ae066a5 fffff8060ec31aa0 fffff8060ec37ef0 ffffc68d8aceb1a0 : nt!KxExceptionDispatchOnExceptionStack+0x12

ffffdd080326f338 fffff8060ae066a5 : fffff8060ec31aa0 fffff8060ec37ef0 ffffc68d8aceb1a0 ffffc68d8c69b001 : nt!KiExceptionDispatchOnExceptionStackContinue

ffffdd080326f340 fffff8060ae023e0 : 0000000000000001 0000000000000000 00000000000000fe 8000000000000001 : nt!KiExceptionDispatch+0x125

ffffdd080326f520 fffff80627752d2d : fffff8062775c117 fffff7d4c0002158 0000000000000000 0000000000000000 : nt!KiGeneralProtectionFault+0x320

ffffdd080326f6b8 ffff89803a040180 : fffff806277518e3 0000000000000000 ffffc68d8c7a7010 00007e8be8610b2c : amdppm!ReadGenAddr+0x29

ffffdd080326f6e8 fffff806277518e3 : 0000000000000000 ffffc68d8c7a7010 00007e8be8610b2c ffffc68d8adfe960 : 0xffff8980`3a040180

ffffdd080326f6f0 fffff8060ad29172 : 000000000000001b 00007e8b00000035 0000000000000000 0000000000000000 : amdppm!AcpiCStateIdleExecute+0x23

ffffdd080326f720 fffff8060ad28884 : 0000000000000000 00001f8000000000 0000000000000000 0000000000000002 : nt!PpmIdleExecuteTransition+0x772

ffffdd080326faf0 fffff8060adf80c4 : ffffffff00000000 ffff89803a04b240 ffffc68d932e90c0 000000000000100b : nt!PoIdle+0x374

ffffdd080326fc60 0000000000000000 : ffffdd0803270000 ffffdd080326a000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x54

SYMBOL_NAME:  amdppm!ReadGenAddr+29

MODULE_NAME: amdppm

IMAGE_NAME:  amdppm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  29

FAILURE_BUCKET_ID:  0x1E_c0000005_R_STACKPTR_ERROR_amdppm!ReadGenAddr

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0de21c6c-a20d-e00a-d34e-e829982c4717}

Followup:     MachineOwner

From what I get from this, it should be a driver issue, but I'm unable to identify which driver is causing this. Also, all drivers are updated to manufacturer standards, and Windows is not showing any compatibility issues or errors. I have already tried an alternative solution provided in https://answers.microsoft.com/en-us/windows/forum/all/bsod-amdppmsys/941dd57b-1bde-453d-a9d9-278942ff38b5 which points to modifying a registry key at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\amdppm. This causes no impact on the system.

Has someone else encountered these issues? Can someone point me in the right direction please?

Thanks!

Dustin

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-10-20T21:49:15+00:00

    Thank you for your copy paste answer! Let me go through it:

    Method 1: Run Memory Diagnostic Tool.

    1.     Press Windows key or click on Start Menu and type Memory Diagnostic.

    2.     Select Windows Memory Diagnostics and click on Restart now and check for problems.

    3.     Follow the on-screen instructions

     A memtest was done, nothing was found. Windows Diagnostic tools are known for being totally useless, so I'll go with the third party ones. A new memory stick is being tested as we speak.

    Method 2: Run Driver verifier

    Driver Verifier monitors Windows kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject Windows drivers to a variety of stresses and tests to find improper behavior. You can configure which tests to run, which allows you to put a driver through heavy stress loads or through more streamlined testing. Please refer this article: Driver verifier

    Stressing a driver can cause it to crash, and not knowing the actual culprit here, it's like shooting in the dark and trying to hit something. Plus, any stressed driver that crashes can lead to a false positive.

    Method 3: Safe mode

    Try booting your PC in safe mode. Refer to the article on how to Start your PC in safe mode in Windows 10

    Safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default settings and basic device drivers aren't causing the issue. Observing Windows in safe mode enables you to narrow down the source of a problem, and can help you troubleshoot problems on your PC.

    Must I?

    Method 4:  Clean boot

    Try booting your PC in clean boot. Refer to the article on How to perform a clean boot in Windows

    Note:  Clean Boot starts Windows with a minimal set of drivers and startup programs, so that you can determine whether a background program is interfering with your game or program. Also, you may not be able to use some programs in clean boot. 

    As stated, this is a new build. 

    Alternatively, I'm in touch with the manufacturer regarding a possible HW issue.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  2. Anonymous
    2020-10-20T11:26:30+00:00

    Hi,

    Thank you for writing to Microsoft Community Forums.

    We understand your concern as you are receiving Blue Screen of Death. As per the analysis of the dump file by you, the faulty module is amdppm.sys

    The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception that the error handler did not catch.

    However, we need the latest dump files for analyzing the issue. You can locate the dump files in the location C:\Windows\MiniDump, then upload them on OneDrive and share the link with us.

    Let us try few methods

    Method 1: Run Memory Diagnostic Tool.

    1.     Press Windows key or click on Start Menu and type Memory Diagnostic.

    2.     Select Windows Memory Diagnostics and click on Restart now and check for problems.

    3.     Follow the on-screen instructions

    Method 2: Run Driver verifier

    Driver Verifier monitors Windows kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject Windows drivers to a variety of stresses and tests to find improper behavior. You can configure which tests to run, which allows you to put a driver through heavy stress loads or through more streamlined testing. Please refer this article: Driver verifier

    Method 3: Safe mode

    Try booting your PC in safe mode. Refer to the article on how to Start your PC in safe mode in Windows 10

    Safe mode starts Windows in a basic state, using a limited set of files and drivers. If a problem doesn't happen in safe mode, this means that default settings and basic device drivers aren't causing the issue. Observing Windows in safe mode enables you to narrow down the source of a problem, and can help you troubleshoot problems on your PC.

    Method 4:  Clean boot

    Try booting your PC in clean boot. Refer to the article on How to perform a clean boot in Windows

    **Note:**Clean Boot starts Windows with a minimal set of drivers and startup programs, so that you can determine whether a background program is interfering with your game or program. Also, you may not be able to use some programs in clean boot. 

    If performing a clean boot fixes the issue then, please refer to the section How to determine what is causing the problem after you do a clean boot to check which program is causing the issue.

    Note: Please refer the section Reset the computer to start normally after clean boot troubleshooting to boot the computer in to normal mode after troubleshooting.

    Let us know the results. If the issue persists, we will certainly assist you further.

    Aditya Roy

    Microsoft Community – Moderator

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments