Have a Core 2 Duo E8400 which is 6 years and 3 months old. Quite venerable for a CPU, I'll give you that, but I was hoping to get it through to when the next generation of CPUs (and video cards) will hit the market. Also, like the person who posted the topic which is the most recently active here as I write this, computer's on 24/7 and running SETI@home. Actually been running it (with brief experiments with other distributed computing projects) since '99 when it was launched, on all 3 computers I had since then.
Well, today I noticed that it kept apparently failing tasks, setting them as completed instantly, always on the 2nd task active. A look through my stats on the project site shows a string of invalid results since Jul 8, but definitely not at this rate. Now, of course, the occasional instant or either way very quick finish, quite clearly with an error, happened all the time, but this is definitely something else, not occasional anymore for a week or so and now permanent. So the question is if it may indicate a subtle failure of a CPU core... and how could I test for such a failure in general.
After some messing with BOINC it seems to work at the moment, but still a few failures earlier, and no idea if the results will be valid anyway. Asked on their forums too, what I did now is based on advice from there, but also saying that if it fails it's probably temperature or failing CPU, and there's definitely still a problem...)
Additional info, temperatures as reported by Open Hardware Monitor are around 67C / core in full load (so permanently), which is where it tends to stay most of the time, maybe 1-2C less when it's cooler, the difference being the cooler speed (stock cooler), around 2400 now, can be below 2000 during cooler times of year. Also, ran IPDT and that said all fine, but it didn't give me any impression that it tested for something relevant in this respect.
Also, Gigabyte motherboard, running its energy saving software at maximum level ever since I got the computer. (Incidentally, significant temperature increase if it's turned off. BIOS is set to beep at 60C (external temperature I assume, OHM measuring internal) and if I turn that off with S@h running it beeps in some 20 sec. Otherwise only ever got the occasional temperature warning on days with over 35C, and if I carefully clean the dust when the summer gets bad often not even then.
So, yeah, sure put it through a lot in all these years, but I want to know what I can do now.