How to fix Live.KernelEvent 141

ruslan shmtv 0 Reputation points
2026-09-07T05:16:27.21+00:00

Hey So I have a newly built PC around a couple months old here having on and off problems with games crashing? Ive had GTA V crash before but I thought I resolved it. I mean GTA didnt crash this time but rocket league did. Here is the Log on the crash in reliability monitor.

Description

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

Problem signature

Problem Event Name: LiveKernelEvent

Code: 141

Parameter 1: ffffb409fa67c010

Parameter 2: fffff80280749fa0

Parameter 3: 0

Parameter 4: ffffb409f85130c0

OS version: 10_0_26200

Service Pack: 0_0

Product: 256_1

OS Version: 10.0.26200.2.0.0.256.48

Locale ID: 1033

Here are my specs as well.

AMD Ryzen 7 9800X3D 8-Core Processor 32 GB Ram NVIDIA GeForce RTX 5070 (12 GB) 2 Tb Storage.
Any help is appreciated thank you.

Windows for home | Other | Performance and system failures
0 comments No comments

2 answers

Sort by: Newest
  1. DaveM121 932.3K Reputation points Independent Advisor
    2026-09-07T05:49:00.2433333+00:00

    That error trace does not indicate the underlying cause of the problem.

    Please check to see if your PC is producing any small Watchdog dump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

    Open Windows File Explorer.

    Navigate to C:\Windows\LiveKernelReports

    If there are any Watchdog dump files in the sub-folders of that folder, copy the files onto your Desktop, then zip those up.

    Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

    Then post the link here to the zip file, so I can take a look for you.

    Was this answer helpful?


  2. AI answer

    2026-09-07T05:16:42.1833333+00:00

    LiveKernelEvent 141 is typically a graphics timeout or hardware/driver-related failure. In the provided scenario, the most relevant path is to check for a graphics driver issue first, then isolate hardware or memory problems.

    1. Check Event Viewer for related errors around the same time as the crash.
      • Open Event Viewer.
      • Go to Windows Logs > System.
      • Look for critical or error events in the same time window as the Rocket League or GTA V crash.
      • This can help identify whether a display driver or another device is involved.
    2. Check Device Manager for graphics or device faults.
      • Open Device Manager.
      • Look for any device marked with an exclamation point (!).
      • Open the device properties and review the events log for the driver.
      • If the graphics adapter shows problems, update or reinstall the related driver.
    3. If a driver is identified in the crash information, disable it temporarily or update it from the hardware manufacturer.
      • The documented guidance for video timeout failures is to disable the identified driver or check with the manufacturer for driver updates.
    4. Make sure graphics-related software is fully up to date.
      • Update graphics components such as DirectX and OpenGL.
      • Make sure graphics-intensive apps and games are fully patched.
    5. Use Safe Mode to isolate whether the issue depends on normal graphics drivers.
      • Go to Settings > Update and Security > Recovery > Advanced startup.
      • Select Troubleshoot > Advanced Options > Startup Settings > Restart.
      • After restart, choose option 4, 5, or 6 for Safe Mode.
      • Safe Mode loads only minimum drivers and services, which helps isolate driver-related failures.
    6. Run Windows Memory Diagnostics.
      • In Control Panel, search for Memory.
      • Select Diagnose your computer's memory problems.
      • After the test, open Event Viewer and check the System log for MemoryDiagnostics-Results.
    7. Run the hardware diagnostics provided by the system manufacturer.
      • This is recommended for bug checks and hardware-related stop code scenarios.
    8. If any hardware was recently added or changed, confirm compatibility with the installed version of Windows.
      • Newly added or incompatible hardware can contribute to stop code and graphics timeout issues.
    9. If the issue continues, collect crash data for deeper analysis.
      • One accepted support path for LiveKernelEvent 141 is to gather System logs from Event Viewer.
      • Another accepted support path is to collect files from C:\Windows\Minidump for analysis.

    Because the crashes happen during games, the most likely first checks are the graphics driver, Device Manager status, and System log entries at the exact crash time.


    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.