PC Drivers & Software

Goodfella3 · ‎09-11-2022

Having an issue where, almost always (or always, I don't perfectly recall) during low load IE Webrowser usage, the screen will hang fully and I need to restart the computer to resume using the device. It is a FE RX480 8GB card that I have not OC'ed in anyway.

I have tried both the recent drivers as they got released, and the oldest one available on the site, 21.12.1. (if anyone knows how to get older RX 480 drivers than that, I'd appreciate it)

I have sent several 'Bug Reports' via AMD Bug Report tool to no avail, they are presumably being completly ignored.

* my CPU, i7 9700K has never got to 55ºC (that I have noticed)

* the GPU due to being a blower cooler system does get to 80ºC.

* Memtest shows no errors

* Fast Boot is disabled

* SSD is fine per Samsung's software

* ALL driver installs done via DDU in safemode, windows settting set to 'not update drivers automatically'

* I have tried setting the TdrDelay registry value to 10, no difference

* I am sometimes able to use my computer for DAYS at time without the issue presenting itself - then days like today it happens 2-3 times.

the text from the .dmp

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.)
Arguments:
Arg1: ffffd28a5036d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff806df56d010, 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.mSec
    Value: 1843

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3350

    Key  : Analysis.Init.CPU.mSec
    Value: 421

    Key  : Analysis.Init.Elapsed.mSec
    Value: 10573

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 96

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x141

    Key  : Bugcheck.Code.Register
    Value: 0x6822310

    Key  : Dump.Attributes.AsUlong
    Value: 18

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  WATCHDOG-20220911-1828.dmp

DUMP_FILE_ATTRIBUTES: 0x18
  Kernel Generated Triage Dump
  Live Generated Dump

BUGCHECK_CODE:  141

BUGCHECK_P1: ffffd28a5036d010

BUGCHECK_P2: fffff806df56d010

BUGCHECK_P3: 0

BUGCHECK_P4: 0

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffd28a5036d010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_NAME:  System

STACK_TEXT:  
fffff189`bb9d73d0 fffff805`445c0ea0     : ffffd28a`5036d010 fffff189`bb9d7640 00000000`00004840 ffffd28a`4f199370 : watchdog!WdpDbgCaptureTriageDump+0x64a
fffff189`bb9d7480 fffff805`44465eb9     : 00000000`00000000 00000000`00050216 00000000`00000001 ffffd28a`4d1f4000 : watchdog!WdDbgReportRecreate+0xd0
fffff189`bb9d74e0 fffff805`44464878     : ffffd28a`00000000 ffff9989`1e0be8d0 00000000`00000000 00000000`00004840 : dxgkrnl!TdrUpdateDbgReport+0x119
fffff189`bb9d7540 fffff805`4ec30e02     : ffffd28a`4bebd000 00000000`00000001 ffffd28a`5036d010 ffffd28a`4bebd000 : dxgkrnl!TdrCollectDbgInfoStage1+0x2d8
fffff189`bb9d7680 fffff805`4ecd12d5     : ffffd28a`4bebd000 00000000`00000000 ffffd28a`4d1f4000 ffffd28a`4bebd001 : dxgmms2!VidSchiResetEngine+0x312
fffff189`bb9d7830 fffff805`4eca60e3     : ffffd28a`4d1f4000 00000000`00000001 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xb1
fffff189`bb9d7880 fffff805`4ec81252     : fffff189`bb9d7901 00000000`001890c6 00000000`00989680 00000000`00000001 : dxgmms2!VidSchiCheckHwProgress+0x24e63
fffff189`bb9d78f0 fffff805`4ec0ba3a     : 00000000`00000000 ffffd28a`4d1f4000 fffff189`bb9d7a19 ffffd28a`4aca1010 : dxgmms2!VidSchiWaitForSchedulerEvents+0x372
fffff189`bb9d79c0 fffff805`4ec8d065     : ffffd28a`47dfb400 ffffd28a`4d1f4000 ffffd28a`47dfb4e0 ffffd28a`4bf55940 : dxgmms2!VidSchiScheduleCommandToRun+0x2ca
fffff189`bb9d7a80 fffff805`4ec8d01a     : ffffd28a`4d1f4400 fffff805`4ec8cf50 ffffd28a`4d1f4000 ffffaa01`1cde8100 : dxgmms2!VidSchiRun_PriorityTable+0x35
fffff189`bb9d7ad0 fffff805`39471d25     : ffffd28a`48e9d040 fffff805`00000001 ffffd28a`4d1f4000 00000000`00000000 : dxgmms2!VidSchiWorkerThread+0xca
fffff189`bb9d7b10 fffff805`39600628     : ffffaa01`1cde8180 ffffd28a`48e9d040 fffff805`39471cd0 00000000`00000246 : nt!PspSystemThreadStartup+0x55
fffff189`bb9d7b60 00000000`00000000     : fffff189`bb9d8000 fffff189`bb9d1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  amdkmdag+cd010

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
---------

Appreciate any assistance as AMD 'Bug Reports' appear to not be monitored. Thank you a lot for your time - cannot afford a new GPU (which wil be a device from the *other* company most likely) at this time, despite being a perpetual AMD / Radeon costumer.

Goodfella3 · ‎09-12-2022

No ideas? Unfortunate

Jonohue · ‎04-30-2023

Hey guys,

I'm having a fun issue where when playing World of Warcraft specifically, I will get crashes / Watchdog violations (code 141) where the monitor loses input and the machine actually times out and crashes, but recovers so quickly that it comes back on a few seconds later asking me to submit a bug report. When this happens it can take 5-10 seconds, but no longer. This is normally at random after playing World of Warcraft Retail 10.0.7 for "X" amount of time (could be 10m, could be 30m, could be 2h) - but it WILL happen. My graphics settings were all maxed (resolution, no framerate cap on foreground). Yesterday as you can see I spent all morning trying to figure it out by disabling ActiveSync, and figuring things out as I go, but it appears that one thing I found worked for me literally all day today.... For SOME REASON... I lowered the maximum framerate in the foreground in the WoW graphics settings to 120fps as it often is seen hitting 144 fps in certain areas - and this seems to have at least for the past 24 hours completely rid me of the Watchdog 141 errors that I was experiencing. I did also uninstall WoW and reinstall as I have many times, ALONG WITH BATTLE.NET CLIENT, but this is an issue that I've had for a LONG time, and it's always in this game and seemingly not in any others. Was wondering if anyone at AMD can take a look at at this and let me know if this would be something Blizzard needs to look at or if this is something that could be looked at in a driver update?

Specs:

AMD Ryzen 7 7700X CPU

G-Skill Trident 16GB RAM DIMM (x2) - NO OVERCLOCKING / XMP ENABLED

ASRock PG Lightning X670E Motherboard - Bios 1.11

AMD RX 7900 XTX 24GB GPU (Reference Card)

Gigabyte M32U 4K 144Hz Monitor w/ AMD FreeSync Premium Pro (ENABLED)

Windows 11 (latest Windows Updates)

AMD Adrenalin / Drivers 23.4.3 (UP TO DATE)

OS Name Microsoft Windows 11 Home
Version 10.0.22621 Build 22621

BIOS Version/Date American Megatrends International, LLC. 1.11, 10/21/2022
SMBIOS Version 3.4
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASRock
BaseBoard Product X670E PG Lightning
BaseBoard Version Default string
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Elevation Required to View
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1

Hardware Abstraction Layer Version = "10.0.22621.1413"

Time Zone Eastern Daylight Time

Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230429-0059.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff805`39a00000 PsLoadedModuleList = 0xfffff805`3a613490
Debug session time: Sat Apr 29 00:59:25.432 2023 (UTC - 4:00)
System Uptime: 0 days 12:56:11.045
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
watchdog!WdpDbgCaptureTriageDump+0xb7:
fffff805`6ae8396d 488b4628 mov rax,qword ptr [rsi+28h] ds:002b:ffffca8b`dde2cd38=????????????????
15: 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.)
Arguments:
Arg1: ffffca8bd8fee010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80583ff5400, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000009338, 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: 1062

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1587

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: 93

Key : Analysis.Init.Elapsed.mSec
Value: 5544

Key : Analysis.Memory.CommitPeak.Mb
Value: 113

Key : Bugcheck.Code.DumpHeader
Value: 0x141

Key : Bugcheck.Code.Register
Value: 0xb96ad8a0

Key : Dump.Attributes.AsUlong
Value: 18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

FILE_IN_CAB: WATCHDOG-20230429-0059.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 141

BUGCHECK_P1: ffffca8bd8fee010

BUGCHECK_P2: fffff80583ff5400

BUGCHECK_P3: 0

BUGCHECK_P4: 9338

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffca8bd8fee010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000009338

PROCESS_NAME: System

STACK_TEXT:
ffffb107`f0646f90 fffff805`6ae98f24 : ffffca8b`bb318030 ffffca8b`bb318030 ffffca8b`dde2cd10 ffffca8b`d8fee010 : watchdog!WdpDbgCaptureTriageDump+0xb7
ffffb107`f0647000 fffff805`6acfd1ad : ffffca8b`d8fee010 ffffb107`f06471c0 00000000`00000000 fffff805`9abe6459 : watchdog!WdDbgReportRecreate+0xd4
ffffb107`f0647060 fffff805`9ab1c03b : ffffca8b`00000000 ffffca8b`cdebebd0 ffffca8b`d8fee010 ffffca8b`cdee3000 : dxgkrnl!TdrUpdateDbgReport+0x11d
ffffb107`f06470c0 fffff805`9abe67c9 : ffffca8b`cdee3000 00000000`00000000 ffffca8b`cdebe000 ffffca8b`cdee3001 : dxgmms2!VidSchiResetEngine+0x70f
ffffb107`f0647270 fffff805`9abb643b : ffffca8b`cdebe000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xb1
ffffb107`f06472c0 fffff805`9ab88c3f : 00000000`00000000 00000000`00000000 00000000`002d79a6 00000000`00989680 : dxgmms2!VidSchiCheckHwProgress+0x2d7bb
ffffb107`f0647340 fffff805`9aaeb669 : 00000000`00000002 ffffca8b`cdebe000 ffffb107`f0647479 00000000`00000002 : dxgmms2!VidSchiWaitForSchedulerEvents+0x37f
ffffb107`f0647410 fffff805`9ab94a75 : ffffca8b`d79d9800 ffffca8b`cdebe000 ffffca8b`d79d9880 ffffca8b`d1895050 : dxgmms2!VidSchiScheduleCommandToRun+0x309
ffffb107`f06474e0 fffff805`9ab949ea : 00000000`00000000 fffff805`9ab94920 ffffca8b`cdebe000 00000000`00000080 : dxgmms2!VidSchiRun_PriorityTable+0x35
ffffb107`f0647530 fffff805`39c0dc67 : ffffca8b`cd2842c0 fffff805`00000001 ffffca8b`cdebe000 005fe07f`bcbbbdff : dxgmms2!VidSchiWorkerThread+0xca
ffffb107`f0647570 fffff805`39e30854 : ffffb801`2aae2180 ffffca8b`cd2842c0 fffff805`39c0dc10 1de8d233`c68b4500 : nt!PspSystemThreadStartup+0x57
ffffb107`f06475c0 00000000`00000000 : ffffb107`f0648000 ffffb107`f0641000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34

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
---------

PC Drivers & Software

'Unable to load image amdkmdag.sys, Win32 error 0n2'