Error message from QuestionExplorer appears briefly before the system stops unexpectedly.
Error message from QuestionExplorer appears briefly before the system stops unexpectedly.
It's not a huge mistake that prevents many people from using Windows... it seems like a minor issue or something I should have solved sooner.
Staff members aren't very active on forums anymore; they only assist Tom when necessary.
I'm curious—do any logs appear in the shutdown and startup records?
Where and how can I view the shutdown and startup log in Windows 10 and 11? A quick solution is needed.
Are you interested in learning where and how to check these logs on Windows 10 and 11? There are several methods, and this guide will show you the simplest ones. Keep reading!
www.auslogics.com
Have you posted anything here before?
https://www.elevenforum.com/
They might help explain how to resolve it. It should be a way to track what's going wrong. I'm not sure yet.
They're the forums I'd reach out to if I got stuck...
Checked for mistakes in the shutdown log
https://imgur.com/ENF3Z1m
Looking at it, I think I should post a question on the forums.
41(63) refers to windows responding after a restart. It doesn’t understand the reason behind the restart. Each time it starts, it generates a report; if a prior shutdown was unexpected, it logs that event. Event 6008 appears related, occurring around the same moment as 41(63), and they seem to function together. There were three restarts within twelve minutes... do you recall three consecutive restarts? Around 1:30 in the afternoon, though it was a Sunday. No BSOD was reported. It could be hardware-related—windows might not know why it restarted. I’m uncertain if the shutdown log would capture all events at that time. Perhaps try running crystaldiskinfo (blue icon) and inspecting drive health as if writing failed, maybe indicating an NVMe issue... Alternatively, use Samsung Magician and check two drives.
I completed three restarts for a clean boot troubleshooting.
Crystaldisk indicates all drives are functioning properly with no errors.
Links: https://imgur.com/PzGtj7C | https://imgur.com/nGdETN1 | https://imgur.com/eWVanw4 | https://imgur.com/KZ1OAqO
I apologize for dragging it this long. I get that its harmless but its an annoying bug especially since there is no possible symptom that I can find other than it being system restore(and the issue persists even if its turned off).
Its very annoying that MS has not done anything to fix this. That said, so far the issue hasn't appeared.
your issue is understood, you may continue the conversation in the thread as long as it remains useful for you.
That's a fresh observation... yes.
It seems unusual for it to happen right after a reinstall. I looked into the drives and found some relevant information. Most of the answers are on the first page.
No USB drives connected?
I could also post this here:
https://www.sysnative.com/forums/