Quote:

Originally Posted by

Well I returned all the clock speeds to stock and it seems to have gone away. I guess my overclock wasn't as stable as I had first believed. Only thing is, now how do I determine exactly how high I can clock it? You'd think an e8400 would be able to do at least 3.8Ghz, but that's what I've had it set on lately and have been experiencing the problems. I ran that overclock on prime for 4 hours. Is there a newer better program that can determine instability in a shorter amount of time?

**PhotonFanatic**Well I returned all the clock speeds to stock and it seems to have gone away. I guess my overclock wasn't as stable as I had first believed. Only thing is, now how do I determine exactly how high I can clock it? You'd think an e8400 would be able to do at least 3.8Ghz, but that's what I've had it set on lately and have been experiencing the problems. I ran that overclock on prime for 4 hours. Is there a newer better program that can determine instability in a shorter amount of time?

No, and there (most probably) will never be such program, since the instability is usually just a erroneous return of an operation, eg. a mathematical calculation (that's btw how p95 "detects" instability, the program knows what the answer should be to this complex mathematical calculation it does, and compares it to the result it gets), and the error can occur in the first minute, or it can even take days of full load. The more instability, the more probability for the error to occur faster. That's why one of the "overclocking thumb rules" is "when you think you got a stable clock, back it down a tiny bit and you're done."

Also, all parts degrade over time, especially when running on high clock speeds and voltages etc, so its normal for the "maximum stable clock" to go down by time