Display driver amdkmdag stopped responding and has successfully recovered.

I have finally fixed this issue though given everyone's different hardware it won't sort it for everyone.

From what i gather if you have general crashing outside of games then its probably hardware seating issue or bad windows install. 

For like me where i only have crashing during games what fixed my particular issue and i have no idea why, is downclocking my video card slightly. I have a msi radeon rx 590 armor 8g oc so its overclocked by default. Ryzen 3600, MSI B450 Gaming Pro Carbon Ac mobo, 144hz full HD monitor. Everything is fully updated.

Downclocked card 100hz in MSI Afterburner and voila, one week later not a single crash whereas I used to have them about every 10 mins in all but the most basic single player games. Obviously this isn't an ideal fix but the most graphics intense stuff I play is Dota 2 at 144hz at highest settings so doesn't create any performance issues for me.

What's also annoying is when I spoke to MSI the support was awful, like talking to someone with 50 IQ, and they claimed based on the tests they made me do it cannot be a card fault. 

Anyway hope this helps a few people at least. I like you all have tried everything under the sun til this downclock in afterburner i found elsewhere that someone had success with.

Just reporting back in with Far Cry 5 test results. You can see from this screenshot that I had a crash today with Far Cry 5. It took around 15 minutes from booting my PC and starting to play to crash.

This is after 10 days of no crashes. 5 of those 10 days were with a single 8GB stick of memory. The second 5 were with both of my 8GB sticks and only playing CoD Black Ops Cold War.

So Far Cry 5 causes a crash for some strange reason. CoD Black Ops Cold War is fine. This is a massive pain in the ****. Apex crashed maybe 4 times in the past few months, so it's pretty rare but can happen.

Hi Folks,

same Problem here, LiveKernelEvent 141 / amdkmdag going **** while playing games (nothing too fancy graphics wise even, just some lol, poe, etc.). I get colorful flicker and artifacts (rainbow dots, funny lines ingame) before the crash, as well as short (~2 seconds) phases of blackscreen a few times before the system shuts down.

Been through all troubleshooting tips (update drivers, downgrade drivers, update bios, turn fan to max speed, undervolt,...) but nothing seems to help... AMD Software Suite seems to make it worse even, since the app (and all games you start from within the app therefore) crash sooner than any given game started by itself. Plus, no more manual driver selection withouth jumping through a lot of hoops...

Anyways, my System:

ASRock B365M Pro4

Intel i5-9400f

Radeon RX Vega 56

I could not reproduce the error with any benchmarks i tried, up until today:

Valley Benchmark 1.0 causes the crash repeatedly at first/second benchmark run on my machine!

(directX9 and directX11, Quality set to Ultra)

Can't help you guys out with a solution sadly, but beeing able to reproduce the error without having to play 2 hours of online matches may help us find the issue faster, so i suggest giving that a try.

Regards,

Funkbrother

TLDR; I think my RAM was not perfectlyseated in the slot*,*and/or a CMOS reset may have cleared something up. Also, my GPU support may have caused poor PCI-E lane contact, but I'm not sure about this one. I had reseated my RAM before, but maybe it really needs to be pushed in.

I may have narrowed my issue down to RAM too. It's been over a week since I've had a crash - a new record since all of this kicked off late last year.

Here's what I've tried since my last post here:

1. GPU underclock/undervolt (fail)
2. GPU fan curve increase (fail)
3. Motherboard CMOS reset (fail)
4. Removed my second stick of RAM, i.e run just single 8GB stick at 2666Mhz (fail)
5. Replaced the remaining stick of RAM with the one I had removed, i.e run just the other 8GB stick at 2666Mhz (success!)

After step #5 my crashes stopped. What's bizarre is that MemTest86 never encountered issues, and I performed those tests many with different default and XMP timing enabled.

The single stick of RAM worked well for a few days in Far Cry and CoD so I added the second one back and I still have no issues. I will test some more games but so far so good in the new Call of Duty even after increasing RAM to 3200Mhz. Far Cry was always a reliable way to cause a driver crash on my first boot of the day, so I'll try that again soon with the two sticks at 3200Mhz. 

The only other thing I can think of is that my GPU support was somehow causing poor contact. After moving the GPU support while swapping RAM I might have helped the GPU contact with PCI-E lanes somehow. My GPU is the Gaming X 5600 XT and it's fat, hence the support.