I’d like to address this specifically because it’s a common misconception about the Rendering Device Lost error. We actually aren’t the only game that has this error. This is just a unique error message we display when you experience a Timeout Detection and Recovery (TDR) error while playing Overwatch. You may be having the same problems with other programs and not associate them because our game has a special error message for this PC level problem.
You may experience them more while playing Overwatch than other applications you use personally, but there are a couple reasons for this. First off, we’re going to be using different drivers than other games you play, most likely. Our engine also doesn’t pull punches with your hardware. It’ll use as much of your PC as you let it, which makes it kind of a stress testing application if you’re at super high settings. If you’re getting a rendering device lost error, the overwhelming majority of the time, there’s something going on with your PC that we are triggering, but that is a legitimate problem you must fix. This isn’t a hard and fast rule - we have had a bug or two in the past that caused this, but these are super rare and we don’t know of any at the moment.
There are a number of possible fixes for the Rendering Device Lost error message, but nothing is one size fix all. I recommend checking out that link and going through the troubleshooting. If it doesn’t work, this is a very involved error message, you’re honestly best supported by contacting our support agents.
At this particular moment in time, we have seen some issues with the most recent driver (417.22) in some of our games. If you’re on this driver, I recommend clean installing the previous driver.
- Download the 417.01 driver from Nvidia
- Proceed until you reach the Options screen
- Choose the Custom (Advanced) option.
- Check the box for Perform a clean installation, then follow the prompts to install the drivers.
For anybody who sees this post in the future - this above work around is for a very specific point in time (the week of Dec 3 2018 until future drivers are released which fix the error.) If you see this post far in the future, you may instead want to update your driver.