Windows 10: BSOD when idling - amdppm.sys

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 = 0xfffff806`0aa00000 PsLoadedModuleList = 0xfffff806`0b62a310

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:

ffff8980`3a099158 fffff806`0aef465e : 00000000`0000001e ffffffff`c0000005 fffff806`27752d2d 00000000`00000000 : nt!KeBugCheckEx

ffff8980`3a099160 fffff806`0adfd462 : fffff806`0aef463c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22

ffff8980`3a0991a0 fffff806`0ac52d97 : ffff8980`3a099710 00000000`00000000 ffffdd08`0326fc60 fffff806`0adf80c4 : nt!RtlpExecuteHandlerForException+0x12

ffff8980`3a0991d0 fffff806`0ac519a6 : ffffdd08`0326f478 ffff8980`3a099e20 ffffdd08`0326f478 ffffc68d`8ad88de8 : nt!RtlDispatchException+0x297

ffff8980`3a0998f0 fffff806`0adf5432 : 88000002`3288b60f c0337f4d`b60f7f4d c48348c0`950fc984 83485540`ccc35d30 : nt!KiDispatchException+0x186

ffff8980`3a099fb0 fffff806`0adf5400 : fffff806`0ae066a5 fffff806`0ec31aa0 fffff806`0ec37ef0 ffffc68d`8aceb1a0 : nt!KxExceptionDispatchOnExceptionStack+0x12

ffffdd08`0326f338 fffff806`0ae066a5 : fffff806`0ec31aa0 fffff806`0ec37ef0 ffffc68d`8aceb1a0 ffffc68d`8c69b001 : nt!KiExceptionDispatchOnExceptionStackContinue

ffffdd08`0326f340 fffff806`0ae023e0 : 00000000`00000001 00000000`00000000 00000000`000000fe 80000000`00000001 : nt!KiExceptionDispatch+0x125

ffffdd08`0326f520 fffff806`27752d2d : fffff806`2775c117 fffff7d4`c0002158 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320

ffffdd08`0326f6b8 ffff8980`3a040180 : fffff806`277518e3 00000000`00000000 ffffc68d`8c7a7010 00007e8b`e8610b2c : amdppm!ReadGenAddr+0x29

ffffdd08`0326f6e8 fffff806`277518e3 : 00000000`00000000 ffffc68d`8c7a7010 00007e8b`e8610b2c ffffc68d`8adfe960 : 0xffff8980`3a040180

ffffdd08`0326f6f0 fffff806`0ad29172 : 00000000`0000001b 00007e8b`00000035 00000000`00000000 00000000`00000000 : amdppm!AcpiCStateIdleExecute+0x23

ffffdd08`0326f720 fffff806`0ad28884 : 00000000`00000000 00001f80`00000000 00000000`00000000 00000000`00000002 : nt!PpmIdleExecuteTransition+0x772

ffffdd08`0326faf0 fffff806`0adf80c4 : ffffffff`00000000 ffff8980`3a04b240 ffffc68d`932e90c0 00000000`0000100b : nt!PoIdle+0x374

ffffdd08`0326fc60 00000000`00000000 : ffffdd08`03270000 ffffdd08`0326a000 00000000`00000000 00000000`00000000 : 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

:)

 

BSOD amdppm stopping me doing a fresh install

Was getting BSOD about 1 or 2 minutes after booting up, tried a system restore which didnt solve the problem but added more problems with provisions for some programs and now cant use start menu amongst others things (only right click works), having problems
opening any MS programs. Eventually solved the amdppm BSOD by changing regedit value of it from 3 to 4 which fixed the quick BSODs I was having. Eventually got another BSOD after few hours so decided to just fresh install but get the amdppm BSOD whilst trying
fresh install so cannot overwrite or repair windows.

Windows 10 Pro, Ryzen 3600, X570, 1070, 32gb Ram, 1gb M.2 nvme.

Trying to upload my minidmps, which will follow but stuck on 0 bytes uploaded via one drive atm and posting in case i get another BSOD

 

dxgmms2.sys BSOD

Hello,

A while back, my computer lost power while it was installing windows updates. Since then, I've had BSODs every couple days, with various errors pointing to a driver error. These were annoying, but manageable. I tried a few basic troubleshooting steps, like
using a removal tool for my graphics card drivers and reinstalling, but I didn't do much else.

The last couple days, the BSOD rate has ramped up, and I started seeing "dxgmms2.sys" get listed in the BSODs, which is relatively new.

I followed the instructions
here.

And here are my dmp files resulting from that:
https://1drv.ms/u/s!Au4wk9mJt6sJgcFgkEXA4rOFod4-cg?e=wIzEMq

Thanks.

 

wdf01000.sys and ntoskrnl.exe BSOD

I'm on Windows 10, 64bit

Basically, whenever I try to update my LPC controller through Device Manager, BSOD with WDF_VIOLATION occurs (culprit being wdf01000.sys)

So I try to use the driver verifier to see which driver is causing the BSOD, but then it causes BSOD (cultprit being ntoskrnl.exe)

Have no idea which driver is causing them

Please help!

Here are my list of drivers and system info: Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.