Can you see my SS with Orthos ??? that's CPU stability my friend

The "In-place large FFTs" test uses relatively large FFTs which cannot fit into the CPU cache so this test accesses main memory a lot. It only accesses a relatively small amount of main memory because it runs the FFTs in-place so it accesses the same RAM over and over.

hmm maybe different mobo... will try again with Mars

Nice results TS.
But it seems like the vcore is a lil bit on the high side right?

1.42V aint that high i think
its still acceptable & with decent(no need those really hi-performance) HSf, temp should be just fine

ps: wolfie really make me itchy..

Yes, 1.42V is decent and is what reported by many other users as well (around that voltage range)
We should go by facts, not the assumption of Super PI completion = stability right?

source -> line -> component -> short line -> termination

the "lines" in this case are signal traces. works a lot like a SCSI bus. high speed switching operations can cause reflections on the line (in essence, this is resonant noise caused from high-speed switching on the lines as the memory controller gates on and off to place data on the bus, nothing more than rising and falling voltages). clearly enough, the faster the signal switches (higher frequency memory) the more noise.

termination resistors, used in passive termination environments, are exactly matched to the target frequency for operation based largely on trace length, ESR (equivalent series resistance) and the over capactive/inductive nature of the circuit, as well as some other things well out of the scope of this post. problem is that this is often matched for a specific frequency...which as we know is not so cool for overclockers. enter the active termination system. this actually uses a voltage bias to set final line resistance value so that the user can tune for better operation when overclocking.

this method of tuning is largely trial and error as you have no way of know the specification of the circuit or have any idea of the calculations need to find the "perfect" value. so anway, the answer is, strangely enough, whatever works best.

hope this helps.

FCG

Hm.. that's only one hour. I've seen OCs that ran fine over one hour but failed at 8 hours. I think if you really want to say "stable" you should run that thing for 8 hours. What I do is I run orthos and ATITool's find artifact. Then  I stop the cube from spinning. That seems to really raise the temperature for some reason.

"The operating system does an excellent job of giving all spare CPU cycles to the program. The only thing that raising the priority will do is make your other jobs less responsive. For example, lets say during the next minute your spreadsheet needs 10 seconds to recalculate. If your spreadsheet is running at a higher priority, then it will take 10 elapsed seconds to display its results. Prime95 will then get the remaining 50 seconds of the minute. If they run at equal priority, then the spreadsheet will get 10 of the next 20 elapsed seconds before it displays its results. Prime95 also gets 10 of the first 20 seconds as well as the remaining 40 seconds. In both cases prime95 got 50 CPU seconds, but in the first case you saw your spreadsheet results faster.

Above is my E8400 is it the same batch? Sorry for the noob question.