I can confirm no EIST for any multiplier except 9.
Printable View
When you set CPU multi other than the default, EIST is automaticaly disabled by bios.
I'm running at FSB 450 and 1,6V so that the CPU to be stable and the temps reach 70-75 degrees at full load.
I see that you have a quad. The 65nm quad needs water cooling or better to be able to work at that frequencyes.
45nm quad has lower temps, so it can reach higher frequencyes than 65nm, with the same cooling.
Read this
http://www.digit-life.com/articles2/...res/index.html
Yes, that is what I was asking. I couldn't find references to it so I had to find out about it by myself.
I do have water cooling -- albeit a fanless one. I had water cooling last 8 years. When I am testing my setup to see how far it can go, I blow 2 x 120mm fans at 12v to my radiator and I keep pump pressure at max in order to eliminate heat issues. So that is not a problem at the moment. At present, I can run 3.0 GHz with ample amount of temperatures to go. I can run 3.2 GHz @1.35v but my temps max out in 1 hour of prime. So I can say that I can safely run 3.2 GHz without difficulty. I haven't used an application that maxes out all for cores for 1 hour nonstop, so no probs there.
I can't do more than 1.45v without active cooling. And at 1.45v, my temps max out in 5 mins of prime. So that is not an option.
Thanks for hte link. Reading it now.
Could I also ask what effect would increasing the FSB from 266MHz to 333MHz or 400MHz on a SATA drive?
I was actually talking about data corruption. What would be the likelihood of that?
I don't think folks running their systems at max care a lot about data integrity.
For one thing, on a very stable oced system (Q6600 @ 3.0 GHz, days of torture tests, prime, orthos, occt, memtest, 3dmark, etc)... I found a corrupt frame in a video I edited. Editing the same video on stock settings did not cause corruption. It was a random check, but it made me nervous. I do work with databases... And i would not want random errors appearing in them coming back to bite me in the butt days or months after coz they probably would propagate to all backups.
EIST does not seem to be activated at any multiplier when manual voltage is selected. It only works with default (NORMAL). I tried all C1E, TM2, EIST one by one, two by two, etc with 9 x 370 @ 1.3750v but voltage is always constant and software is reporting it is not enabled. Can someone please confirm this?
I run mine (see sig) as a 24/7 editing rig without any probs. I do use 1.10v on SB and 1.58v on SB 1.5 for SATA RAID 0 @ 500FSB but on 1:1 for stability.
If I was doing more serious work, I would use a lesser profile for that as well as ECC RAM wich my ASUS X38 does support but timings are less, but safer.
Does the DQ6 offer ECC DDR option?
Thanks ChrissTi.
So EIST works only when no vcore is set -- simply meaning that when there is no overclocking in most cases.
Why hasn't this been mentioned at anywhere? Why do people advise for turning EIST off during overclocking and turning it back on once a stable oc is achieved if EIST is not even working with oc in the first place?
I tried ECC before and I wasn't happy with it. It is not necessary for me. RAM is pretty stable as it is and few random errors would not make a big difference in my life or in my work... As for CPU, RAM and all the other hardware where data does not reside, I am not worried. If it broke, replace it.
But I would like to know the consequences of running the system with a higher FSB... I don't mind if the hard drive gets corrupted and does not boot, does not spin, etc... I can fix/replace it. But I would mind if every so few bytes of files were corrupted randomly since I would not be finding about out that right away. And when I find out about that, there would be no way of quantifying how much data was corrupted.
How much standard voltage is on SB? What is SB 1.5?
Well, if you system is stable when running Prime or Orthos for all cores, and another application like winamp so that the CPU load to be for real full, you will get no file corruption.
Higher FSB means higher temperatures, so you will need better cooling, otherwise it's a risk to burn some components, especialy the CPU.
Chris, I don't think that is accurate. EIST is totally disabled.
The one that works is C1E as nucking_futs explained. That is what drops the multi down. Dropping the multi down without voltage has no effect on my system except a 1-2C on cpu temps. Heat increases exponentially with voltage and linear with speed. So without voltage drop, not much of a difference here. I was under the same impression with you about EIST until nucking_futs explained previously.
Here is an example:
3.0 GHz no voltages (25C ambient)
[nb, cpu, gpu, hd]
36 61 54 39 load temps 2h prime
36 35 48 35 (NO EIST) idle: 30m cool down from load
39 32 46 32 (EIST) idle: 30m cool down from load
EIST brings down temps 3C on every component. But it increases NB temp by 3C.
3.2 GHz @ 1.35v (25C ambient)
40 69 55 41 load temps 1h prime (cpu temp maxed out)
37 40 50 37 (NO C1E) idle: 30m cool down from load
34 39 49 36 (C1E) idle: 30m cool down from load
C1E brings down temps 1C on each component except NB where the decrease is 3C.
I don't like EIST, it makes my system less responsive. So I have it disabled anyway. C1E does not seem to affect temps much. So I have it disabled too.
No but if there are errors, those errors can be written on hdd, and even in bad sectors ...
I always disable EIST but leave everything else enabled...i knew from many a bios ago that once you overclock or alter FSB or alter default CPU voltage the bios automatically disables the option in bios anyways.
It disappears from the bios menu, so for a long time i have disbaled it BEFORE i start to overclock.
there was some mention of that DES feature
dynamic energy saver
i don't think it works if your system is overclocked
only with stock settings :)
On a side note...the new 00NLR5 Raptors show no difference in raw numbers compared to my older 00NLR1 drives, but they do seems quieter.