It's MSE - sorry.
One of the reasons I was looking forward to building this system was to ditch McAfee. It hogged memory and failed to catch Antimalware Doctor. So far I've been quite happy with MSE.
I'll do the memory test overnight and keep my fingers crossed. For what, I'm not really sure, but I'll keep them crossed anyway.
OK, I left memtest going all night and all day while I was at work. I came back just now and found that after 17 passes memtest found no errors.
And now the good stick in each slot test has passed as well. What's next? I'm starting to wonder if a repair install is in my future ...
Using event viewer, by typing that in search. What are the codes and errors that caused the crash?
In the left panel use the adminsitrative position to look for the errors.
There is a series of errors associated with each crash:
1) Warning from Kernel-Tm (event id 4) stating "The TransactionManager [snip] has failed to advance its log tail, due to the transaction [snip] being unresolved for some time.
2) Crash happens some time after that, with "some time" being anywhere from a few minutes to a few hours.
Then in rapid succession ...
3) Error from EventLog (event id 6008) stating "The previous system shutdown at xxx on xxx was unexpected."
4) Critical from Kernel-Power (event id 41) stating "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
5) Error from EventLog (event id 1101) stating "Audit events have been dropped by the transport. 0"
Screenshot is attached.
I've been testing different permutations of the memory chips and am still able to get it to crash. Not done with all the possibilities yet but am not having any luck with finding bad RAM.
They are the events that happen at a time surrounding one of the crashes, yes. There is never a logged error at the specific time of a crash. When the system comes back up it logs the events I mentioned earlier:
3) Error from EventLog (event id 6008) stating "The previous system shutdown at xxx on xxx was unexpected."
4) Critical from Kernel-Power (event id 41) stating "The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly."
I should add that when the crash occurs I usually just leave the machine off until I need to bring it back up - the amount of time between the pre- and post-crash events of course includes that.
Quote