"Render Device Lost" Fix for RTX

Technical Support
466

Actually now that you guys mention it, I recall the very same thing happening on my 1080 MSI gaming as well.

Come to think of it, every time I go to OW (I play it very rarely), the crash has usually been there. I’ve always thought that OW is just extremely sensitive to overclocking seeing as all my tech is OC-ed (at least both my 1080 and 2080 were), however all of these complaints here make me think that it might be an issue with the game itself - seeing as my OCs are always stable in every other game and benchmarks.

WoW, SC2 and HoTS have no issues either.

I did rename the .exe and didn’t crash for like 7-8 games, so maybe it’s the newest NVIDIA drivers at fault here.

467

Based on this thread it is clearly not only the latest drivers. I am not even using the latest drivers and I still had crashes. Since using the renaming method I have had zero crashes. So it is clearly an issue with something in NVidia’s driver profile which doesn’t play nice with Overwatch. Of course, this does mean there is some code in Overwatch which does something other games don’t do but that is much harder to solve if you don’t know where to look; a generic error code is rather meaningless. This crash is also rather difficult to replicate consistently. Some have a lot of crashes and others only rarely. The latter is what Blizzard saw in-house.

468

There was a Nvidia Driver update today. Going to try launching the game the regular way. Will report back with results.

469

I really hope the update has some bearing on this issue.

I was running an i5/gtx 750 ti for 4 years without anything major…
Then I update to
GPU: EVGA GeForce RTX 2070 BLACK EDITION GAMING 8GB GDDR6
CPU: Intel Core i7 8700
MBO: MSI Z390-A PRO
RAM: 32GB (2x16GB)
HDD: 3TB Toshiba P300
SSD: 240GB Kingston A400
PSU: 650W Gigabyte P650B
OS: Windows 10 Pro

And I’m getting this error daily.

I followed the steps previously given on this thread but while I know its a ‘first world problem’ it’s bloody disheartening too splash out on all new gear and then get hit with this problem.

General annoyance, loss of endorsement levels etc etc

What is always the bothersome thing in these type of scenarios is no one ever admits the issue was their side so you end up going back and forth between companies.
Regardless quite frustrating all round -_-

470

Played three matches today. No issues. The latest Nvidia Driver targeted TDR errors in Apex and maybe that has also fixed Overwatch?

1 Like
472

RTX 2060 owner here…still getting this with the new 419.35 drivers :frowning:

473

Don’t want to jinx myself. But I have been solid since installing the 419.35 Drivers. I also noticed they updated the Physx software as well in this latest release.

474

Spoke to soon… Just happened again. This is terrible Blizzard.

1 Like
475

Months now and this still isn’t fixed. My patience is wearing thin, Blizzard.

476

You may try the “Registry-Hack” as I mentioned 2 Post above yours. It hasn’t crashed for me since I changed the TDR value from 2 sec. to 10 sec. It’s worth a try! :slight_smile:

477

I have an EVGA RTX 2070 XC Ultra, I7-8700, Adata XPG Dazzle 2x8GB 2400mhz. I always get “rendering device lost” after playing for 1 or 2 hours. I get this error even when I play in ultra or high settings. I never play using epic settings and my card barely reaches 70 ºC ( 158 °F).

478

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 2216077360598888284, type 5
Event Name: StoreAgentSearchUpdatePackagesFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Acquisition;DSIC
P2: 803fb005
P3: 17763
P4: 348
P5: Windows.Desktop
P6: 7
P7:
P8:
P9:
P10:

+++ WER1 +++:
Fault bucket rejected_by_rule, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 2538b7e7-e02a-4eda-a229-fa140871c8f6

Problem signature:
P1: 141
P2: ffffb401b9b87460
P3: fffff80203afe718
P4: 0
P5: 111c
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9:
P10:

+++ WER2 +++:
Fault bucket , type 0
Event Name: StoreAgentSearchUpdatePackagesFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Acquisition;DSIC
P2: 803fb005
P3: 17763
P4: 348
P5: Windows.Desktop
P6: 7
P7:
P8:
P9:
P10:

+++ WER3 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 2538b7e7-e02a-4eda-a229-fa140871c8f6

Problem signature:
P1: 141
P2: ffffb401b9b87460
P3: fffff80203afe718
P4: 0
P5: 111c
P6: 10_0_17763
P7: 0_0
P8: 768_1
P9:
P10:

+++ WER4 +++:
Fault bucket 1286299651715438134, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
P1: Windows Defender Antivirus (77BDAF73-B396-481F-9042-AD358843EC24)
P2: 4.18.1902.2
P3: TimeOut
P4: 1.1.15700.9
P5: fixed
P6: 8 / 2049+
P7: 5 / not boot
P8:
P9:
P10:

+++ WER5 +++:
Fault bucket , type 0
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
P1: Windows Defender Antivirus (77BDAF73-B396-481F-9042-AD358843EC24)
P2: 4.18.1902.2
P3: TimeOut
P4: 1.1.15700.9
P5: fixed
P6: 8 / 2049+
P7: 5 / not boot
P8:
P9:
P10:

+++ WER6 +++:
Fault bucket 2216077360598888284, type 5
Event Name: StoreAgentSearchUpdatePackagesFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Acquisition;DSIC
P2: 803fb005
P3: 17763
P4: 348
P5: Windows.Desktop
P6: 7
P7:
P8:
P9:
P10:

+++ WER7 +++:
Fault bucket , type 0
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: Overwatch.exe
P2: 1.33.0.55290
P3: 10.0.17763.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:

+++ WER8 +++:
Fault bucket , type 0
Event Name: StoreAgentSearchUpdatePackagesFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Acquisition;DSIC
P2: 803fb005
P3: 17763
P4: 348
P5: Windows.Desktop
P6: 7
P7:
P8:
P9:
P10:

+++ WER9 +++:
Fault bucket , type 0
Event Name: StoreAgentSearchUpdatePackagesFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Acquisition;DSIC
P2: 803fb005
P3: 17763
P4: 348
P5: Windows.Desktop
P6: 7
P7:
P8:
P9:

479

Yeah, so I also started getting this error… it has NEVER happened before. I’m using a Gigabyte RTX 2080. Slightly OC:d.

The thing is - I have played Overwatch with my OC:d settings since dec/jan, and only started having this crash since early march. I could previously play full days without issues. Sooo… I just don’t see that it’s related to OC:ing your system (unless it’s a super aggresive OC of course).

I always use the latest nvidia drivers, and as of now, I’m using 419.35.

I hope this gets resolved soon.

480

Apex legends is all good with 419.35 on my end. But Overwatch isn’t “healed” :frowning:

481

I am not sure why anyone has previously come to the conclusion it has to be directly related to OC when there are plenty of people who haven’t OC’ed anything and still have Overwatch crash to desktop.

Make sure to try to use the renaming method. It works for a bunch of us without no crash whatsoever since using it (I have been using it for 1.5 months with no crash). I must say I don’t use the latest drivers. I don’t trust NVidia enough to update my drivers because I fear it will only bring back the crashes. I won’t install new drivers until Blizzard tells us the issue has been fixed.

482

Oh god… I thought my Windows is bad, but reinstalled and found out that Overwatch have issues. I had GTX 980 and not have this issue, but on RTX 2080, i do.
Tried: New drivers, Lower the Memory speed from 7000 to 6000, closed all background application, made the change in Windows Registry settings, checked if some temp issue is happening, set the render scale to 100% and 150%.
Results: Yesterday i had 3 crashes. I cannot go in Comp like this.
The main problem is, some days i can play 5-6 hours straight without any problems, other days 1-2-3-4 crashes.

483

I may have something here… I just got a shiny new Cyberpowerpc with a top of the line intel CPU, an RTX 2070… initially, i had found early in this thread to set the “render scale” setting in game to 100… so i did… then the Geforce “experience” recognized that I had Overwatch installed and changed the settings… game crashed a lot again… I disabled the “experience” and set the “render scale” back to 100 in game and it didn’t crash for one game… more testing to follow… I don’t even know what “render scale” is…

1 Like
484

I’m installing the new March 5th drivers as I’m writing this. Not for Overwatch, but Apex Legends. From what I’ve heard here it doesn’t make a difference.

I had my drivers backdated further than anyone I saw on here, made no difference. Backdated to somewhere in the middle. No difference. And now, I’m finally updating to current drivers that supposedly make no difference. Sucks that this is still an issue, it’s been like 4 months. You’d think with this big of an issue affecting this much of their audience they’d jump right on it.

That’s it for now. However–I’m sure I speak for many when I say we’re tired of waiting. Two of my friends and I have moved on, hence the Apex Legends thing. I need to constantly be outputting content, and if I can’t even play one game of Overwatch without this crash… well, you can see the issue here.

485

Please blizzard can we just get a patch instead of some bootleg “fix” that does not actually fix anything, I love this game but it’s going to have to go to the side, it’s tough because I log 4 hours a day just about in this game and I feel as if it’s gonna be gone for a wile

486

They can’t patch if they don’t even have a fix. A fix doesn’t just magically happen. And this especially with an issue that is hard to replicate consistently. From a customer point of view it always seems easy to just “fix it” but that is not how it works in development with countless lines of code.

@Gen
They have been actively trying to deal with this issue but that is never about just throwing developers at the issue. The problem is that the crashes are hard to replicate. They happened so rarely for some of us, including Blizzard. And this is why they asked for data from us. They have looked into that and came with the temporary solution of renaming Overwatch.exe into something else so NVidia’s profiles doesn’t change anything. For some of us this has worked. This means the problem lies with NVidia, in part.

I saw your post history and I have to say I rather doubt it is overheating issue. Whenever I crashed my GPU wasn’t even overheating but showed average temperatures. I do believe that the 2080 is having far more issues than 2070 though. Most of the time when people post about having numerous crashes a day it seems they own a 2080. I do find it rather odd that you crash 5 times in one match whereas others can play a couple of matches before a crash even occurs. You absolutely should try the renaming method. See if that works for you.

1 Like