When I purchased my 2080 Super (years ago) I remember trying at least 5 different cards from different manufacturers. One of them (the Asus ROG Strix 2080 Super) crashed OW every few minutes. The GPU load was only moderate (my average load is always well below 100% to be able to keep stable frame rate) and the temps were low/average. The crashes happened only with that card and only in OW. The other cards could run OW without issues and they were tried in the exact same machine with the exact same software and hardware environment.
All cards had their default settings without tweaks but I used MSI Afterburner and hwinfo64 for monitoring. The Asus ROG Strix 2080 Super was the only card with boost clock going above 2GHz. I ended up keeping the MSI 2080 Super Gaming X Trio that had way better thermal performance and no issues in OW (it has much bigger cooler fins, lower minimum clock and can run with zero-rpm fans when I’m not gaming). The default variable clock of the MSI GPU is between 300MHz and 1995MHz. The other cards I tried were cheaper models with lower clocks.
Overwatch is an application running without administrative privileges. It shouldn’t be able to crash anything by simply asking the CPU and the GPU to do work. The “Rendering Device Has Been Lost” problem is highly unlikely to be the fault of Overwatch.
Video drivers can detect specific applications (for example by the name of the executable) and behave differently. This way the developers of the driver and the GPU can provide backward compatibility for some popular old 3D applications and they can manipulate benchmark results too. This is why some older 3D apps and games crash or disfunction after renaming the executable.
Since OW is a popular “old” game I wouldn’t be surprised if the NVidia drivers tried to do OW-specific tricks. This means that it can very easily be an NVidia driver issue that causes problems only when you play OW. This is something over which Blizzard may have zero or little influence.