Display driver amdkmdag stopped responding and has successfully recovered.

Hi Mate,

Was having the same issue and sent my pc off for repairs. Turns out it was faulty RAM. Installed new RAM and havent had an issue since. Honeslty have tried everything udner the sun regarding this issue and nothing prevailed apart from the RAM. This was annoying as the PC was telling me its a graphical issue when actually it was something else. I even ran MEM tests to test the RAM and was totally fine. So yeah just try replacing RAM and see how you get on.

Same problem, no solution.

In my case I don´t have any monitor on DisplayPort, Windows still searching and installing a display on DisplayPort, when it realize that there is no hardware conected then drivers quits. This operation repeats again, while it happens I have black screen but audio still running on game. That is stupid, windows search for a driver on AMD GPU where there is not a display conected. Something on AMD driver is calling that action.

I have been trying everything, also on RegEdit, PnP, DDU, old windows versions. Nothing works...
tried on win7, at the beginning it improved but I always reached the same problem.

On win10 it is more intense.

Sorry for my bad english.

My GPU is a Sapphire RX 460, Also I played with no problem before a Windows update, after update it happens once a week, but now it happens every 10 secs, it get worst on any update I do, not possible to use GPU. It 's really frustrating

Well, just in case someone runs into this thread. I found another fix. Turns out that my VRAM locks at 1745 to 1750Mhz when I set my refresh rate to 144Hz, even when not gaming! This is a known issue in the AMD drivers. For some people it just makes their cards run hotter, but I guess it made mine and some other people have crashes.

After following this YouTube video I was able to create a new custom resolution and refresh rate. This means I can select 142Hz instead of 144Hz. I have gamed at 142Hz for two days now with no crashes. Fingers crossed this has been the solution for some of us all along.

It's strange since my VRAM still runs around 1750Mhz when gaming as you would expect, so I'm nto sure what craziness the AMD drivers are doing when using 144Hz.

https://www.youtube.com/watch?v=Td3mBgE1Dsc

This issue amazes me... over the last 5 years I have tried million different things, but it still persists and by the looks of it still to this day nobody has figured out the definitive reason why it happens.

So I read all 16 pages of the thread and it seems all the same suggestions and potential causes are being discussed:

* undervolt/overcolt the GPU

* increase/decrease power limit

* downclock GPU

* uninstall additional software (like Radeon software i.e. ReLive)

* uninstall High Definition Audio

* issues linked to 120/144Hz monitors or DisplayPort

* issues linked to PSU

* one solution which I have never seen before was related to dual/single-channel memory, but it seems that has not definitively fixed the issue.

Have I missed anything else?

Just a little bit of my story - I had this issue probably for 5 years if not more. I had it on R9 290X, R9 390X, R9 Fury X and on RX5700XT. All except RX5700XT were purchased used. At the same time, I only had a single Nvidia card and that was GTX260 and it did not have this issue. I always assumed this is AMD issue, but I can see some people reporting it on Nvidia as well. Now if there is a suggestion on the internet on how to fix this - I bet you I have tried it.

I always had an overkill power supply (Enermax Platimax 1500W) from the days of me owning 2X4870X2 on quad-CF, later on I have downscaled to a more "reasonable" Corsair AX1200i and AX860i, so that is not power supply issues either.

What makes this issue particularly annoying is that the causes for it are always different, for one person it will crash in Warzone, but not in Whicher, for another person is exactly the opposite, for one person the cause is HDAD, for others it does not.

Now there is an interesting twist on my story... my RX5700XT was a new card with a warranty and it turned out to be defective in more than one way. Eventually it was RMA'ed and thoroughly tested by the manufacturer before it was sent back to me. Guess what - it doesn't have this issue. And it wasn't 2 days in a row, or 2 weeks. I got RMA back in May and since then I have had no issues with driver stopping.

So my conclusion here - AMD drivers are kind of ****, they have been unreliable for as long as I can remember, but importantly for this issue there are:

* your card is defective, even if it is rejected by RMA (they just trying to stonewall you).

* the way windows handles the video drivers is unstable and even the smallest issue will trigger the driver crash - that is why so many different reasons exist... literally anything can cause the display driver to crash and it is just not acceptable.

What is the solution - buy a new graphics card thoroughly test it before 30 days the return policy expires, if you get a driver not responding error just return it and do it as many times as it requires. If your GPU does it then it is faulty, and even if it is not faulty you still don't want to get involved with this issue... as there are quite clearly no solutions for it. Windows are just **** like that and unstable (not like we have the option to use anything else), so to avoid the issues you need a perfectly working GPU.