Question Event Viewer is being spammed with 1001 ID logs ?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
May 24, 2025
35
1
35
Hello, my pc keeps getting spammed with event logs, i dont get any crashes and my GPU performs perfectly fine under stress & also when being benchmarked but it is still worrying . I won't post the logs because they're very large but I will comment the important parts;

They are Fault bucket , type 0 with event Name: LiveKernelEvent, under the event ID 1001. The problem signatures I get on P1 are 193, 1b8, and 1a8. They dont necessarily appear when an app crashes, or anything similar. Nothing happens at the time that these events pop (from what I know) however I am scared they'll eventually hinder performance. Any help? It's driving me a bit crazy and I'd rather fix it before it does something bad.

PC Specs
GPU: 4070 VENTUS 3X OC 12GB
CPU: i5-12600KF
MOBO: B760M GAMING X AX DDR4
RAM: Kingston FURY Beast DDR4 3200 MHz 16GB 2x8GB CL16
SSD: WD Black SN850X
PSU: ATX 750W THERMALTAKE SMART BM2
HDD: Seagate barracuda st1000dm010 1tb 3.5" sata3
MOUSE: Corsair Harpoon
KEYBOARD: Tactical Ozone Mini
 
Last edited:
what is parsec virtual usb driver for?
parsecvusba.sys Fri Aug 23 08:16:11 2024

note: you need to change memory dump type to kernel and provide memory.dmp file to figure out usb related issues and watchdog timeout issues.

dump could not read bios info/mahine info
Parsec virtual usb driver is for an app called Parsec where you can share control to your PC. Think anydesk but gaming. I guess its for controllers to connect to my PC when I share with my friends. I changed my memory dump type to kernel, but I'm not sure where to find memory.dmp.
 
what is parsec virtual usb driver for?
parsecvusba.sys Fri Aug 23 08:16:11 2024

note: you need to change memory dump type to kernel and provide memory.dmp file to figure out usb related issues and watchdog timeout issues.

dump could not read bios info/mahine info

parsec must be this:
https://parsec.app/pricing

you might just download microsoft autorun64.exe and disable or delete parsecvusba.sys
reboot and see if it was the cause of your issue.
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

if it does what it is supposed to do i can see it causing timeouts in the graphic kernel.
Autorun did not help, unfortunately. and i cant find memory.dmp
 
How are you searching for memory.dmp or using some wildcard search (e.g., "*.dmp")?

Starting drive/directory?

What windows or other results, if any, result?
im searching in the root directory, filtering both by files starting by M and files ending in .dmp. nothing seems to be available with the name "memory.dmp"