LiveKernelEvent 141

[Sunny]

Ok.
I whitelisted (excluded) within Virus & Threat protection:

• EasyAntiCheat.exe within C:\Program Files (x86)\EasyAntiCheat
• The Folder: C:\Program Files (x86)\Steam\steamapps\common\Wildlands\EasyAntiChe at
• The Game File: C:\Program Files (x86)\Steam\steamapps\common\Wildlands\GRW.exe

[HEADING=1]I also whitelisted EasyAntiCheat.exe within Firewall (inbound and outbound rule), verified my game files and repaired EAC with the setup.exe.[/HEADING]
Unfortunately, it still crashed shortly after loading into the game (approx 5 minutes).
There were no new minidump files unfortunately but I’ll attach a fresh MiniToolBox file in case it’s useful (although Event Viewer’s not recognizing the latest crashes as “errors” so MTB doesn’t necessarily provide the most up to date info).
I’ll also add one of the WatchDog.dmp files that accompany each of the thousands of LiveKernelEvents. My apologies if this is a useless addition…

Finally, here are some of the error reports. It’s still ranging from 20-50 LiveKernelEvents per second for a few seconds shortly before each crash. They’re 95 percent 141 with a few of these others mixed in:

---

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: a1000001
P2: 1
P3: 0
P4: 0
P5: 0
P6: 10_0_26100
P7: 0_0
P8: 768_1
P9:
P10:

---

Fault bucket 1668190160296570244, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Engine.exe
P2: 9.1.1.10162
P3: 67d30000
P4: KERNELBASE.dll
P5: 10.0.26100.4061
P6: c24bdd22
P7: c000041d
P8: 0015df24
P9:
P10:

---

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 1b8
P2: a
P3: 0
P4: 0
P5: 0
P6: 10_0_26100
P7: 0_0
P8: 768_1
P9:
P10:

---

Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff801935dd890
P4: ffffffffffffffff
P5: 0
P6: 10_0_26100
P7: 0_0
P8: 768_1
P9:
P10:

=====================================

Finally, I’d like to point out that I use an Azeron game-pad and reWASD (key remapper) for most gaming. I’m only thinking about them because reWASD is mentioned as a faulting application in the MTB.txt file. I’ve managed to replicate the crash both with the game-pad unplugged and with reWASD turned off but I haven’t yet tried to run the game with neither active. One of the error codes seems to pertain to USB devices but I’m not sure if it’s part of the cause or simply a symptom. Do you think there’s a chance that EAC is finding issue with either of these things or can I just ignore them?

I am legitimately curious about why EAC has this much agency over my PC. How does it even affect games that don’t utilize it? Helldivers uses a completely different anti cheat and it’s still getting affected… Just bonkers.
Sorry for the almost certainly overzealous volume of stuff in this update. I want to provide useful info but I’m too ignorant to really know what’s usefull or not.
I’ll endeavor to reduce the bombardment levels in future messages.

What would you suggest as my next steps?

[Sunny]

Ok.
I whitelisted (excluded) within Virus & Threat protection:

• EasyAntiCheat.exe within C:\Program Files (x86)\EasyAntiCheat
• The Folder: C:\Program Files (x86)\Steam\steamapps\common\Wildlands\EasyAntiChe at
• The Game File: C:\Program Files (x86)\Steam\steamapps\common\Wildlands\GRW.exe

[HEADING=1]I also whitelisted EasyAntiCheat.exe within Firewall (inbound and outbound rule), verified my game files and repaired EAC with the setup.exe.[/HEADING]
Unfortunately, it still crashed shortly after loading into the game (approx 5 minutes).
There were no new minidump files unfortunately but I’ll attach a fresh MiniToolBox file in case it’s useful (although Event Viewer’s not recognizing the latest crashes as “errors” so MTB doesn’t necessarily provide the most up to date info).
I’ll also add one of the WatchDog.dmp files that accompany each of the thousands of LiveKernelEvents. My apologies if this is a useless addition…

Finally, here are some of the error reports. It’s still ranging from 20-50 LiveKernelEvents per second for a few seconds shortly before each crash. They’re 95 percent 141 with a few of these others mixed in:

---

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: a1000001
P2: 1
P3: 0
P4: 0
P5: 0
P6: 10_0_26100
P7: 0_0
P8: 768_1
P9:
P10:

---

Fault bucket 1668190160296570244, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Engine.exe
P2: 9.1.1.10162
P3: 67d30000
P4: KERNELBASE.dll
P5: 10.0.26100.4061
P6: c24bdd22
P7: c000041d
P8: 0015df24
P9:
P10:

---

Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: 1b8
P2: a
P3: 0
P4: 0
P5: 0
P6: 10_0_26100
P7: 0_0
P8: 768_1
P9:
P10:

---

Fault bucket , type 0
Event Name: BlueScreen
Response: Not available
Cab Id: 0

Problem signature:
P1: 1e
P2: ffffffffc0000005
P3: fffff801935dd890
P4: ffffffffffffffff
P5: 0
P6: 10_0_26100
P7: 0_0
P8: 768_1
P9:
P10:

=====================================

Finally, I’d like to point out that I use an Azeron game-pad and reWASD (key remapper) for most gaming. I’m only thinking about them because reWASD is mentioned as a faulting application in the MTB.txt file. I’ve managed to replicate the crash both with the game-pad unplugged and with reWASD turned off but I haven’t yet tried to run the game with neither active. One of the error codes seems to pertain to USB devices but I’m not sure if it’s part of the cause or simply a symptom. Do you think there’s a chance that EAC is finding issue with either of these things or can I just ignore them?

I am legitimately curious about why EAC has this much agency over my PC. How does it even affect games that don’t utilize it? Helldivers uses a completely different anti cheat and it’s still getting affected… Just bonkers.
Sorry for the almost certainly overzealous volume of stuff in this update. I want to provide useful info but I’m too ignorant to really know what’s usefull or not.
I’ll endeavor to reduce the bombardment levels in future messages.

What would you suggest as my next steps?

[phillpower2]

About a month ago I started experiencing very frequent game crashes (reliably every 5-30 minutes in certain games) accompanied by many LiveKernelEvent errors showing up in event viewer (mostly 141 with a few 193/1e/1b8 in there too). Usually, the game just hangs or sends me to the desktop but occasionally, the crash will force my PC to automatically restart.

Some clarity first of all;

Software such as Windows can crash and when it does crash you get a BSOD and when enabled a crash dmp is generated, programs or games when they crash can on occasion close to the desktop but the computer will still be 100% functional.

Hardware failure such as a weak power supply and/or overheating are not software related and when a computer for example suddenly turns off, freezes or the screen goes black etc the behaviour should be described as the “computer shut down unexpectedly” or froze etc and not as having crashed as the latter implies a software issue as opposed to an obvious hardware issue when described properly.

Having the correct info means that helpers will not be looking for a software issue when the problem is clearly hardware related.

The latest crash dmp is dated May 5th 2025 and therefore so old as to be of any present help.

Unless an issue is recurring crash dmps more than a couple of days old are of no use I`m afraid, this because updates are constantly being released to address known issues and the issue that you have been having may well have been fixed by a recent update, if we do see the same cause days or weeks etc later we know that the issue has not been fixed so needs investigation.

Windows throws up errors in Event Viewer all the time, most of them are innocuous and can/should be ignored by novice users, any errors marked as Critical do need attention.

The stand out thing for me is the spec of RAM.

The RAM is not appropriate for your CPU, AMD state here up to 5600MHz/MT/s and if you have EXPO/XMP enabled the RAM will get auto OCd past what the CPU can handle and the PC will become unstable.

As a starting point;

Try restoring the MBs default factory settings in the BIOS, they are sometimes listed as one of the following " factory defaults" “most stable” or on newer boards “optimized” please note that if you have both the “most stable” and the “optimized” options in the BIOS you should choose the most stable" option as in this instance the “optimized” settings are a form of overclocking that can cause instability.

Save the new settings, exit the BIOS, restart the computer, test by using the computer as you normally would, post back with an update once you have done this.

[phillpower2]

About a month ago I started experiencing very frequent game crashes (reliably every 5-30 minutes in certain games) accompanied by many LiveKernelEvent errors showing up in event viewer (mostly 141 with a few 193/1e/1b8 in there too). Usually, the game just hangs or sends me to the desktop but occasionally, the crash will force my PC to automatically restart.

Some clarity first of all;

Software such as Windows can crash and when it does crash you get a BSOD and when enabled a crash dmp is generated, programs or games when they crash can on occasion close to the desktop but the computer will still be 100% functional.

Hardware failure such as a weak power supply and/or overheating are not software related and when a computer for example suddenly turns off, freezes or the screen goes black etc the behaviour should be described as the “computer shut down unexpectedly” or froze etc and not as having crashed as the latter implies a software issue as opposed to an obvious hardware issue when described properly.

Having the correct info means that helpers will not be looking for a software issue when the problem is clearly hardware related.

The latest crash dmp is dated May 5th 2025 and therefore so old as to be of any present help.

Unless an issue is recurring crash dmps more than a couple of days old are of no use I`m afraid, this because updates are constantly being released to address known issues and the issue that you have been having may well have been fixed by a recent update, if we do see the same cause days or weeks etc later we know that the issue has not been fixed so needs investigation.

Windows throws up errors in Event Viewer all the time, most of them are innocuous and can/should be ignored by novice users, any errors marked as Critical do need attention.

The stand out thing for me is the spec of RAM.

The RAM is not appropriate for your CPU, AMD state here up to 5600MHz/MT/s and if you have EXPO/XMP enabled the RAM will get auto OCd past what the CPU can handle and the PC will become unstable.

As a starting point;

Try restoring the MBs default factory settings in the BIOS, they are sometimes listed as one of the following " factory defaults" “most stable” or on newer boards “optimized” please note that if you have both the “most stable” and the “optimized” options in the BIOS you should choose the most stable" option as in this instance the “optimized” settings are a form of overclocking that can cause instability.

Save the new settings, exit the BIOS, restart the computer, test by using the computer as you normally would, post back with an update once you have done this.

[Sunny]

Thank you for the insights. Wording is certainly important and I’m greatful to get a concrete definition for each term.
I will try to use clearer vocabulary in future.

I’ll restore factory settings in the BIOS and see what the results are. I’d mistakenly thought that a few clean Memtest86 passes cleared the RAM of suspicion. There’s a lot to learn, that’s for sure.
If a new, slower RAM kit turns out to be the solution, that’d actually be so convenient. Fingers crossed.

Thanks again.

[Sunny]

Thank you for the insights. Wording is certainly important and I’m greatful to get a concrete definition for each term.
I will try to use clearer vocabulary in future.

I’ll restore factory settings in the BIOS and see what the results are. I’d mistakenly thought that a few clean Memtest86 passes cleared the RAM of suspicion. There’s a lot to learn, that’s for sure.
If a new, slower RAM kit turns out to be the solution, that’d actually be so convenient. Fingers crossed.

Thanks again.

[phillpower2]

If a new, slower RAM kit turns out to be the solution, that’d actually be so convenient.

There may be something else causing or contributing to this but when troubleshooting you correct the obvious first and if not the cure you look elsewhere, the solution for the present RAM would be to manually OC it to 5600MTs so no new RAM is required.

Just a fwiw, the LiveKernelEvent 141 can be a tricky one to crack as it can be hardware or software related, two such examples, something overheating and causing a shutdown while Windows was still running would cause the error and any driver or software conflict that caused a shutdown or restart before Windows was correctly shutdown would likewise cause an LiveKernelEvent 141 error.

You are welcome btw

[phillpower2]

If a new, slower RAM kit turns out to be the solution, that’d actually be so convenient.

There may be something else causing or contributing to this but when troubleshooting you correct the obvious first and if not the cure you look elsewhere, the solution for the present RAM would be to manually OC it to 5600MTs so no new RAM is required.

Just a fwiw, the LiveKernelEvent 141 can be a tricky one to crack as it can be hardware or software related, two such examples, something overheating and causing a shutdown while Windows was still running would cause the error and any driver or software conflict that caused a shutdown or restart before Windows was correctly shutdown would likewise cause an LiveKernelEvent 141 error.

You are welcome btw

[Sunny]

There may be something else causing or contributing to this but when troubleshooting you correct the obvious first and if not the cure you look elsewhere, the solution for the present RAM would be to manually OC it to 5600MTs so no new RAM is required.

Just a fwiw, the LiveKernelEvent 141 can be a tricky one to crack as it can be hardware or software related, two such examples, something overheating and causing a shutdown while Windows was still running would cause the error and any driver or software conflict that caused a shutdown or restart before Windows was correctly shutdown would likewise cause an LiveKernelEvent 141 error.

You are welcome btw

[Sunny]

There may be something else causing or contributing to this but when troubleshooting you correct the obvious first and if not the cure you look elsewhere, the solution for the present RAM would be to manually OC it to 5600MTs so no new RAM is required.

Just a fwiw, the LiveKernelEvent 141 can be a tricky one to crack as it can be hardware or software related, two such examples, something overheating and causing a shutdown while Windows was still running would cause the error and any driver or software conflict that caused a shutdown or restart before Windows was correctly shutdown would likewise cause an LiveKernelEvent 141 error.

You are welcome btw

[phillpower2]

Can I ask that you do not quote every reply as we have to read the full post to make sure nothing gets missed, thanks.

[phillpower2]

Can I ask that you do not quote every reply as we have to read the full post to make sure nothing gets missed, thanks.

[Sunny]

OK, so. I tried factory default RAM speed (4800Mhz) and the game crashed and produced the LiveKernelEvents again. The time before the crash was consistent with what I’d experienced with my prior RAM settings. That suggests that the RAM isn’t the culprit but I suppose it’s not conclusive.

I’ll set it to 5600Mhz anyway but look to other solutions next. It was worth a shot (I won’t write it off completely though).

[Sunny]

OK, so. I tried factory default RAM speed (4800Mhz) and the game crashed and produced the LiveKernelEvents again. The time before the crash was consistent with what I’d experienced with my prior RAM settings. That suggests that the RAM isn’t the culprit but I suppose it’s not conclusive.

I’ll set it to 5600Mhz anyway but look to other solutions next. It was worth a shot (I won’t write it off completely though).

[Sunny]

Oh shoot. I’m really sorry.
I hadn’t even realized that I’d been quoting the previous messages. Not sure what I even did to make that happen.
I’m certainly going to make a donation. You guys have already proven vastly more helpful than my weeks of research and phone calls.