Question Random LiveKernelEvent 141/117 in event viewer ?

[BaaaaL44]

I have noticed that upon PC startup, and also at random intervals, three LiveKernelEvent warnings appear in my event viewer. Two of them are always event 141s and one is always an event 117. These always appear as a batch of three, logged at the exact same time. They appear in the "application" tab in the event viewer, as "information", not as error or warning, and they are also not logged in the reliability monitor. There is no corresponding error in the 'system" tab either. When they are logged, the PC is functioning normally, no blue/black screens, no crashes or hangups.

I have been having some issues with random driver timeouts (9070XT) in certain games since I got this GPU, which are also logged as event 141s, but those actually result in black screens/error messages from AMD Adrenaline telling me a driver timeout has occured.

Any ideas what these errors may be?

Gigabyte Z790 UD AX
13600KF
Sapphire 9070XT
32GB Corsair Vengeance 6000Mhz
Asus ROG STRIX 850W
Windows 11 24H2

All PC components are tested in OCCT/Memtest86/3D Mark/Furmark and stable individually

 

[ubuysa]

The 0x141 and 0x117 are both graphics related. The 0x141 is a VIDEO_ENGINE_TIMEOUT_DETECTED and the 0x117 is a VIDEO_TDR_TIMEOUT_DETECTED. TDR is the Windows Timeout Detection & Recovery feature, it detects graphics hangs and recovers by resetting the driver and graphics card - this usually causes a crash to desktop.

These live kernel events happen when a failure occurs but Windows is able to recover. Dumps are written but to the C:\Windows\LiveKernelReports folder. If you navigate to that folder you'll likely see several sub-folders. Upload (to a cloud service) any dump files you find in these folders and we'll take a look.

In the meantime ensure that you have the latest driver for your graphics card installed.

 

[BaaaaL44]

The 0x141 and 0x117 are both graphics related. The 0x141 is a VIDEO_ENGINE_TIMEOUT_DETECTED and the 0x117 is a VIDEO_TDR_TIMEOUT_DETECTED. TDR is the Windows Timeout Detection & Recovery feature, it detects graphics hangs and recovers by resetting the driver and graphics card - this usually causes a crash to desktop.

These live kernel events happen when a failure occurs but Windows is able to recover. Dumps are written but to the C:\Windows\LiveKernelReports folder. If you navigate to that folder you'll likely see several sub-folders. Upload (to a cloud service) any dump files you find in these folders and we'll take a look.

In the meantime ensure that you have the latest driver for your graphics card installed.

I navigated to the folder, and there is a 10GB dmp file (that I can obviously not upload), and several sub-folders with multiple .dmp files inside each. However, none of these files' creation dates correspond to the dates and times of the events I see in the event viewer.

 

[BaaaaL44]

This is what I got now in the event viewer: When it was logged, PC was working normally, no crashes or hangups. Weirdly enough it says "Windows 10" even though I'm using Win 11.

EDIT: Reinstalled my drivers (latest ofc) and the error was still produced at startup with no AMD drivers installed. After rebooting and driver installation I also got an 1a8 and 1b8 event. PC still working normally, and experienced no crashes when they were logged at startup. Also, when these errors happen, the AMD Adrenaline software does not reset default settings like it does after an actual driver timeout crash.

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: ffffb787e0185460, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80550b77740, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: ffffb787df29c080, 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: 1234

Key : Analysis.Elapsed.mSec
Value: 3164

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27871.1001

Key : Analysis.Version.Description
Value: 10.2505.01.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2505.1.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x141

Key : Bugcheck.Code.TargetModel
Value: 0x141

Key : Dump.Attributes.AsUlong
Value: 0x18

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Failure.Bucket
Value: LKD_0x141_IMAGE_amdkmdag.sys

Key : Failure.Exception.IP.Address
Value: 0xfffff80550b77740

Key : Failure.Exception.IP.Module
Value: amdkmdag

Key : Failure.Exception.IP.Offset
Value: 0x1e7740

Key : Failure.Hash
Value: {48b738dd-5a92-7ff8-63d0-f075fc680fe0}


BUGCHECK_CODE: 141

BUGCHECK_P1: ffffb787e0185460

BUGCHECK_P2: fffff80550b77740

BUGCHECK_P3: 0

BUGCHECK_P4: ffffb787df29c080

FILE_IN_CAB: WATCHDOG-20250801-0557.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

FAULTING_THREAD: ffffb787ca70a3c0

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


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

PROCESS_OBJECT: ffffb787df29c080

PROCESS_NAME: System

STACK_TEXT:
ffff8d88`737c6de0 fffff805`a8704f99 : ffffb787`e0185460 00000000`00000000 00000000`00000000 00000000`00000000 : nt!DbgkpWerCaptureLiveTriageDump+0x8e
ffff8d88`737c7310 fffff805`a8ab5a9a : 00000000`00000000 00000000`00000000 fffff805`a8adb8b0 00000000`c0000022 : nt!DbgkpWerProcessPolicyResult+0x21
ffff8d88`737c7340 fffff805`a8ab5899 : 00000000`00000003 ffff8d88`737c7520 ffffb787`e0185460 ffffb787`e1016050 : nt!DbgkWerCaptureLiveKernelDump2+0x1ea
ffff8d88`737c73a0 fffff805`3a3241a9 : ffffa40d`18c284f0 ffffa40d`18c284f0 ffffa40d`2303c7ca ffffb787`e0185460 : nt!DbgkWerCaptureLiveKernelDump+0x69
ffff8d88`737c7420 fffff805`57c94da8 : ffffb787`d263e000 ffffb787`d263e000 ffffb787`d263e000 00000000`00000001 : dxgkrnl!TdrCollectDbgInfoStage1+0xd69
ffff8d88`737c75e0 fffff805`57ce7187 : ffffb787`d263e001 ffffb787`d263e6f8 00000000`00000000 fffff805`57ce6f84 : dxgmms2!VidSchiResetHwEngine+0x210
ffff8d88`737c77d0 fffff805`57ce9d86 : 00000000`00000000 ffffb787`d2596000 00000000`00000000 00000000`00000000 : dxgmms2!VidSchiResetEngines+0xcb
ffff8d88`737c7820 fffff805`57ce92f9 : 00000000`00000000 00000000`00000000 00000000`88eeffe0 00000000`0000351e : dxgmms2!VidSchiCheckHwProgress+0x316
ffff8d88`737c78b0 fffff805`57c6c0c2 : ffffb787`d2596000 ffffb787`d2596000 ffff8d88`737c7a39 00000000`00000000 : dxgmms2!VidSchiWaitForSchedulerEvents+0x3f9
ffff8d88`737c7980 fffff805`57cea742 : ffffb787`d2596000 ffff8d88`737c7af0 ffffb787`e0ed1050 ffffb787`d2596000 : dxgmms2!VidSchiScheduleCommandToRun+0x2e2
ffff8d88`737c7aa0 fffff805`57ce733c : ffffb787`d2596500 ffffb787`d2596000 fffff805`57ce7260 00000000`00000000 : dxgmms2!VidSchiRun_PriorityTable+0x42
ffff8d88`737c7af0 fffff805`a849e2da : ffffb787`ca70a3c0 fffff805`00000001 ffffe201`94390180 066fe47f`b19bbdff : dxgmms2!VidSchiWorkerThread+0xdc
ffff8d88`737c7b30 fffff805`a86a67e4 : ffffe201`94390180 ffffb787`ca70a3c0 fffff805`a849e280 00680074`00200068 : nt!PspSystemThreadStartup+0x5a
ffff8d88`737c7b80 00000000`00000000 : ffff8d88`737c8000 ffff8d88`737c1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: amdkmdag+1e7740

MODULE_NAME: amdkmdag

IMAGE_NAME: amdkmdag.sys

STACK_COMMAND: .process /r /p 0xffffb787964c2040; .thread 0xffffb787ca70a3c0 ; 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

 

[ubuysa]

I navigated to the folder, and there is a 10GB dmp file (that I can obviously not upload), and several sub-folders with multiple .dmp files inside each. However, none of these files' creation dates correspond to the dates and times of the events I see in the event viewer.

That's not important, as long as the dumps in there are within the last month or two they may contain useful information.

And where did the dump you posted above come from? Please upload the actual dump file.

Also, in the Run command box enter the command winver and click OK. Post a screenshot of the window that opens.

 

[BaaaaL44]

That's not important, as long as the dumps in there are within the last month or two they may contain useful information.

And where did the dump you posted above come from? Please upload the actual dump file.

Also, in the Run command box enter the command winver and click OK. Post a screenshot of the window that opens.

Thanks for the help, I think I managed to solve it! I looked at the timestamp inside the dump and realized it was from a crash that happened over 2 weeks ago. For some reason Windows insisted on relogging the latest 5 crashes at every single startup and periodically during normal operation. After I deleted the .dmp files from both the windows/livekernelevents folder and the programdata folder, the errors no longer show up at startup or during normal use.