Originally posted by: Jeff7181
Until I see an explanation of WHY any type of "burn in" would do anything to increase overclockability, or allow lower voltages at the same speed I can't help dismissing all these "results" as coincidence. I suppose one could say I burned in my CPU and got an additional 75 MHz because during my initial testing I could only get to 2.4 GHz before it was unstable... a week or two later I decided to play with it more and now I'm running at 2.475 GHz. I don't believe it's because I "burned in" the CPU... or conditioned the transistors or anything silly like that. It's just because I didn't try all combinations of memory speed & voltage & timings and HTT speed and multiplier settings and CPU voltage, etc. etc.
Originally posted by: Sentential
Just as a side note, THIS program isnt the reason why the CPU speed is being increased. Anything that keeps the CPU at 100% load without erroring out (like P95) will do the very same thing.
I just use CPU burn out of habit. S&M, Toast, K7 burn any many others serve the same purpose.
Originally posted by: Jeff7181
Originally posted by: Sentential
Just as a side note, THIS program isnt the reason why the CPU speed is being increased. Anything that keeps the CPU at 100% load without erroring out (like P95) will do the very same thing.
I just use CPU burn out of habit. S&M, Toast, K7 burn any many others serve the same purpose.
Got a link to those? I don't think I'd ever find S&M if I searched google for that.![]()
Originally posted by: GML3G0
Originally posted by: Jeff7181
Originally posted by: Sentential
Just as a side note, THIS program isnt the reason why the CPU speed is being increased. Anything that keeps the CPU at 100% load without erroring out (like P95) will do the very same thing.
I just use CPU burn out of habit. S&M, Toast, K7 burn any many others serve the same purpose.
Got a link to those? I don't think I'd ever find S&M if I searched google for that.![]()
S&M - http://www.benchmarkhq.ru/english.html?/be_cpu.html
Originally posted by: Sentential
Originally posted by: GML3G0
Originally posted by: Jeff7181
Originally posted by: Sentential
Just as a side note, THIS program isnt the reason why the CPU speed is being increased. Anything that keeps the CPU at 100% load without erroring out (like P95) will do the very same thing.
I just use CPU burn out of habit. S&M, Toast, K7 burn any many others serve the same purpose.
Got a link to those? I don't think I'd ever find S&M if I searched google for that.![]()
S&M - http://www.benchmarkhq.ru/english.html?/be_cpu.html
Yea...anything that keeps a CPU at 100% load will do the job. The trick is to not let up on the CPU even if it produces minor errors. So long as you forcibly keep running it into the ground it will eventually get accustomed to it.
Originally posted by: Jeff7181
I guess it's possible that the CPU could "learn" to work with smaller voltage differentials. You would think that would require some logic built into the CPU though... wonder if anyone "in the know" could confirm or deny that.
Originally posted by: Justin343563611
true, how you get hd corruption out of burning in. gosh.
Originally posted by: Duvie
I may try it but I stress my system far most then most do in here...My systems pass 24+ hours of prime....then run 1 week solid of FH....I dont know but I may very well have done more then cpu burn does anyways.....
Originally posted by: DrCrap
Originally posted by: Duvie
I may try it but I stress my system far most then most do in here...My systems pass 24+ hours of prime....then run 1 week solid of FH....I dont know but I may very well have done more then cpu burn does anyways.....
why de fu** you stress test you MF computer for a week? are you building a space shuttle?
Originally posted by: Ackbar
Originally posted by: Justin343563611
true, how you get hd corruption out of burning in. gosh.
The method involves using lower the voltage to the point where your CPU is erroring, so it's possible you may be corrupting some files.
Originally posted by: scott
Burn-in is a quality control measure taken by producers of hardware. In the areospace biz, just about everything is burned in at each higher assembly level. In the semiconductor biz, burn-in is on a statistical sampling plan.
Its purpose is to promote ( to reveal ) any latent (non-obvious) defects in the product. That's called "infant mortality" and it's a step taken by Quality engineers employed at the producers of hardware. It's to accumulate data on recurring failure modes, for feedback into design of improvements.
Burn-in IS NOT in any way for the purpose of a customer enhancing performance of the product he bought. It's done at the semiconductor fab.
from original post by: Ackbar
Did you even bother reading the thread? The process that Sen is proposing is not actually a burn-in, it's a misnomer.
Sen- Rename the process to "low-voltage conditioning" so people stop associating it with the "burn-in" that 99% of people believe doesn't work.
