Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
I thought that the following information might be helpful:
I will continue to update the graph to include more datapoints as I record them.
The wattage measurements were done at the wall with a Kill-A-Watt power meter.
I guessed that the best way to prolong my chip's life was probably to...
For the most part you can just recompile an app with GCC. I was part of the initial porting effort of porting Debian to the amd64/em64t platform back in early 2004. From what I recall about the only problems we had were with applications that either used x86 assembly instead of higher level...
I got this before when attempting to overclock my system, I think in my case it was just using too low vcore.
One cause of resets if you are seeing them inside Windows is from getting a bluescreen. By default if the system bluescreens it automatically restarts the system.
To disable this...
I overclocked a Duron 600 to 1GHz on a Abit KT7-RAID motherboard around mid 2000 that I used for several years. I am not sure about the K7S41 motherboard though.
Intel documents mention that the maximum voltage for the chips is 1.5v so I wouldn't personally push it past that point. Always remember that temperature isn't the only thing that can destroy electronics, the more voltage you use the faster electromigration will cause the chip to fail also.
And you can undervolt the hell out of C2D chips at stock speeds which should dramatically lower the energy usage. From what I recall I was able to run my E6300 266x7 1.32500v stock at ~ 260x7 0.95000v, which is only slightly underclocked.
Also note that Orthos - small FFT is not enough to find stability by itself since it does not stress your ram. I think this is a large part of the reason people consider OCCT better. If your memory is overclocked as well you need to run something like Orthos - blend or OCCT for a prolonged...
There is of course a way to get higher load temps than even with Orthos... use Intel TAT to load both cores, it causes the temps to go much higher than even Orthos does.
Like you mention while tweaking cpu voltage to get the minimum required to be stable, I have regularly seen it fail in the 12-14 hour time range. I haven't run a burn in lasting over 14 hours so far, so I don't know if just upping the voltage the next level (0.00625v on my board) is enough to...
OCCT misses errors as well. I have seen it miss several bad voltage levels while building a graph of FSB vs Voltage on my E6300, that Orthos (small fft) caught. However, I definitely will be running OCCT for 24h as well when I think I have "stabilized" my system.