Can we please get back to the XMP Memory issue? I know that you purists have utter disdain for this setting but it is awesome for those of us who have an OC time budget of about five minutes.

If I select XMP memory profile, dummy OC and turbo mode then I have a clock of 3.352 GHz on a 920 in the old bios. In less than two minutes. And it is STABLE.

But the XMP does not work with the new bios. I can tweak it up to that level and maybe a little beyond but the big difference is that the Everest Torture Test never causes a fail for the XMP setting in the old bios but destroys my own tweaked non-XMP setting in the new bios. Forget the 95 Prime. It just destroys the computer into a BSOD. But 95 Prime works great with the old bios XMP.

So for the time pressed (or lazy) of us, how about getting that XMP setting to where it was in the previous bios?

The problem with the new bios that is killing some over clocks is more than likely you are running a 22x multiplyer insted of the old 21x. I am not 100% sure of this but it seems to be what happened to me, As soon as i got booted up and ran a single thread app it bumped me to 22X and then hard locked. I backed my oc down a bit and it is working fine.

rody

Thank you for the above informative replies. I am now back on the S227 bios and it is working like it did. The only thing that keeps me going back and forth is the new "HPET Support" entry in the bios. Which did not make any noticeable improvement. But new must be better. Just look at the new Toyotas. (couldn't resist that. I had a Camry that was one of the best cars I ever had.)

These boards do take a long time to post, it's normal and no BIOS updates change that boot time.

lcd1860nx

Can we please get back to the XMP Memory issue? I know that you purists have utter disdain for this setting but it is awesome for those of us who have an OC time budget of about five minutes.

If I select XMP memory profile, dummy OC and turbo mode then I have a clock of 3.352 GHz on a 920 in the old bios. In less than two minutes. And it is STABLE.

But the XMP does not work with the new bios. I can tweak it up to that level and maybe a little beyond but the big difference is that the Everest Torture Test never causes a fail for the XMP setting in the old bios but destroys my own tweaked non-XMP setting in the new bios. Forget the 95 Prime. It just destroys the computer into a BSOD. But 95 Prime works great with the old bios XMP.

So for the time pressed (or lazy) of us, how about getting that XMP setting to where it was in the previous bios?

XMP while overclock?
Sorry thas not a very good idea.
better lets get back to the real problems, no offence.

3D Modeller

Hey guys...hope you can help.

My E759 has the factory bios and has always been unbelievably slow to post. In fact it's slower to post than it is to get the whole OS loaded.

Does this or any bios release fix post time? It's my only reason to upgrade the bios to be honest.

All the best

There's a number of thing in bios that you can disable to shorten the boot time. Namely, stuff that you don't use, so the bios can skip that confirmation check when booting up. See what items you have need for bios to see and disable the rest.

I found another problem with this BIOS.  It won't run 2:10 DRAM multiplier correctly.  I have it set in the BIOS, tried everything imaginable to get it to take and no matter what the board keeps going back to 2:8 multiplier.  The BIOS is showing 2:10 to be set, but it is not taking.  Actual multiplier is 2:8.  Impossible to run 2GHz DRAM at 200MHz BCLK.

BIOS is too buggy.  I'm down to S22D again for the time being.  We'll see if they fix some stuff in the next release.  A comment by anyone at EVGA would be appreciated, however, nobody will show up here to say anything.

i use it with Gulftown Q3QP , dominator gt 2000 cl7 on E759.

Sweet bios, flashed from beta bios to 44bios, and it's working great, more options, better memory stability,

turbo performance working great, notice sometimes reacts faster en Wprime1024m shortened on the same clocks with 6sec.
from 116sec to 110 sec wprime1024m.

Now stabile at 4.6Ghz with same Vcore as with previous bios version on 4.5Ghz 6cores/12treads HT enabled.

Here's my 24/7 use screenshot, benchmarks, gaming everything stable : 

http://i47.tinypic.com/2qkjfk6.jpg

Welkom to the club ?

i got my Gulfy from september 2009.
bought a new vapo in decmeber and putted the chip direct under it : http://valid.canardpc.com/show_oc.php?id=861006
look at date of submission
only still under vapochiller done, because this is my 24/7 chip.

under SS i got 5.45Ghz benchstable.

With this new bios 44 i tesed the "Turbo performance" option in bios on and off.

When i turn it off, everything is like it supossed to be, but with "Turbo performance" enabled, my memoey drops from 2020mhz (cpuz says 1011).
But i thought maybe more performance on cpu????

let's test it :

3dmark vantage cpu test without "Turbo performance" option :

http://i49.tinypic.com/2e5sa9w.jpg

3dmark vantage cpu test with "Turbo performance" option enabled :

http://i47.tinypic.com/30283n5.jpg

So i don't use this option anymore.............
for the rest, this bios version is not bad at all.
to 1685Mhz (cpuz 840)

Does this BIOS version report NB temperatures correctly?

I've just installed the EK full-board block, and am enjoying temperatures in the 20s-30s on all of the components as reported in BIOS...except the NB, which reads 127C!  Now unfortunately, I didn't think to record the temps on stock cooling before I removed the stock cooler, and it's no trivial affair to mount the EK block in the first place (fellow EK users know what I'm talking about - it's very difficult to keep the required spacers in place while mounting).  So I don't want to remove the EK block except as a very last resort.

My first thought was that it must not be reported correctly, or that there is a faulty sensor, because surely the poor NB chip could never tolerate such a high temp in reality for more than a second or two??!!  But when it occurred to me that it might, I shut down pronto.  My next step will be to remove the motherboard and try tightening up the EK's mounting screws in the NB area.  But at such a high temp reading, I'm thinking that could only occur if the cooling block wasn't making any contact AT ALL with the NB; and that's just not possible.  Everything else is being cooled too well, and this EK block is, after all, one massive, long, straight piece.  So how could it be making no contact?

Hi azamat,

These are all BIOS readings.  I'm still building the hardware base and testing, so I haven't gone as far as installing an OS yet.

Money keeps me from buying another SSD!  But for now, I have a great HDD silencing enclosure, although I can't recall the name.

Sorted.

I tightened the block's screws, especially in the NB area - and with a bit more effort than I'm comfortable with on such an expensive rig (fingers crossed, sweating, heart pounding) --- but now all is well.  All temps in line, with NB 38C.

Thanks for the help!

If the block fasteners are not fastened in a certain order you can have poor contact with certain components.  You should start from the top of the board (MOSFET area) and work your way down gradually to the SB.  I strongly recommend using spacers around the SB area instead of the NF200 area, unless EK now includes spacers for all areas.  Not using spacers around SB area can cause the board to warp and malfunction, sometimes not showing any symptoms for quite a while (several months).

Anyway, back on topic, is there anyone from EVGA that reads this thread or do I have to contact Peter directly again?

firerx

yeah,
I've turn that turbo performance off too. BTW, nice OC on that vaporchill!

thanks