LiveKernalEvent 17d LKD_0x17D_TOAST_IMAGE_twinui.dll

Question

Hello, Today, my laptop decided to randomly shut itself off. It took around 3 bootups before it actually showed something. It showed a scanning screen where is was scanning my hardware for problems. It showed no problems even though it just shut down. I looked into my repair software and reverted back to a safe state. I also tried to update to the latest drivers using SupportAssist. I've already ran DISM and also sfc /scannow now with not much process. If we were not in a pandemic, I would've already bring my computer to a repair place. I am running a Dell Vostro 7500. My computer has had a LiveKernalEvent 17d problem before. But not with these parameters and also not this severe! Please give me answers or at least try to help. I found this problem using the reliability history. I'm worried that this could be a recurring problem.

Problem: Hardware error
Description: A problem with your hardware caused Windows to stop working correctly.

Problem signature
Problem Event Name: LiveKernelEvent
Code: 17d
Parameter 1: 26
Parameter 2: ffffc40eb2de8a20
Parameter 3: ffffc40eb3354af0
Parameter 4: ffffd78d6af2fa70
OS version: 10_0_19043
Service Pack: 0_0
Product: 256_1
OS Version: 10.0.19043.2.0.0.256.48
Locale ID: 1033

Extra information about the problem
Bucket ID: LKD_0x17D_TOAST_IMAGE_twinui.dll

Answer 1

Hello @Ryan Le

I would like to suggest you below troubleshooting steps.

1. Please uninstall any Windows update recently installed.
2. Please scan your disk using command c:\> chkdsk c:\ \f \r
3. Please disable any Antivirus program for Temporary to see if works.
4. If you have a system restore point created then you can go back to previous working state and this should not effect your data files.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Answer 2

If there are recurrent problems logs can be collected for troubleshooting.

The chkdsk command above was incorrectly typed.

If you want to run chkdsk then run using: chkdsk /f /r

C:\WINDOWS\system32>chkdsk /f /r
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process. Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N)

Type: Y

.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

Answer 3

Use the information in this link to find the chkdsk report in the event viewer.
Copy and paste into notepad > save to the desktop > post results into the thread using a share link: one drive, drop box, or google drive

https://www.tenforums.com/tutorials/40822-read-chkdsk-log-event-viewer-windows-10-a.html

A reference for 17d to run chkdsk was not found.
However it is generally a good idea to check the drive file system.

.
.
.
.
.
Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post: Vote = a helpful post
.
.
.
.
.

Answer 4

Hello @Limitless Technology

I have tried most of it.

1 - I have not had any recent windows update.

2 - The Command did not work and showed up with 'c:\' is not recognized as an internal or external command,
operable program or batch file. And also yes, I ran command in administrator.

3 - I will try this if it happens again.

4 - After my computer scan, there was a repair section that I could go to. It tried to repair my files and then it made me go back to a previous working state.

I have not had any problems with this error yet but will keep updated if it happens again.

Thank you, Ryan

Answer 5

Hello,

I ran the command that you gave and it worked. I typed Y and restarted my machine. During the scan, I had to eat dinner since I thought it would be productive. But when I finished dinner, I was not there for the scan finishing so I was wondering on where I would find the logs.

Thank You, Ryan