Microsoft Q&A tells me to go to AMD, AMD Community tells me to go to Microsoft.
PC - Custom Built
MoBo - Gigabyte Aorus Gaming 5 WiFi x470 AM4
CPU - AMD Ryzen 7 2700x w/ CoolerMaster 240mm closed-loop liquid cooler
GPU - Asus Arez AMD Radeon RX Vega 64
Memory - G.Skill TridentZ RGB 32GB 4x8GB 3200 - BRAND NEW NO FIX (replaced memory of same model in fix attempt)
PSU - Corsair SF750 - BRAND NEW NO FIX (replaced Corsair AX1200i in fix attempt)
Seemingly random crash while gaming. Doesn't matter which game: Destiny 2, RDR2, KSP, BF, CoD, etc. For some reason it doesn't apply to PCMark10 or 3DMark, completed both full benchmarks with no issues. No BSOD, no reboot, just complete flatline. The screen goes black and the fans throttle to 100%. I have to hold the power button until the fans stop then power it back on. No overheating. No overclocking. I've tried DDU and install drivers I know work. I've completely reset windows and formated the drives. I've replaced the RAM (MemTest yeilded no errors) and the PSU, even though the old ones tested fine, to no avail.
- System
[ Name] Microsoft-Windows-Kernel-Power
[ Guid] {331c3b3a-2005-44c2-ac5e-77220c37d6b4} EventID 41 Version 8 Level 1 Task 63 Opcode 0 Keywords 0x8000400000000002
[ SystemTime] 2021-04-02T03:31:48.9117797Z EventRecordID 1145 Correlation
[ ProcessID] 4
[ ThreadID] 8 Channel System Computer DESKTOP-MH3KDNO
[ UserID] S-1-5-18
- EventData BugcheckCode 0
BugcheckParameter1 0x0
BugcheckParameter2 0x0
BugcheckParameter3 0x0
BugcheckParameter4 0x0
SleepInProgress 0
PowerButtonTimestamp 0
BootAppStatus 0
Checkpoint 0
ConnectedStandbyInProgress false
SystemSleepTransitionsToOn 0
CsEntryScenarioInstanceId 0
BugcheckInfoFromEFI false
CheckpointStatus 0
CsEntryScenarioInstanceIdV2 0
LongPowerButtonPressDetected false
WinDiag WATCHDOG .dmp Analysis
Microsoft (R) Windows Debugger Version 10.0.19041.685 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20210401-2331.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19042 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff8062ac00000 PsLoadedModuleList = 0xfffff806
2b82a490
Debug session time: Thu Apr 1 23:31:05.195 2021 (UTC - 4:00)
System Uptime: 0 days 2:52:02.844
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
14: kd> !analyze -v
VIDEO_ENGINE_TIMEOUT_DETECTED (141)
One of the the display engines failed to respond in timely fashion.
(This code can never be used for a real bugcheck.)
Arguments:
Arg1: ffffdf88921d5050, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8063f1edac0, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, 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.Sec
Value: 2
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-MH3KDNO
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.Sec
Value: 9
Key : Analysis.Memory.CommitPeak.Mb
Value: 87
Key : Analysis.System
Value: CreateObject
DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump
BUGCHECK_CODE: 141
BUGCHECK_P1: ffffdf88921d5050
BUGCHECK_P2: fffff8063f1edac0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
PROCESS_NAME: System
STACK_TEXT:
ffff888d84b384d0 fffff806
37a50ea0 : ffffdf88921d5050 ffff888d
84b38740 0000000000004840 ffffdf88
8e465d10 : watchdog!WdpDbgCaptureTriageDump+0x64a
ffff888d84b38580 fffff806
378f1d69 : 0000000000000000 00000000
00050216 0000000000000001 ffffdf88
88da0000 : watchdog!WdDbgReportRecreate+0xd0
ffff888d84b385e0 fffff806
378f0728 : ffffdf8800000000 ffffb600
c20cf900 0000000000000000 00000000
00004840 : dxgkrnl!TdrUpdateDbgReport+0x119
ffff888d84b38640 fffff806
37410ff2 : ffffdf8888e7d000 00000000
00000001 ffffdf88921d5050 ffffdf88
88e7d000 : dxgkrnl!TdrCollectDbgInfoStage1+0x2d8
ffff888d84b38780 fffff806
374b17e5 : ffffdf8888e7d000 00000000
00000000 ffffdf8888da0000 ffffdf88
88e7d001 : dxgmms2!VidSchiResetEngine+0x312
ffff888d84b38930 fffff806
3748528d : ffffdf8888da0000 00000000
00000001 0000000000000000 00000000
00000000 : dxgmms2!VidSchiResetEngines+0xb1
ffff888d84b38980 fffff806
3745f202 : ffff888d84b38a01 00000000
000a142d 0000000000989680 00000000
00000001 : dxgmms2!VidSchiCheckHwProgress+0x2605d
ffff888d84b389f0 fffff806
373ea8ea : ffffdf88884dcbf0 ffffdf88
88da0000 ffff888d84b38b19 00000000
00989680 : dxgmms2!VidSchiWaitForSchedulerEvents+0x372
ffff888d84b38ac0 fffff806
3746d2e5 : ffffdf888f043000 ffffdf88
88da0000 ffffdf888f043010 ffffdf88
8f74f5e0 : dxgmms2!VidSchiScheduleCommandToRun+0x2ca
ffff888d84b38b80 fffff806
3746d29a : ffffdf8888da0400 fffff806
3746d1d0 ffffdf8888da0000 ffffcd01
4f763100 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffff888d84b38bd0 fffff806
2af17e85 : ffffdf8888df5280 fffff806
00000001 ffffdf8888da0000 000f8067
b4bbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffff888d84b38c10 fffff806
2affd408 : ffffcd014f763180 ffffdf88
88df5280 fffff8062af17e30 00000011
00000000 : nt!PspSystemThreadStartup+0x55
ffff888d84b38c60 00000000
00000000 : ffff888d84b39000 ffff888d
84b33000 0000000000000000 00000000
00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: amdkmdag+adac0
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
STACK_COMMAND: .thread ; .cxr ; 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