AMD 7XXX crashing (DO NOT BUY AMD)

[freeagent]

My bad, cant remember the last time I had a driver crash outside of something that I did..

[Dibbsey]

Everyone accusing the poster of its his fault is plain dumb as fuck. Its a fucking problem a real one happening with many many new 7000 series amd cards. Its the drivers I believe and hope. If its driver easy fix , if its hardware harder fix. Either way its not the user its the fucking product you absolute assuming assholes. You just straight up assume this guy is like 12 years old and has no idea what hes talking about and stupid, you assume that in your brain so you must think its his fault. You guys are worse than microsoft help forums. 

[Dibbsey]

1 minute ago, Dibbsey said:

Everyone accusing the poster of its his fault is plain dumb as fuck. Its a fucking problem a real one happening with many many new 7000 series amd cards. Its the drivers I believe and hope. If its driver easy fix , if its hardware harder fix. Either way its not the user its the fucking product you absolute assuming assholes. You just straight up assume this guy is like 12 years old and has no idea what hes talking about and stupid, you assume that in your brain so you must think its his fault. You guys are worse than microsoft help forums. 

But if it was Linus posting and asking or Jaystwocents yall would believe them instantly. You treat people differently, everything you say is null and void. Not trustworthy.

[trufret]

I've been able to resolve my driver timeout issues with my 7900XTX.

After digging deeper into event viewer, I found my WMR VR environment was crashing (DHolographicDisplay.dll taking down dwm.exe) which was crashing the games and resulting in the driver timeout message.

 

The issue turned out to be an incompatibility with an older version of a program called OpenKneeboard and the WMR OpenXR implementation which would cause the crash no matter if OpenKneeboard was running or not.

 

I found if I switched to Steam's implementation of OpenXR runtime

or

Removed the OpenKneebaord registry entry in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1\ApiLayers\Implicit

(installing latest build of OpenKneebaord seems to work fine)

I no longer get the driver timeouts.

 

This is probably a pretty niche situation in my case but after these fixes I can run CPU + GPU O.C plus Ram EXPO and system no longer crashes.

 

Update: WMR was not the problem after all as I was still getting crashes, although less frequent with SteamVR OpenXR and Oculus OpenXR.

I finally bit the bullet and did a clean install of Windows 10 ( I suspect the issue is between Win 11 and AMD 7000 series drivers) and even with all Ram Expo and CPU GPU O.C in place it's been stable for 12 hours of flights which never happened on Win 11 as the longest i could make it was about 1.5 hours with  the lowest being under 5 mins.

My cousin built the exact same pc as me and is still on Win 11 and getting regular timeouts in DCS and ARK which means its not just a VR issue either. He'll be doing a clean install of Win 10 too until Windows/AMD can sort out Win 11 and AMD 7000 series drivers.

 

Not the solution I was hoping for but if you're having GPU driver timeouts with 7000 series AMD cards and are on Windows 11, Try going back to Windows 10.

[Echothedolpin]

9 hours ago, Dibbsey said:

Everyone accusing the poster of its his fault is plain dumb as fuck. Its a fucking problem a real one happening with many many new 7000 series amd cards. Its the drivers I believe and hope. If its driver easy fix , if its hardware harder fix. Either way its not the user its the fucking product you absolute assuming assholes. You just straight up assume this guy is like 12 years old and has no idea what hes talking about and stupid, you assume that in your brain so you must think its his fault. You guys are worse than microsoft help forums. 

Creating a new account to insult people really makes you look like OP sock puppetting, friend.

[IkeaGnome]

1 hour ago, Echothedolpin said:

Creating a new account to insult people really makes you look like OP sock puppetting, friend.

Not really, they've got a valid point. It happens on just about any thread with AMD issues. 

[Raansu]

13 hours ago, Dibbsey said:

Everyone accusing the poster of its his fault is plain dumb as fuck. Its a fucking problem a real one happening with many many new 7000 series amd cards. Its the drivers I believe and hope. If its driver easy fix , if its hardware harder fix. Either way its not the user its the fucking product you absolute assuming assholes. You just straight up assume this guy is like 12 years old and has no idea what hes talking about and stupid, you assume that in your brain so you must think its his fault. You guys are worse than microsoft help forums. 

Ya, it's definitely on AMD and not an instability of the PC itself for most people imo. My new build ran fine when I installed my old gpu and runs great on my 4090. I also tried my buddies 6000 series AMD card which runs on RDNA2 and it ran fine as well. This is strictly a driver instability problem with cards on the new RDNA3 architecture imo because I used two different 7900xtx cards (RMA'd the first one) and it was the same problem on both. My system is completely stable. The problem is purely GPU drivers from AMD with RDNA3.

 

With that said, while I agree with your post being a AMD issue, maybe tone down the insults lol.

 

5 hours ago, trufret said:

I've been able to resolve my driver timeout issues with my 7900XTX.

After digging deeper into event viewer, I found my WMR VR environment was crashing (DHolographicDisplay.dll taking down dwm.exe) which was crashing the games and resulting in the driver timeout message.

 

The issue turned out to be an incompatibility with an older version of a program called OpenKneeboard and the WMR OpenXR implementation which would cause the crash no matter if OpenKneeboard was running or not.

 

I found if I switched to Steam's implementation of OpenXR runtime

or

Removed the OpenKneebaord registry entry in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR\1\ApiLayers\Implicit

(installing latest build of OpenKneebaord seems to work fine)

I no longer get the driver timeouts.

 

This is probably a pretty niche situation in my case but after these fixes I can run CPU + GPU O.C plus Ram EXPO and system no longer crashes.

 

Nice. I hope that is a solid fix for you. Everything I tried on mine made the crashes less frequent, but it would still eventually crash, so I gave up on the card. It really is a shame, because performance wise its a fantastic card for the price.

[Sir Beregond]

On 10/31/2023 at 11:50 PM, Dibbsey said:

But if it was Linus posting and asking or Jaystwocents yall would believe them instantly. You treat people differently, everything you say is null and void. Not trustworthy.

As a watercolor, Jayztwocents is an idiot.

 

Frankly most watercooling content on any of these channels is hot garbage because its just sponsored EK ads and no one ever talks about prepping loops, part selection, and Jay especially spreads a ton of misinformed opinions or just flat out misinformation. As for watercooling in LTT videos, they always make it look like you can just take parts out of the box, slap a loop together, and pour in tap water from your water bottle. Its quite atrocious.

[XxlDozerlxX]

Has anyone found a solution to this problem? I'm also having the same issue. 7900xtx merc 310.

[OccasionalSmarts]

I happened to find a working fix on another forum until AMD finally releases their fix. From my understanding (which could be completely off) the card runs faster than the drivers allow, so artificially limiting the clock speed of the GPU will fix the problem. The first game I played with my 7900xtx was Control in July-August 2023, and although I was getting great frame rates, it crashed all the time, with varying play lengths. I finally found the fix as I neared the end of the game and had no further problems. 

 

Display clock speed on the overlay while playing whatever game and try to catch what it was reading as it's crashing. Mine was about 2800MHz so I went into adrenalin and tuned my global settings to 2750MHz max clock speed. Been using it ever since and have had no issues. Updating the drivers will reset any manual tuning you have done, so be sure to re-implement after updating adrenalin. Have seen the crash occasionally after updating and forgetting to re-limit, but after doing it again no issues. 

 

A bit of a shame because I'm leaving a couple hundred MHz on the table, but I don't think I lost but a handful of frames in the grand scheme of things. Worked for me, hope it can work for someone else. Hopefully they release an official fix soon...