"Render Device Lost" Fix for RTX

This issue is pertaining to the RTX line of video cards from NVidia only. A rendering device lost error is extremely generic and it can happen with any card from any manufacturer but that doesn’t mean it is the same issue on your RX from AMD. If your video card had the same issue as the RTX does then the vast majority of people playing Overwatch would be reporting about this error, and this doesn’t seem to be the case.

I haven’t crashed since using the OverwatchTest.exe trick and logging in manually bypassing Battle .net launcher. Just wondering when I can stop doing this? Still on 417.71 drivers though - I don’t really trust Nvidia’s drivers at the moment so I like to stick with what I know works.

Renaming overwatch to overwatchtest has been working for me. Haven’t had a crash in over a week using this method. Will report back if that changes. Thanks for the temporary solution to this issue!

System specs:
Gigabyte Windforce OC 2080 TI
I7 9700k
16gb DDR4 3200mhz cl16
1TB Samsung 970 evo
CPU/GPU water cooled with an EKWB custom loop

418.81 will still occasionally (for me its around 1 in 100 games) crash during the PotG with the same low temp, but 100% gpu usage as before.

Guys, overwatch does NOT support overclocking AT ALL, so don’t do it. They have already said it!

Reset overclock settings for overwatch, you won’t get this error anymore!!!

Hi Drakuloth,

I am a very stubborn person and I own a GTX1070. And I tried your solution which is actually meant for RTX users.

And it actually worked. I finally play Overwatch for 2 weeks without any crashes!!

It seems that your solution also works for GTX 10 series. I am very happy with the solution (Which was not meant for me). :smiley:

2 Likes

Thanks for sharing, at least it seems like theyre getting somewhere.

this have been passing to me with RTX 2060, only with overwatch, none of my other games gets a similar issue, 1st day got it like 5 times, then stopped to happen magically for like 6 hours, then this saturday played with 0 issued, then yesterday started to happen every 2 games, i underclocked the memory and stopped to happen for the day, i will see if this still happens or not, but this is something that i see have almost 2 months and not a real fix =(

How long do I need to keep using the OverwatchTest.exe method? I never know when the game has updates now. I have to randomly log into the Battle .net launcher to check for updates - this ends up creating another Overwatch.exe file in addition to my Test file.

Can we get an update?

1 Like

tip:
you can remove overwatch profile froms nvidia driver, with “nvidia inspector”

1 Like

Can we get an update Blizz?

1 Like

i still face the same issue if I use the launcher but works fine with overwatchtest.exe method

Why are my frames now capping at 70-80? I have it set to Custom 300, Ultra settings. Vsync OFF. Setting in Nvidia settings for Vsync is USE 3D APPLICATION’S SETTING. So why am I not seeing my 200 FPS anymore?

Still going strong without crashes on 418.81. I’m now updating to 418.91… fingers crossed.

Everything was working fine when I downgraded to 416.34, no crashes for weeks.

Then I updated to 417.71 and It’s been crashing a lot, even with the OverwatchTest.exe method

timotmcc, you should try 418.81 or above… that fixed it for me.

i think nvidia have fixed it in the newest driver version.
Its OverwatchLeague time with RTX GPUS :slight_smile:

Still having the issue even after the latest nvidia driver.

1 Like

I still just launch from OverwatchTest… not sure when I’ll ever go back to the launcher honestly. Unless I’m playing a different game of course.