Every day, consistently, I will get at least one CTD while playing Overwatch. Both my monitors go black for 10-15 seconds, then when display comes back, the game is closed and there’s a popup that says “Rendering device has been lost. Application closing.”
Analyzing the crash dump gives me this:
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
Which matches what Blizzard says in their help topic for this error message. But I’ve tried every suggested solution and it’s still happening.
I’ve:
-
Updated drivers and OS
-
Rolled back my display drivers
-
Completely uninstalled and reinstalled my display drivers
-
Disabled overclocking
-
Confirmed nothing is overheating
-
Closed background programs
-
Changed from Steam to Battle.net version
-
Reinstalled the game on a different SSD
-
Reset to default settings
-
Validated game files
-
Flashed my BIOS
This only happens in Overwatch.
Specs:
Ryzen 7 7800X3D
Radeon RX 9070 XT
32 GB RAM
Edit: fix found. Copying my post from elsewhere:
What eventually worked was one of the two following things:
- Changing the TdrDelay registry value from 2 to 10. This property lives here:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers
You may need to create the TdrDelay DWORD property if you don’t see it there.
- Underclocking my GPU via the ‘Core Clock Offset’ setting in Adrenalin. I underclocked by about 200 MHz (by setting a value of -200 on the slider).
I have the exact same issue, and I had to stop playing comp because of it. I kept getting longer and longer bans.
The one part that I hate to admit because I don’t want this to be the culprit, is that I also have an AMD CPU & GPU. It may be AMD’s fault somehow. If anyone with Nvidia GPU’s could confirm whether this has happened to them or not, we could get to the bottom of this.
That being said, it could also be part of OW’s programming that is negatively impacting AMD GPU’s, but right now, I have no idea what it is or how to fix it.
I use an AMD CPU and GPU but I don’t have this issue. I did have this issue back when Overwatch 2 first launched however, but back at that time, I only had a CPU (which is an APU, running the game on the Lowest graphics preset).
Now that I have both a CPU and a GPU, and haven’t had this problem since. I also believe this error can happen if your RAM is entirely occupied by other processes in the background. I am not sure if the error that brings up if RAM is 100% is regarding RAM or the Rendering Device being Lost.
You do have 32GB of RAM and stated you closed background processes, so this might not be the issue. I suggest try setting your game to always use High Performance.
Settings → Display → Graphics → Click “Add desktop app”.
Navigate where you installed Overwatch, and select the .exe found at …\Overwatch\_retail_\Overwatch.exe
Set the GPU preference to High Performance.
Try also setting back to DirectX 11, if you have it set to DirectX 12.
Personally I play the Battle.NET version as opposed to the Steam version, which I prefer.
My Google searches found that a ton of people with NVIDIA GPUs had this problem a couple years ago, so I don’t think it’s an AMD-specific thing.
Re: Zeugziumy, I monitor my RAM usage with ISLC and I’m not running out - pretty sure the error message would say something about low memory, also.
Funny that you mention DX12 though because turning on DX12 actually made the crashes stop. However, it also makes the game stutter weirdly sometimes, which is frustrating, so it’s not a perfect fix. Would love for Blizzard to actually resolve the crash so I can go back to DX11.
@daniel-1125
Hmm, another thing I could suggest is going to Windows’ settings → Gaming → Game Mode, disable it.
Similar to the Graphics Settings I posted earlier, try going to the same path as Overwatch’s .exe (\Overwatch\_retail_\Overwatch.exe), and enable “Disable fullscreen optimizations” on the Compatibility tab.
I play this game on borderless windowed, but even if you don’t run in fullscreen, it’s worth a try doing both of those things.
The DirectX 12 stutter seems to be because it doesn’t cache all the shaders as the DirectX 11 does. There was an issue before where everytime I launched Overwatch, the first few minutes would lag (even on dx11). Back then, I was kinda forced to always wait a bit on practice range until the fps would resolve itself. Idk if waiting a bit on Practice Range would fix that with dx12.
Bump, since this wasn’t addressed in the patch yesterday.
Hello!
I had this issue a while back and made a post about it too
here was my solution at the time
”SOLUTION: I rolled back to previous graphic drivers and the issue seems to have been solved.”
idk if this would help this time around but it did for me when I got that same message May last year
Hope this helps c:
As I said in the OP, I already tried rolling back my drivers.
Oh my bad, Check my post because there was something else someone else tried that worked for them instead
Hope u find a solution!
Bump. Unfortunately I just crashed tonight while on DX12, so it’s not a foolproof fix. Please resolve this error, Blizzard!