GPU started crashing

Hi,
I recently came back in preparation for S8 after 1-2 months of inactivity.
Out of nowhere, while in town, game is eating 100% of CPU, GPU and RAM. Crashed with not enough GPU message. Game crashed 2 times in few hours.

This never happened to me, I have hundreds of hours played on this PC, never had any problem.

Also one of my friend had similar issue yesterday.

Is this because of some recent updates?
Is there known solution?

Thx

1 Like

What applications are you trying to use at the same time or do you not have anything else open? Sometimes steam or discord give me issues when I use them at the same time as playing the game is why I ask.

I have discord open, but I always had that. I also have Steam active, that might be something I was not using as much before. Not sure.

BTW forgot to mention that my normal CPU/GPU usage while playing D4 is ~20%, so 100% everywhere is extreme.

1 Like

If you recently updated your video driver, then yes. The newer drivers suck.

You need to be on the older drivers, either 566.36 or 561.09.

Do not use roll back. And the nVidia recommended method is hit or miss on results. They say to uninstall the newer driver then install the older one, but that doesn’t work well with this newer driver.

You may need to use the DDU tool from Wagnardsoft to remove the newer driver completely and then install one of those two older ones.

This will fix the issue.

You can get the DDU tool here:

https://www.wagnardsoft.com/content/Download-Display-Driver-Uninstaller-DDU-18110

Instruction page:

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

FOLLOW THE DIRECTIONS ON THAT PAGE for best results.

Good luck.

Thx.
Seems I have not updated drivers for some time, Im at 566.03
As Im saying I really have no idea whats different over past 2 months, except that maybe I was using Steam less back then.

Should I try to upgrade to 566.36 or no point?

It can’t hurt. You could also still use the tool to clean out the driver then install the 566.36 after.

That would ensure there are no issues that may have cropped up during Windows updates, which I’m sure you continued to get between then and now.