Game Crashes with RTX 2080 SUPER

Technical Support
1

Hello everyone,

I have recently been experiencing issues while gaming and I hope you can somehow help me with them…

What happens:
Without any recognizable pattern, first, the screen on which the game is running goes black, followed shortly after by my second monitor.
(The second monitor is connected to the onboard GPU of the motherboard via HDMI, and the main monitor is connected to my main GPU - RTX 2080 SUPER - via DP).
At the same time, the GPU fans suddenly become extremely loud (as if it’s about to take off), and the only way to shut it down is by completely shutting down the computer.
When I restart it, it initially has some trouble and ends up in the BIOS, but on the second attempt to boot, everything works normally again.

What I have tried so far:

  • Lowering graphics settings
  • Updating GPU drivers
  • Completely reinstalling GPU drivers
  • Cleaning the PC (not much dust inside)
  • Performing a clean reinstall of Windows 10

Additional observations:
Unfortunately, it is always difficult to find proper error messages or anything similar. The only thing I could find (thanks to the clean reinstall) is the following error message in the Windows Event Viewer:

The description for Event ID ‘14’ from source ‘nvlddmkm’ could not be found. Either the component that triggers this event is not installed on the local computer, or the installation is corrupted. You can install or repair the component on the local computer.
If the event occurred on another computer, the display information had to be saved with the event.
The following information was saved with the event:
\Device\Video11
CMDre 0000004a 00003ffc ffffffff 00000007 ffffffff
The message resource is present but the message was not found in the message table.

Name of the faulty application: dwm.exe, Version: 10.0.19041.746, Timestamp: 0x6be51595
Name of the faulty module: KERNELBASE.dll, Version: 10.0.19041.2913, Timestamp: 0xa1c3e870
Exception code: 0xe0464645
Fault offset: 0x000000000012d862
Faulting process ID: 0x3660
Faulting application start time: 0x01d99a441debf338
Faulting application path: C:\WINDOWS\system32\dwm.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 4be1a99c-3d33-4594-9ff5-49d512d76232
Full name of the faulty package:
Application ID relative to the faulty package:

This issue/behavior has happened to me once before with COD MW2. However, it was only once, and since then, I haven’t had any issues with that game. But with Diablo 4, this happens very frequently.

Furthermore, I have tried to monitor the usage of my hardware during gameplay. However, I couldn’t find anything noteworthy. The CPU and GPU are always between 80-90% usage, and the fans sound normal. It’s only when the screen suddenly goes black that the fans go crazy.

I hope someone can help me. I don’t think the GPU is faulty since I can still play other games (like COD MW2) without any problems.

P.S.
My PC specs:

  • Asus 90MB0MD0-M0EAY0 MB Intel 1151 Z170 Pro Gaming ATX Mainboard
  • Intel(R) Core™ i7-6700 CPU @ 3.40GHz 3.40 GHz
  • G.Skill F4-3200C16D-8GRB 8GB (CL15, 2x 4GB) DDR4-RAM
  • ATX-Netzteil BeQuiet Straight Power BQT E10-600Watt Modular
  • NVIDIA GeForce RTX 2080 SUPER
  • Windows 10 Pro
2

What are your graphics settings?

FPS cap:
VSYNC:
NVIDIA Low Latency:
NVIDIA DLSS:
Texture:

3

Max Forgreound FPS: 150
Max Background FPS: 8
NVIDIA DLSS: DLAA
NVIIDIA Reflex Low Latency: Disabled

Quality Preset ist set to Low → did not additionally change the detailed quality settings

Edit:
Deactivated the DLSS Setting and really thought that was it.

No Crashes for like an Hour just enjoying the game and even set the Quality back to high.

But then suddenly in a Dungeon bevor the Bossroom, it crashed again…

No Idea what to do else…

4

Can try deleting the LocalPrefs.txt file in Documents\Diablo IV I’ve found this to work, but will still get occasional crashes after several hours.

5

Lower your FPS from 150 to 50, see if that works. I am able to play for about 1-3 hours now, before it was 10-30 mins then fenris crash. But loweing my FPS seems to help me play a bit longer but it still crash’s. I still think that blizzard needs to fix this on their end, way to many people with this issue.

6

Thx for the advice.

I deleted the LocalPrefs.txt and lowered the FPS cap to 60.

Playtime was indeed like 2-3 hours perhaps a bit more the it crashed again…

Is this really a Diablo4 Issue and not sth with my GPU? Kinda sucks…

8

I also have a 2080 Super with this same issue, all other games work fine. Did you get any resolution for this?

9

Same Issue Any resolutin ?

10

Minimum System Requirements
System Power Supply
Minimum 650 W or greater system power supply with one 6-pin and one 8-pin
PCI Express supplementary power connectors.

https://www.nvidia.com/content/geforce-gtx/GEFORCE_RTX_2080_SUPER_User_Guide.pdf

Maybe just not enough power.

11

Did you end up fixing the problem?

I have been having the exact same issue in World of Warcraft since I built my new Intel 13th Gen Z790 system last Christmas. I brought over my Asus STRIX GAMING OC GeForce RTX 2080 SUPER 8 GB from my old PC and from day one I have had this issue. Although I’m running Windows 11 I am getting the exact same nvlddmkm error.

I have done everything you have done and then some, and have yet to find a Fix. Tried re-seating and different PCIe Slots without success.

I played around with OC’ing my GPU in Afterburner and I managed to force the error consistently within 20 seconds of launching WoW and even Diablo IV. Managed to find some stability using GPU Tweak III’s profiles, but after a week the driver crashes started happening again. And now I’m back looking for a solution.

Don’t know if you used HWinfo but whilst monitoring my Temps I noticed the GPU Temp was well within the thermal limits but the Hot Spot Temperature was constantly above 100 Degrees Celcius. From what I can tell the 20 series seemed to run hotter than previous-gen cards so I’m not sure if the Hot Spot temps are within normal limits.

12

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