Nimoy
edit2:
test with Multi 46 and 1,25vcore and this Settings:
vdroop-disable
internal pll-enable
c1e-disable
c3,c6,c7 -disable

.......... after few minutes under load ...... Multi drop again to 35 -.-

regards

Check your Event Manager, do you have any WHEA-Logger (EventID 19) warnings? If so, you may need to increase your CPU VCore.   
 
Which version Linx and Prime are you using?

hi
no warnings (Event id 19)
 
bios r22
test with Multi 46 - 1,35 and 1,4 - same Problem aftre few minutes - Multi drop to 35
 
Multi 43 and 1,25 - same Problem - after few minutes drop to 37
 
bios a05
Multi 43 with 1,2 - works perfect !
 
regards
 

AllenSitho

 
This BIOS update works for me. I flashed from A05 to R22, and now I can set VCore, Voltage for DIMM, and I am able to hit 4.6GHz  at 1.38VCore. Previously I was stuck at 4.3GHz with VCore at Auto (got up to 1.3 I think). I do have to set my DIMM timing manually as well because both XMP Profiles do not set the timings correctly, but I am fine with that. I left just about everything at stock. I am glad I waited and didn't sell the board.
i7-2600k, OC to 4.6GHz, 1.38 VCore, Idle Temp 30C, Load Temp 75C
G.Skils Ares, 4x4GB = 16GB @2133MHz, 11-11-11-31-2T, 1.6V
Seasonic X-1250
Intel 330 180GB SSD
EVGA Z68 FTW
Still trying to figure out how to configure Turbo Boost so it is not running @4.6GHz at all times.
Thank you EVGA! This is what I have come to expect from you.

EIST or Enable Intel Speed step does not work for me. I can not boot with it enabled. Using an i7 2700k. In AO5, R21,R22 and the stock bios that came with my board. I could not enable EIST. It would not boot. In all honesty. I'd rather be refunded for my board. EVGA has amazing video cards and power supplies. The EVGA motherboards are making me very sad.

this is a great BIOS for me.
 
FINIALLY able to run 4 DIMMS of 4GB Ares ram @ 2133 speeds with a 4.6ghz overclock on the 2600k.
 
great work EVGA!

First of all, thanks for continuing to work on the BIOS for this board.  It's nice to see IVB support.  With that out of the way, what sort of voodoo is required to bring back my IBM M1015 SAS HBA (PCI-E 8x) with this release?  The BIOS for the card never even displays during boot, and as you'd assume windows can't see any of the drives connected to it.  I went into the BIOS and fiddled with all of the fancy new PCI-E settings, disabling almost all of the new stuff, manually setting the PCI-E gen, enabling the warn on incompatible device option, all to no avail.  I can see the card in the Z68 BIOS, it's there and listed at 8x speed.  But the BIOS for the HBA never loads (normally happens right after the Marvell one on the board).  I went back to A05 and all was well again.  SAS HBA BIOS loads, Windows sees all 8 drives attached to it, pools using the drives work, yadda yadda.  Any pointers for non-video PCI-E cards with this BIOS?

Has to do with Int19 capturing. Was it working before?

stonerhino

Has to do with Int19 capturing. Was it working before?

 
Thanks for the response.  Unfortunately messing with the Int 19 Capture options doesn't fix the issue.  With the old A05 BIOS for this board, the Int 19 Capture options were "Disabled" (this is the default) and "Enabled".  Everything worked just fine with it set to "Disabled", the BIOS for the HBA SAS card loaded and all was well.  However, with this new R22 BIOS, the Int 19 Capture options have changed to "Immediate" (this is the default) and "Postponed".  Unfortunately neither one lets the BIOS of the SAS card load.  This new BIOS is a nonstarter for me if I can't use my SAS cards, and I imagine other people needing HBAs/RAID cards might be in the same boat.

Set XMP profile 1 in the Bios (didn't touch anything else in the memory options) and it recognizes my Ram perfectly.

G.Skill  F3-14900CL9D-8GBSR

Devmani

Set XMP profile 1 in the Bios (didn't touch anything else in the memory options) and it recognizes my Ram perfectly.

G.Skill  F3-14900CL9D-8GBSR

Wow really I don't know what to say. After turning on overclock mode I was able to set the XMP profile to 1. Strange bug I guess not too critical at the moment.

Out of curiosity, have you tried disabling the onboard intel raid rom? It might be fighting your HBA for that same address space.