Drivers & Software

sofanta · ‎03-08-2023

When playing a game with AdaptiveSyncCompatible enabled, either a driver crash, BSoD, or game crash occurs.

This bug has been reported several times in the bug report tool since shortly after the release of the 7900XTX, but it still has not been treated as a known issue.
I tried again because a similar bug was fixed in 23.3.1, but it does not seem to be fixed in AW2721D+7900XTX.

PC Setup:

Driver: 23.3.1

OS: Windows 11 22H2, Build 22621.1265

CPU: AMD Ryzen 9 7950X3D 16-Core Processor

GPU: Sapphire R9 7900 XTX (MBA)

MB: Biostar X670E VALKYRIE

RAM: F5-5600J3036D16GX2-FX5

Monitor: Alienware AW2721D (G-Sync Ultimate) with DP 2560*1440@240hz@8bit

Jonohue · ‎04-25-2023

That is the first driver version that I actually used (along with 22.11.1 actually).

That was the version I was using when I had the card in December 2022 and what prompted me to hope this would eventually one day be solved.

The AMD folder would be wiped by this time as I've since completely reformatted my SSD containing the OS and everything else and reinstalled Windows fresh, and fresh installed drivers back around a few releases ago.

Jonohue · ‎04-28-2023

I’m getting a ton of VIDEO_ENGINE_STOPPED errors from Watchdog along with Windows LiveKernel events (141) in my event viewer when playing World of Warcraft. I play MANY MANY games on my 7900 XTX at the latest driver version, but only World of Warcraft retail specifically causes the TDR Watchdog (code 141) driver timeouts. I noticed oddly too that when WoW is playing and I am running into the driver timeout and the screen goes blank and comes back on that the game is still running and the bug report tool is running, as is all other software in the system tray. However, when you go to left click on Discord in the system tray, it disappears and is no longer running.

Very odd case for sure, and currently I am testing turning AMD FreeSync Premium Pro completely off on my monitor itself which is Gigabyte M32U 144Hz.

i am running and stressing the game currently with the setting off completely on my monitor for a few hours (would normally force a TDR timeout multiple times in this time window) and will report back.

I can provide memory dumps as well if needed.

Jonohue · ‎04-28-2023

I am replying back as I just played the exact same game after making the change to turn AMD FreeSync Premium Pro off on the MONITOR ITSELF (thus also toggling it off / showing it not available anymore within the Radeon software).

I also attempted to reproduce the issue by alt-tabbing with Edge open (with hardware acceleration enabled, Discord on and hardware acceleration, etc) - things that have all contributed in my opinion to the demise of the game and resulting in driver timeouts in the past.

HOWEVER - I just spent the last two to two and a half HOURS playing without a single driver timeout error or any Watchdog error of any kind after turning off AMD FreeSync Premium Pro.

My monitor model is Gigabyte M32U - the resolution in game is set at 3860x2140, and I have the frame-rate capped at 144 fps.

Below is the content of my most recent crash from today, BEFORE I turned AMD FreeSync Premium Pro off:

Fault bucket LKD_0x141_Tdr:6_IMAGE_amdkmdag.sys-SCH, type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: cee690fe-db3d-404d-9218-a11553b8e67c

Problem signature:
P1: 141
P2: ffffca8bdbebc460
P3: fffff80583ff5400
P4: 0
P5: 1464
P6: 10_0_22621
P7: 0_0
P8: 768_1
P9:
P10:

Attached files:
\\?\C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230428-1508.dmp
\\?\C:\Windows\SystemTemp\WER-11131281-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f3e498dd-8262-4197-acd1-edfb6e151377.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.c40b65da-845b-44e8-befc-6621a891a412.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.34e4eb94-0ffd-4b7d-95b5-8014b0447b5b.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.b2947ca1-92bb-4d7c-af2b-b5b9fe80f94f.tmp.xml
\\?\C:\Windows\SystemTemp\WER.13c54a0f-792e-4c6f-b040-5676ed7b3bcb.tmp.WERDataCollectionStatus.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_686ba245756e79f94d9565625296f5465fdd7_00000000_cab_9b0e26d0-14e2-490f-bde7-119cbddb973b

Analysis symbol:
Rechecking for solution: 0
Report Id: 9b0e26d0-14e2-490f-bde7-119cbddb973b
Report Status: 268435460
Hashed bucket:
Cab Guid: 0

MORE INFORMATION:

Loading Dump File [C:\Windows\LiveKernelReports\WATCHDOG\WATCHDOG-20230428-1508.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: Fri Apr 28 15:08:45.613 2023 (UTC - 4:00)
System Uptime: 0 days 3:05:31.225
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`d00edd38=????????????????
11: 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: ffffca8bdbebc460, 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: 0000000000001464, 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: 921

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 1573

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x141

Key : Bugcheck.Code.Register
Value: 0x92d9fae0

Key : Dump.Attributes.AsUlong
Value: 18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

FILE_IN_CAB: WATCHDOG-20230428-1508.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 141

BUGCHECK_P1: ffffca8bdbebc460

BUGCHECK_P2: fffff80583ff5400

BUGCHECK_P3: 0

BUGCHECK_P4: 1464

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

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

PROCESS_OBJECT: 0000000000001464

PROCESS_NAME: System

STACK_TEXT:
ffffb107`f0646f90 fffff805`6ae98f24 : ffffca8b`bb318030 ffffca8b`bb318030 ffffca8b`d00edd10 ffffca8b`dbebc460 : watchdog!WdpDbgCaptureTriageDump+0xb7
ffffb107`f0647000 fffff805`6acfd1ad : ffffca8b`dbebc460 ffffb107`f06471c0 00000000`00000000 fffff805`9abe6459 : watchdog!WdDbgReportRecreate+0xd4
ffffb107`f0647060 fffff805`9ab1c03b : ffffca8b`00000000 ffffca8b`cdebebd0 ffffca8b`dbebc460 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`000addac 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`bb152800 ffffca8b`cdebe000 ffffca8b`bb152850 ffffca8b`cdf1e820 : 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
---------

NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis'
NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2210.3001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Usb4Kd.natvis'

Jonohue · ‎04-29-2023

Unfortunately for me, yesterday while playing World of Warcraft, the driver timeout error ended up happening even without AMD FreeSync Premium Pro enabled or on. I still ended up getting a 141 error similar to the one above. I completely reinstalled WoW haphazardly this morning to see if this helps. If it doesn’t, it looks like I’m off to DDU and repair Windows again potentially.

I tried Direct X version 11 instead of 12 for API in WoW yesterday as well, same thing, driver timeout errors occur.

What can I do to combat this?

Jonathan

Qoojo · ‎04-29-2023

I would suggest starting a new thread because your issue is not the same issue, especially if you can run at all with freesync enabled.

stan · ‎04-30-2023

Yes, this is different issue.

Just like Qoojo said, start a new thread to describe your problem.

Let AMD engineer can identify problem easily.

Thanks!

PS: And some suggestion, check your RAM, (disable XMP or EXPO), if you overclock any component, back to default status, swap PCI-E cable or slot.

sw11sh · ‎05-25-2023

is the problem fixed in the new version of driver? thanks

stan · ‎06-03-2023

Still can reproduce on 7900XTX/G-Sync Ultimate monitor when enable Adpative-Sync.... T_T

Driver: 23.5.2

Display: AW3821DW (G-Sync Ultimate)

Reproduce:
1. Enable Adaptive-Sync.
2. Launch some games. (example: Returnal)
3. Random get BSOD.
4. No issue is experienced when disable Adaptive-Sync.

Fresh minidump:

Qoojo · ‎06-03-2023

and they still haven't fixed edid overrides, right?

stan · ‎06-03-2023

Yes, CRU edid override is not worked on 23.5.2 w/RDNA3.

By the way, i just see this comment on reddit, maybe AMD have internal solution to fix G-Sync ultiamte monitor but not merge to the release driver now.

https://www.reddit.com/r/Amd/comments/10aumlr/comment/jk8fkz6/?utm_source=share&utm_medium=web2x&con...

Qoojo · ‎06-03-2023

The term "workaround" seems strange, as that would mean not fixed. There is already a workaround called not using it. Workaround to me would be that they fix EDID overrides, then users can set a higher minimum which prevents the issue.

jellemees · ‎06-16-2023

I want to confirm that I have this issue since day one combining my 7900XT and my Dell Alienware 3423dw. Enable freesync and games become unstable or crash and disable freesync and performance is smooth as it can be...

Qoojo · ‎06-17-2023

See Stan's reply with link to reddit saying that there is apparently a work-around, but no idea when it will make it to drivers.

The fixes have been at a glacial pace.

jellemees · ‎06-20-2023

The work around is to simply disable it? That's not a workaround

stan · ‎06-18-2023

Hello, You can reference this post from AMD or post reply to reddit.

https://www.reddit.com/r/Amd/comments/10aumlr/comment/jk8fkz6/?utm_source=share&utm_medium=web2x&con...

Please also help to report this issue use AMD Bug Report Tool.

https://www.amd.com/en/support/kb/faq/amdbrt

jellemees · ‎06-20-2023

I have commented on reddit and submitted a bug report like you suggested.

jellemees · ‎07-22-2023

Still not fixed in 23.7.1

Qoojo · ‎07-22-2023

Did you try using CRU to reduce the freesync range minimum? I set mine to 10, and 24 also worked.

doll1 · ‎07-22-2023

My problem persists despite the fact that I have tried different PSUs and cables. My PC's issues were fixed when I swapped back my old GPU into it and switched back to the new GPU. My card has been refunded and I have purchased a 4090 in its place.

lfu8cy0w · ‎09-10-2023

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- 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.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Xen3\Desktop\091023-25046-01.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 (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951
Kernel base = 0xfffff800`33e00000 PsLoadedModuleList = 0xfffff800`34a130e0
Debug session time: Sun Sep 10 12:36:36.971 2023 (UTC + 4:00)
System Uptime: 1 days 15:11:10.625
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................................................
Loading User Symbols

Loading unloaded module list
...........................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`34232230 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`3810ef80=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff80034b1c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for amdkmdag.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1608

    Key  : Analysis.Elapsed.mSec
    Value: 15566

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_amdkmdag!unknown_function

    Key  : Failure.Hash
    Value: {ce335412-b260-6bc1-3af9-ea5584f041c4}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: ni_release_svc_prod3

    Key  : WER.OS.Version
    Value: 10.0.22621.1928


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80034b1c340

BUGCHECK_P4: 0

FILE_IN_CAB:  091023-25046-01.dmp

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


DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8003810f550 -- (.trap 0xfffff8003810f550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000940 rbx=0000000000000000 rcx=000000000000016d
rdx=00000000002bcdca rsi=0000000000000000 rdi=0000000000000000
rip=fffff80086af46e6 rsp=fffff8003810f6e8 rbp=ffffd304823fb580
 r8=ffffd3048a5dd0c0  r9=0000000000003697 r10=ffffd304823fb580
r11=0000000000003697 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
amdkmdag+0x1f946e6:
fffff800`86af46e6 c3              ret
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`3810ef78 fffff800`340cfdd1     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`34b1c340 : nt!KeBugCheckEx
fffff800`3810ef80 fffff800`340cf64c     : 00021ae8`6eb209ee fffff800`30f6a180 00000000`0089c3a7 00000000`00000202 : nt!KeAccumulateTicks+0x231
fffff800`3810efe0 fffff800`340ccc23     : 00000000`00000020 00000000`00001388 00000000`0089c300 00000000`00521d29 : nt!KiUpdateRunTime+0xcc
fffff800`3810f150 fffff800`340cd868     : 00000000`00000000 ffff8681`d6ab5e00 fffff800`30f6a180 00000000`00000000 : nt!KiUpdateTime+0x613
fffff800`3810f3f0 fffff800`340cd119     : fffff800`34a5fdf8 ffff8681`d6ab5e70 ffff8681`d6ab5e70 00000000`00000007 : nt!KeClockInterruptNotify+0x228
fffff800`3810f490 fffff800`3411b4ac     : 00000148`74a83a80 fffff800`34b0d2b0 fffff800`34b0d360 00001f80`00b007b0 : nt!HalpTimerClockInterrupt+0x109
fffff800`3810f4c0 fffff800`3423438a     : fffff800`3810f5d0 fffff800`34b0d2b0 00000000`00012b57 fffff800`3412639a : nt!KiCallInterruptServiceRoutine+0x9c
fffff800`3810f500 fffff800`34234bf7     : 00000000`00000000 00000000`0004dd90 00000000`00000000 00000005`5a8e6ada : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`3810f550 fffff800`86af46e6     : fffff800`8687f698 03d3b154`00000000 ffffd304`8a6d0c60 ffffd304`823fb580 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`3810f6e8 fffff800`8687f698     : 03d3b154`00000000 ffffd304`8a6d0c60 ffffd304`823fb580 00000002`00000000 : amdkmdag+0x1f946e6
fffff800`3810f6f0 03d3b154`00000000     : ffffd304`8a6d0c60 ffffd304`823fb580 00000002`00000000 ffffd304`8a6d0c60 : amdkmdag+0x1d1f698
fffff800`3810f6f8 ffffd304`8a6d0c60     : ffffd304`823fb580 00000002`00000000 ffffd304`8a6d0c60 fffff800`8687d3dc : 0x03d3b154`00000000
fffff800`3810f700 ffffd304`823fb580     : 00000002`00000000 ffffd304`8a6d0c60 fffff800`8687d3dc 00000000`00002000 : 0xffffd304`8a6d0c60
fffff800`3810f708 00000002`00000000     : ffffd304`8a6d0c60 fffff800`8687d3dc 00000000`00002000 00000000`00000000 : 0xffffd304`823fb580
fffff800`3810f710 ffffd304`8a6d0c60     : fffff800`8687d3dc 00000000`00002000 00000000`00000000 00000940`00000000 : 0x00000002`00000000
fffff800`3810f718 fffff800`8687d3dc     : 00000000`00002000 00000000`00000000 00000940`00000000 00002000`00000900 : 0xffffd304`8a6d0c60
fffff800`3810f720 00000000`00002000     : 00000000`00000000 00000940`00000000 00002000`00000900 ffffd304`82f19910 : amdkmdag+0x1d1d3dc
fffff800`3810f728 00000000`00000000     : 00000940`00000000 00002000`00000900 ffffd304`82f19910 fffff800`8687d779 : 0x2000


SYMBOL_NAME:  amdkmdag+1f946e6

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1f946e6

FAILURE_BUCKET_ID:  0x133_ISR_amdkmdag!unknown_function

OS_VERSION:  10.0.22621.1928

BUILDLAB_STR:  ni_release_svc_prod3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ce335412-b260-6bc1-3af9-ea5584f041c4}

Followup:     MachineOwner
---------

lfu8cy0w · ‎09-10-2023

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : false
   AllowNugetExeUpdate : false
   AllowNugetMSCredentialProviderInstall : false
   AllowParallelInitializationOfLocalRepositories : true

   -- 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.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25921.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Xen3\Desktop\091023-25046-01.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 (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951
Kernel base = 0xfffff800`33e00000 PsLoadedModuleList = 0xfffff800`34a130e0
Debug session time: Sun Sep 10 12:36:36.971 2023 (UTC + 4:00)
System Uptime: 1 days 15:11:10.625
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................................................
Loading User Symbols

Loading unloaded module list
...........................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`34232230 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`3810ef80=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
	DISPATCH_LEVEL or above.
Arg2: 0000000000001e00, The watchdog period (in ticks).
Arg3: fffff80034b1c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
	additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for amdkmdag.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1468

    Key  : Analysis.Elapsed.mSec
    Value: 16412

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_amdkmdag!unknown_function

    Key  : Failure.Hash
    Value: {ce335412-b260-6bc1-3af9-ea5584f041c4}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

    Key  : WER.OS.Branch
    Value: ni_release_svc_prod3

    Key  : WER.OS.Version
    Value: 10.0.22621.1928


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80034b1c340

BUGCHECK_P4: 0

FILE_IN_CAB:  091023-25046-01.dmp

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


DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8003810f550 -- (.trap 0xfffff8003810f550)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000940 rbx=0000000000000000 rcx=000000000000016d
rdx=00000000002bcdca rsi=0000000000000000 rdi=0000000000000000
rip=fffff80086af46e6 rsp=fffff8003810f6e8 rbp=ffffd304823fb580
 r8=ffffd3048a5dd0c0  r9=0000000000003697 r10=ffffd304823fb580
r11=0000000000003697 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
amdkmdag+0x1f946e6:
fffff800`86af46e6 c3              ret
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff800`3810ef78 fffff800`340cfdd1     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`34b1c340 : nt!KeBugCheckEx
fffff800`3810ef80 fffff800`340cf64c     : 00021ae8`6eb209ee fffff800`30f6a180 00000000`0089c3a7 00000000`00000202 : nt!KeAccumulateTicks+0x231
fffff800`3810efe0 fffff800`340ccc23     : 00000000`00000020 00000000`00001388 00000000`0089c300 00000000`00521d29 : nt!KiUpdateRunTime+0xcc
fffff800`3810f150 fffff800`340cd868     : 00000000`00000000 ffff8681`d6ab5e00 fffff800`30f6a180 00000000`00000000 : nt!KiUpdateTime+0x613
fffff800`3810f3f0 fffff800`340cd119     : fffff800`34a5fdf8 ffff8681`d6ab5e70 ffff8681`d6ab5e70 00000000`00000007 : nt!KeClockInterruptNotify+0x228
fffff800`3810f490 fffff800`3411b4ac     : 00000148`74a83a80 fffff800`34b0d2b0 fffff800`34b0d360 00001f80`00b007b0 : nt!HalpTimerClockInterrupt+0x109
fffff800`3810f4c0 fffff800`3423438a     : fffff800`3810f5d0 fffff800`34b0d2b0 00000000`00012b57 fffff800`3412639a : nt!KiCallInterruptServiceRoutine+0x9c
fffff800`3810f500 fffff800`34234bf7     : 00000000`00000000 00000000`0004dd90 00000000`00000000 00000005`5a8e6ada : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`3810f550 fffff800`86af46e6     : fffff800`8687f698 03d3b154`00000000 ffffd304`8a6d0c60 ffffd304`823fb580 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`3810f6e8 fffff800`8687f698     : 03d3b154`00000000 ffffd304`8a6d0c60 ffffd304`823fb580 00000002`00000000 : amdkmdag+0x1f946e6
fffff800`3810f6f0 03d3b154`00000000     : ffffd304`8a6d0c60 ffffd304`823fb580 00000002`00000000 ffffd304`8a6d0c60 : amdkmdag+0x1d1f698
fffff800`3810f6f8 ffffd304`8a6d0c60     : ffffd304`823fb580 00000002`00000000 ffffd304`8a6d0c60 fffff800`8687d3dc : 0x03d3b154`00000000
fffff800`3810f700 ffffd304`823fb580     : 00000002`00000000 ffffd304`8a6d0c60 fffff800`8687d3dc 00000000`00002000 : 0xffffd304`8a6d0c60
fffff800`3810f708 00000002`00000000     : ffffd304`8a6d0c60 fffff800`8687d3dc 00000000`00002000 00000000`00000000 : 0xffffd304`823fb580
fffff800`3810f710 ffffd304`8a6d0c60     : fffff800`8687d3dc 00000000`00002000 00000000`00000000 00000940`00000000 : 0x00000002`00000000
fffff800`3810f718 fffff800`8687d3dc     : 00000000`00002000 00000000`00000000 00000940`00000000 00002000`00000900 : 0xffffd304`8a6d0c60
fffff800`3810f720 00000000`00002000     : 00000000`00000000 00000940`00000000 00002000`00000900 ffffd304`82f19910 : amdkmdag+0x1d1d3dc
fffff800`3810f728 00000000`00000000     : 00000940`00000000 00002000`00000900 ffffd304`82f19910 fffff800`8687d779 : 0x2000


SYMBOL_NAME:  amdkmdag+1f946e6

MODULE_NAME: amdkmdag

IMAGE_NAME:  amdkmdag.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1f946e6

FAILURE_BUCKET_ID:  0x133_ISR_amdkmdag!unknown_function

OS_VERSION:  10.0.22621.1928

BUILDLAB_STR:  ni_release_svc_prod3

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ce335412-b260-6bc1-3af9-ea5584f041c4}

Followup:     MachineOwner
---------

Happens on 23.9.1 on LG C2 Monitor.

jackwolfskin · ‎09-11-2023

Since 23.8.1 I am having freeze to BSOD , with freesync on (Dell Alienware AW2723DF ) when I alt+tab "Baldur´s Gate 3 "(game) to a browser or anything that uses gpu acceleration like Discord.

It doesn't happen with any other game I could test and it doesn't happen with freesync off, I also tested 23.7.2, which works flawlessly.

AllRed69 · ‎10-11-2023

RX 6700 XT - 23.9.1 (GIGABYTE G24F1) doing the same thing here. Either my PC freeze with artifacts then BSOD with amdkmdag.sys in DUMP OR my PC freeze but will run again with my monitor glitching like it's broken & adrenalin crashed (RX 6700 XT also disabled in device manager), in the end still need reboot. It's already OCTOBER 2023 and this problem still not fixed?? already tried 23.5.2, 23.7.1, 23.7.2, 23.8.1, 23.8.2 and still doing the same thing if freesync enabled. driver 23.9.2 & 23.9.3 much worse with freezing by just opening browser (known issue, a lot of people already report the same problem).

ForIdent · ‎11-19-2023

AOC C24G1 screen, and an iiyama... Both have a Freesync function. Blackscreen and so on. Now I can have freezes without errors! I disabled Copilot, same. Good. It's starting to annoy me.

Drivers & Software

Driver crashes when AdaptiveSyncCompatible is enabled