Thanks a lot Now i'm back to A05 .

rsabatino

yo guys if you want to overclock any z68 boards and you are using sandy bridge not ivy bridge use the A05 bios. now this is for sandy bridge if you have ivy download the latest

this is the best for overclocking sandy bridge at normal settings my cpu does not go over 28 C over clocking is easy fallow the p67 over clocking guide. with this bios with air cooling I can get a stable 4.5 ghz      that's my rig as proof xmp profile set at 1.

yeah I did not upgrade to ivy but when I use the new bios my cpu temps jump up an extra 22 degrees and crashes during a overclock the a05 bios is the better for sandybridge chips.

rsabatino

yo guys if you want to overclock any z68 boards and you are using sandy bridge not ivy bridge use the A05 bios. now this is for sandy bridge if you have ivy download the latest
http://forums.evga.com/tm.aspx?&m=1252762&mpage=1
this is the best for overclocking sandy bridge at normal settings my cpu does not go over 28 C over clocking is easy fallow the p67 over clocking guide. with this bios with air cooling I can get a stable 4.5 ghz   http://www.modsrigs.com/detail.aspx?BuildID=29493   that's my rig as proof xmp profile set at 1.

 
The release notes for this new BIOS says it adds Ivy Bridge support, not that it degrades support for Sandy Bridge. Furthermore, A05 also had a major bug in it that caused Code 69 errors at POST every 2 of 3 times I booted up. That was a bug that was acknowledges elsewhere in these forums and this new release is the only update we got since then. This isn't good enough. I don't want to have to choose between two unstable scenarios. I bought a board that's supposed to be overclock friendly and honestly, I've never had problems like this with boards from bigger manufacturers.

Hello, on R22 bios i have problem that under load CPU Freq downclocking. E.p i set mult 42, under load i have only 3900Mhz. With EIST and C1 disabled same problem, but without load it set correctly 42.
My board Z68 FTW cpu 2500k .
Maybe somebody make new faq with overclocking on R22, because differential between A05 too match  

well my system usually around 28c with the old bios. with the new bios at least 10 to 20 degrees more and inability to overclock because of the heat. with a05 I can get the cpu up 4.5ghz on air cooling no problems or codes.

rsabatino

The release notes for this new BIOS says it adds Ivy Bridge support, not that it degrades support for Sandy Bridge. Furthermore, A05 also had a major bug in it that caused Code 69 errors at POST every 2 of 3 times I booted up. That was a bug that was acknowledges elsewhere in these forums and this new release is the only update we got since then. This isn't good enough. I don't want to have to choose between two unstable scenarios. I bought a board that's supposed to be overclock friendly and honestly, I've never had problems like this with boards from bigger manufacturers.

It does change the Management Engine (ME) Microcode so that "could" cause an effect of the Sandy Bridge Chips.

This bios can handle with 32gb of ram?
I use some heavy software and 16gb come to heir limits....

EVGA Z68 3WAY SLI FTW MOTHERBOARD WITH THE NEWEST BIOS DOES IT OVER-CLOCK MUCH BETTER OR STILL THE SAME.FEW FRIENDS OF MINE HAVE THE EVGA Z68 FTW MOBO ONE OVERCLOCKS TOO 4.1 MAX.OTHER MOBO EVGA Z68 FTW OVERCLOCKS TO 4.5 BUT ITS FAKE WHEN YOU TEST IT NOT OVERCLOCK THAT HIGH AT ALL,IVE BEEN BUILDING PC OVER 15 YEARS SAME CPU I5 2500K I PUT IN A GIGABYTE G1 SNIPER M3 AN GET 4.8 GHZ EASY EVGA WHATS GOING STILL EVGA Z68 FTW MOBO OVERCLOCKING SUCKS.....

Caps lock?.....
Too bad for you now i'm stable at 5,8Ghz with my I7 2600K...

Every time I update the bios on this mobo I have to reactivate windows. What a pain in the butt. Never had this happen with any other board unless I actually changed the CPU.
 
Just a heads up for anyone that has a per seat activation that you may actually have to contact MS like I do every time you update the bios on this board. weeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee. <3 it! not.