LiveKernelEvent 141. Computer screen goes black and resets graphics drivers.

Question

So I have a 1 year old lenovo laptop. It is the Lenovo Yoga Pro 9i 16IMH9 with 185H processor and RTX4070. The laptop daily runs into the following event kernel event even after full windows reinstall. I really hope it is not hardware, since Lenovo support is terrible in my country (literally nonexistent and other regions refuse support saying to contact my region). How can I diagnose this? There is also a Watchdog dmp file included, is there any good info there and what do I even look for?

Description

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

Problem signature

Problem Event Name: LiveKernelEvent

Code: 141

Parameter 1: ffffd708cbbea050

Parameter 2: fffff8036d502760

Parameter 3: 0

Parameter 4: ffffd708b8cbd080

OS version: 10_0_26200

Service Pack: 0_0

Product: 256_1

OS Version: <removed>

Locale ID: 1033

Files that help describe the problem

WATCHDOG-20260302-1445.dmp

sysdata.xml

WERInternalMetadata.xml

memory.csv

sysinfo.txt

WERInternalRequest.xml

Answer 1

Here is the dmp file:
https://tartuulikool-my.sharepoint.com/:u:/g/personal/banatovski_ut_ee/IQD1uKJZd51SS4EkgDlkxSY-AR_uiSveCemM-DE1_FPgte4?e=7Z9foN

Answer 2

Most likely, it is just the Nvidia graphics drivers causing the black screens, Nvidia have indicated they are investigating reported problems with their drivers with the latest couple of Windows updates.

Please upload the WATCHDOG-20260302-1445.dmp file and any minidump file that may exist in the C:\WIndows\Minidump folder to OneDrive or any other cloud service and provide a share link here for analysis.

Answer 3

LiveKernelEvent code 141 is a GPU-related hardware error that triggers a kernel live dump (WATCHDOG-*.dmp) without fully crashing Windows. It typically indicates that the graphics driver or GPU stopped responding and had to be reset.

For Windows 11, repeated GPU-related stop/live errors are handled similarly to other stop code issues. Use these steps to diagnose and mitigate:

1. Basic system checks
   1. Remove any recently added external hardware (docks, USB hubs, external GPUs, extra monitors) and test if the issue persists.
   2. Ensure there is sufficient free disk space (ideally 10–15% free) on the system drive so Windows can create dumps and swap files.
2. Boot in Safe Mode to isolate drivers
   1. Start the PC in Safe Mode as described in Start your PC in safe mode in Windows 11.
   2. In Safe Mode, the system uses basic display drivers. If the black-screen/resets do not occur there, this strongly points to the RTX 4070 driver or related software.
3. Check Device Manager for driver issues
   1. Right-click Start → Device Manager.
   2. Expand Display adapters and check for warning icons.
   3. Right-click the GPU → Update driver. If that does not help, use Uninstall device (including driver software), then reinstall the latest graphics driver from Lenovo or the GPU vendor.
   4. Also check other devices (especially anything with warning icons) and update or temporarily disable them to see if the issue stops.
4. Update Windows and all drivers
   1. Go to Start → Settings → Windows Update → Check for updates and install all available updates.
   2. Update display, chipset, and firmware/BIOS drivers from Lenovo’s support site for the Yoga Pro 9i 16IMH9.
   3. For Office or app crashes related to drivers, ensure video, mouse, keyboard, and printer drivers are current, as older drivers can cause instability.
5. Analyze the watchdog dump (advanced)
   1. LiveKernelEvent 141 produces a WATCHDOG-*.dmp, which is a kernel live dump. This is designed to capture kernel memory when a subsystem (like GPU) stops responding, without resetting the OS.
   2. Install the Windows Debugger (WinDbg) and load the WATCHDOG-20260302-1445.dmp or the system memory dump (for example, C:\Windows\memory.dmp).
   3. With public symbols configured, analyze the dump to identify which driver module is involved. For GPU-related issues, look for the graphics driver or any third-party filter driver on the stack.
   4. For DPC watchdog–type issues, follow the guidance in Determining the source of Bug Check 0x133 (DPC_WATCHDOG_VIOLATION) errors on Windows Server 2012 to identify problematic drivers from the dump; the same approach applies to GPU watchdog live dumps.
6. Check Event Viewer logs
   1. Open Event Viewer → Windows Logs → System.
   2. Look for errors or warnings around the time of the LiveKernelEvent 141 (especially display, GPU, or driver timeouts). These entries can point to the specific driver or component failing.
7. If the issue persists after clean OS and driver updates
   1. If a full Windows reinstall plus clean GPU driver install does not resolve the repeated LiveKernelEvent 141, and the dumps consistently implicate the GPU or its driver, this strongly suggests a hardware or firmware problem.
   2. At that point, contact Lenovo support with:
      • The LiveKernelEvent 141 details
      • The WATCHDOG dump and any memory dumps
      • Event Viewer logs showing GPU/driver errors
   3. Use Lenovo’s diagnostics tools (if available) to run GPU and system tests and provide those results to support.

If the system also shows blue screens with stop codes such as DPC_WATCHDOG_VIOLATION (0x133), follow the same advanced steps: collect the memory dump, analyze it with Windows Debugger to find the faulty driver, disable or update that driver, and verify any new hardware is compatible with the installed Windows version.

---

References:

• Troubleshooting Windows unexpected restarts and stop code errors
• Advanced troubleshooting for stop code errors
• Kernel Live Dump Code Reference
• I get a "stopped working" error when I start Office applications on my PC