Experiencing LiveKernel 117 GPU crahses on RX 6600 XT AMD…
0 reactions
Experiencing LiveKernel 117 GPU crahses on RX 6600 XT AMD Adrenalin 26.6.4
I have recently been experiencing a driver timeout issue on my pc. I'm not entirely sure why and there's a few possible factors. I recently upgraded my CPU and Motherboard, the CPU is new and the board was bought used. It is a Asus TUF Gaming B550 plus. Initially I though the error could be related to pbo and my curve optimser I had to undervolt my cpu. After fully removing the undervolt and running my gpu at complete stock with a fresh install of drivers using DDU and fully reseating the GPU I still get the timeout error. It only ever happens when doing low intensity tasks such as browsing, discord calls and basic usage, It has never crashed or given me any issues under load or whilst playing. I even ran it through 3DMark Timespy, Steel Nomad, Heaven Benchmark and 30 mins of Furmark without one single error. I did repaste the GPU a couple months back and I've had it for around 4 months. I also messed around with overclocking the GPU for a bit, but im not very good with those things and I couldnt get it to run stable so I didnt use it after that at all and basically didnt game with any type of overclock ever. Even after the repaste, and overclocking I did not experience any of these issues before upgrading my board and cpu and installing the newest amd drivers. The temps are quite good and iv'e never really had an issue with them. My PSU is also a brand new CoolerMaster MWE 850W Gold and my motherboard bios is updated to the latest one. Im not entirely sure if this is an issue with my gpu hardware, my board or potentially a driver issue with the latest amd drivers. Any help would be largely appreciated. I will also upload a .dmp extract from one of the crashed I experienced.
PC SPECS :
* CPU: Ryzen 7 5700X
* GPU: Exact RX 6600 XT model (Sapphire Pulse, XFX SWFT, etc.)
* Motherboard: ASUS TUF Gaming B550-Plus
* RAM: 32gb 3200mhz cl16
* PSU: Cooler Master MWE 850W Gold
* Windows version (Windows 11 home)
* AMD Adrenalin version (26.6.4)
Bucket ID :
LKD\_0x117\_Tdr:3\_TdrVTR:0\_IMAGE\_amdkmdag.sys-V-GRE=c860
.dmp Extract :
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
\* \*
\* Bugcheck Analysis \*
\* \*
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
VIDEO\_TDR\_TIMEOUT\_DETECTED (117)
The display driver 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: ffffd50b28df1010, Optional pointer to internal TDR recovery context (TDR\_RECOVERY\_CONTEXT).
Arg2: fffff806143cb6a0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: ffffd50b1dd860c0, Optional internal context dependent data.
Debugging Details:
\------------------
Mini Kernel Dump does not contain unloaded driver list
Mini Kernel Dump does not contain unloaded driver list
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: 1468
Key : Analysis.Elapsed.mSec
Value: 2218
Key : Analysis.IO.Other.Mb
Value: 21
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 23
Key : Analysis.Init.CPU.mSec
Value: 765
Key : Analysis.Init.Elapsed.mSec
Value: 17747
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Analysis.Version.DbgEng
Value: 10.0.29617.1000
Key : Analysis.Version.Description
Value: 10.2604.29.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2604.29.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x117
Key : Bugcheck.Code.TargetModel
Value: 0x117
Key : Dump.Attributes.AsUlong
Value: 0x18
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: LKD\_0x117\_IMAGE\_amdkmdag.sys
Key : Failure.Exception.IP.Address
Value: 0xfffff806143cb6a0
Key : Failure.Exception.IP.Module
Value: amdkmdag
Key : Failure.Exception.IP.Offset
Value: 0x1eb6a0
Key : Failure.Hash
Value: {eb317d22-0fcb-4b7a-404e-a69301cad237}
Key : Faulting.IP.Type
Value: Paged
BUGCHECK\_CODE: 117
BUGCHECK\_P1: ffffd50b28df1010
BUGCHECK\_P2: fffff806143cb6a0
BUGCHECK\_P3: 0
BUGCHECK\_P4: ffffd50b1dd860c0
FILE\_IN\_CAB: WATCHDOG-20260722-1954.dmp
DUMP\_FILE\_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump
FAULTING\_THREAD: ffffd50b21b97180
TAG\_NOT\_DEFINED\_202b: \*\*\* Unknown TAG in analysis list 202b
VIDEO\_TDR\_CONTEXT: dt dxgkrnl!\_TDR\_RECOVERY\_CONTEXT ffffd50b28df1010
Symbol dxgkrnl!\_TDR\_RECOVERY\_CONTEXT not found.
PROCESS\_OBJECT: ffffd50b1dd860c0
PROCESS\_NAME: System
IP\_IN\_PAGED\_CODE:
amdkmdag+1eb6a0
fffff806143cb6a0 ?? ???
STACK\_TEXT:
ffffbc0286bfef40 fffff80673d06a59 : ffffd50b28df1010 0000000000000000 0000000000000000 0000000000000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e
ffffbc0286bff470 fffff806740a4e3a : 0000000000000000 00000000c0000099 fffff806740ecc50 00000000c0000099 : nt!DbgkpWerProcessPolicyResult+0x21
ffffbc0286bff4a0 fffff806740a4c39 : 0000000000000003 ffffbc0286bff680 fffff806143cb6a0 0000000000000000 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea
ffffbc0286bff500 fffff80605918dff : 0000000000000057 ffff858267ab0b60 000000000002fa00 0000000000000001 : nt!DbgkWerCaptureLiveKernelDump+0x69
ffffbc0286bff580 fffff806056d5595 : ffffd50b28df1010 ffffd50b28df1010 ffffd50b28df1010 000000000002625a : dxgkrnl!TdrCollectDbgInfoStage1+0xe7f
ffffbc0286bff760 fffff806136132f0 : ffffbc0286bff849 01dd1a032d00cbdd 0000000000000000 0000000000000000 : dxgkrnl!TdrIsRecoveryRequired+0x155
ffffbc0286bff790 fffff80613686a49 : 000000000000000e ffffd50b21ad3000 ffffd50b21ad3000 0000000000000001 : dxgmms2!VidSchiReportHwHang+0x658
ffffbc0286bff8b0 fffff806136e4d65 : 0000000000000001 0000000000000000 ffffd50bffffffff 0000000000045438 : dxgmms2!VidSchiCheckHwProgress+0x3e9
ffffbc0286bff940 fffff806135e758d : ffffd50b21ad3000 ffffd50b21ad3000 ffffbc0286bffab9 0000000000000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x385
ffffbc0286bffa10 fffff80613687332 : ffffd50b21ad3000 ffffd50b201cf7b0 ffffd50b252b8050 ffffd50b266e9010 : dxgmms2!VidSchiScheduleCommandToRun+0x46d
ffffbc0286bffb20 fffff80613675ddc : ffffd50b21ad3500 ffffd50b21ad3000 fffff80613675d00 ffffd50b21ad3000 : dxgmms2!VidSchiRun\_PriorityTable+0x42
ffffbc0286bffb70 fffff80673a8212a : ffffd50b21b97180 fffff80600000001 0000000000000000 ffffe500de6ca180 : dxgmms2!VidSchiWorkerThread+0xdc
ffffbc0286bffbb0 fffff80673cacd94 : ffffe500de6ca180 ffffd50b21b97180 fffff80673a820d0 0000000000000000 : nt!PspSystemThreadStartup+0x5a
ffffbc0286bffc00 0000000000000000 : ffffbc0286c00000 ffffbc0286bf9000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34
SYMBOL\_NAME: amdkmdag+1eb6a0
MODULE\_NAME: amdkmdag
IMAGE\_NAME: amdkmdag.sys
STACK\_COMMAND: .process /r /p 0xffffd50b116aa040; .thread /r /p 0xffffd50b21b97180 ; kb
FAILURE\_BUCKET\_ID: LKD\_0x117\_IMAGE\_amdkmdag.sys
OSPLATFORM\_TYPE: x64
OSNAME: Windows 10
FAILURE\_ID\_HASH: {eb317d22-0fcb-4b7a-404e-a69301cad237}
Followup: MachineOwner
\---------
#technology
source
I have recently been experiencing a driver timeout issue on my pc. I'm not entirely sure why and there's a few possible factors. I recently upgraded my CPU and Motherboard, the CPU is new and the board was bought used. It is a Asus TUF Gaming B550 plus. Initially I though the error could be related to pbo and my curve optimser I had to undervolt my cpu. After fully removing the undervolt and running my gpu at complete stock with a fresh install of drivers using DDU and fully reseating the GPU I still get the timeout error. It only ever happens when doing low intensity tasks such as browsing, discord calls and basic usage, It has never crashed or given me any issues under load or whilst playing. I even ran it through 3DMark Timespy, Steel Nomad, Heaven Benchmark and 30 mins of Furmark without one single error. I did repaste the GPU a couple months back and I've had it for around 4 months. I also messed around with overclocking the GPU for a bit, but im not very good with those things and I couldnt get it to run stable so I didnt use it after that at all and basically didnt game with any type of overclock ever. Even after the repaste, and overclocking I did not experience any of these issues before upgrading my board and cpu and installing the newest amd drivers. The temps are quite good and iv'e never really had an issue with them. My PSU is also a brand new CoolerMaster MWE 850W Gold and my motherboard bios is updated to the latest one. Im not entirely sure if this is an issue with my gpu hardware, my board or potentially a driver issue with the latest amd drivers. Any help would be largely appreciated. I will also upload a .dmp extract from one of the crashed I experienced.
PC SPECS :
* CPU: Ryzen 7 5700X
* GPU: Exact RX 6600 XT model (Sapphire Pulse, XFX SWFT, etc.)
* Motherboard: ASUS TUF Gaming B550-Plus
* RAM: 32gb 3200mhz cl16
* PSU: Cooler Master MWE 850W Gold
* Windows version (Windows 11 home)
* AMD Adrenalin version (26.6.4)
Bucket ID :
LKD\_0x117\_Tdr:3\_TdrVTR:0\_IMAGE\_amdkmdag.sys-V-GRE=c860
.dmp Extract :
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
\* \*
\* Bugcheck Analysis \*
\* \*
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
VIDEO\_TDR\_TIMEOUT\_DETECTED (117)
The display driver 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: ffffd50b28df1010, Optional pointer to internal TDR recovery context (TDR\_RECOVERY\_CONTEXT).
Arg2: fffff806143cb6a0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: ffffd50b1dd860c0, Optional internal context dependent data.
Debugging Details:
\------------------
Mini Kernel Dump does not contain unloaded driver list
Mini Kernel Dump does not contain unloaded driver list
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: 1468
Key : Analysis.Elapsed.mSec
Value: 2218
Key : Analysis.IO.Other.Mb
Value: 21
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 23
Key : Analysis.Init.CPU.mSec
Value: 765
Key : Analysis.Init.Elapsed.mSec
Value: 17747
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Analysis.Version.DbgEng
Value: 10.0.29617.1000
Key : Analysis.Version.Description
Value: 10.2604.29.1 amd64fre
Key : Analysis.Version.Ext
Value: 1.2604.29.1
Key : Bugcheck.Code.LegacyAPI
Value: 0x117
Key : Bugcheck.Code.TargetModel
Value: 0x117
Key : Dump.Attributes.AsUlong
Value: 0x18
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: LKD\_0x117\_IMAGE\_amdkmdag.sys
Key : Failure.Exception.IP.Address
Value: 0xfffff806143cb6a0
Key : Failure.Exception.IP.Module
Value: amdkmdag
Key : Failure.Exception.IP.Offset
Value: 0x1eb6a0
Key : Failure.Hash
Value: {eb317d22-0fcb-4b7a-404e-a69301cad237}
Key : Faulting.IP.Type
Value: Paged
BUGCHECK\_CODE: 117
BUGCHECK\_P1: ffffd50b28df1010
BUGCHECK\_P2: fffff806143cb6a0
BUGCHECK\_P3: 0
BUGCHECK\_P4: ffffd50b1dd860c0
FILE\_IN\_CAB: WATCHDOG-20260722-1954.dmp
DUMP\_FILE\_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump
FAULTING\_THREAD: ffffd50b21b97180
TAG\_NOT\_DEFINED\_202b: \*\*\* Unknown TAG in analysis list 202b
VIDEO\_TDR\_CONTEXT: dt dxgkrnl!\_TDR\_RECOVERY\_CONTEXT ffffd50b28df1010
Symbol dxgkrnl!\_TDR\_RECOVERY\_CONTEXT not found.
PROCESS\_OBJECT: ffffd50b1dd860c0
PROCESS\_NAME: System
IP\_IN\_PAGED\_CODE:
amdkmdag+1eb6a0
fffff806143cb6a0 ?? ???
STACK\_TEXT:
ffffbc0286bfef40 fffff80673d06a59 : ffffd50b28df1010 0000000000000000 0000000000000000 0000000000000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e
ffffbc0286bff470 fffff806740a4e3a : 0000000000000000 00000000c0000099 fffff806740ecc50 00000000c0000099 : nt!DbgkpWerProcessPolicyResult+0x21
ffffbc0286bff4a0 fffff806740a4c39 : 0000000000000003 ffffbc0286bff680 fffff806143cb6a0 0000000000000000 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea
ffffbc0286bff500 fffff80605918dff : 0000000000000057 ffff858267ab0b60 000000000002fa00 0000000000000001 : nt!DbgkWerCaptureLiveKernelDump+0x69
ffffbc0286bff580 fffff806056d5595 : ffffd50b28df1010 ffffd50b28df1010 ffffd50b28df1010 000000000002625a : dxgkrnl!TdrCollectDbgInfoStage1+0xe7f
ffffbc0286bff760 fffff806136132f0 : ffffbc0286bff849 01dd1a032d00cbdd 0000000000000000 0000000000000000 : dxgkrnl!TdrIsRecoveryRequired+0x155
ffffbc0286bff790 fffff80613686a49 : 000000000000000e ffffd50b21ad3000 ffffd50b21ad3000 0000000000000001 : dxgmms2!VidSchiReportHwHang+0x658
ffffbc0286bff8b0 fffff806136e4d65 : 0000000000000001 0000000000000000 ffffd50bffffffff 0000000000045438 : dxgmms2!VidSchiCheckHwProgress+0x3e9
ffffbc0286bff940 fffff806135e758d : ffffd50b21ad3000 ffffd50b21ad3000 ffffbc0286bffab9 0000000000000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x385
ffffbc0286bffa10 fffff80613687332 : ffffd50b21ad3000 ffffd50b201cf7b0 ffffd50b252b8050 ffffd50b266e9010 : dxgmms2!VidSchiScheduleCommandToRun+0x46d
ffffbc0286bffb20 fffff80613675ddc : ffffd50b21ad3500 ffffd50b21ad3000 fffff80613675d00 ffffd50b21ad3000 : dxgmms2!VidSchiRun\_PriorityTable+0x42
ffffbc0286bffb70 fffff80673a8212a : ffffd50b21b97180 fffff80600000001 0000000000000000 ffffe500de6ca180 : dxgmms2!VidSchiWorkerThread+0xdc
ffffbc0286bffbb0 fffff80673cacd94 : ffffe500de6ca180 ffffd50b21b97180 fffff80673a820d0 0000000000000000 : nt!PspSystemThreadStartup+0x5a
ffffbc0286bffc00 0000000000000000 : ffffbc0286c00000 ffffbc0286bf9000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34
SYMBOL\_NAME: amdkmdag+1eb6a0
MODULE\_NAME: amdkmdag
IMAGE\_NAME: amdkmdag.sys
STACK\_COMMAND: .process /r /p 0xffffd50b116aa040; .thread /r /p 0xffffd50b21b97180 ; kb
FAILURE\_BUCKET\_ID: LKD\_0x117\_IMAGE\_amdkmdag.sys
OSPLATFORM\_TYPE: x64
OSNAME: Windows 10
FAILURE\_ID\_HASH: {eb317d22-0fcb-4b7a-404e-a69301cad237}
Followup: MachineOwner
\---------
#technology
source
| 3,000 mlx | |
| 4 | |
| 0 |