ASUS Intel Beta BIOS Releases and Official Support

[mjgr33n]

Any update as to an official BIOS that fixes the stuff we've had to modify ourselves? Re: Marvell/Intel SATA controllers

Aye, it would be nice to get an update to R2E, my R3E board got updated but it is just sat in a corner gathering dust as it is not great with my 975EE, have to use my older R2E and would be great to have the later Intel OROMS officially in it, it is such pain that it is not so easily moddable like the old P5Q boards, used to love modding them with OROMS etc. But when I try doing the R2E mod myself the OROM fails to load.

[danielkza]

2133 9-10-9-28-2T at 1.6v was unstable for me and tbh I do not want to go over 1.6v so I will stick with 1866 8-9-8-24-2T at 1.5v, not like much more performance benefit you get form overclocking memory anyway and the whole point of the g-skill eco's is too run at lower voltages, also the heatsinks on the eco memory do not look great for overclocking compared to memory designed to be run at 1.65v.

Also I always use auto for the sub-timings except for tWR which I find can be a little low at times with the eco's.

Anyway 1866 has been running completely stable since I last posted about it ))))

I did some testing and I was able to get 1866 7-9-7-24-2T at 1.5V with XMP timings except for tCWL at 8, 1:30h Prime stable (haven't had time to test further).

I'm also not perfectly comfortable with 1.65V, but considering these are PSC chips after all (most of them run like that), and the RAM doesn't stop scaling earlier like some other people experienced, my guess is that it's reasonably safe.

And I don't believe there is much difference between a plain heatsink and one with twists and bends as long as you get just enough airflow to cool it down a little (my kit gets only mildly hot while Priming at 2133 1.65V).

[mjgr33n]

I did some testing and I was able to get 1866 7-9-7-24-2T at 1.5V with XMP timings except for tCWL at 8, 1:30h Prime stable (haven't had time to test further).

I'm also not perfectly comfortable with 1.65V, but considering these are PSC chips after all (most of them run like that), and the RAM doesn't stop scaling earlier like some other people experienced, my guess is that it's reasonably safe.

And I don't believe there is much difference between a plain heatsink and one with twists and bends as long as you get just enough airflow to cool it down a little (my kit gets only mildly hot while Priming at 2133 1.65V).

Hmm, your response has made me think about trying 1.65v then )))) Plus I guess having 3 viper fans right above the memory on my TFC 360 would keep it cool.

I am surprised you need to have tWCL at 8 though with CL at 7, they should always be the same or at least the memory should always be able to handle them both being the same, although I suppose there is always slight variations in kits, have you tried posting on the gskill.us forums, I would think they might replace them for you given that as it should be able to run at those parameters, I actually have 3 of these kits and all of them run with tWCL and CL being the same.

[danielkza]

Hmm, your response has made me think about trying 1.65v then )))) Plus I guess having 3 viper fans right above the memory on my TFC 360 would keep it cool.

I am surprised you need to have tWCL at 8 though with CL at 7, they should always be the same or at least the memory should always be able to handle them both being the same, although I suppose there is always slight variations in kits, have you tried posting on the gskill.us forums, I would think they might replace them for you given that as it should be able to run at those parameters, I actually have 3 of these kits and all of them run with tWCL and CL being the same.

They can run at equal CL and tCWL, just not on this board, so it's most likely not the RAM itself. RMAing the would be a pain for me considering I have no other DDR3 kits lying around, and it would take upwards of a month for me to get them back considering I live in Brazil.

BTW, I found out 9-10-9-28 was not stable after all, I got a Prime fail after 8h. I discarded 7-11-7-28 and 8-11-8-28 after Prime fails in minutes, and am now trying 9-11-9-28, hopefully it'll finally be stable, or I'll just go back to 1866.

[mjgr33n]

They can run at equal CL and tCWL, just not on this board, so it's most likely not the RAM itself. RMAing the would be a pain for me considering I have no other DDR3 kits lying around, and it would take upwards of a month for me to get them back considering I live in Brazil.

BTW, I found out 9-10-9-28 was not stable after all, I got a Prime fail after 8h. I discarded 7-11-7-28 and 8-11-8-28 after Prime fails in minutes, and am now trying 9-11-9-28, hopefully it'll finally be stable, or I'll just go back to 1866.

I just tried 2133 9-10-9-28-2T @ 1.65v and that was not stable for me, but then I am running 4 of these sticks, so back to 1866 for me, at least I know 1866 - 8-9-8-24-2T runs stable for me at 1.5v which is pretty good for 4 sticks ))), will keep it at 1866 unless ASUS provide a new BIOS with some more memory tweaks, but as from next week I will only be able to test at weekends as will be staying in hotels and B&B's for the next 4 months, so not sure how much time I will get to test, need to buy a laptop now :P

[therat]

Looks like a new BIOS has been released for all the P67 boards on the Asus ftp server.

Not sure if it's beta or not. BIOS 1702

ftp://ftp.asus.com.tw/pub/ASUS/mb/LGA1155/

[Leeghoofd]

BTW, I found out 9-10-9-28 was not stable after all, I got a Prime fail after 8h. I discarded 7-11-7-28 and 8-11-8-28 after Prime fails in minutes, and am now trying 9-11-9-28, hopefully it'll finally be stable, or I'll just go back to 1866.

Tried 9-11-10-27 ? Only way to get my 4gb dimms running at 2133Mhz... wanna quick test the rams try HCI memtest in windows... unstable ram timings will error out under 10 mins...

[IronAge]

Looks like a new BIOS has been released for all the P67 boards on the Asus ftp server.

Not sure if it's beta or not. BIOS 1702

ftp://ftp.asus.com.tw/pub/ASUS/mb/LGA1155/

Not for all - just for the Deluxe and Sabertooth so far. They just have added 1702 for the evo too.

[danielkza]

Tried 9-11-10-27 ? Only way to get my 4gb dimms running at 2133Mhz... wanna quick test the rams try HCI memtest in windows... unstable ram timings will error out under 10 mins...

Prime95 Blend usually fails for me in under 10min too, it's either that or 8h+, very rarely anything in between. And I'll try 9-11-10 when I get home later, thanks for the tip

[mjgr33n]

http://dlcdnet.asus.com/pub/ASUS/mb/...-ASUS-1702.zip for fast Sabertooth P67 link ))

[mjgr33n]

Well for one thing in 1702 BIOS Intel RST has been updated to 10.5.0.1034, so I am guessing at least one of the updates is the same as the Z68 boards which is as follows -

Update RAID OPROM to version 10.5.0.1034 to enable the support of Intel Rapid Storage Technology version 10.5.0.1026

[mjgr33n]

So far seems very stable at the same settings, still can't have C3 and C6 enabled with same settings or get instability according to Intel Burn Test after 10 minutes at Very High.

Speaking of Intel Burn Test, am getting over 130 GFlops at 4.8Ghz on Very High Setting, loving this CPU )))

[danielkza]

Does anyone have the 1702 BIOS for the P8P67 PRO? The P67 thread in Overclock.net links to it, but it seems to have been pulled from ASUS' FTP (the modification date for the folder is today, but the file itself is not accessible anymore).

[mjgr33n]

Tried http://dlcdnet.asus.com/pub/ASUS/mb/...-ASUS-1702.zip but it failed ((

[Havokator]

The 1702 BIOS was there for the P8P67 Pro last night. So Asus must have taken it down today. They never released it publicly on their website, so maybe it was a mistake that it was on their ftp server. Anyone got a copy of it that they can upload somewhere? I should have grabbed it last night.

[roman63]

Does anyone have the 1702 BIOS for the P8P67 PRO?

http://www.box.net/shared/8gs280zj8d

[spoolindsm127]

I'll just make this public so maybe Raja@ASUS will be inclined to actually respond and further explain this:

Hq has confirmed QPI PLL is indeed tied to VIOH as I suspected.

-Raja

Obviously referring to beloved R3E.

[donmarkoni]

I'll just make this public so maybe Raja@ASUS will be inclined to actually respond and further explain this:

Hq has confirmed QPI PLL is indeed tied to VIOH as I suspected.

-Raja

Obviously referring to beloved R3E.

Thanks mate!

[spoolindsm127]

Not a prob glad I can help

[zoson]

It's so about time that we finally have closure on QPI PLL voltage... I sense a new era of juicing up our IOH's above 1.3v to see what higher QPI PLL will do for us...

[idahosurge]

I installed BIOS 0003 in my R3E, I was using 0901. Now the motherboard temp and the CPU temp do not read correctly. The MB temp never goes above 38C. The CPU idle temp is now close to 10C higher than it was with BIOS 901 and it does not read as high when under load (OCCT) as it should. I have seen two threads on the Asus R3E support forum that BIOS 1301 has CPU temp problems also.

Is Asus ever going to fix this on going temp problem in the R3E BIOS?

It works in 901 so why can it not be fixed in the new BIOS releases?

[Irocing]

A bios that supports lower then 1.8 cpu pll for the P6X58D-E would be awesome.

Thats what I've been waiting for.

Later

[zoson]

I installed BIOS 0003 in my R3E, I was using 0901. Now the motherboard temp and the CPU temp do not read correctly. The MB temp never goes above 38C. The CPU idle temp is now close to 10C higher than it was with BIOS 901 and it does not read as high when under load (OCCT) as it should. I have seen two threads on the Asus R3E support forum that BIOS 1301 has CPU temp problems also.

Is Asus ever going to fix this on going temp problem in the R3E BIOS?

It works in 901 so why can it not be fixed in the new BIOS releases?

I don't have this problem with 0003 or 1301...
4.4ghz HT on idling below 30C:

[idahosurge]

I don't have this problem with 0003 or 1301...
4.4ghz HT on idling below 30C:

Thanks for the screenshot Zoson. I think that SYSTIN is your R3E MB temp, I could be wrong, but when stress testing with BIOS 901 and OCCT or LinX I really think that I had more than a 4C degree swing from idle to the high temp and you only show a four degree swing. With 0003 my R3E MB temp only goes from 34C up to 38C at the most.

I think that I am going to try 1301 and see if that makes a difference. If I do not like what I see then I will put 901 back in just to at least verify if there is any noticable difference.

[zoson]

Thanks for the screenshot Zoson. I think that SYSTIN is your R3E MB temp, I could be wrong, but when stress testing with BIOS 901 and OCCT or LinX I really think that I had more than a 4C degree swing from idle to the high temp and you only show a four degree swing. With 0003 my R3E MB temp only goes from 34C up to 38C at the most.

I think that I am going to try 1301 and see if that makes a difference. If I do not like what I see then I will put 901 back in just to at least verify if there is any noticable difference.

Ah, I see. Sorry, my initial response was regarding CPU temps... I think you'll agree that I do not suffer from any CPU temp bug, though.

I still pose the question to you: How do you know 901 was correct and 0003/1301 are incorrect?

I agree that SYSTIN is the MB temp, however... 44C seems right in line with what it should be. My board has an EK-FC-RE3 waterblock, and my OPT2 sensor is the temperature of my coolant(40C). OPT1 is my ambient temp sensor, and OPT3 is the temperature of my exhaust.

I think it's more likely that 901 and bios's before it were wrong, and 0003/1301 are correct.