I noticed something weird about my Windows 10 system log. It seems ever since last May I have got several "Critical" Kernel errors, event ID 41. So that usually indicates BSOD, system was shut down unexpectedly. But the thing is, I can't remember getting a single BSOD.
I've been just using it, never noticed anything until I saw the logs, checked them for other reason.
Also it seems I get kernel boot event 29 occasionally.
For example last time this was logged, I just installed some WIndows updates and normally rebooted. Didn't notice anything weird.
Also it seems even though I've set my Windows to save minidump, no dump can be found, the directory is empty (I have hidden files visible).
I also ran memory diagnostic, no errors.
Also I tried with different set. First I used CMK16GX4M2A2666C16, then I installed the current one and it seems I've got it once after the change and never noticed before checking the log. Happened at 7 PM, I would have noticed if it would have rebooted or something as I had everything open, up and running.
Can this be an error of a kind, I mean can it sometimes interpret that Windows was not shut down correctly when it in fact was? Any ideas how to solve what is causing it, and as I haven't noticed anything weird, should I even care?
Specs:
Ryzen 5 2400G
ASUS B350-M TUF Gaming plus
Corsair CMK16GX4M2B3000C15
Seasonic 620W PSU
Samsung 840 EVO 256gb SSD
nVidia GTX 760
Win10 Pro 1903
I've been just using it, never noticed anything until I saw the logs, checked them for other reason.
Also it seems I get kernel boot event 29 occasionally.
For example last time this was logged, I just installed some WIndows updates and normally rebooted. Didn't notice anything weird.
Also it seems even though I've set my Windows to save minidump, no dump can be found, the directory is empty (I have hidden files visible).
I also ran memory diagnostic, no errors.
Also I tried with different set. First I used CMK16GX4M2A2666C16, then I installed the current one and it seems I've got it once after the change and never noticed before checking the log. Happened at 7 PM, I would have noticed if it would have rebooted or something as I had everything open, up and running.
Can this be an error of a kind, I mean can it sometimes interpret that Windows was not shut down correctly when it in fact was? Any ideas how to solve what is causing it, and as I haven't noticed anything weird, should I even care?
Specs:
Ryzen 5 2400G
ASUS B350-M TUF Gaming plus
Corsair CMK16GX4M2B3000C15
Seasonic 620W PSU
Samsung 840 EVO 256gb SSD
nVidia GTX 760
Win10 Pro 1903
Last edited: