[SOLVED] LiveKernelEvent 1001 - - - I'm not sure what to do about this ?

[Zerquetch]

I have a few of these in my event log that I just started going thru due to a virus (I suppose) that killed all my USB ports:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

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

Attached files:
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20250415-0256.dmp
\\?\C:\WINDOWS\SystemTemp\WER-5353078-0.sysdata.xml
\\?\C:\WINDOWS\LiveKernelReports\WATCHDOG-20250415-0256.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.8248d192-8c80-4122-998d-34778983aa81.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5a950362-3a30-4b4b-a212-384485fecf93.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9843f108-38d7-4149-ae23-e2d5437f01db.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1c76ad57-c600-404c-84a6-7e5abefc4b7a.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Kernel_141_39a0f8648824b76b613449e865eda58c7e482040_00000000_dfefbb3b-a19e-4c68-8854-cccee5484e34

Analysis symbol:
Rechecking for solution: 0
Report Id: dfefbb3b-a19e-4c68-8854-cccee5484e34
Report Status: 2049
Hashed bucket:
Cab Guid: 0

I've tried to gain ownership of the reportqueue\kernal### dir to no avail.
WTH do I glean from this, and can this be (does it need to be) fixed?

 

[johnbl]

windows error reporting tried to debug a problem on your machine and sent the results back to microsoft.
I am guessing they detected a bug in your usb, sent diagnostic info back to microsoft then rebooted your machine.
Microsoft generally will apply a fix but they will not if the fix requires a bios update.
First fix attempt would be to go to your motherboard vendors website and update your bios and cpu chipset drivers. If this is a older machine also look for usb drivers for add on USB chipsets.

often these chipsets had bugs that required custom drivers to fix.
(microsoft will not install these custom drivers since they require bios and driver from motherboard vendor to match)

problem happened on my friends old machine from 2015, they did not notice the failed ports but would just complain about the rebooting of the machine.

 

[johnbl]

note: you do not want to take ownership of the reports. the system has ownership. You have read rights which means you can copy the reports to a different location but can not move the reports to a different location. You have to copy them (read rights) move would require write rights since the file would be deleted from the current location.

 

[Zerquetch]

note: you do not want to take ownership of the reports. the system has ownership. You have read rights which means you can copy the reports to a different location but can not move the reports to a different location. You have to copy them (read rights) move would require write rights since the file would be deleted from the current location.

Yeah, this relic is from all the way back in 2022 with a 12th gen i7 with a new 9070xt, lol
I found on reboot that I had kbd/mouse in the bios so rebooted into the Windows 'How fkd am I" screen
Tried to repair - nope
Tried cloud based repair - Gold star!
Minimal loss of files

I did roll back the recent Win 11 update and regained some functionality then in tandem with the BIOS/Chipset update, seemed to do the trick.
I'm so used to having windbg running, permissions are usually someone else's issue.
Found a chunk of code called Event Log Explorer that adds a little extra and restored all the other diag tools so I can monitor things a little better but all the prep in the world seems insignificant when when the nuke goes off and you can only silently scream "Oh Fk!"
4th Virus in 40 years. Not bad. Never good, but I have a Fallout Shelter, lol

Thanks for the shove in the right direction!