Overwatch hard-crashes to desktop after update to 1.57.1.0.78777

The game will crash at random intervals straight to desktop with no prior symptoms. Usually happens about 20 mins into a play session. No freezes, or stutters, prior to crash, but only happens in game, not on the menus.

I already got a warning for exiting while being in a match, as well, even though hard-crash of the client is to blame. How hard is it to link the issue report system with the match behavior tracking, so that this doesn’t happen…

Windows 10 Build 19042.804, RTX 3090 NVIDIA Driver 461.40.

Have you worked through this troubleshooting guide yet? It helps resolves the most common of crashes related to Overwatch:

Unfortunately all disconnections and game crashes counts as leaving the match and will be penalized appropriately. The game server has no way to discern a legitimate disconnection or game crash from one that is forcefully caused by a dishonest player to bypass leaver penalties. You can learn about this policy here:

If you need more assistance, please start a new post in the technical support forum. The bug report forum is typically not monitored by MVPs or Blizzard Tech Support, and is only for reporting in-game bugs.

Hi there,
I have worked my way through the troubleshooting guide. It does not change the situation.
Does a hard-crash not qualify for a bug? I am happy to post this in its respective place (alongside a diagnostic log), just point me to it.

Edit: posting the crash diagnostics HERE (can post the full thing as well, it’s just rather long) because I get none of the symptoms @Teawy has posted but the thread is locked until other users respond to it? It seems to me this is a memory access issue, rather than a GPU problem (I ran full diagnostics on the GPU with an intensive VRAM/3D test, all good there)

-------------------------------------------------------------------
                                ERROR                              
-------------------------------------------------------------------
<Inspector.Summary:>
Overwatch - 1.57.1.0: EXCEPTION_ACCESS_VIOLATION reading from 0x000001d993db8d80
<:Inspector.Summary>

<Inspector.Assertion:>
EXCEPTION_ACCESS_VIOLATION reading from 0x000001d993db8d80

**Crashing Thread** (ID: 13096)

A crash would classify as a Bug if there are multiple people having the Issue and it has a consistent method of triggering.
The “Technical Support” Forum would be the place to post this.

If you didn’t do so already Update your Graphics Card driver and OS if any updates are available.

Do you get a short Black-Screen when the Crash happens ?
If you’re not playing in Full-Screen that is.
If so then it should be GPU related crash as long as the System proceeds to Operate like normal after the Crash

I am playing in full screen and there is no black screen or immediate graphical glitches before or after.

I have updated all gpu drivers to their latest and the problem persists.

I also ran an intensive GPU VRAM / 3D test to disqualify faulty hardware being the reason for this. Passes with flying colours.

The overwatch logs indicate a possible memory access violation.
I am attaching the start of the diagnostic log below (I can attach the whole thing, alongside the produced memory dump, if it would be useful, it’s just rather long)

-------------------------------------------------------------------
                                ERROR                              
-------------------------------------------------------------------
<Inspector.Summary:>
Overwatch - 1.57.1.0: EXCEPTION_ACCESS_VIOLATION reading from 0x000001d993db8d80
<:Inspector.Summary>

<Inspector.Assertion:>
EXCEPTION_ACCESS_VIOLATION reading from 0x000001d993db8d80

**Crashing Thread** (ID: 13096)
DBG-ADDR<00007FF777986A20>()
DBG-ADDR<00007FF7779862EB>()
DBG-ADDR<00007FF777983185>()
DBG-ADDR<00007FF77798650F>()
DBG-ADDR<00007FF7779841F4>()
DBG-ADDR<00007FF7779ACC44>()
DBG-ADDR<00007FF7779286B4>()
DBG-ADDR<00007FF7779578FF>()
DBG-ADDR<00007FF777959C87>()
DBG-ADDR<00007FF77795956A>()
DBG-ADDR<00007FF777941EEB>()
DBG-ADDR<00007FF777955738>()
DBG-ADDR<00007FF777952BEE>()
DBG-ADDR<00007FF7779E679D>()
DBG-ADDR<00007FF7779FD3CA>()
DBG-ADDR<00007FF77775B6E1>()
DBG-ADDR<00007FF7779F82FE>()
DBG-ADDR<00007FF777A03670>()
DBG-ADDR<00007FF777757F96>()

<:Inspector.Assertion>

-------------------------------------------------------------------
                             SYSTEM INFO                           
-------------------------------------------------------------------
Application:               C:\Program Files (x86)\Overwatch\_retail_/Overwatch.exe
Build:                     Overwatch_78777_Retailx64
Created:                   16:33:15 Feb 10 2021
Game Server IP:            5.42.170.106
Bnet Account ID:           463322335
Game Account ID:           125017443
Operating System:          Windows v10.0 Professional
Operating System Version:  10.0 Version 2009 (OS Build 19042)
Operating System Platform: 64-bit
Application Platform:      64-bit
GPU Type:                  NVIDIA GeForce RTX 3090
GPU Driver:                27.21.14.6140 - C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_5e5ddf14f45dc8f6\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_amd64_5e5ddf14f45dc8f6\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispsi.inf_
GPU Driver Date:           20210122000000.000000-000
GPU Core Delta Freq:       0
GPU Memory Delta Freq:     0
GPU Voltage Delta Freq:    0
Physical Resolution:       3840x2160
Effective Resolution:      3840x2160
Display Mode:              Full Screen
Active GPUs:               1
Number of cores:           12
Total Memory:              32683 MBs
Available Memory:          26774 MBs
Total Page File:           37547 MBs
Avail Page File:           29080 MBs
GPU Memory:                4095 MBs
GPU Allocated Memory:      3616 MBs
GPU Temp:                  51 C

Do you use Avast or AVG ?
If so deactivate it or add anything Blizzard related to their Exceptions. (Similar Issue)

I run no third party anti-virus programs, and I’ve set up Windows Defender to not scan folders where games are installed, including Overwatch and other Blizzard stuff.

Have you found a resolution for this issue? I’m experiencing the exact same thing, also with an RTX 3090. I’ve found that playing at all Low Graphics prevents crashes. Obviously though with a 10900K and 3090, I’d love to be able to play with good graphics. I only seem to have this issue with Overwatch, and somewhat with World of Warcraft. Other games like CoD, Control, Rogue Squadron, MSFS 2020, etc all work flawlessly.

Unfortunately I haven’t. The game keeps crashing with various RTX 3000 series cards I’ve tried. Just like you, swapping over to Low graphics presets largely solves the issue. I’ve tried fresh-installing windows (tried both Windows 10 and 11 now), different drivers, I even tried a friend’s RTX 3090 for a sanity check to make sure it’s not my specific GPU. In the meantime online reports from other people seem to confirm my suspicions - Overwatch is unstable with RTX 3000 series GPUs and the devs are not interested in fixing it.

Like you, I’ve found it’s ONLY Overwatch that does this. I am able to play any other title at full tilt for hours without any issues.

If you’ve been able to get your hands on a rtx 3000 card, you really have nothing to complain about. I’m glad the devs are not fixing it.

I think you’re looking in the wrong place. If your GPU was unstable, in 99% cases you’d be getting driver crashes (aka. nvlddmkm.sys for nvidia) or worse - artifacts.

EXCEPTION_ACCESS_VIOLATION is usually a software error but not always. It can also indicate a problem with your RAM (timings, frequency or voltage). Perhaps the reason you only crash in OW is because it stresses your RAM the most out of any game you play.

That’s a good point. I opened up the memory dump and did some limited debugging (as much as I can with compiled software). It seems the exception stems directly from a call in ntdll.dll rather than through the nvidia driver, which doesn’t feature in the call chain at all. I’ll be running some memtest86 cycles I guess…