Two months ago I first posted on this forum regarding my RX 5700 XT (The Post), a nice guy helped me giving me further information on my GPU and as to why it may be crashing; he told me that the GPU is highly OC'ed by defaulted cause AMD tried to compete with NVIDIA with this release. So I lowered both the voltage and frequency down and it seemed to stabilise my GPU for about 2/3 weeks and then all of a sudden it went mad again and started crashing. ATP I assume my GPU just doesn't like me as I've had it for like 3 years and it's been crashing since the day it came, every day. I've tried to tweak around it every time it crashed to see if I can find a sweet spot with the voltage and frequency but to no help.
That's why I'm writing here again, I'm not sure what info to include that any tech guy could help me with though I did include some in my first post, but if you need any additional software/hardware info please write down below and I will provide it if you're willing to help me with these crashes.
One thing I can add is that I've found the crash logs and they're all regarding the same error.
VIDEO_ENGINE_TIMEOUT_DETECTED (141)
Here's the full report:
*******************************************************************************
* *
* 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: ffff978c508f3460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80352d55400, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000005a00, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2733
Key : Analysis.Elapsed.mSec
Value: 4609
Key : Analysis.IO.Other.Mb
Value: 20
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 27
Key : Analysis.Init.CPU.mSec
Value: 656
Key : Analysis.Init.Elapsed.mSec
Value: 71870
Key : Analysis.Memory.CommitPeak.Mb
Value: 97
Key : Bugcheck.Code.LegacyAPI
Value: 0x141
Key : Dump.Attributes.AsUlong
Value: 18
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: LKD_0x141_IMAGE_amdkmdag.sys
Key : Failure.Hash
Value: {48b738dd-5a92-7ff8-63d0-f075fc680fe0}
BUGCHECK_CODE: 141
BUGCHECK_P1: ffff978c508f3460
BUGCHECK_P2: fffff80352d55400
BUGCHECK_P3: 0
BUGCHECK_P4: 5a00
FILE_IN_CAB: WATCHDOG-20230515-0016.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 ffff978c508f3460
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000005a00
PROCESS_NAME: System
STACK_TEXT:
ffffc007`4d4e75d0 fffff803`40950ea0 : ffff978c`508f3460 ffffc007`4d4e7840 ffff978c`508f3460 ffff978c`51411a70 : watchdog!WdpDbgCaptureTriageDump+0x64a
ffffc007`4d4e7680 fffff803`407f60e9 : 00000000`0000000c 00000000`00000000 ffff978c`4b143000 ffff978c`00000001 : watchdog!WdDbgReportRecreate+0xd0
ffffc007`4d4e76e0 fffff803`660510b9 : ffff978c`00000000 ffff978c`53ccd500 ffff978c`508f3460 ffff978c`4b192000 : dxgkrnl!TdrUpdateDbgReport+0x119
ffffc007`4d4e7740 fffff803`660f11c5 : ffff978c`4b192000 00000000`00000000 ffff978c`4b145000 ffff978c`4b192001 : dxgmms2!VidSchiResetEngine+0x709
ffffc007`4d4e78f0 fffff803`660bb24f : ffff978c`4b145000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xb1
ffffc007`4d4e7940 fffff803`66088142 : ffffc007`4d4e7a01 00000000`0082f0c1 00000000`00989680 00000000`00000001 : dxgmms2!VidSchiCheckHwProgress+0x330df
ffffc007`4d4e79b0 fffff803`6602a11a : ffff978c`5104cb00 ffff978c`4b145000 ffffc007`4d4e7ad9 00000000`00989680 : dxgmms2!VidSchiWaitForSchedulerEvents+0x372
ffffc007`4d4e7a80 fffff803`660ad405 : ffff978c`501f6a00 ffff978c`4b145000 ffff978c`501f6a20 ffff978c`4b16b690 : dxgmms2!VidSchiScheduleCommandToRun+0x2ca
ffffc007`4d4e7b40 fffff803`660ad3ba : ffff978c`4b145400 fffff803`660ad2f0 ffff978c`4b145000 ffffd600`698ea100 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffc007`4d4e7b90 fffff803`301265f5 : ffff978c`469333c0 fffff803`00000001 ffff978c`4b145000 000fe067`bcbbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffc007`4d4e7bd0 fffff803`302048d8 : ffffd600`698ea180 ffff978c`469333c0 fffff803`301265a0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffffc007`4d4e7c20 00000000`00000000 : ffffc007`4d4e8000 ffffc007`4d4e1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: amdkmdag+f5400
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: LKD_0x141_IMAGE_amdkmdag.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {48b738dd-5a92-7ff8-63d0-f075fc680fe0}
Followup: MachineOwner
---------
