Question LiveKernelEvent Code: 193

[Railen]

Oh boy where do i start. I guess for now i'll try to keep this simple and save the story. Overall i've dealt with so many symptoms and because the machine has given me barely any feedback i've had no real way to troubleshoot. I'm experienced with computers but i'm by no means an expert at troubleshooting hardware. I can logically feel things out but i reach my limit when swapping parts and standard troubleshooting doesn't work.

I've ruled out my GPU, seemingly my ram... software as a whole, and so on. (90% sure, i don't deal in absolutes with this stuff)

Anyway... i had a breakthrough today. I found this.

 

[Railen]

I've had many different symptoms and errors depending on the structure of my components.
With the GPU in and while on a game: Green screen crash after flickering.

With the HDMI plugged into the Moba and not the GPU: Mouse freezes, videos continue playing buffered content and then cease.

With the GPU completely removed from the case, utilizing cpu graphics only: Computer gradually froze to a halt, i could still move the mouse and only the mouse.

The first and most common experience people will have is with the GPU running normally.

Display cuts off, i can't get it to come back on or "wake up" its basically like its gone to sleep. Hard reset is the only fix. The issue occurs mostly during photoshop activity or more commonly during my media server usage.

The green screen crash now occurs during games, but didn't do so at first.

I am not looking for an easy solution, but an isolation of this problem. Which component is the problem.

I was primed to replace the GPU, but now... after removing it.. well as you can see.

In anycase i want to provide a bunch of logs that i THINK are relevant, i only just figured out how to get minidumps, and well, my latest breakthrough was finding... this.

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

Problem signature
Problem Event Name: LiveKernelEvent
Code: 193
Parameter 1: 80b
Parameter 2: 1002
Parameter 3: 1a0014
Parameter 4: 2b080001
OS version: 10_0_19041
Service Pack: 0_0
Product: 768_1
OS Version: 10.0.19041.2.0.0.768.101
Locale ID: 2057

This doesn't always appear during these crashes, a couple of times it has. This is my only lead at this time, but there are 5 minidump logs.

The one i'll provide initially will be matched with this as close as possible. just 1 minute after this, the minidump file was saved.

Okay so ... no attachments, i'll try and copy this all in.

~~

Microsoft (R) Windows Debugger Version 10.0.19041.1 X86
Copyright (c) Microsoft Corporation. All rights reserved.


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

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff80473a00000 PsLoadedModuleList = 0xfffff8047462a310
Debug session time: Tue Aug 4 16:25:18.570 2020 (UTC + 1:00)
System Uptime: 0 days 0:00:04.224
Loading Kernel Symbols
...............................................................
............................................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
For analysis of this file, run !analyze -v
2: kd> !analyze -v
***

• *
• Bugcheck Analysis *
• *

***

VIDEO_DXGKRNL_LIVEDUMP (193)
Livedumps triggered by dxgkrnl
Arguments:
Arg1: 0000000000000801, Reason Code.
100 Internal
Arg2: ffffffffc0000182, Reserved.
Arg3: 0000000000000000, Reserved.
Arg4: 0000000000000000, Reserved.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 6

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-N6UCN3O

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 13

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

Key : Analysis.System
Value: CreateObject


DUMP_FILE_ATTRIBUTES: 0x18
Kernel Generated Triage Dump
Live Generated Dump

BUGCHECK_CODE: 193

BUGCHECK_P1: 801

BUGCHECK_P2: ffffffffc0000182

BUGCHECK_P3: 0

BUGCHECK_P4: 0

PROCESS_NAME: System

LOCK_ADDRESS: fffff80474644b60 -- (!locks fffff80474644b60)
Cannot get _ERESOURCE type

Resource @ nt!PiEngineLock (0xfffff80474644b60) Available
1 total locks

PNP_TRIAGE_DATA:
Lock address : 0xfffff80474644b60
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

STACK_TEXT:
fffff28167517000 fffff8047f790ea0 : ffff9587a8475101 fffff281675172c0 ffffffffc0000182 0000000000000001 : watchdog!WdpDbgCaptureTriageDump+0x64a
fffff281675170b0 fffff8047f790d7d : ffff958700000000 0000000000000000 ffff9587a88f58c0 fffff8047ebad90e : watchdog!WdDbgReportRecreate+0xd0
fffff28167517110 fffff8047f5ec1df : 0000000000000001 fffff8047f6a3a8f 0000000000000001 ffff9587a88f58c0 : watchdog!WdDbgReportCreate+0x3d
fffff28167517170 fffff8047f5392d0 : ffff9587a8475101 fffff281675172c0 ffffffffc0000182 ffff9587a84756b8 : dxgkrnl!DxgCreateLiveDumpWithWdLogs+0x3f
fffff281675171c0 fffff80473d59497 : ffff9587a845ce30 fffff80473fe46ed fffff8047f537360 0000000000000000 : dxgkrnl!DpiAddDevice+0x1f70
fffff281675176e0 fffff804741283c0 : ffff9587a845ce30 ffff9587a88a2990 0000000000000003 ffff9587a32cbc00 : nt!PpvUtilCallAddDevice+0x3b
fffff28167517720 fffff8047412c0bf : 0000000000000003 0000000000000000 000000006e657050 0000000000000000 : nt!PnpCallAddDevice+0x94
fffff281675177e0 fffff8047412b349 : ffff9587a3d53c70 fffff28167517a18 ffff9587a3d53c70 0000000000000000 : nt!PipCallDriverAddDevice+0x827
fffff281675179a0 fffff804741c1b4c : ffff9587a88e6800 fffff28167517b01 fffff28167517ab0 fffff80400000000 : nt!PipProcessDevNodeTree+0x1b9
fffff28167517a60 fffff80473d5bd6c : 0000000100000003 ffff9587a88e6840 0000000000000000 ffff9587a88e6840 : nt!PiProcessStartSystemDevices+0x60
fffff28167517ab0 fffff80473c33f45 : ffff9587a88bd540 ffff9587a3270550 fffff804746434a0 ffff958700000000 : nt!PnpDeviceActionWorker+0x4cc
fffff28167517b70 fffff80473d46735 : ffff9587a88bd540 0000000000000080 ffff9587a32cc040 000f8067b4bbbdff : nt!ExpWorkerThread+0x105
fffff28167517c10 fffff80473de51b8 : ffffcb8139340180 ffff9587a88bd540 fffff80473d466e0 0000000000000000 : nt!PspSystemThreadStartup+0x55
fffff28167517c60 0000000000000000 : fffff28167518000 fffff28167512000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: dxgkrnl!DxgCreateLiveDumpWithWdLogs+3f

MODULE_NAME: dxgkrnl

IMAGE_NAME: dxgkrnl.sys

IMAGE_VERSION: 10.0.19041.329

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 3f

FAILURE_BUCKET_ID: LKD_0x193_dxgkrnl!DxgCreateLiveDumpWithWdLogs

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {4b6fafa0-b740-8186-967a-4fb4d108708f}

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

I know there's a lot you seem to be able to do with these that might provide even more information so if i have to send the file i'll take some backups for them just incase so i can send them on demand. There are 4 other minidumps but i'm not sure if they're relevant. To be honest i'm not sure any of them are relevant... i've been running hot cpu tester pro (lite) and it consistently shows no errors... unless the computer freezes up.

All in all, i can't really do much else. I'm out of options for troubleshooting with my knowledge now.

 

[Railen]

i wanted to get some information before making any nuclear option plays regarding fixing kernal event hardware failures.

I have now got a CPU replacement ready to replace my existing one which is to be returned. The hope was to get some help or feedback from people here to help further isolate what the problem could be, since it is progressively getting worse and seems to be either the motherboard or cpu.

Issues that could be these two, especially one as maddeningly obscure as mine can be a number of other causes such as the bios or a tiny power related fault.

Instead, both of my posts on the issue vanish and i'm left with no time.

You see i am dubious about installing my CPU into the moba incase it IS faulty, i don't want it to go and take down other parts with it. Especially with how the problem gets worse with the gpu plugged in (its not inside the case right now)

so it leaves me with a lot of theories and not alot of concrete information.

I've always felt as if toms hardware is often far too trigger happy with blaming hard drives. Nearly every time i chance upon this website with the issues i've faced over the years, every single time i come here, its always the hard drives fault. When i fix it, its never been the hard drive.

My own little pet peave aside, i expected that to be just my impression, and nothing more. Probably still is, and that it was a coincidence.

Considering i'm not sure what the problem is, bios, cpu, moba, psu, i put it in the systems area which has a lot of similar issues being described such as the bsod and so on.

I find it irritating and a huge time waster that it vanished on me so, my feedback is just that my experience was an irritating one.

I don't want to blame anyone or be irational, but this is a huge inconvenience for me. Though thankfully i can rule out the CPU with the replacement, the manufacturer for the moba wants me to test the bios and so on, which i'm not sure i can do with the cpu thing like i said before.

I provided the kernal error and the minidump relating to it in an attempt to provide as much complete information as i could for a quickfire response, which was two days ago.

Its a shame its vanished and i'm not sure why but if there are rules and that is why, or if its been moved and i dont get an alert.

Thats where the feedback is, i've got no idea. I should be informed in some way.

Communication with the user in this scenario would help me at least know why and that way i can adjust for future reference.

Its irritating but unfortunate, and i'm not ruling out some random one off weirdness either. So, no blame is coming from me.

Just wanted to talk about my experience.

Its too late for me to post my issue, but if after dealing direct with the moba manufacturer, and replacing my cpu, i STILL have the issue, i'll certainly be back.

I've ruled out basically everything at this point, each time i switch a part (removal of gpu, removal of ram, shuffling of usb ports) the crash behaves slightly differently.

Keyboard still showing a tiny sign of life one time.
Mouse cursor remaining fully functioning while everything else dies.

That type of stuff. Its weird.

 

[rgd1101]

full system spec? include make and model of the psu?

 

[Rogue Leader]

Your posts are not vanishing. You are a new user and therefore they need to be approved by the moderation team before displaying. This is one of the many triggers to help stop spam in this forum. Please do not make any more new threads for the same issue.

 

[Railen]

Thanks for that rogue.
The vanishing i talked of was that the bookmarks stopped working and they had vanished last night, i just wanted to make it known just incase it was some kind of bug - if not, just to report that it was very confusing for me.

Okay so, the request for a system spec.

Currently after removing GPU
CPU: AMD Ryzen 3 3200G (vega graphics)
Motherboard: Prime B450-plus atx Asus
Ram: 8gb DDR-2400 (1200mhz) Corsair
GPU: Vega Graphics

GPU sat beside me, which intensifies the issue.

MSI R9 380 4gb. Planning on replacing this regardless.

PSU:EVGA 500W 80plus cert UK

HDD (off the top of my head now)
WDBlack 1tb

WDGreen 240gb SSD (with nothing on it right now, its completely empty but plugged in)

This issue occurs with or without the ssd.

I have other ram sticks that failed the memtest sat outside of the case, they didn't impact the issue at all. Didn't see any improvement by removing them.

I've not ruled out...

Bios issues
Moba issues
PSU issues
CPU issues (replacement should rule that out)

Corruption issues impacting bios or that can survive a full system format + recovery.

There is a minidump i THINK is associated with the relevant hardware failure up above along with the livekernal error code.

There was a new error code that popped up and replaced one of the two i saw, which i found very weird.

Originally 193 i think, now 141.

So i have a 193 and 141. The 141 does not have a minidump near the same date so that one is a tricky one to find.

I'll probably be going dark before i can check on any responses with the removal of the old cpu. If i get the go ahead from the moba manufacturer that i can safely install the cpu, i'll be back pretty soon.

CPU and Motherboard are essentially brand new. Psu and Hard drive are fairly new. SSD newest part.

GPU oldest (sat outside of the computer)

I'm pretty peaved to be dealing with this right after upgrading lol. But what can i do.