Curious thing for me is… I have been playing for almost 6 month on my new PC ( Ryzen 2700X, G.Skill FlareX DDR4 3200 PC4-25600 16GB 2x8GB CL14, MSI GeForce RTX 2080 Gaming X Trio, and a MSI B450 Gaming Pro Carbon AC) And never had an issue until almost 20 days ago. When I changed my settings inside the game ( Deactivated a lot of stuff like lights, lowered shadows, etc…) Most notable change was deactivate the V-sync and put the target frames at maximum, (something used to avoid the input delay of the V-sync and minimize tearing).
I recently got this rendering device lost, which is a surprise, as I have been playing like 6 months with no problems whatsoever, so my gut is telling me that somewhat this problem is an stability issue more than a real. Anyways, for me is just a very uncommon problem, last time have been playing like a whole week or so with 0 problems, until yesterday, when on a ranked it popped out.
I am comming back to fullscreen game and V-sync, If I have another crash, I’ll write here to inform.
Just adding to this. 2080 Strix. I was getting constant RDL crashes but since I’ve renamed Overwatch.exe to anything else.exe I’ve not dropped once in 3 months. Same fix worked for 2 other friends 100%.
So for those whom have factory overclocked MSI cards, the issue seams to happen only if you have the MSI afterburner program installed, reguardless of what setting you even if you underclock, if the afterburner program is installed you get the problem with out it havent had one issue.
Oh wow, there appear to be more a lot of people having this issue. I think I might have found a solution. For some reason by default my fps cap was set to 300 fps… this is a bit silly because the human eye can only see at 60 fps, so what are the other 240 fps supposed to be doing? Anyway, if you set your fps cap to something reasonable like 120 fps (only 2x as much as you need) it runs perfectly well.
and just quick fyi, reason you want higher refresh rate than you can “see” is because our eyes just bring in light our brain is doing the seeing and our brains kinda have its only compression algorithm and some of the information we see gets lost before it gets to our brain cuz our brain decided it wasn’t important, with 120 and 240hz refresh rates that provides more information (think signal input) and this helps our brains reduce blur. tust me spend an hour or 2 on a game at 60hz then bump it up to 240 and honestly tell me you don’t see a diffrence
I had this issue. I wrote a detailed description of how to fix it. System used to diagnose was Windows 10 Version 1903, 64 Bit. Tools used to diagnose, debug and correct issue: WinDbg, Visual Studio 2017, Proc Explorer, AIDA 64 Engineer and Hyper-V. In my view this issue is high priority and relates to memory management issues. Also observed in logs and forced crashes were avoidable errors caused by a NULL ptr Dereference
described in CWE-476 - https://cwe.mitre.org/data/definitions/476.html
(I guess I can’t include hyperlinks here).
Suffice it to say this is not isolated to 2xxx Series cards, but is likely isolated to NVIDIA GPUs.
I would post the procedure I went through to fix it, but I really don’t care anymore. This game feels toxic. It seems as if Blizzard has both stopped trying to create a positive environment, let alone moderate their own game. Feel free to PM me for the method that worked for me, if they have that feature enabled on Discourse.
2 Likes
Yes the launcher makes a new .exe file but don’t start the game from the launcher. You have to run it from file you renamed every time. Annoying because you have to log in every time… but it works crash free. Also when there is and update you’ll have to delete the old renamed file and rename the new one again
I’ve been getting this problem for a couple of months on a 2070, but the last couple of weeks it has gone from maybe once a week to once a day. Suddenly today, I started getting the crash every single match I tried to play. I couldn’t finish any. So far I was able to play without errors after changing the .exe to overwatchtest.exe. I’m kind of at a loss as to why I have to do that though, why isn’t this something Blizzard fixes?
Been getting this for what feels like forever now. Sent in my MSInfo to the email that you’ve requested. I’m currently running a 2080 RTX, and I hope we can get a fix soon.
Welp, I thought the “renaming” thing fixed my game. Psych. It did not. Of course, the first crash it decides to do in three days is during comp. Yay for 10 minute ban!
I left my dxdiags already (above), as I mentioned, short of completely re-installing, I don’t know what’s wrong. Help.
Also, I disabled ShadowPlay overlay as well (that actually seemed to INCREASE the crashes, but whatever…)
I don’t know if someone replied you already, but I downloaded it from Guru3D website.
Remember that after a Nvidia Driver update you must delete the OW profile again.
Since I did it, I can play tons of hours without problems. But yet just played QP games at Medium settings. I will try Competitive next week.
We have seen a lot of succesful reports using this method. So WHY isn’t this issue fixed yet so we can at least stop using this method and start the game normally ???
We are 6months further now and still at the same step as when the topic was created
You are right, Raven. And they don’t seem interested in this anymore.
This is the most used post in this forum (712 replies, 30k visits) and Blizzard didn’t even pinned this reply: "Render Device Lost" Fix for RTX - #563 by Kaldraydis-1147 (email collecting errors)
Maybe they don’t even look at that email anymore like it seems with this post.
this seems to work for me aswell. after days or searching. it was only this ez to fix.
tyvm good sir! have a good day!
It’s by far the most popular topic on the eu forums as well. I guess if you look on the bright side, that means there are comparatively few other issues to complain about. With the adoption of RTX cards the number of people affected by this is going to increase so I guess it will come up on their radar again at some point.
For now, since I’ve started renaming two months ago, I haven’t had a single crash in hundreds of games so I’m satisfied it works for me.
1 Like
Thank you for this. forget the 2xxx cards, am i the only one who is getting this all the time with my 1060s?
HeyNow + owlie - as the devs have said over an over again, Rendering Device Lost has dozens of potential root causes. This particular thread is for the RTX 20x0 line of cards. There are other posts for your cards - try searching.
I agree completely - the rename fix is a complete solve for the RTX 20x0 cards. The biggest problem people with RTX 20x0 cards seem to be having here is following instructions. Time and again people posting “the launcher just makes another Overwatch.exe” - well, yes. It does. So what. Run the OverwatchTest.exe (not the launcher) and your crashes will be fixed.
Hey there. Using a GTX 1660 Ti myself, and I started getting the error two days ago at random. I scoured the interwebs for advice and found that at some point my render scale (OW Settings menu, under Video tab, Graphics Quality, Advanced) was bumped up to 150% in OW. I set it to 100, and no crashes since. Temperature has gone down a few degrees too.
May this help you and not jinx my game. knocks on wood
FXXK it man. I have a laptop with GTX1060 and a desktop with RTX2080. The game crashes on both devices every single day !!! I am a rank player and it always happens during the first and last 30 seconds of the game. I am just keeping lost 50 points even I won the game!!! FFFFUUUUUCCCCCKKKKKK