Windows LiveKernelEvent Errors

5ubsonic · Friday at 14:49

Hi all, I bought a wireless mouse (Endgame Gear OP1we) from OCUK a while ago and a few times a day at random times the mouse cursor briefly freezes for a second before continuing as normal. So far I haven't got to the bottom of the problem despite trying numerous things but while investigating I noticed a string of 6 LiveKernelEvent errors in Event Viewer which I'm now trying to diagnose in case they are related in some way to the mouse issue.

After booting into Windows I get the following 6 LiveKernelEvent errors in a row, and then the same again exactly 3 minutes later. I'll post one error in full but the P1 codes for each are:

141
117
1a8
1b8
117
a1000005

They aways occur immediately after each other in that order, with the same time stamp.

Here's the full error report from the last one in the sequence - it's the only one that mentions AMD_WATCHDOG in the attached files section which makes me wonder if it's realted to my CPU (Ryzen 7600X) or GPU (RX 6600):

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

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

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\AMD_WATCHDOG\AMD_WATCHDOG-20250910-1310.dmp
\\?\C:\WINDOWS\SystemTemp\WER-4288578-0.sysdata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.f196a071-61b1-4a40-968a-7d9615e58fdc.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.7d00ce40-44ce-48af-9c56-c4763c4a0c02.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.2cb7c99f-63cb-4ec7-8060-8f19bbff44b5.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4b98ddd2-f6f1-44f3-8356-bba4b6d8a85f.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_a1000005_3c2f1d51d8c832b86164f5d651ad5838b466557_00000000_b03b57cd-baf8-487e-aa4f-c8fee4c81efa

Analysis symbol:
Rechecking for solution: 0
Report Id: b03b57cd-baf8-487e-aa4f-c8fee4c81efa
Report Status: 2051
Hashed bucket:
Cab Guid: 0

Any ideas on the cause of these? So far I've tried the following without success:

Updated to the latest ASRock BIOS (I'm using the B650M-HDV/M.2 mobo)
Reset GPU tuning to default settings in Adrenalin as I was using an undervolt
Reset memory to default non-EXPO as I was using EXPO settings (DDR5 6000) with Buildzoid's "low effort" timings
Reset CPU to default settings as I was using a performance preset with an undervolt
Run DDU and re-installed AMD's GPU drivers

None of this made any difference. The exact same errors keep showing.

Any ideas anyone? I've searched online and found lots of people with the same error codes but can't seem to find a fix.

Note that I'm not having any other problems like crashes while gaming etc - the only issue is this occasional brief mouse freeze and I'm pretty sure that only happens when using it wirelessly - so maybe I should just ignore these errors?

Tetras · Friday at 14:52

5ubsonic said:
so maybe I should just ignore these errors?

Yeah. Tell me if I'm missing something, but why are you doing all these troubleshooting steps? You didn't have a problem before the mouse, so just send the mouse back?

5ubsonic · Friday at 14:58

Tetras said:
Yeah. Tell me if I'm missing something, but why are you doing all these troubleshooting steps? You didn't have a problem before the mouse, so just send the mouse back?

Fair point. The errors may have been there before the mouse, I just had no reason to look in Event Viewer before that.

I did contact Endgame Gear directly who gave a me a list of troubleshooting things to test, none of which helped. I still need to do their last one which was to try the mouse on a different PC or laptop. I'm just waiting to borrow a laptop from a friend for that.

I guess I could send the mouse back but I don't have a spare at the moment so was hoping to avoid that, but yes I'll be doing that once I've tested with another machine (assuming the problem still happens).

Murphy · Friday at 16:31

They're all related to the GPU/GPU driver, it's resetting the driver but that's just Windows trying to recover from the driver, assumedly timing out.

If you wanted to investigate beyond what's logged in event viewer you could open the .wer file in notepad (should've saved them to sub folders of C:\WINDOWS\LiveKernelReports) and/or download...

Resplendence Software - WhoCrashed, automatic crash dump analyzer

WhoCrashed, automatic crash dump analyzer for Windows

www.resplendence.com

To get some details from the .dmp files

It's doubtful that anything other than it being an issue with the GPU driver will be revealed but you never know.

I assume you've installed the chipset drivers?

5ubsonic · Friday at 21:16

Murphy said:
They're all related to the GPU/GPU driver, it's resetting the driver but that's just Windows trying to recover from the driver, assumedly timing out.

If you wanted to investigate beyond what's logged in event viewer you could open the .wer file in notepad (should've saved them to sub folders of C:\WINDOWS\LiveKernelReports) and/or download...

Resplendence Software - WhoCrashed, automatic crash dump analyzer

WhoCrashed, automatic crash dump analyzer for Windows

www.resplendence.com

To get some details from the .dmp files

It's doubtful that anything other than it being an issue with the GPU driver will be revealed but you never know.

I assume you've installed the chipset drivers?

Thanks, I downloaded WhoCrashed and it gave the following from August 5th, but nothing else:

On Tue 05/08/2025 11:58:57 your computer crashed or a problem was reported

Crash dump file: C:\WINDOWS\LiveKernelReports\WATCHDOG-20250805-1158.dmp (Kernel memory dump)
Bugcheck code: 0x141(0xFFFF9E89019A4050, 0xFFFFF800A9C17E40, 0x0, 0xFFFF9E88F14C80C0)
Bugcheck name: VIDEO_ENGINE_TIMEOUT_DETECTED
Driver or module in which error occurred: dxgkrnl.sys (dxgkrnl!TdrCollectDbgInfoStage1+0xD29)
File path: C:\WINDOWS\System32\drivers\dxgkrnl.sys
Description: DirectX Graphics Kernel
Product: Microsoft® Windows® Operating System
Company: Microsoft Corporation
Bug check description: This indicates that one of the display engines failed to respond in timely fashion.
Analysis: This is a video related crash. A DirectX driver was identified on the stack. Since there is no other responsible driver detected, it is suggested that you look for an updated driver for your graphics hardware. It's also possible that your graphics hardware was non-functional or overheated.

Murphy · Saturday at 00:07

Sadly that just confirms what we already knew, that the GPU driver is timing out and being reset by Windows. Other than the usual update drivers, overheating/unstable OC / undervolt, a third party overlay (Steam, discord, etc), the sort of things you seem to have already tried I've got nothing more to suggest.

You could try running a diagnostic startup via msconfig one time just to see if you get the same events reported in the event log, but I'll be honest if you do or don't i wouldn't know what more to suggest outside of the usual troubleshooting steps for GPU related issues.