Share via

Recurring "LiveKernelEvent 1b8" hardware error (Watchdog Timeout)

Furkan Aka 20 Reputation points
2026-04-11T21:34:24.3666667+00:00

Hi,

I am experiencing an issue where my system encounters a hardware error, documented in the Reliability Monitor as LiveKernelEvent 1b8 and 141.

Symptoms: Black Screen & Signal Loss: While gaming, after some time, the monitor suddenly goes black and displays a "No Signal" (DPI/DisplayPort No Signal) message. Fan Ramp-up: Immediately after the screen goes black, the GPU fans start spinning at 100% maximum speed (extremely loud). Audio Behavior: Background audio (game sounds or music) continues for a short while, but then eventually cuts off or the system hangs completely. System Power State: The PC remains powered on (lights and fans are active), but it becomes unresponsive, requiring a hard manual reset.

Reliability Monitor Log Analysis: I have checked my Reliability Monitor history and found a recurring pattern of critical events. Every "Hardware Error" (LiveKernelEvent 1b8) is accompanied by the simultaneous crashing of the following processes:

  • NVIDIA App (Container for GPU drivers)
  • MicrosoftSecurityApp.exe
  • cmw_srv.exe

The crashes occur in clusters (e.g., at 23:10, 22:30, and 18:59 on 11.04.2026). This suggests that the GPU driver is failing under load or due to a TDR (Timeout Detection and Recovery) issue, causing dependent system applications to terminate unexpectedly.

Additional System Context:

  • GPU: NVIDIA RTX3050
  • Driver Version: VERSİON 595.97 Released: Tue, Mar 24, 2026
  • SFC Scan Result: Passed (No integrity violations).1

Problem Details:

  • Problem Event Name: LiveKernelEvent
  • Code: 1b8
  • Parameter 1: a
  • OS Version: 10.0.26200.2.0.0.256.48 (Windows 11 Insider Preview)
  • Related files: WATCHDOG4400-20260411-2229.dmp
    WERInternalMetadat.xml
    memory.csv
    sysinfo.txt
    WERInternalRequest.xml

2

What I have tried so far:

  1. I ran the sfc /scannow command as an administrator. The result was: "Windows Resource Protection did not find any integrity violations."
  2. I ran the DISM RestoreHealth command as an administrator. The result was: "The component store is repairable. The operation completed successfully."
  3. The system seems to recover itself, but the error log persists in the reliability history.

Could you please help me identify the root cause of this "1b8" error? Is it related to a specific driver (GPU/Network) or a known issue in this Windows build (26200)?

Thank you.

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

Answer accepted by question author

  1. Ivan B 109.5K Reputation points Independent Advisor
    2026-04-11T22:05:40.5233333+00:00

    Hi ,

    If it is a laptop or desktop, if possible, could you provide the laptop model or your desktop configuration?

    Access the c:\windows\minidump folder, copy the files to your desktop, then upload them to OneDrive or Google Drive and post the link here for analysis.

    Thanks

    1 person found this answer helpful.

Answer recommended by moderator

  1. Furkan Aka 20 Reputation points
    2026-04-14T07:05:36.7133333+00:00

    Hi Ivan,

    I've managed to completely resolve the LiveKernelEvent 1b8 error and the black screen issues I was having during gaming. I wanted to share the steps I took to fix it:

    1. Power Flush (Discharging Static Electricity):

    To stop the USB port disconnects and general system instability, I unplugged the power cable and held down the power button for about 30 seconds. This successfully discharged the static electricity (ghost charge) in the system. Since doing this, the USB errors and the momentary mouse freezes have completely disappeared.

    2. GPU Maintenance (Thermal Paste):

    I noticed in OCCT overview that my card was hitting 79°C - 80°C in the game and immediately going into protection mode, cutting the display. I opened up my Zotac RTX 3050 Twin Edge and saw that the thermal paste had completely dried out. I replaced it with a high-quality thermal paste and put everything back together carefully.

    3. Latest Test Results:

    Temperatures: Before, the card was struggling at 80°C even with restricted settings. Now, with no restrictions (83°C limit and 100% power), it stays stable at around 74°C under full load.

    Performance: The GPU clock is now running smoothly between 1987 MHz and 2055 MHz without any fluctuations or stuttering.

    Fans: The fans used to go crazy at 100% speed; now they stay at a quiet and efficient 1800-1850 RPM under full load.

    The root causes were dried-out thermal paste leading to overheating and static electricity buildup on the motherboard. The system is now running like clockwork with no black screens or freezes.

    Thanks for the support!

    2 people found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Q&A Assist
    2026-04-11T21:34:47.51+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The symptoms and the LiveKernelEvent entries with WATCHDOG dump files match a GPU timeout/TDR-type condition under load rather than a general OS corruption issue.

    From the context provided, similar watchdog and TDR-related problems are typically caused by:

    • Faulty or unstable graphics drivers
    • Graphics stack issues in a specific Windows build
    • Underlying hardware problems (GPU, VRAM, or power delivery)

    For this type of issue, the recommended path is:

    1. Treat it as a graphics/TDR problem
      • Bug checks such as VIDEO_TDR_TIMEOUT_DETECTED (0x117) are explicitly associated with GPU timeouts. The documented guidance is to focus on the graphics driver and stack.
    2. Update or roll back the GPU driver
      • If a driver is implicated, disable it or check with the manufacturer for an updated or alternative version. In practice this means:
        • Cleanly reinstalling the NVIDIA driver, or
        • Rolling back to a previous stable driver version if the issue started after a recent update.
    3. Ensure all graphics-related components are current
      • Verify that DirectX/OpenGL components and any graphics‑intensive applications (games) are fully patched. Out-of-date graphics software can contribute to TDRs.
    4. Validate hardware and memory
      • Run the Windows Memory Diagnostics tool to rule out RAM issues that can surface as watchdog/TDR failures.
      • Run any OEM‑supplied hardware diagnostics for the GPU and system to check for hardware faults.
    5. Use Safe Mode for isolation
      • Because Safe Mode loads only minimal drivers, it can help confirm whether third‑party graphics drivers or services are involved. If the system is stable in Safe Mode under similar conditions, that further points to the display driver or related software.
    6. If blue screens or additional stop codes appear
      • Use the stop code information and the associated dump (for example, VIDEO_TDR_TIMEOUT_DETECTED or other watchdog‑related codes) with tools such as !analyze in the debugger to pinpoint the failing module, as recommended in the watchdog/TDR documentation.

    Given the Insider Preview build and the clustering of GPU‑related crashes, the most likely root cause is interaction between the current NVIDIA driver and the graphics stack in this Windows build, but hardware should still be validated using the above diagnostics.


    References:

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.