After the latest update Overwatch frequently crashes in matches when processing keypress commands such as TAB, SPACE, ENTER.
It almost never happens after the first press of any reproducing key. Only 4-5 presses of e.g. the TAB key in a match causes the game to crash.
The game closes either silently without any message or with a message box saying that external software prevented the game from working properly.
No third-party software like antiviruses are installed.
The game logs directory (\Documents\Overwatch\Logs\errors) contains error logs and a dump.
All logs contain the following information:
-------------------------------------------------------------------
ERROR
-------------------------------------------------------------------
<BlizzardError.Summary:>
Overwatch - 2.4.0.2: EXCEPTION_ACCESS_VIOLATION executing 0x0000000000000000
<:BlizzardError.Summary>
<BlizzardError.Assertion:>
EXCEPTION_ACCESS_VIOLATION executing 0x0000000000000000
<:BlizzardError.Assertion>
Build: Overwatch_111774_Retailx64
Operating System: Windows v10.0d Core
Operating System Version: 10.0 Version 2009 (OS Build 25346)
GPU Type: NVIDIA GeForce RTX 3060 Laptop GPU
GPU Driver: 31.0.15.3168
Tank State: Loop Running
Video Device State: Active
Device Ext Refs Count: 8
Last OS Error: 0x0
2 Likes
Overwatch tried to execute an function pointed to uninitialized memory address. This may indicate an callback or detour function wasn’t loaded or delete deleted before its attempt to invoke. I hope devs can fix this. There’s some additional logs? Also try include crashlog from Windows Log Viewer.
- I can assume is not related to GPU/Graphics Card because RefCount on GPU device is
greater than 0
- Also this indicate, that was not caused by a winapi call because LastError was zeroed (when
::GetLastError() != 0 this means have an error otherwise == 0 was success)
You said something about pressing keys, maybe is related to DirectInput/RawInput. An tip try if you have RAW Input enabled in settings, try disable. Usually direct raw input, should allocate some memory before each frame to query keyboard key states and mouse states.
2 Likes
Event Logs contain no information about the crash associated with Overwatch; the game closes silently.
Updating a video driver, reinstalling the game and Battle.net didn’t help.
2 Likes
Sad. This is most big problem in all games, in Release mode compilation all useful debug information to help find bugs and report crashes are stripped from game code.
2 Likes
Yeah, having the debug symbols, I’d be glad to explore generated dump.
Stacktrace contains only Overwatch functions.
2 Likes
Reporting the same error. It only just started today, before today a crash was pretty rare.
playing this afternoon, I had 2 crashes extremely similar to what the OP describes. In the middle of a match and then just suddenly the window closes. Battle.net doesn’t even lag on the ‘playing’ button like it does when closing normally, just, window closed, no error message whatsoever, poof as if I hadn’t been playing at all.
I went and updated my graphics driver as a new one just dropped. Played a couple matches and then had a 3rd crash at the end of the match, though this one actually threw up an error message before it closed the game and appeared in the crash log folder. Results below:
Blockquote -------------------------------------------------------------------
ERROR
BlizzardError.Summary:
Overwatch - 2.4.0.2: EXCEPTION_ACCESS_VIOLATION reading from 0xffffffffffffffff
<:BlizzardError.Summary>
BlizzardError.Assertion:
EXCEPTION_ACCESS_VIOLATION reading from 0xffffffffffffffff
Crashing Thread (ID: 3624)
DBG-ADDR<00007FFB47EA104C>()
DBG-ADDR<00007FFB38EE5ED1>()
DBG-ADDR<00007FFB38F4206F>()
DBG-ADDR<00007FFB38F42219>()
DBG-ADDR<00007FFB39AC1DE2>()
<:BlizzardError.Assertion>
SYSTEM INFO
Application: C:\Program Files (x86)\Overwatch_retail_/Overwatch.exe
Build: Overwatch_111774_Retailx64
Is Elevated: 0
Created: 12:12:02 Apr 13 2023
Game Server IP: 0.0.0.0
Bnet Account ID: 82105126
Game Account ID: 147040788
Operating System: Windows v10.0 Core
Operating System Version: 10.0 Version 2009 (OS Build 19044)
Operating System Platform: 64-bit
Application Platform: 64-bit
GPU Type: AMD Radeon RX 6600 XT
GPU Driver: 31.0.14051.5006 - C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository
GPU Driver Date: 20230420000000.000000-000
GPU Core Delta Freq: 0
GPU Memory Delta Freq: 0
GPU Voltage Delta Freq: 0
Physical Resolution: 1808x1017
Effective Resolution: 1808x1017
Display Mode: Windowed
Number of physical cores: 8
Logical core: 0 - phsyical mapping: 0 (group 0) - efficiency class: 0
Logical core: 1 - phsyical mapping: 0 (group 0) - efficiency class: 0
Logical core: 2 - phsyical mapping: 1 (group 0) - efficiency class: 0
Logical core: 3 - phsyical mapping: 1 (group 0) - efficiency class: 0
Logical core: 4 - phsyical mapping: 2 (group 0) - efficiency class: 0
Logical core: 5 - phsyical mapping: 2 (group 0) - efficiency class: 0
Logical core: 6 - phsyical mapping: 3 (group 0) - efficiency class: 0
Logical core: 7 - phsyical mapping: 3 (group 0) - efficiency class: 0
Logical core: 8 - phsyical mapping: 4 (group 0) - efficiency class: 0
Logical core: 9 - phsyical mapping: 4 (group 0) - efficiency class: 0
Logical core: 10 - phsyical mapping: 5 (group 0) - efficiency class: 0
Logical core: 11 - phsyical mapping: 5 (group 0) - efficiency class: 0
Logical core: 12 - phsyical mapping: 6 (group 0) - efficiency class: 0
Logical core: 13 - phsyical mapping: 6 (group 0) - efficiency class: 0
Logical core: 14 - phsyical mapping: 7 (group 0) - efficiency class: 0
Logical core: 15 - phsyical mapping: 7 (group 0) - efficiency class: 0
Total Memory: 32619 MBs
Available Memory: 26949 MBs
Total Page File: 37483 MBs
Avail Page File: 29013 MBs
GPU Memory: 4095 MBs
GPU Allocated Memory: 909 MBs
GPU Peak Memory: 1336 MBs
GPU Temp: 70 C
Reporting a similar set of crashes to the OP. Only just started today, before this it’s been rare for the game to crash. Had 2 exactly as OP described, mid-match and then poof, the window closes suddenly, no warning, no error, just gone like I hadn’t been playing.
I went and updated my driver to see if that was the issue and ran a scan and repair, nothing found. I played 2 more matches and had a crash at the end of the match, thought his one threw up a more normal error before it closed the window and let me describe what was going on, also appears in the crash log folder, as below:
ERROR
BlizzardError.Summary:
Overwatch - 2.4.0.2: EXCEPTION_ACCESS_VIOLATION reading from 0xffffffffffffffff
<:BlizzardError.Summary>
BlizzardError.Assertion:
EXCEPTION_ACCESS_VIOLATION reading from 0xffffffffffffffff
Crashing Thread (ID: 3624)
DBG-ADDR<00007FFB47EA104C>()
DBG-ADDR<00007FFB38EE5ED1>()
DBG-ADDR<00007FFB38F4206F>()
DBG-ADDR<00007FFB38F42219>()
DBG-ADDR<00007FFB39AC1DE2>()
<:BlizzardError.Assertion>
SYSTEM INFO
Application: C:\Program Files (x86)\Overwatch_retail_/Overwatch.exe
Build: Overwatch_111774_Retailx64
Is Elevated: 0
Created: 12:12:02 Apr 13 2023
Game Server IP: 0.0.0.0
Bnet Account ID: 82105126
Game Account ID: 147040788
Operating System: Windows v10.0 Core
Operating System Version: 10.0 Version 2009 (OS Build 19044)
Operating System Platform: 64-bit
Application Platform: 64-bit
GPU Type: AMD Radeon RX 6600 XT
GPU Driver: 31.0.14051.5006 - C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository\u0391252.inf_amd64_b298c070ddf486e2\B391109\aticfx64.dll,C:\Windows\System32\DriverStore\FileRepository
GPU Driver Date: 20230420000000.000000-000
GPU Core Delta Freq: 0
GPU Memory Delta Freq: 0
GPU Voltage Delta Freq: 0
Physical Resolution: 1808x1017
Effective Resolution: 1808x1017
Display Mode: Windowed
Number of physical cores: 8
Logical core: 0 - phsyical mapping: 0 (group 0) - efficiency class: 0
Logical core: 1 - phsyical mapping: 0 (group 0) - efficiency class: 0
Logical core: 2 - phsyical mapping: 1 (group 0) - efficiency class: 0
Logical core: 3 - phsyical mapping: 1 (group 0) - efficiency class: 0
Logical core: 4 - phsyical mapping: 2 (group 0) - efficiency class: 0
Logical core: 5 - phsyical mapping: 2 (group 0) - efficiency class: 0
Logical core: 6 - phsyical mapping: 3 (group 0) - efficiency class: 0
Logical core: 7 - phsyical mapping: 3 (group 0) - efficiency class: 0
Logical core: 8 - phsyical mapping: 4 (group 0) - efficiency class: 0
Logical core: 9 - phsyical mapping: 4 (group 0) - efficiency class: 0
Logical core: 10 - phsyical mapping: 5 (group 0) - efficiency class: 0
Logical core: 11 - phsyical mapping: 5 (group 0) - efficiency class: 0
Logical core: 12 - phsyical mapping: 6 (group 0) - efficiency class: 0
Logical core: 13 - phsyical mapping: 6 (group 0) - efficiency class: 0
Logical core: 14 - phsyical mapping: 7 (group 0) - efficiency class: 0
Logical core: 15 - phsyical mapping: 7 (group 0) - efficiency class: 0
Total Memory: 32619 MBs
Available Memory: 26949 MBs
Total Page File: 37483 MBs
Avail Page File: 29013 MBs
GPU Memory: 4095 MBs
GPU Allocated Memory: 909 MBs
GPU Peak Memory: 1336 MBs
GPU Temp: 70 C
Have had 2 similar crashes to what the OP describes as of today. Playing a match and then suddenly -poof- the window closes as if I was never playing at all, no warning, no message, just closed and gone. This is very unusual for me, prior to today the game has crashed only rarely.
Went and updated my graphics driver and ran a scan and repair, then tried again. Completed 2 matches, then had a ‘standard’ crash at the end of the 2nd match as XP was counted for the pass, where it gave me a dialogue box to let me describe what I was doing before the game window closed and appeared in the crash log folder.
2 Likes
I added Overwatch and Battle.net directories to the Microsoft Windows Defender exception list - didn’t help.
Report ID from CrashReporter: 3A03F5C9-9F30-45C5-ACCC-611C37476DE4