LiveKernelEvent 141 in Windows 11: Causes and Fixes (2026)

You open Reliability Monitor and find a wall of red entries labelled LiveKernelEvent, Code 141. The message says "A problem with your hardware caused Windows to stop working correctly", yet the PC never actually showed a blue screen. This is a common and often misunderstood event, and in most cases it points to one specific component: your graphics driver or GPU.

This guide explains what LiveKernelEvent 141 really means, how to confirm it on your own PC, and how to fix it step by step.

PAGE CONTENT

• What LiveKernelEvent 141 Means
• Symptoms That Point to LiveKernelEvent 141
• Confirm the Event on Your PC
• Fix 1: Clean Reinstall the GPU Driver with DDU
• Fix 2: Roll Back Other Drivers and Update Firmware
• Fix 3: Rule Out Heat, Power, and Overclocking
• Fix 4: Repair System Files and Check Memory
• FAQs About LiveKernelEvent 141
• Back Up and Restore Windows with Qiling Disk Master

What LiveKernelEvent 141 Means

LiveKernelEvent is not a bug check in the usual sense. Instead of crashing the whole system, Windows writes a live kernel dump, usually named WATCHDOG-*.dmp in C:\Windows\LiveKernelReports, and keeps running. Code 141 is the graphics variant: it indicates that the graphics driver or the GPU itself stopped responding and had to be reset.

Internally, code 141 belongs to the same family as VIDEO_TDR, which stands for Timeout Detection and Recovery. Codes 117, 1a8, and 1b8 are close relatives and also relate to the GPU or the display pipeline.

The practical consequence is important. Because Windows recovered instead of crashing, the event usually does not produce a blue screen. You simply experience a black screen, a flash, a frozen game, or a brief stutter, and the Reliability Monitor records the reset afterwards.

Symptoms That Point to LiveKernelEvent 141

Users report a fairly consistent set of symptoms alongside this event:

• The screen goes black for a few seconds, then returns
• Screens flash or flicker, and the desktop briefly changes resolution
• A game closes unexpectedly, often with a negative exit code such as -1073740791
• A second monitor connected to integrated graphics freezes while the main display recovers
• The keyboard still responds, since the system never fully crashed
• Video playback stutters or the browser tab with hardware acceleration turns black
• In some cases the PC needs a hard reset because the display never comes back

One detail surprises many users: this problem often happens under light or moderate load, such as watching video or playing an older title, and not during heavy stress tests. That pattern does not mean the hardware is healthy, but it does help narrow down the cause.

Confirm the Event on Your PC

Step 1. Press Win + R, type perfmon /rel, and press Enter to open Reliability Monitor.

Step 2. Find red X entries and click one. Expand the details and look for "Problem Event Name: LiveKernelEvent" together with "Code: 141".

Step 3. Note the times. If the events cluster around gaming, video playback, or waking from sleep, that pattern is useful evidence.

Step 4. Open File Explorer and look in C:\Windows\LiveKernelReports for WATCHDOG-*.dmp files, which accompany this event.

Step 5. Also check Event Viewer under Windows Logs > System for display or video errors around the same timestamps, using the "display" and "nvlddmkm" or "amdkmdag" keywords.

Fix 1: Clean Reinstall the GPU Driver with DDU

An upgrade install of a graphics driver often leaves old files behind. A clean removal is the single most effective fix for this event.

Step 1. Go to your GPU vendor's website, or your PC manufacturer's page, and download the driver package you intend to use. Keep it on the local disk so you can install it offline.

Step 2. Disconnect the network cable or turn off Wi-Fi so Windows cannot install a different driver in the middle of the process.

Step 3. Restart the PC in Safe Mode. Press and hold Shift while choosing Restart, then go to Troubleshoot > Advanced options > Startup Settings > Restart, and select Safe Mode.

Step 4. Run Display Driver Uninstaller (DDU) in Safe Mode and choose "Clean and restart" for your GPU vendor. This removes leftover registry entries and driver files that a normal uninstall leaves behind.

Step 5. Back in normal Windows, install the downloaded driver package and restart.

Step 6. Test the same scenarios that used to trigger the event. If the black screens stop, keep that driver version and avoid third-party driver updater tools.

Fix 2: Roll Back Other Drivers and Update Firmware

The GPU driver is the main suspect, but it is not the only one.

Step 1. Open Device Manager, expand Display adapters, and look for warning icons on either the discrete or the integrated GPU. Both matter, since a fault in the integrated graphics driver can produce the same event.

Step 2. If the event started after a recent update, right-click the device and choose Properties > Driver > Roll Back Driver.

Step 3. Install the latest chipset driver from your PC or motherboard manufacturer. Chipset drivers govern communication between the CPU, PCIe lanes, and storage, and an outdated one can destabilise the display pipeline.

Step 4. Update the UEFI or BIOS firmware if a newer release exists. Firmware problems have caused repeated GPU resets on some board models.

Step 5. Update DirectX and your game clients, since GPU stability fixes are also delivered through Windows cumulative updates and game patches.

Step 6. Remove third-party driver and overclocking utilities such as vendor tuning suites, RGB controllers, and driver updater tools, then retest. These are frequent sources of conflicts.

Fix 3: Rule Out Heat, Power, and Overclocking

Step 1. Monitor GPU and hotspot temperatures under load with a hardware monitoring tool. Sustained temperatures well above the normal range for your card point to airflow or thermal paste problems.

Step 2. Clean the dust from the case and GPU fans, and confirm that all fans actually spin.

Step 3. Check the PCIe power cables. Use separate cables rather than a single daisy-chained connector where possible, and make sure each connector is fully seated.

Step 4. Check the power supply rating against your GPU's requirement. An ageing or underpowered PSU cannot deliver stable power to a modern card, and the result is exactly this kind of driver reset.

Step 5. Return the GPU to stock clocks and voltages. Remove any overclock, undervolt, or fan curve you applied, and disable memory overclocking profiles such as XMP or EXPO while testing.

Step 6. Reseat the graphics card in its slot. Occasionally the PCIe slot or the contact surface is the actual culprit.

Fix 4: Repair System Files and Check Memory

Step 1. Run the system file checks from an elevated Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Step 2. Check the drive for errors with chkdsk C: /f /r. A failing SSD that stalls under load can trigger display resets during heavy file operations, such as downloading or installing a large game.

Step 3. Run the Windows Memory Diagnostic with mdsched.exe. For a thorough result, use a bootable memory tester and let it complete several passes.

Step 4. If the crashes continue, analyse the dump. Open the WATCHDOG-*.dmp file in a debugger and run !analyze -v to see which module is named. Repeating the same module across several dumps is strong evidence of a specific driver or a hardware fault.

Step 5. If another graphics card is available, test with it. A card that behaves normally while the original fails under both drivers usually confirms a hardware problem that no software fix will solve.

FAQs About LiveKernelEvent 141

Is LiveKernelEvent 141 the same as a BSOD?

No. A BSOD stops the system and produces a bug check code such as 0x116 or 0x117. LiveKernelEvent 141 is a live kernel dump, written while Windows keeps running, so the PC usually recovers without a restart.

My PC works fine. Should I worry about these entries?

An occasional single entry after a driver update is usually harmless. Repeated entries over days or weeks are not, because they show the GPU driver is failing regularly and can eventually cause game crashes or data loss in open documents.

Does LiveKernelEvent 141 always mean a broken GPU?

No. A corrupt graphics driver is the most common cause. Hardware is the likely explanation only after a clean driver reinstall, a BIOS update, and a power and cooling check have all failed to help.

Why does it happen at low load instead of during stress tests?

Light workloads use different GPU power states and clock transitions than heavy 3D load. A card or driver can be perfectly stable in one state and unstable in another, which is why benchmarks sometimes pass while desktop video playback fails.

Can LiveKernelEvent 117 appear together with 141?

Yes. Code 117 is VIDEO_TDR_TIMEOUT_DETECTED, and 141, 117, 1a8, and 1b8 all belong to the same GPU or display pipeline group. Seeing several of them together reinforces the same conclusion.

Will reinstalling Windows fix it?

Usually not. Users often reinstall Windows and see the event return because the cause is a driver, firmware, power, or hardware issue that survives a clean install.

Back Up and Restore Windows with Qiling Disk Master

Before you roll back a graphics driver, flash a BIOS, or reseat hardware, create a full system backup. Driver and firmware changes are the operations most likely to leave a PC unbootable, and a system image is the fastest way back to a working state. Qiling Disk Master handles both the backup and the restore.

• Free Download
• Windows 11/10/8/7, 100% Secure

Part 1: Create a Full System Backup

Step 1. Install and open Qiling Disk Master. On the home screen, open "Backup and Recovery" and choose "System Backup". This option automatically includes Windows and the hidden boot partitions, so you do not have to select them one by one.

Step 2. Check the source. The disk where Windows is installed and its system partitions are already ticked for you. If you only need your personal documents, run a separate "File Backup" task instead.

Step 3. Click the destination box and choose where the image should be saved. Use an external HDD or SSD, a NAS, or any drive other than the one Windows is installed on, and make sure it has enough free space.

Step 4. Review the task summary and click "Proceed". Wait until the progress bar reaches 100%. Do not unplug the drive or turn off the PC while the backup is running.

Part 2: Restore Windows from the Backup

Step 1. Open Qiling Disk Master again, go to "Backup and Recovery", and select the recovery option. Your backup images are listed, so pick the one you created before the driver change.

Step 2. Choose the target disk or partition. Normally you restore to the original system disk. If the drive was replaced, select the new disk instead, and the restore rebuilds Windows together with its boot partitions.

Step 3. Preview the restore plan, click "Proceed", and confirm the warning. The PC restarts to finish the job, and Windows comes back exactly as it was on the day the image was created, with your files and programs intact.

Conclusion

LiveKernelEvent 141 is a GPU timeout recorded as a live kernel dump, not a fatal crash. It means the graphics driver or card stopped responding and Windows reset it. Work through the fixes in order: clean-reinstall the graphics driver with DDU, roll back or update related drivers and firmware, exclude heat, power, and overclocking as causes, then repair system files and test the memory. If every software step fails and another GPU works normally, treat it as a hardware fault.

Protect your PC with Qiling Backup—create a system image before your next driver or firmware change.

Related Articles

• Fix VIDEO_TDR_FAILURE BSOD in Windows 11
  VIDEO_TDR_FAILURE is the blue screen version of the same GPU timeout. See how to identify the failing driver and stop the crashes.
• Windows 11 Keeps Crashing? 8 Proven Fixes
• Screen Freezes but PC Keeps Running: How to Fix It
  A frozen picture while the system still responds often has the same root cause as a live kernel event. These steps isolate the driver at fault.
• How to Monitor Your PC Temperature in Windows
• Fix DRIVER_POWER_STATE_FAILURE BSOD (0x0000009F)