Non-stop crashing of Diablo 4 (every hour) on an AMD system with Nvidia GPU (Error : NONCONTINUABLE_EXCEPTION_c0000025)

Technical Support
1

TLDR; Rolled back to driver version 561.09 on my 3080 Ti fixed the crashing issue on my Ryzen 7 9800X3D system.

Just wanted to say that I crashed non-stop after upgrading my computer from a I9 10850k to a Ryzen 7 9800X3D. I kept the same graphic card, a 3080 Ti. I played the new season 3 days with my old system with no crash and after upgrading, I crashed every 1h30-2h. Since I kept the same graphic card, I thought it was an issue with the CPU or a BIOS setting, but nope. After trying everything under the sun and after reading every threads on reddit and Blizzard’s forum, it was my graphic driver the problem.

When I upgraded, I did a clean install of the driver version 572.16. Crashed on that version. I rolled back to the same driver version I had before changing my system, so 566.36, crashed on that version.

Finally, I saw some people recommending the driver version from september, 561.09, and… I DIDN’T CRASH!!!

There’s definitely an issue with a mix of having an AMD CPU, the drivers version on an Nvidia graphic card and Diablo 4.

Error :
UNHANDLED EXCEPTION: NONCONTINUABLE_EXCEPTION (c0000025)

2 Likes
2

Rolled back to 561.09 Game Ready Driver fixed crashing for me too, on my 2070 Super, i7-9700K, 32Gb DDR4-3000 RAM, 1Gb SSD, Win 10 Pro.
With 572.16 latest Nvidia Driver, D4 crashes every 1-1,5 hours on my PC BNet Account.

1 Like
3

I’m gonna give this a shot. I NEVER had a single crash before Season 6. Ever since VoH came out, it’s been non-stop crashing every time I play. I get about an hour out of it and then it starts to give me some micro-studders. If I keep going, about another 10 minutes and it crashes. Sometimes it will give ‘out of memory’ errors, other times it does not.

It’s the ONLY game I play that does this. Nothing else I play behaves like this at all. It’s beyond frustrating.

4

I will add, that to this point, 561.09 has been a stable driver release for the game.

And to those worried about it being an older driver, don’t. You can safely run on a driver as old as 8 months before the game would even be mad about it. And even then you can tell it to run it anyway. Mine was not happy (had a red banner in settings, but played fine) as I ran this game on 551.31 up till last week. (1 year old driver) Since then I have been updating each day I go to play, to see if any of the drivers cause me issues. It wasn’t till I hit 556.12 that the game stopped complaining.

I have not had a problem yet. But I know the last couple drivers were problematic for many, so I expect at some point to have issues potentially.

Those wanting to use the driver, please follow these suggestions:

Do NOT use rollback.

nVidia recommendations:

  • Download driver you want
  • Uninstall current driver
  • Install the downloaded driver
  • Restart the system (use restart, not shut down)

If that FAILS to help:

You need to get the DDU tool. You can find that here at Wagnarsoft:

https://www.wagnardsoft.com/display-driver-uninstaller-DDU-

The full guide can be found here:

https://www.wagnardsoft.com/content/How-use-Display-Driver-Uninstaller-DDU-Guide-Tutorial

Download the tool, then read the instructions on the site on how to properly use the tool for your system.

  • It will remove the driver completely, then you can install the one you downloaded in the previous step.
  • It will require you to go offline during the process (again, read the instructions).
  • But its safe to run and can fix issues that reverting, rolling back or simply uninstalling/reinstalling won’t fix.

Finally, I might suggest not using the nVidia experience software or app, at least till you are sure the game is running fine.

1 Like
5

I love you! This has been a giant thorn in my side. Only Diablo would crash!

9800X3D, ASRock X870 Pro Wifi, Asus 2800ti

6

Hello,

I can also confirm that all versions after 561.09 have problems in Diablo 4.

Yesterday, I naively thought that this problem was fixed and I applied the release 572.16 of January 30th
What a big mistake.

I’m good to do the DDU circus again + reinstall 561.09.

GTX1070 - i5-11400F - 32Gb RAM - CT1000P3SSD8 - W11

7

I will be upgrading to 566.36 later today then playing again for a bit.

Tomorrow I will be testing 572.16

As of today, nVidia is still listing that version as the latest.

8

I was so hopeful about this and followed all of the instructions precisely.
My time in the game was noticeably longer, but I still got disconnected before I reached the 30-minute mark.
Oh well, at least I didn’t have to pay for the DDU tool.
I guess I’ll just playing D3 until Blizzard and Nvidia work this out, which will hopefully be sometime prior to Season 8.

9

Well, I will be updating mine again here in a bit to the 566.36 and playing tonight. Will see if that has any effect on the playability, but if the past results hold true, I doubt it will cause me an issue.

12

I also play on another gaming PC that is configured identically, except it has a different motherboard than the one I’m playing on at the moment.
All the drivers on the second PC are up to date and I’ve never had an issue on that PC nor have I ever had to tweak anything.
So, I have a feeling that the conflict goes deeper than the display driver and that some folks have just been unlucky.

13

Pretty much.

I think there is a basic issue going on within the game that it fights the drivers too, but only under certain conditions.

It all boils down to an issue that affects a decent chunk of players, but in the grand scheme not as many as you would think, or the numbers of players complaining would be a LOT higher here.

I played for a while tonight on the driver as I had mentioned above. No issues. *shrug

Tomorrow going up a driver again, and will be on the newest one.

14

Ive tried several drivers and Im still crashing. WHen are we getting a response or a fix for this crap.

1 Like
15

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.