Share via

Multiple Windows Error Reporting 1001 in Event Viewer

Anonymous
2025-01-26T22:00:54+00:00

Hello,

I've just noticed that my event viewer has been flooded with the same event: Windows Error Reporting.

Should also note I'm not getting any bluescreens, or abnormal crashes. Games are running mostly fine (Diablo 4 crashed earlier today which lead me to running the memory checker which reported no issues)

My specs: i7 9700f

RTX 2080 super (Driver: 566.36 - Nvidia App installed)

MSI z390 gaming Edge AC

x2 g.skill 16gb ddr4

3 drives - 2 samsung ssds (One is a 980 pro 1tb, the other is a 970 evo plus 500gb)

I have installed a new Wifi card (and disabled my mobo's built in wifi) and added a second monitor (Small little KYY monitor connected via hdmi to my card), but this event seems to be going back quite some time before those changes.

The earliest I see it pop up was back on 12/31/24. It appears that, at first it was only popping up a few times but around 1/6/25 it was doing it more and more frequently. Now it's all over the event viewer, well over 100 reports today alone.

I'm not seeing anything weird with CPU/GPU temps, all normal at idle and while gaming. GPU does run a bit hotter with the second screen but from what I can tell, that's expected (30-35 idle without second monitor, 40-45 with.)

Also I updated my bios around the time I hooked up the second monitor, no issues there, and again, long after these events started appearing.

As far as I can tell all my drivers are up to date and running fine.

That's all the info I could think to include, any help would be greatly appreciated.

All the events have the same ID's and what not.

Event ID 1001

Fault bucket , type 0

Event Name: LiveKernelEvent

Response: Not available

Cab Id: 0

Problem signature:

P1: 193

P2: 80e

P3: ffffd50df6314080

P4: ffffe6877780cd60

P5: 0

P6: 10_0_26100

P7: 0_0

P8: 768_1

P9: 

P10: 

Attached files:

\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20250122-2021.dmp

\?\C:\WINDOWS\SystemTemp\WER-19367031-0.sysdata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.94cbc73e-26c8-4573-aa60-972027d3bce9.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.3c89e6eb-f110-4231-976e-b8a5b41bde0d.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.09f8f17f-51b8-42b1-997a-22212ef24ae0.tmp.txt

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.175e7fe5-6030-4446-bc3a-6ca1f41ff0e1.tmp.xml

These files may be available here:

\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_193_ab5379fa9a6525638a6d68e9dbe7e1cdd6b17_00000000_51731a4d-c058-4d7b-a411-0d9dd425246f

Analysis symbol: 

Rechecking for solution: 0

Report Id: 51731a4d-c058-4d7b-a411-0d9dd425246f

Report Status: 2049

Hashed bucket: 

Cab Guid: 0

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2025-01-28T09:21:09+00:00

    Thanks for the response!

    I've gone through your list and done most everything. Still need to do MemTest86, just haven't had a full night to let it run.

    I've checked all my drivers and everything is up to date, I've purged and reinstalled all my peripherals.

    Stressed the CPU and GPU with no issues. Even dusted and replaced the thermal paste while I was at it.

    Checked the power settings and PCI-Express was already Off.

    BIOS is up to date.

    I'm not quite sure what triggers the error but it is still showing up.

    I've reached the limit of my knowledge and know how so can I ask which dump files and logs exactly you need?

    Thanks again!

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2025-01-27T10:34:45+00:00

    Dear Fuzzy_Knightmare,

    Welcome to the Microsoft Community

    It sounds like you are experiencing consistent Windows Error Reporting (WER) events related to LiveKernelEvent in your Event Viewer. These events can be indicative of underlying hardware or driver issues, even if you aren't experiencing visible system instability like blue screens.

    Let's go through a comprehensive set of steps to diagnose and potentially resolve this problem.

    Check for Hardware Issues

    Memory Check: You've already run a memory checker, which is good. You can also use MemTest86 for a more thorough test. Download MemTest86, create a bootable USB, and let it run overnight.

    Stress Test GPU and CPU: Use tools like FurMark for GPU stress testing and Prime95 for CPU stress testing. Monitor the temperatures to ensure they remain within safe limits.

    Update and Revert Drivers: Ensure all drivers are up to date, especially the graphics driver, chipset driver, and network drivers. You can download and install the latest drivers directly from the manufacturer’s website.

    Check for USB Device Issues: KernelEvent code 193 is sometimes associated with USB devices. Disconnect all USB devices except the essential ones and see if the issue persists. This will help identify if a particular device or port is causing the issue.

    Power Settings: Adjust power settings for USB and PCI-Express devices. Go to Control Panel > Power Options > Change plan settings > Change advanced power settings. Under USB settings and PCI-Express, set the options to Disabled or Off.

    BIOS and Firmware Updates: Updating the BIOS can sometimes resolve hidden hardware compatibility issues. Go to the MSI support page for your motherboard, download the latest BIOS update, and follow the instructions to flash your BIOS.

    If the problem persists, share the dump file and detailed logs in a reply so I can investigate more leads.

    Best Regards,

    Martin | Microsoft Community Support Specialist

    0 comments No comments