Critical System Shutdown Errors

OK...then those errors can and most likely are attributed to browsers or an extension/add-on not shutting down correctly would be my best guess. Since there is nothing physically wrong with your system and it seems to be functioning correctly....I would just monitor the event viewer and see how often (what days and how many times) that shut down error shows up.
 
How do I run the memory testers for "several" passes?

Is there any way to figure out which program is causing the event viewer errors?
 
Don't stop it. It will start then next pass when the previous pass completes
Click to expand...
I didn't stop Memtest, I let it run until it was finished. I think I remember it saying 44 passes were run. How many passes are there total on Memtest?

xilolee: I haven't used steam forums, and I have only chatted with 1 trusted person so far on steam chat.
 
Last time I ran Memtest (either version) it never stopped on its own. When it completed a pass, it simply started over again. If you got several passes and 0 errors, then memtest is reporting your RAM is fine. But again, these are not 100% conclusive.
 
1. Great!
2. How the heck did you discover that?

I find it odd that feature would cause this. I have not seen it causing problems with other systems and I have it enabled (the default setting) on my W8.x systems.

Disabling it should not really cause much in the way of delays, and any delays that do happen will only be when rebooting. If me, I might try enabling it again and see if the problem returns. Because the feature saves system information into a special file when shutting down that is read in when rebooting, I am wondering if your file somehow became corrupt, causing your problems. And now that you disabled it, I am hoping the corrupt file has been deleted, and by enabling the feature again, the hope is a new, un-corrupted file will be saved - and work.
 
Hopefully, I think that was the problem, I could always be wrong. I discovered it by re reading this thread and seen xilolee suggested that a while back. I searched it online, and it is a known problem apparently. Who'd a thunk it? I will try enabling it and checking periodically to see if the problem reoccurs. I will also do some more RAM tests I never did do (eventually). Microsoft, or somebody, needs to fix this bug.
 
FWIW, I had to disable FS on my system as it conflicts with my webcam (Logitech drivers :r1:) and doesn't allow my system to fully shut down. It gets caught in a hibernate kernel > wake loop.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top