That is why ... that is why ... I was avoiding your event logs.Most of those are old, and so not applicable in the current situation, viewed it, as you wanted.
If dumps provide adequate information, that is fairly enough to judge the situation, compared with MSINFO32. But in some cases, event logs are needed. Your case is not among those cases :)
As the monitor works without any crashes, let it be there. Best of luck!
I'm used to running right to the logs to see whats going on behind the scenes :) Old habits die hard, and I was at least hoping the logs could give me a better idea what exactly was happening at the time of each crash that might give me a lead to reliably reproduce the issue for better troubleshooting.That is why ... that is why ... I was avoiding your event logs.
If dumps provide adequate information, that is fairly enough to judge the situation, compared with MSINFO32. But in some cases, event logs are needed. Your case is not among those cases :)
As the monitor works without any crashes, let it be there. Best of luck!
However, thats the thing. I literally changed *nothing*, and i'm going on day three with no lockups and *plenty* of idle time and paranoid checking :) It's the same monitor, the only one I have that's been going strong through three computers and five years now.
I just uninstalled Microsoft Security Essentials to see if it's the cause of all those OOBE errors since a bit of googling came up with some people claiming it was the cause of those as well as some on and off bluescreens, i'll install something like AVG or Avast! in its place in a day or two. I also disabled a handful of services like Windows Media Server that I honestly dont need. If everything keeps working, great, and if I crash again I'll take the whole thing apart, reseat everything, and do a full format/reinstall.
Quote