05-30-2013 11:44 AM
05-30-2013 12:24 PM
05-30-2013 03:16 PM
05-30-2013 04:02 PM
xeromist wrote:
I would check the Windows event log for anything useful and try running everything at stock for a few days or however long the average occurrence interval is. Over time chips get old so even if it's not overheating it might require more voltage to achieve the same stable clock you had last year. Also you might run memtest86 to see if one or more of your modules has gone bad.
HiVizMan wrote:
Do you have a AV application running and please do look at the even viewer to see what is causing this to happen.
05-31-2013 02:10 AM
05-31-2013 08:00 AM
HiVizMan wrote:
Which AV do you have, and I might suggest that you run an stand alone scan. What you are describing sounds very much like a system that was brought to me recently and the shut down was causes by a virus. Worth doing as no AV is perfect they just make it harder....
05-31-2013 09:17 AM
Dreamtool wrote:
But wouldnt there be a more exact time between the shutdowns if it was a virus ?
06-08-2013 07:50 AM
06-08-2013 08:11 AM