Still experiencing this error.
I think your problem is different than some of us, for me only overwatch crash, the rename fix works, not any other game does this, even overclocking my 2060 to 2070mhz, and 1000+ on memory, all the other games work just fine, but overwatch? so weeeird.
1 Like
I don’t have any issues in any other games. Just Overwatch. Just to clarify. I have overclocking profiles for other games specifically for this reason now.
still you said you getting other errors, for me it is only the render device lost, nothing else, and after 3 months, the rename is working for me without any problem, just annoying to put the user/password/verification code, every time you want to log in.
I"m a technical guy, reinstalling drivers is the least you can do to fix an issue. If that doesn’t work. Dig deeper. In doing so, I created other issues for myself that only Overwatch didn’t like.
The shortcut rename workaround works for me. No crashes since using it. Sure is getting old though.
It is time that Blizzard admits there is some issue instead of sending users down a path of trying a million different options that have not actually fixed the issue for anyone.
I have a RTX 2080 TI with an 8700k in my home PC that started getting this issue after updating from a 1080. Nothing is overclocked at all. I have formatted my computer, installed all of the latest updates and drivers. Disabled 3D Acceleration on everything that might utilize the GPU (browsers, etc.) No apps are creating an overlay ingame, including Geforce Experience. Closed all extra apps that are running and I constantly get these errors once or twice a night, I literally cannot do competitive because of this and I have been googling this same error for months now.
To top it off, I bought an Acer Predator 500 laptop the other night ($2500- has a i7 8750H, RTX 2080 in it) and I am now getting these same errors on the laptop.
Does Blizzard have this issue with their code documented is actively pursuing a fix?
1 Like
Last update on this thread from a blue was first week of February from what I can see.
The dev team have been looking into this since Dec if not earlier. I’d love to know what they have found so far after 3 months investigations.
1 Like
Been having this issue ever since I upgraded from my 1080 to a 2080 as well. This is the only game that ever has issues. I’m at factory gpu settings. Latest drivers. Get a device render crash almost daily.
I was at a lan party friday-saturday and had it happen 3 times. It was especially infuriating due to the fact we hit our connection cap to blizzards servers so if you crashed it took upwards of 15 minutes to log in.
This is just unacceptable.
Anyone wanna bet the computers running Overwatch League don’t have RTX cards?
Blizzard has already admitted there is an issue. But admitting there is an issue isn’t the same thing as knowing exactly what is causing the issue. Not to mention that for some people it is more than one thing causing the crashes.
Have you already tried renaming Overwatch.exe to something like OverwatchTest.exe?
It would be nice if they bothered to do a pinned post stating “Known issues with RTX cards” with a run down of temporary fixes instead of fishing everything from a 500+ post thread.
We’re still checking this out and communicating with NVidia on it, but have no updates to share at the moment, unfortunately. The quoted text is still the method players should be using to troubleshoot this issue. Rename the file and see if it works. If it doesn’t, you have a different problem most likely and should try troubleshooting it in another thread or with support. Make sure you let us know that you tried the rename method if you contact us so we don’t send you back to this thread.
5 Likes
3 months and still no progress between ye 
I’d like to think that ‘if’ this is eventually resolved that they will actually advise what happened and how they fixed it.
Unlikely but transparency isn’t exactly a thing in these situations as no one wants to admit fault.
Ah well
1 Like
The Overwatchtest.exe fix doesn’t let me get past the Authentication stage. I get no notifications needing authentication from the app, and using the manually generated codes don’t work either.
I had this issue for 2 years, now i play MH mode only, I’m scared to play ranked.
GTX1080TI, windows 10, tried everything, i give up, now Im happy with Apex. never crash.
Have you tried resyncing the authenticator? With the renaming method you won’t get a notification but you will need to sync manually. It is possible your app is out of sync. If it isn’t that it is also possible you are filling in the wrong credentials. As your last resort you should contact Blizzard directly, not the forum, in case it is still doesn’t work even with what you may believe are the right login codes.
@Vike The issue you are experiencing is likely not related. This is an issue concerning the RTX graphics cards only. Any card can get a render device lost error with it being a rather generic error which doesn’t immediately explain why the graphics card stopped for a short moment.
This keeps happening to me as well, this is getting crazy, my LOCK OUT TIME FROM NEXT COMP GAME 2 HOURS??? and I cant join back in. This only happens when I play COMP
I’ve put the RTX 2060 back, turned off Shader Cache option in NVIDIA Control Panel and restarted the computer, after doing that I was able to play for 3 hours without any crashes or problems.
-i.imgur.com/CoTLsIM.png
Switched from an RX 580 to RTX 2060. Now I am getting this problem. Where I didn’t have this issue before. It really seems like an issue with RTX Cards… Novideo memes are kicking in 