LiveKernelEvent 193 Issue

System:

• GPU: MSI RTX 5090 Lightning Z
• CPU: AMD Ryzen 7 9800X3D
• Motherboard: ASUS ROG Crosshair X870E Apex
• RAM: 32GB DDR5
• PSU: Cooler Master X Mighty 2000 (80 Plus Platinum, ATX 3.1)
• OS: Windows 11 Pro
• NVIDIA Driver: 591.88

NO OVERCLOCKS

Issue:

I am experiencing intermittent LiveKernelEvent 193
The latest event occurred while NOT gaming. Windows remained responsive. There was no BSOD, reboot, or full system freeze.

I have observed these issues across multiple NVIDIA driver versions, not just 591.88.

WinDbg output from the latest dump:

• PROCESS_NAME: dwm.exe
• MODULE_NAME: dxgkrnl
• IMAGE_NAME: dxgkrnl.sys
• FAILURE_BUCKET_ID: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs2
• Bugcheck: VIDEO_DXGKRNL_LIVEDUMP (193)
• Arg1: 0x80e

Relevant output:

PROCESS_NAME: dwm.exe

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

FAILURE_BUCKET_ID:
LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs2

Troubleshooting already attempted:

• Clean Windows installation
• DDU driver cleanup
• Multiple NVIDIA driver versions tested
• Different display configurations tested
• Long gaming sessions can sometimes run for hours without issue

Has anyone seen LiveKernelEvent 193 (0x80e) involving dwm.exe and dxgkrnl on RTX 50-series systems, and is there a known root cause or additional debugging method that could narrow this down further?

Description
A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 193
Parameter 1: 80e
Parameter 2: ffffa88aab6e2080
Parameter 3: ffff888460c175a0
Parameter 4: 0
OS version: 10_0_26200
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.26200.2.0.0.256.48
Locale ID: 1033

Files that help describe the problem
WATCHDOG-20260602-1827.dmp
sysdata.xml
WERInternalMetadata.xml
memory.csv
sysinfo.txt
WERInternalRequest.xml

5: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000b9`79c38018). Type ".hh dbgerr001" for details
Mini Kernel Dump does not contain unloaded driver list

---

• 
  
  <span> *</span>
• 
  
  <span> Bugcheck Analysis *</span>
• 
  
  <span> *</span>

---

VIDEO_DXGKRNL_LIVEDUMP (193)
Livedumps triggered by dxgkrnl when a problem is detected.
(This code can never be used for a real BugCheck; it is used to identify live dumps.)
Arguments:
Arg1: 000000000000080e, Reason Code.
100 Internal
Arg2: ffffa88aab6e2080, Reserved.
Arg3: ffff888460c175a0, Reserved.
Arg4: 0000000000000000, Reserved.

Debugging Details:​

Mini Kernel Dump does not contain unloaded driver list
Mini Kernel Dump does not contain unloaded driver list

KEY_VALUES_STRING: 1

<span>Key : Analysis.CPU.mSec<br>Value: 812<br><br>Key : Analysis.Elapsed.mSec<br>Value: 837<br><br>Key : Analysis.IO.Other.Mb<br>Value: 0<br><br>Key : Analysis.IO.Read.Mb<br>Value: 1<br><br>Key : Analysis.IO.Write.Mb<br>Value: 0<br><br>Key : Analysis.Init.CPU.mSec<br>Value: 328<br><br>Key : Analysis.Init.Elapsed.mSec<br>Value: 45784<br><br>Key : Analysis.Memory.CommitPeak.Mb<br>Value: 94<br><br>Key : Analysis.Version.DbgEng<br>Value: 10.0.29547.1002<br><br>Key : Analysis.Version.Description<br>Value: 10.2602.27.2 amd64fre<br><br>Key : Analysis.Version.Ext<br>Value: 1.2602.27.2<br><br>Key : Bugcheck.Code.LegacyAPI<br>Value: 0x193<br><br>Key : Bugcheck.Code.TargetModel<br>Value: 0x193<br><br>Key : Dump.Attributes.AsUlong<br>Value: 0x18<br><br>Key : Dump.Attributes.KernelGeneratedTriageDump<br>Value: 1<br><br>Key : Failure.Bucket<br>Value: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs2<br><br>Key : Failure.Hash<br>Value: {f51452f1-290a-6a1b-5cf3-c8f949ad9c33}</span>
BUGCHECK_CODE: 193

BUGCHECK_P1: 80e

BUGCHECK_P2: ffffa88aab6e2080

BUGCHECK_P3: ffff888460c175a0

BUGCHECK_P4: 0

FILE_IN_CAB: WATCHDOG-20260602-1827.dmp

DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

FAULTING_THREAD: ffffa88aab6e2080

PROCESS_NAME: dwm.exe

STACK_TEXT:
ffffe08a<span>cc207220 fffff806</span>50c071d8 : ffffa88a<span>aee65d00 00000000</span>00000000 00000000<span>00000000 00000000</span>0000080e : watchdog!WdpDbgCaptureTriageDump+0xe6
ffffe08a<span>cc207290 fffff806</span>50c03bf8 : ffff8884<span>60c17500 00000000</span>00000193 00000000<span>0000080e ffff8884</span>779a6008 : watchdog!WdDbgReportRecreate+0x108
ffffe08a<span>cc2072f0 fffff806</span>50ff63b2 : ffff8884<span>60c175a0 ffffe08a</span>cc2074e0 0000029c<span>6824d57c 00000000</span>c000000d : watchdog!WdDbgReportCreate+0x58
ffffe08a<span>cc207360 fffff806</span>50ff635b : ffff8884<span>60c175a0 ffffe08a</span>cc2074e0 00000000<span>c000000d fffff806</span>9a15a3d2 : dxgkrnl!DxgCreateLiveDumpWithWdLogs2+0x4a
ffffe08a<span>cc2073d0 fffff806</span>50f4dfb6 : 00000005<span>00000000 ffffa88a</span>ab6e2080 ffffa88a<span>ab6e2080 000000b9</span>7a07f910 : dxgkrnl!DxgCreateLiveDumpWithWdLogs+0x2b
ffffe08a<span>cc207420 fffff806</span>bf4bc558 : ffffa88a<span>ab6e2080 00000000</span>00003670 ffffa88a<span>ab6e2080 0000029c</span>68ecde20 : dxgkrnl!NtDxgkPinResources+0x76
ffffe08a<span>cc207460 00007ffa</span>e2b33f04 : 00000000<span>00000000 00000000</span>00000000 00000000<span>00000000 00000000</span>00000000 : nt!KiSystemServiceCopyEnd+0x28
000000b9<span>7a07f148 00000000</span>00000000 : 00000000<span>00000000 00000000</span>00000000 00000000<span>00000000 00000000</span>00000000 : 0x00007ffa`e2b33f04

SYMBOL_NAME: dxgkrnl!DxgCreateLiveDumpWithWdLogs2+4a

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.26100.8457

STACK_COMMAND: .process /r /p 0xffffa88aab670080; .thread /r /p 0xffffa88aab6e2080 ; kb

BUCKET_ID_FUNC_OFFSET: 4a

FAILURE_BUCKET_ID: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs2

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f51452f1-290a-6a1b-5cf3-c8f949ad9c33}

Followup: MachineOwner​

This is Per AI so use this information accordingly
VIDEO_DXGKRNL_LIVEDUMP (193) withDxgCreateLiveDumpWithWdLogs2 means Windows detected a GPU/driver stall long enough to trigger a diagnostic dump, but not long enough to crash the system. This is why you don’t see a BSOD or reboot.

These are the fixes that have helped other users with the same signature:
1. Disable HAGS (Hardware‑Accelerated GPU Scheduling)
Settings → System → Display → Graphics → Default settingsTurn off Hardware‑accelerated GPU scheduling.

This alone resolves 193 for many users.

2. Force PCIe to Gen4 in BIOS​

On X870E boards, set:

• PCIe Slot Configuration → Gen4
• Disable PCIe ASPM (L0s/L1)

This removes link‑state instability.

3. Disable MPO (Multiplane Overlay)​

MPO is a known cause of DWM stalls.

Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm<br>OverlayTestMode = 5 (DWORD)<br>
Reboot.

4. Try running without G‑Sync/VRR temporarily​

If the issue disappears, it confirms a timing/handshake stall.

5. Check for early BIOS AGESA updates​

X870E boards are still receiving stability patches.

Drivers prior to the 59x series seem to be much more stable. I was getting the black screen TDR errors with 591 but never had one with 581.80

Check your DirectX.
To do so,type ---dxdiag ---into the Search box and in the Systems page see that DirectX v 12 is in use.
Also the WHQL box is ticked,this is the Default.
In the Display page,note the driver in use and if you want to try other drivers,temporarily uncheck WHQL,but do not leave it permanently unchecked.Its function is to only allow Microsoft approved drivers to download,preventing dodgy drivers from downloading.
Also see if Reliability History has any entries which may help to determine the problem.Start typing ---reliability ---into the Search box.
Have you tried running--- dism /online /cleanup-image /restorehealth---inTerminal [admin ] and then followed by ---sfc /scannow ---in that sequence ?