OW2 Crashing mid game randomly after multiple hours playing

Technical Support
1

I just recently built a new PC with a 7800x3d, and used my 2080 super for some time without issue. I recently purchased a PNY Triple Fan Verto 4090 and installed it. Played it last week without issue. Please it this week and it seems randomly after a few hours of gaming in overwatch specifically i’m getting application hangs. My drivers were all upgraded after build of the new PC. The game will just lock and i have to end task on it. The last time it happened after another 3-4 hours gaming session I end task had no effect and the exe would just sit there. I just went through a ddu graphics uninstall and reinstalled nvidia and updated graphics again so I’m monitoring but was wondering if anyone has any clue here.

Here is the DXDIAG output. I went into event viewer and couldn’t find much around the same time. I ran a crash program and there’s no dump files that I could dissect so it’s not like the PC is bsodding. I ran hwfinfo and all my temps are within spec with hottest the 4090 is getting being 68c. 7800x3d got to 80 as a max temp. Not seeing anything standing out as to what’s causing this. Have an 850w recommended psu and am not seeing the system exceed power usage.

I tried to attach a dx diag but the characters are too many. Here’s the end of the diag.

EVR Power Information
---------------
Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality) 
  Quality Flags: 2576
    Enabled:
    Force throttling
    Allow half deinterlace
    Allow scaling
    Decode Power Usage: 100
  Balanced Flags: 1424
    Enabled:
    Force throttling
    Allow batching
    Force half deinterlace
    Force scaling
    Decode Power Usage: 50
  PowerFlags: 1424
    Enabled:
    Force throttling
    Allow batching
    Force half deinterlace
    Force scaling
    Decode Power Usage: 0

---------------
Diagnostics
---------------

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

Problem signature:
P1: MicrosoftTeams_23216.905.2334.6698_x64__8wekyb3d8bbwe
P2: praid:msteamsupdate
P3: 23216.905.2334.6698
P4: 64e799a8
P5: ucrtbase.dll
P6: 10.0.22621.608
P7: f5fc15a3
P8: 000000000007f61e
P9: c0000409
P10: 0000000000000007


+++ WER1 +++:
Fault bucket LKD_0x193_DxgkrnlLiveDump:810__dxgkrnl!DxgkProcessCallout_dxgkrnl!DXGDEVICE::FlushDeferredDestruction_nt!KeWaitForSingleObject_dxgkrnl!DXGDEVICE::FlushDeferredDestruction, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: c3ff2091-b96a-41d1-b6c8-fd842bb6c3bb

Problem signature:
P1: 193
P2: 810
P3: ffffd18feeef0000
P4: ffffd18ffae9c080
P5: 339
P6: 10_0_22621
P7: 0_0
P8: 256_1
P9: 
P10: 


+++ WER2 +++:
Fault bucket 1510325945516945196, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Overwatch.exe
P2: 2.6.0.50734
P3: 64ded186
P4: 5231
P5: 67246080
P6: 
P7: 
P8: 
P9: 
P10: 


+++ WER3 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Overwatch.exe
P2: 2.6.0.50734
P3: 64ded186
P4: 5231
P5: 67246080
P6: 
P7: 
P8: 
P9: 
P10: 


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

Problem signature:
P1: MicrosoftTeams_23216.905.2334.6698_x64__8wekyb3d8bbwe
P2: praid:msteamsupdate
P3: 23216.905.2334.6698
P4: 64e799a8
P5: ucrtbase.dll
P6: 10.0.22621.608
P7: f5fc15a3
P8: 000000000007f61e
P9: c0000409
P10: 0000000000000007


+++ WER5 +++:
Fault bucket 1510325945516945196, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Overwatch.exe
P2: 2.6.0.50734
P3: 64ded186
P4: 5231
P5: 67246080
P6: 
P7: 
P8: 
P9: 
P10: 


+++ WER6 +++:
Fault bucket , type 0
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: Overwatch.exe
P2: 2.6.0.50734
P3: 64ded186
P4: 5231
P5: 67246080
P6: 
P7: 
P8: 
P9: 
P10: 


+++ WER7 +++:
Fault bucket 1738052624331859758, type 5
Event Name: MoBEX
Response: Not available
Cab Id: 0

Problem signature:
P1: MicrosoftTeams_23216.905.2334.6698_x64__8wekyb3d8bbwe
P2: praid:msteamsupdate
P3: 23216.905.2334.6698
P4: 64e799a8
P5: ucrtbase.dll
P6: 10.0.22621.608
P7: f5fc15a3
P8: 000000000007f61e
P9: c0000409
P10: 0000000000000007


+++ WER8 +++:
Fault bucket 2278248362683513654, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: NVDisplay.Container.exe
P2: 1.37.3103.4323
P3: 621dbda6
P4: nvxdapix.dll
P5: 8.17.15.3699
P6: 64cd7686
P7: c0000005
P8: 000000000042430d
P9: 
P10: 


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

Problem signature:
P1: Update;ScanForUpdates
P2: 80240024
P3: 22621
P4: 2134
P5: Windows.Desktop
P6: H
P7: 
P8: 
P9: 
P10:


Here's a few event logs errors I found.

Faulting application name: msteamsupdate.exe, version: 23216.905.2334.6698, time stamp: 0x64e799a8
Faulting module name: ucrtbase.dll, version: 10.0.22621.608, time stamp: 0xf5fc15a3
Exception code: 0xc0000409
Fault offset: 0x000000000007f61e
Faulting process id: 0x0x1DD8
Faulting application start time: 0x0x1D9D97F0BB1692D
Faulting application path: C:\Program Files\WindowsApps\MicrosoftTeams_23216.905.2334.6698_x64__8wekyb3d8bbwe\msteamsupdate.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 6775dc49-f200-4d0d-9cf3-6f7ea34e0846
Faulting package full name: MicrosoftTeams_23216.905.2334.6698_x64__8wekyb3d8bbwe
Faulting package-relative application ID: msteamsupdate

Faulting application name: msteamsupdate.exe, version: 23216.905.2334.6698, time stamp: 0x64e799a8
Faulting module name: ucrtbase.dll, version: 10.0.22621.608, time stamp: 0xf5fc15a3
Exception code: 0xc0000409
Fault offset: 0x000000000007f61e
Faulting process id: 0x0x68E0
Faulting application start time: 0x0x1D9D9775B34CA86
Faulting application path: C:\Program Files\WindowsApps\MicrosoftTeams_23216.905.2334.6698_x64__8wekyb3d8bbwe\msteamsupdate.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: c5d41aef-0a65-42c0-9b0b-f32ef444f1da
Faulting package full name: MicrosoftTeams_23216.905.2334.6698_x64__8wekyb3d8bbwe
Faulting package-relative application ID: msteamsupdate



The program Overwatch.exe version 2.6.0.50734 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.


Faulting application name: NVDisplay.Container.exe, version: 1.37.3103.4323, time stamp: 0x621dbda6
Faulting module name: nvxdapix.dll, version: 8.17.15.3699, time stamp: 0x64cd7686
Exception code: 0xc0000005
Fault offset: 0x000000000042430d
Faulting process id: 0x0xCBC
Faulting application start time: 0x0x1D9D7A4C82A1AB4
Faulting application path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1ddf203f8d876fdf\Display.NvContainer\NVDisplay.Container.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_1ddf203f8d876fdf\nvxdapix.dll
Report Id: 8e1ad691-700d-4afc-9726-ca6478b17794
Faulting package full name: 
Faulting package-relative application ID:
2

Howdy Oceans,

It looks like something may be causing a conflict with the Nvidia drivers or graphics while the game is running. To help narrow down the cause, we should try disabling all other programs temporarily so we can test the game by itself.

If this persists, let’s get a new DxDiag:

  1. Press Windows Key + R.
  2. Type DxDiag and press Enter.
  3. In the DxDiag window, click Save All Information.
  4. Name the file “dxdiag” and click Save
  5. Paste the DXdiag into the post, select and highlight everything you just pasted, and hit the “preformatted text” button (</>). That’ll make the information much more readable.
It should look like this.

If you have issues pasting here, please use Pastebin and post the link then highlight the link and press the ˂/˃ button.

3

I had the same issue again tonight after disabling start up items.

Game hard locks frozen on the game, but sound just repeats. Immediately after while it was still locked I launcehd call of duty to see if it would launch and play and it did so it seems my GPU was still functioning. Temps on my system were normal as well. Voltages good in hwinfo

4

Howdy Oceans,

I didn’t see any obvious cause for OW2 crashing in the system file. It’s possible that security software like an anti-virus program may be blocking OW2 specifically. I’d suggest making sure that the game is allowed as exclusion in that software if you have any installed.

If that doesn’t help, I’d suggest trying the advanced steps listed here, such as disabling overclocking as well as the memory and harddrive tests.

5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.