Windows 10: LiveKernelEvent 117 & 141

Discus and support LiveKernelEvent 117 & 141 in Windows 10 Gaming to solve the problem; My PC is having critical errors whereby the screen flickers and after which, the computer often reboots. On reliability monitor is gives a couple of... Discussion in 'Windows 10 Gaming' started by Ak 0897, Apr 26, 2023.

  1. AK 0897
    Ak 0897 Win User

    LiveKernelEvent 117 & 141


    My PC is having critical errors whereby the screen flickers and after which, the computer often reboots. On reliability monitor is gives a couple of critical errors, both code 117 and 141. The PC is only a couple months old, drivers have been reinstalled, memory check complete, burn-in test complete with no faults as to the hardware. I am stumped as to what to do. So far it only occurs when I am on games even lobbies of some games which, prior to these errors ran perfectly. I have no clue what to do or where to go from here. Any help whatsoever would be amazing and would mean the world.

    :)
     
    Ak 0897, Apr 26, 2023
    #1
  2. WESSEL VAN STUIJVENBERG
    Wessel van Stuijvenberg Win User

    Livekernelevents 117 and 141

    Hi,

    I have a brand new gaming setup and i keep getting Livekernelevents 117 and 141 in several games.

    Not all games but i saw this in 3 games already.

    I tried modifying the TDR but this only resolved the issue for 1 game.

    I also tried to stress test my GPU and CPU to see if they are running correctly. No problems were found.

    The temp is also OK. This problem will arise even when playing on very low settings for my system.

    Does anybody know what to do?

    My system: MSI A320M-A PRO MAX (MS-7C52) Performance Results - UserBenchmark

    Kind regards,

    Wessel

    Lastest events:

    Description

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

    Problem signature

    Problem Event Name: LiveKernelEvent

    Code: 117

    Parameter 1: ffffc38ed7baf010

    Parameter 2: fffff80175f2d740

    Parameter 3: 0

    Parameter 4: b84

    OS version: 10_0_19041

    Service Pack: 0_0

    Product: 256_1

    OS Version: 10.0.19041.2.0.0.256.48

    Locale ID: 8192

    &

    Description

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

    Problem signature

    Problem Event Name: LiveKernelEvent

    Code: 141

    Parameter 1: ffffae0a467d1010

    Parameter 2: fffff8005964d740

    Parameter 3: 0

    Parameter 4: 1bec

    OS version: 10_0_19041

    Service Pack: 0_0

    Product: 256_1

    OS Version: 10.0.19041.2.0.0.256.48

    Locale ID: 8192
     
    Wessel van Stuijvenberg, Apr 26, 2023
    #2
  3. RSHAM123
    rsham123 Win User
    LiveKernelEvent 141 and 117 BSOD

    Can someone please help me. I've been getting the BSOD on a freshly new build for the past month or so.

    Description

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

    Problem signature

    Problem Event Name: LiveKernelEvent

    Code: 141

    Parameter 1: ffffb0017d88e460

    Parameter 2: fffff8053df609f0

    Parameter 3: 0

    Parameter 4: 4c4

    OS version: 10_0_19041

    Service Pack: 0_0

    Product: 256_1

    OS Version: 10.0.19041.2.0.0.256.48

    Locale ID: 1033

    Description

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

    Problem signature

    Problem Event Name: LiveKernelEvent

    Code: 117

    Parameter 1: ffffb00174f33460

    Parameter 2: fffff8053df609f0

    Parameter 3: 0

    Parameter 4: 0

    OS version: 10_0_19041

    Service Pack: 0_0

    Product: 256_1

    OS Version: 10.0.19041.2.0.0.256.48

    Locale ID: 1033

    I am running the following specs:

    https://pcpartpicker.com/list/XkTbJb
     
    rsham123, Apr 26, 2023
    #3
  4. MKLIM95
    MKlim95 Win User

    LiveKernelEvent 117 & 141

    LiveKernelEvent 141 and 117, BSOD with FAULTY_HARDWARE_CORRUPTED_PAGE

    Original Title: LiveKernelEvent 141 and 117

    I was in a skype call and had a few browser tabs open and I got a BSOD with FAULTY_HARDWARE_CORRUPTED_PAGE as the message. I am running a crossfire setup with two R9 380 cards. Up to date drivers as of 1/2/16. System details, MSinfo32 output, and .dmp file
    are available at the google drive link below. In the reliability manager there are several 141 and 117 errors with the same timestamp. One of each is included in this message below. I cannot reliably recreate the problem, but I also have 141 and 144 error
    codes from GTAV when that crashed to a black screen a couple times this week. A 144 code is also posted here. Any ideas?

    https://drive.google.com/file/d/0B5G4ZhKWdfoZWU9pYW1sZzcwdUE/view?usp=sharing

    Source

    Windows

    Summary

    Hardware error

    Date

    ‎1/‎2/‎2016 5:44 PM

    Status

    Report sent

    Description

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

    Problem signature

    Problem Event Name: LiveKernelEvent

    Code: 141

    Parameter 1: ffffe000297ff4c0

    Parameter 2: fffff801516fce98

    Parameter 3: 0

    Parameter 4: 27e4

    OS version: 10_0_10586

    Service Pack: 0_0

    Product: 768_1

    OS Version: 10.0.10586.2.0.0.768.101

    Locale ID: 1033

    Extra information about the problem

    Bucket ID: LKD_0x141_Tdr:6_IMAGE_atikmpag.sys

    Source

    Windows

    Summary

    Hardware error

    Date

    ‎1/‎2/‎2016 5:44 PM

    Status

    Report sent

    Description

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

    Problem signature

    Problem Event Name: LiveKernelEvent

    Code: 117

    Parameter 1: ffffe0002b0e63c0

    Parameter 2: fffff801516fce98

    Parameter 3: 0

    Parameter 4: 0

    OS version: 10_0_10586

    Service Pack: 0_0

    Product: 768_1

    OS Version: 10.0.10586.2.0.0.768.101

    Locale ID: 1033

    Extra information about the problem

    Bucket ID: LKD_0x117_Tdr:9_IMAGE_atikmpag.sys

    Source

    Windows

    Summary

    Hardware error

    Date

    ‎1/‎1/‎2016 7:43 PM

    Status

    Report sent

    Description

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

    Problem signature

    Problem Event Name: LiveKernelEvent

    Code: 144

    Parameter 1: 1004

    Parameter 2: ffffd00026fb5970

    Parameter 3: 0

    Parameter 4: 0

    OS version: 10_0_10586

    Service Pack: 0_0

    Product: 768_1

    OS Version: 10.0.10586.2.0.0.768.101

    Locale ID: 1033

    Extra information about the problem

    Bucket ID: LKD_0x144_CONTEXT_ERROR_AFTER_STOP_USBXHCI!TelemetryData_CreateReport_VEN_1B6F_DEV_7052_REV_00_FW_1
     
    MKlim95, Apr 26, 2023
    #4
Thema:

LiveKernelEvent 117 & 141

Loading...

  1. LiveKernelEvent 117 & 141 - Similar Threads - LiveKernelEvent 117 141

  2. LiveKernelEvent 141, 117, a1000001

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 141, 117, a1000001: Witam mam problem z komputerem zawiesza się zarówno pod obciążeniem jak i bez, czasami zawiesi się na pare sekund a czasami wymaga restartu. Błąd pojawia się zarówno na GTX 1060 6gb oraz RX590 fatboy. Poniżej wrzucam kody z historii niezawodności:ŹródłoWindowsPodsumowanieBłąd...

  3. LiveKernelEvent 141, 117, a1000001

    in Windows 10 Gaming
    LiveKernelEvent 141, 117, a1000001: Witam mam problem z komputerem zawiesza się zarówno pod obciążeniem jak i bez, czasami zawiesi się na pare sekund a czasami wymaga restartu. Błąd pojawia się zarówno na GTX 1060 6gb oraz RX590 fatboy. Poniżej wrzucam kody z historii niezawodności:ŹródłoWindowsPodsumowanieBłąd...

  4. LiveKernelEvent 141, 117, a1000001

    in Windows 10 Software and Apps
    LiveKernelEvent 141, 117, a1000001: Witam mam problem z komputerem zawiesza się zarówno pod obciążeniem jak i bez, czasami zawiesi się na pare sekund a czasami wymaga restartu. Błąd pojawia się zarówno na GTX 1060 6gb oraz RX590 fatboy. Poniżej wrzucam kody z historii niezawodności:ŹródłoWindowsPodsumowanieBłąd...

  5. LiveKernelEvent 117 & 141

    in Windows 10 Software and Apps
    LiveKernelEvent 117 & 141: My PC is having critical errors whereby the screen flickers and after which, the computer often reboots. On reliability monitor is gives a couple of critical errors, both code 117 and 141. The PC is only a couple months old, drivers have been reinstalled, memory check...

  6. LiveKernelEvent 117 & 141

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 117 & 141: My PC is having critical errors whereby the screen flickers and after which, the computer often reboots. On reliability monitor is gives a couple of critical errors, both code 117 and 141. The PC is only a couple months old, drivers have been reinstalled, memory check...

  7. LiveKernelEvent 141, 117

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 141, 117: So recently I started getting error on my PC. I have clean installed Windows and are still getting the same issue.SourceWindows Summary Hardware failure Date08. 05. 2021 19:46 Status Report sent Description A hardware problem caused Windows to stop working properly. Problem...

  8. LiveKernelEvent 117 and 141

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 117 and 141: Hello, My PC turns black screen, the GPU fan works at max speed and I can still hear the sound of the PC but no signal to monitor when I try to start Overwatch or Apex Legend or sometimes played a while. And if it turns black screen sometimes I won't be able to turn the...

  9. LiveKernelEvent 117 & 141

    in Windows 10 BSOD Crashes and Debugging
    LiveKernelEvent 117 & 141: My PC is having critical errors whereby the screen flickers and after which, the computer often reboots. On reliability monitor is gives a couple of critical errors, both code 117 and 141. The PC is only a couple months old, drivers have been reinstalled, memory check...

  10. Livekernelevents 117 and 141

    in Windows 10 BSOD Crashes and Debugging
    Livekernelevents 117 and 141: Hi, I have a brand new gaming setup and i keep getting Livekernelevents 117 and 141 in several games. Not all games but i saw this in 3 games already. I tried modifying the TDR but this only resolved the issue for 1 game. I also tried to stress test my GPU and CPU to...