LiveKernelEvent - What is the problem and how to fix it?

When reviewing the problem reports in the Security and Services Center or in the System Stability Monitor of Windows 10, Windows 11 and earlier versions of the operating system, especially when a computer or laptop crashes, users may encounter an error of Hardware for which the LiveKernelEvent problem event name appears and code 141, 144, 117, and others.

This manual details what may be causing the problem, how you can find out what hardware caused the error, and fix the problem.

LiveKernelEvent hardware error code 141, 144 and others in Windows 10 and Windows 11

The above error explicitly indicates that a hardware failure has occurred during operation: controller malfunction, shutdown for some reason (lack of power, hardware problems), or something else. Most of the time the driver is the cause.

Sometimes there is additional information in the error description below the problem signature, where an indication of the driver file can be found, for example, starting with "nv" (indicating NVIDIA hardware, for other files it can be found designation information online), but this information is not always present. If this is the case, you can try to find out more about the exact cause of the error.

Read More: Problems with Cyrillic in TextEdit on Mac OS X. How to fix it?

1. Make a note of the date and time of the LiveKernelEvent hardware failure.
2. Start the «Event Viewer» using the search or pressing the keys Win + R on the keyboard, enter eventvwr.msc and press Enter.
3. In the event view, go to Windows Logs - System.
4. In the right pane, click on "Current Record Filter" and then set a configurable range in the "Date" field, specify "Event" in the "Start and End" fields and then the LiveKernelEvent date and time specific, capturing the full minute it occurred, an example is in the image below.
5. Filter the events by the specified time and examine the alerts during this period - they can give you more complete information.

For example, in the above screenshots we can see that the error is caused by the video card driver and, in fact, the video card driver or problems with its operation (for example, caused by overclocking or lack of power under high load) is in fact the most common cause of the hardware error logged as a LiveKernelEvent.

However, here we see an important nuance: as a rule, when a problem with a video card is suspected, the user tries to remove its drivers completely (for example, using DDU), install the official drivers again, update them from the official site, but only focuses on the discrete video card. However, the event view shows that it is the integrated video (igfx) that is often forgotten and does not follow the same procedures as the discrete video card.

Anyway in the above example we have seen that the IGFX (embedded video) driver has stopped responding and has been restored and we can apply methods for this case - What to do if the video driver has stopped responding and has been restored in Windows .

Read More: Time issue on Steam. How to solve it

Ways to fix the error

Depending on your specific situation, the following methods to fix LiveKernelEvent hardware error are possible:

1. If you know what hardware has caused the problem, especially if it is a video card, install the original drivers for it (downloaded manually from the official site and installed, not using the "Update" button in Device Manager), disable overclocking (if enabled), make sure the device is properly connected (sits firmly in the socket, additional power is plugged in if needed).
2. If the error occurs in a particular game or program - it may be peculiarities of the program itself (especially if it is something without a license) with this hardware, or there are parameters set in it, which cause your hardware to fail.
3. When the LiveKernelEvent crashes irregularly, consider that these types of crashes can occur when the drivers update automatically (you can ignore it here), and also when your computer's power supply cannot provide the necessary power at peak loads .
4. If the error does not occur after a reboot, but may reappear after powering off and powering on, try disabling fast startup.
5. If the error has started to occur recently and no hardware replacement has been done, system restore points can help.
6. It may make sense to check the integrity of Windows system files.
7. Installing the latest Windows 10 or Windows 11 updates or, if available, BIOS updates may also work for some cases where the error occurs.