search

IGCIT / Intel-GPU-Community-Issue-Tracker-IGCIT

IGCIT is a Community-driven issue tracker for Intel GPUs.
GNU General Public License v3.0
112 stars 3 forks source link

[Overwatch 2] Frequent "rendering device lost" crashes with driver 5186-5382 #757

Closed zp closed 2 months ago

zp commented 2 months ago

Checklist [README]

Game [Required]

Overwatch 2

Game Platform [Required]

Other game platform

No response

Processor / Processor Number [Required]

AMD Ryzen 5900X

Graphic Card [Required]

Arc A770 16GB (ASRock Phantom Gaming)

GPU Driver Version [Required]

31.0.101.5382

Other GPU Driver version

No response

Rendering API [Required]

Windows Build Number [Required]

Other Windows build number

No response

Intel System Support Utility report

igcit_ssu.txt

Description and steps to reproduce [Required]

With the following driver versions, the game will randomly but frequently crash with a "Your rendering device has been lost" error message. For me it most frequently crashes when loading a level/map (I just constantly join/left/rejoined the practice lobby as method of testing) but will also randomly crash during gameplay.

Those are just the version I've checked, but I assume it's just anything starting with 5186 or newer

https://github.com/IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT/assets/170573/43e15d4d-c1a1-4d50-9162-9816a926a382

The last known 'good' driver for me is 31.0.101.5085, I have probably ~20 hours recently on that driver with 0 crashes, 31.0.101.5186 and above will crash within 5-10 minutes.

List of things I've tried

The crash still occurs on all of those configurations.

It seems something got changed between driver 5085 and 5186 that is affecting my setup somehow, as I've seen other people on the Arc subreddit posting videos of them testing Overwatch 2 recently with seemingly no issues using driver 31.0.101.5333 (https://www.youtube.com/watch?v=y4zk-Cyjg04)

gpu-z info just for good measure arcgpuz

Game graphic quality [Required]

Game resolution [Required]

1920x1080

Game VSync [Required]

Off

Game display mode [Required]

Detailed game settings [Required]

video

graphics

Device / Platform name

No response

Crash dumps [Required, if applicable]

No response

Save game

No response

zp commented 2 months ago

Enabled getting dump files as noted here and was able to get something that hopefully helps diagnose

edit: captured on driver 31.0.101.5382

WATCHDOG-20240410-1734.dmp

dump log (click to expand) ``` ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToV8JsProvider : false -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.031 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 41 Microsoft (R) Windows Debugger Version 10.0.27553.1004 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20240410-1734.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv*https://msdl.microsoft.com/download/symbols Symbol search path is: srv*https://msdl.microsoft.com/download/symbols Executable search path is: Windows 10 Kernel Version 26100 MP (24 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff804`cc200000 PsLoadedModuleList = 0xfffff804`cd0f4420 Debug session time: Wed Apr 10 17:34:42.005 2024 (UTC - 5:00) System Uptime: 0 days 0:05:50.626 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ........ Loading User Symbols Mini Kernel Dump does not contain unloaded driver list For analysis of this file, run !analyze -v nt!DbgkpWerCaptureLiveTriageDump+0x8e: fffff804`cc8b616e 488b8788000000 mov rax,qword ptr [rdi+88h] ds:002b:ffff9b04`61c930c8=???????????????? 5: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_ENGINE_TIMEOUT_DETECTED (141) One of the display engines failed to respond in timely fashion. (This code can never be used for a real BugCheck; it is used to identify live dumps.) Arguments: Arg1: ffffd38f6765f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: fffff8046c086f00, The pointer into responsible device driver module (e.g. owner tag). Arg3: 0000000000000000, The secondary driver specific bucketing key. Arg4: ffffd38f6788e080, Optional internal context dependent data. Debugging Details: ------------------ Unable to load image igdkmdnd64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for igdkmdnd64.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1812 Key : Analysis.Elapsed.mSec Value: 2105 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 327 Key : Analysis.Init.Elapsed.mSec Value: 3969 Key : Analysis.Memory.CommitPeak.Mb Value: 102 Key : Bugcheck.Code.LegacyAPI Value: 0x141 Key : Bugcheck.Code.TargetModel Value: 0x141 Key : Dump.Attributes.AsUlong Value: 18 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Failure.Bucket Value: LKD_0x141_IMAGE_igdkmdnd64.sys Key : Failure.Hash Value: {02a74750-0720-371b-c596-ab42d088df21} BUGCHECK_CODE: 141 BUGCHECK_P1: ffffd38f6765f010 BUGCHECK_P2: fffff8046c086f00 BUGCHECK_P3: 0 BUGCHECK_P4: ffffd38f6788e080 FILE_IN_CAB: WATCHDOG-20240410-1734.dmp DUMP_FILE_ATTRIBUTES: 0x18 Kernel Generated Triage Dump Live Generated Dump TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd38f6765f010 Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found. PROCESS_OBJECT: ffffd38f6788e080 PROCESS_NAME: System STACK_TEXT: fffff98b`4dd3ef30 fffff804`cc8b6679 : ffffd38f`6765f010 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e fffff98b`4dd3f460 fffff804`ccc66f4a : 00000000`00000000 00000000`00000000 fffff804`ccc857c0 00000000`c0000022 : nt!DbgkpWerProcessPolicyResult+0x21 fffff98b`4dd3f490 fffff804`ccc66d49 : 00000000`00000003 fffff98b`4dd3f670 ffffd38f`6765f010 ffffd38f`6bb09b70 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea fffff98b`4dd3f4f0 fffff804`5f32e959 : ffff9b04`61bac700 ffff9b04`61bac700 ffff9b04`681e9b4e ffffd38f`6765f010 : nt!DbgkWerCaptureLiveKernelDump+0x69 fffff98b`4dd3f570 fffff804`6fe3a012 : 00000000`d0982ae5 00000000`00000006 ffffd38f`63374000 ffffd38f`63303000 : dxgkrnl!TdrCollectDbgInfoStage1+0xd69 fffff98b`4dd3f730 fffff804`6fe96ec6 : ffffd38f`63374000 ffffd38f`63374000 ffffd38f`63303000 00000000`00000000 : dxgmms2!VidSchiResetEngine+0x37a fffff98b`4dd3f920 fffff804`6fe9bfc6 : fffff780`00000000 ffffd38f`63303000 fffff98b`4dd3fab9 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xea fffff98b`4dd3f970 fffff804`6fdfc6e4 : ffffd38f`63303000 00000000`00000000 fffff98b`4dd3fab9 00000000`00005761 : dxgmms2!VidSchiCheckHwProgress+0x316 fffff98b`4dd3fa00 fffff804`6fe9c982 : ffffd38f`63303000 fffff98b`4dd3fb70 ffffd38f`69d95000 ffffd38f`63303000 : dxgmms2!VidSchiScheduleCommandToRun+0x64 fffff98b`4dd3fb20 fffff804`6fe9705c : ffffd38f`63303500 ffffd38f`63303000 fffff804`6fe96f80 ffffd38f`63303000 : dxgmms2!VidSchiRun_PriorityTable+0x42 fffff98b`4dd3fb70 fffff804`cc61d24a : ffffd38f`63379180 fffff804`00000001 ffffbf81`b83c7180 024fe07f`b4bbbdff : dxgmms2!VidSchiWorkerThread+0xdc fffff98b`4dd3fbb0 fffff804`cc85c664 : ffffbf81`b83c7180 ffffd38f`63379180 fffff804`cc61d1f0 006c0069`00770020 : nt!PspSystemThreadStartup+0x5a fffff98b`4dd3fc00 00000000`00000000 : fffff98b`4dd40000 fffff98b`4dd39000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34 SYMBOL_NAME: igdkmdnd64+16f00 MODULE_NAME: igdkmdnd64 IMAGE_NAME: igdkmdnd64.sys STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: LKD_0x141_IMAGE_igdkmdnd64.sys OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {02a74750-0720-371b-c596-ab42d088df21} Followup: MachineOwner --------- ```
zp commented 2 months ago

Latest Overwatch 2 patch (2.10.0.0.124591) seems to have fixed the crash issue on driver(s) 5186+

So far I've played a few hours on driver 5382 with no random renderer crashes.

Will go ahead and close for now, and reopen if I experience it again.