Windows 10 AMDPPM.sys causing Bsods need help.

Toggle sidebar Toggle sidebar
J

JosiahCrawford

Prominent
Apr 3, 2017
25
0
530
So like the title say's i am having issue with blue screens, however they happen specifically when i'm playing games. And i have been trying my damn best to do it with what info i've found online
sfc /scannow, dism /online /restorehealth, chkdisk, device verifyer, i've done all of that multiple times. And i have fixed a couple of the bsods that have been plaguing me but this one is just beyond me, i don't know how to read a lot of the technical jargon that Who Crashed gives me so some help would be appreciated.

Also here is the Who Crashed stuff

On Wed 7/5/2017 4:57:47 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\070517-20453-01.dmp
This was probably caused by the following module: amdppm.sys (amdppm+0x7160)
Bugcheck code: 0xA (0xFFFF89011F4A1F00, 0xFF, 0x4C, 0xFFFFF800A42FAE31)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\amdppm.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Processor Device Driver
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Wed 7/5/2017 4:57:47 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0xA (0xFFFF89011F4A1F00, 0xFF, 0x4C, 0xFFFFF800A42FAE31)
Error: IRQL_NOT_LESS_OR_EQUAL
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 7/5/2017 1:58:46 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\070517-20015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0xA (0xFFFF86011DDAE151, 0xFF, 0x0, 0xFFFFF80055F8F124)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 7/5/2017 1:21:53 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\070517-114640-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR



On Wed 7/5/2017 12:44:40 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\070517-17890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0xA (0x0, 0xE, 0x1, 0xFFFFF80113982ACC)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Sort by date Sort by votes
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
I would guess that the gpu is using too much power and it is causing power fluctuations to your cpu. I would underclock the gpu and see if it has an effect. I would also check the rating the psu.

I assume you have a amd gpu. They tend to produce the unknown bug check when the card gets a power brown out
 
Upvote 0 Downvote
J

JosiahCrawford

Prominent
Apr 3, 2017
25
0
530
Also here is the latest Bsod info

On Thu 7/6/2017 5:01:15 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\070617-19109-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C3F0)
Bugcheck code: 0x1E (0xFFFFFFFF80000004, 0xFFFFF80191C8DAA8, 0x0, 0x1)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 7/6/2017 5:01:15 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x1E (0xFFFFFFFF80000004, 0xFFFFF80191C8DAA8, 0x0, 0x1)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
error code 0xFFFFFFFF80000004 = 0x80000004 = No such interface supported

I would be looking for mis-mached binaries. IE if you update a driver but not the BIOS
or you have a set of drivers and fail to update the entire set.
for example, most graphic drivers might have 3 different drivers but sometimes people do not use the sound that the graphics driver provides so they don't update the GPU sound driver. It works for a while but if the build becomes too old then you can get a mismatched set installed and problems like this) It is why some of the GPU driver removers work, they remove the entire set and then you reinstall the entire of drivers.

just hard to tell without looking at the list of drivers you have installed (from a minidump)
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
all of the driver dates in the memory dump are corrupted so I can not look for mismatched binaries by looking at the dates.


I do see that you have
\SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_2386fda73b467ac8\nvlddmkm.sys Tue Jun 27 13:02:17 2017

being loaded from the hidden driver store.

I would suspect that it does not match the build of the other NVidia driver.
\SystemRoot\System32\drivers\nvvhci.sys Tue Dec 27 17:44:00 2016


you should uninstall both drivers, use this method to remove the one from the driver store:
https://technet.microsoft.com/en-us/library/cc730875(v=ws.11).aspx

then install the current NVidia driver and see if it works as expected.
 
Upvote 0 Downvote
J

JosiahCrawford

Prominent
Apr 3, 2017
25
0
530
OK, so to skip a few steps i used DDU (Display driver uninstaller) to just wipe Nvidia from my machine i had to do that a few times cause an older driver took its place so i just kept doing it until that stopped happening and a basic PNP driver took it's place. After that i checked if the drivers you were talking about were still there which they weren't then i restarted and redownloaded all the Nvidia drivers again. Then i checked if they still were back which they were, played a bit and got a Bsod again. The who crashed being virtually the same as all the others.

https://1drv.ms/u/s!AtAatBnpGovgb_Kbd18nzKM7FK8

https://1drv.ms/u/s!AtAatBnpGovgcOIl-ps2H-7d1nw

I decided to do it that way cause i figured it would have the same effect as the method that you suggested however with much less effort and chance of me misinterpreting written instructions however if you think that i need to try your way i'll give it another shot.
 
Upvote 0 Downvote
J

JosiahCrawford

Prominent
Apr 3, 2017
25
0
530
OK new stuff happened last night playing Overwatch

On Tue 7/11/2017 12:20:10 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\071117-18750-01.dmp
This was probably caused by the following module: dxgmms2.sys (0xFFFFF8007D8DB52C)
Bugcheck code: 0xD1 (0x9A, 0x6, 0x0, 0xFFFFF8007D8DB52C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.



On Tue 7/11/2017 12:20:10 AM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: dxgmms2.sys (dxgmms2+0xB52C)
Bugcheck code: 0xD1 (0x9A, 0x6, 0x0, 0xFFFFF8007D8DB52C)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\dxgmms2.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

and here are the mini's from that crash

https://1drv.ms/u/s!AtAatBnpGovgce_1ThtCKs8D8e4
 
Upvote 0 Downvote
J

JosiahCrawford

Prominent
Apr 3, 2017
25
0
530
From what i can tell from forums is that dxgmms2,sys is related to DirectX 12 in some way, might be a another driver or lack of said driver that is causing it to freak out during gaming at the moment i have no idea what is causing this to happen the forums i found weren't helpful.
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
for the directx bugcheck the memory address passed to directx (0x9a) is clearly a bogus memory address. This means that the graphic driver most likely messed up. I would disable any unused sound drivers after you update them all. also remove any overclock.

I will see what the mindump indicates
------------
I think it is the directx graphics memory manager.
I would be looking for a graphics card that has overclocked memory or is not getting proper power to the memory card.
I might even go in and set the graphics card to stock memory clock or even under clock the graphics card memory by 200 MHZ to see if it helps. (also make sure the GPU fans are running as fast as they can go)



 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
I could not tell what the problem was from the minidump. mainly because the driver table time stamps are all messed up in the debubugger.

I would change the memory dump type to kernel and provide the kernel memory dump
c:\windows\memory.dmp
it will include much more debug info in the file.

you might also want to go into bios and reset it to defaults and reboot
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom