ASUS Intel Beta BIOS Releases and Official Support

[Raja@ASUS]

Raja is there any possibility of releasing beta bios's to the public as gigabyte does, it somehow feels good playing with different bios.

Any time soon will it be there.

The BIOSes I posted above are beta.

[Raja@ASUS]

Raja, I asked asus tech support:


And got this reply:

She misunderstood what you were asking for as CPU PLL - so disregard it.

-Raja

[danielkza]

@Raja:

Great seeing we're getting some real help from ASUS, so I'll just be opportunistic and ask a question of my own.

I have a P8P67 PRO paired with a 2500K and 2x2GB of G.Skill ECO DDR3-1600 7-8-7-24 1.35V RAM. Booting with a tRCD of 9 at 1866 and over causes an infinite reboot cycle. 'Your RAM simply cannot handle it' you'd say. The catch is, I can boot without problems with a tRCD of 8 at DDR3-1866 1.65V. I tried upping RAM voltage up to 1.7V and VCCIO up to 1.2V to no avail. The only sensible explanation considering the symptoms is a BIOS bug of some sort. Have I mentioned the RAM does not work at stock settings at my board, but runs perfectly on a friend's Biostar TP67XE and on a P7P55D Deluxe?

And last time I upgraded my BIOS from 1305 to 1502 I had to downgrade due to S3 simply being non functional even at stock settings. Were there any other changes in that area in the 16xx series? I really don't want to have to downgrade again.

EDIT: Just did a couple more tests. DDR3-1600 7-8-7-24 works if I give the RAM some more voltage, but 7-9-7-24 causes a reboot cycle. Weird to say the least.

Thank you for your time.

[Raja@ASUS]

@Raja:

Great seeing we're getting some real help from ASUS, so I'll just be opportunistic and ask a question of my own.

I have a P8P67 PRO paired with a 2500K and 2x2GB of G.Skill ECO DDR3-1600 7-8-7-24 1.35V RAM. Booting with a tRCD of 9 at 1866 and over causes an infinite reboot cycle. 'Your RAM simply cannot handle it' you'd say. The catch is, I can boot without problems with a tRCD of 8 at DDR3-1866 1.65V. I tried upping RAM voltage up to 1.7V and VCCIO up to 1.2V to no avail. The only sensible explanation considering the symptoms is a BIOS bug of some sort. Have I mentioned the RAM does not work at stock settings at my board, but runs perfectly on a friend's Biostar TP67XE and on a P7P55D Deluxe?

And last time I upgraded my BIOS from 1305 to 1502 I had to downgrade due to S3 simply being non functional even at stock settings. Were there any other changes in that area in the 16xx series? I really don't want to have to downgrade again.

EDIT: Just did a couple more tests. DDR3-1600 7-8-7-24 works if I give the RAM some more voltage, but 7-9-7-24 causes a reboot cycle. Weird to say the least.

Thank you for your time.

Hi,

Could be a SPD/sub-timing issue. Fill out a BIOS template showing what all the DRAM timings are going to.

The BIOS fixes are listed on the previous page - if there was anything else to mention it would have been in the list.

-Raja

[danielkza]

Will do that, thanks for the help so far.

BTW I just flashed 1606 and I have the S3 issue as with 1502: with the exact same settings I was using without problems in 1305, sleep fails every single time.

I do like the board, but it is one temperamental beast.

[pr@$r1g]

The BIOSes I posted above are beta.

OK good to know. So do u have anything for P8P67 WS Revolution

[brammers]

Running 1606 here (On a B2 Deluxe). Other than the usual re-entering of settings (as the flash util clears CMOS) nothing abnormal to report, yet.

Still running 4.9G @ 1.4v.

All the usual quirks are still present (annoying intermittent several-second pause during POST etc). If anything changes I'll report back.

J

[Raja@ASUS]

OK good to know. So do u have anything for P8P67 WS Revolution

No, I have posted everything I was sent.

-Raja

[danielkza]

I made some small progress. I found out that a tRCD of nine with a CAS Write Latency of 8 over DDR3-1600 causes the reboot cycles. Chaning tCWL to 9 instead causes a hang with the DRAM LED lit up. The other subtimings don't make any difference at all: I relaxed CAS Write Latency, Write Recovery Time and Read to Pre Time up to 12, and DRAM RTL up to 40, and nothing changed. The funny thing is with a tRCD of 10, CAS Write Latency of 9 and above also causes the hang. Maybe it's my RAM after all?

Here are the subtimings set by the board, with XMP and 2133 9-10-9-28, respectively.

* Primary Timings *
DRAM CAS# Latency:       7
DRAM RAS# to CAS# Delay: 8
DRAM RAS# PRE Time:      7
DRAM RAS# ACT Time:      24
DRAM COMMAND Mode:       2

* Secondary Timings *
DRAM RAS# to RAS# Delay:      5
DRAM REF Cycle Time:          88
DRAM Refresh Interval:        6240
DRAM Write Recovery Time:     10
DRAM READ to PRE Time:        6
DRAM FOUR ACT WIN Time:       24
DRAM WRITE to READ Delay:     6
DRAM CKE Minimum pulse width: 4 
DRAM CAS# Write Latency:      7
DRAM RTL(CHA):                D0: 32, D1: 33
DRAM RTL(CHB):                D0: 32, D1: 34

* Primary Timings *
DRAM CAS# Latency:       9
DRAM RAS# to CAS# Delay: 10
DRAM RAS# PRE Time:      9
DRAM RAS# ACT Time:      28
DRAM COMMAND Mode:       2

* Secondary Timings *
DRAM RAS# to RAS# Delay:      7
DRAM REF Cycle Time:          118
DRAM Refresh Interval:        8139
DRAM Write Recovery Time:     10
DRAM READ to PRE Time:        9
DRAM FOUR ACT WIN Time:       33
DRAM WRITE to READ Delay:     9
DRAM CKE Minimum pulse width: 6 
DRAM CAS# Write Latency:      8
DRAM RTL(CHA):                D0: 32, D1: 39
DRAM RTL(CHB):                D0: 32, D1: 40

[Raja@ASUS]

I made some small progress. I found out that a tRCD of nine with a CAS Write Latency of 8 over DDR3-1600 causes the reboot cycles. Chaning tCWL to 9 instead causes a hang with the DRAM LED lit up. The other subtimings don't make any difference at all: I relaxed CAS Write Latency, Write Recovery Time and Read to Pre Time up to 12, and DRAM RTL up to 40, and nothing changed. The funny thing is with a tRCD of 10, CAS Write Latency of 9 and above also causes the hang. Maybe it's my RAM after all?

Here are the subtimings set by the board, with XMP and 2133 9-10-9-28, respectively.

* Primary Timings *
DRAM CAS# Latency:       7
DRAM RAS# to CAS# Delay: 8
DRAM RAS# PRE Time:      7
DRAM RAS# ACT Time:      24
DRAM COMMAND Mode:       2

* Secondary Timings *
DRAM RAS# to RAS# Delay:      5
DRAM REF Cycle Time:          88
DRAM Refresh Interval:        6240
DRAM Write Recovery Time:     10
DRAM READ to PRE Time:        6
DRAM FOUR ACT WIN Time:       24
DRAM WRITE to READ Delay:     6
DRAM CKE Minimum pulse width: 4 
DRAM CAS# Write Latency:      7
DRAM RTL(CHA):                D0: 32, D1: 33
DRAM RTL(CHB):                D0: 32, D1: 34

* Primary Timings *
DRAM CAS# Latency:       9
DRAM RAS# to CAS# Delay: 10
DRAM RAS# PRE Time:      9
DRAM RAS# ACT Time:      28
DRAM COMMAND Mode:       2

* Secondary Timings *
DRAM RAS# to RAS# Delay:      7
DRAM REF Cycle Time:          118
DRAM Refresh Interval:        8139
DRAM Write Recovery Time:     10
DRAM READ to PRE Time:        9
DRAM FOUR ACT WIN Time:       33
DRAM WRITE to READ Delay:     9
DRAM CKE Minimum pulse width: 6 
DRAM CAS# Write Latency:      8
DRAM RTL(CHA):                D0: 32, D1: 39
DRAM RTL(CHB):                D0: 32, D1: 40

What slots are you using??

At DDR3-2133 you'd definitely need a tWR of 12. Can you get the DRAM 100% stable at any frequency timing combo? What's it like at DDR3-1333 with 7-8-7-20 2N timings (super slack I know)? Just want to see where it's stable and where it falls over.

Also, can you list your third set of timings please?

-Raja

[danielkza]

I'm using slots A2 and B2 as recommended in the manual for 2 DIMMs.

Surprisingly the 9-10-9-28 setting I just posted is stable for 12h Prime Blend, even with a (automatic) tWR of 10. I tried setting the tWR to 12 at tRCD 9 again, and it doesn't change much: with CAS Write Latency of 8 or less I get a reboot cycle, of 9 or more hang at DRAM LED. I'll try 1333 7-8-7-20 latter and post my results.

BTW, it's great to get support from people that really know their stuff, and in my favorite forum. ASUS just got a couple more points in my book.

Here are the automatically set third timings for XMP 1600 7-8-7-24-2N and 2133 9-10-9-28, respectively.

* Third timings *
tWRDR(DD): 1
tRWDR(DD): 3
tRWSR:     3
tRR(DD):   3
tRR(DR):   1
tRRSR:     4
tWW(DD):   3
tWW(DR):   3
tWWSR:     4

* Third timings *
tWRDR(DD): 1
tRWDR(DD): 4
tRWSR:     4
tRR(DD):   3
tRR(DR):   1
tRRSR:     4
tWW(DD):   3
tWW(DR):   3
tWWSR:     4

[Raja@ASUS]

Thanks, looks like you need to keep a one clock spacing between CAS and tRCD - I think there is an SPD~BIOS issue when you set tRCD and CAS two clocks apart (so it seems). How does the same ram overclock in the Biostar board, do you have any CAS~tRCD spacing POST issues? I think the Eco sticks use Elpida BBSE type variants, which don't like tRCD too tight, although a two clock spacing should be possible.

[danielkza]

With the Biostar board I just enable XMP and it works perfectly at 1.35V (20min Prime95 blend). That was the only stress test I managed to do (since I was doing a build for a friend that doesn't really like to have his computer lying 'naked' on the desk. Some people are just no fun ), but I did get to boot at 2133 8-9-8-28.

And I believe ECOs are (reasonably binned) PSC chips like most G.Skill kits these days. If I had other kits around I'd take the heatspreader out and discover it myself, but my current budget is kind of non-existing.

EDIT: Just tested 1333 7-8-7-20N and it's stable for 1:30h Prime blend at 1.35V, with all subtimings at auto.

[amdsempron_xs]

Hi Raja,

I need your help here.

I have 2600K, P8P67 Pro (BIOS 1502) and Corsair DDR3-1866 7-8-7 Ver2.1 (Elpida Hyper confirmed).

The issue is it can't do DDR3-2133 with both 7-7-7 and 8-8-8 event at 1.75V

This Corsair kit is able to do DDR3-2133 8-8-8 at 1.675V on Gigabyte P67A-UD7.

I'm pretty this is the BIOS issue.

Do you have a beta BIOS for this issue already?

Thanks.

[Raja@ASUS]

Hi Raja,

I need your help here.

I have 2600K, P8P67 Pro (BIOS 1502) and Corsair DDR3-1866 7-8-7 Ver2.1 (Elpida Hyper confirmed).

The issue is it can't do DDR3-2133 with both 7-7-7 and 8-8-8 event at 1.75V

This Corsair kit is able to do DDR3-2133 8-8-8 at 1.675V on Gigabyte P67A-UD7.

I'm pretty this is the BIOS issue.

Do you have a beta BIOS for this issue already?

Thanks.

It's not BIOS per se. Some kits do better on some boards than others depending upon the PCB used. Here's my Corsair DDR3-2200 8-8-8-24 Rev kit 2.1 doing 8-8-8-20 (1485 or 1407):

http://imageshack.us/m/860/6121/mive32m5734.jpg at 1.67V or so on the MIVE


There is no BIOS fix for Hyper kits that don't work well.

-Raja

[amdsempron_xs]

It's not BIOS per se. Some kits do better on some boards than others depending upon the PCB used. Here's my Corsair DDR3-2200 8-8-8-24 Rev kit 2.1 doing 8-8-8-20 (1485 or 1407):

_http://imageshack.us/m/860/6121/mive32m5734.jpg at 1.67V or so on the MIVE


There is no BIOS fix for Hyper kits that don't work well.

-Raja

Did searching around, no hope

I'll return that kit and get a BBSE kit.

Thanks for your reply.

[Raja@ASUS]

Did searching around, no hope

I'll return that kit and get a BBSE kit.

Thanks for your reply.

If running single thread 32M there are a few tricks one can employ to aid stability, although it can be processor dependant. What kind of CPU speeds are you running and is this under sub-zero cooling or not?

-Raja

[Raja@ASUS]

With the Biostar board I just enable XMP and it works perfectly at 1.35V (20min Prime95 blend). That was the only stress test I managed to do (since I was doing a build for a friend that doesn't really like to have his computer lying 'naked' on the desk. Some people are just no fun ), but I did get to boot at 2133 8-9-8-28.

And I believe ECOs are (reasonably binned) PSC chips like most G.Skill kits these days. If I had other kits around I'd take the heatspreader out and discover it myself, but my current budget is kind of non-existing.

EDIT: Just tested 1333 7-8-7-20N and it's stable for 1:30h Prime blend at 1.35V, with all subtimings at auto.

Ok that means it's not completely unstable on the board. I would go up slowly from there and see at which point things start to be come "unfixable" via BIOS settings and get that back to me in a well laid out post that I can send off to HQ to see what is happening.

-Raja

[JohnZS]

I still believe that ASUS need to add more DDR3 RAM support for their LGA775 Rampage Extreme X48 based boards. 4GB DIMMS seem to be the norm these days and it would be nice for ASUS to upgrade the RAM compatibility.
Not only that but the ICH9R ROM and Marvell ROM's desperately need upgrading too.
Oh and the QX9650 CPU RATIO COLD BOOT issue needs resolving as well.
Thankfully ASUS support have provided me with a BIOS not to be issued externally which fixes the QX9650 manual multiplier cold boot issue and the ICH9R ROM, however ASUS need to issue these fixes for everyone.
I do appreciate LGA775 is old, but that is no excuse to leave the platform with an unfinished BIOS.
Please fix the remaining issues with 8GB and Quad Cores, MSR errors in BITS, update the ROMS and also add compatibility for 4GB DIMMS.
John

[Raja@ASUS]

Please fix the remaining issues with 8GB and Quad Cores, MSR errors in BITS, update the ROMS and also add compatibility for 4GB DIMMS.
John

Full validation of 4GB DIMMs may not be possible as the X48 chipset was designed around 2GB DIMMs at stock VMCH - so timings and frequency may be too conditional to validate in accordance with current 4GB DIMMs. I will take a look at the Intel white papers and see what the supported timings and frequency stipulations are for 4GB DIMMs on this now dated platform.

-Raja

[Brama]

Hi,

I have not had anything sent to me today. Which board do you have and what issues do you have with the BIOS please?

-Raja

I have an R3BE that is a little better than R3E but it has still the issues of R3E that Donmarkoni explained perfectly.
Plus there is another issue: if you use a PCIe raid disk controller, you can no more use the Intel raid controller since the update of Intel Option Rom in the BIOS to version 10.x.

Any other improvement is well accepted.

[Raja@ASUS]

I have an R3BE that is a little better than R3E but it has still the issues of R3E that Donmarkoni explained perfectly.
Plus there is another issue: if you use a PCIe raid disk controller, you can no more use the Intel raid controller since the update of Intel Option Rom in the BIOS to version 10.x.

Any other improvement is well accepted.

Well the QPI PLL I have already answered, so that leaves the OROM updates which will need to be validated before we update. I will ask HQ about that.

-Raja

[Ian[Frozen]]

Plus there is another issue: if you use a PCIe raid disk controller

Which many do..

you can no more use the Intel raid controller since the update of Intel Option Rom in the BIOS to version 10.x.

Can't understand why anyone would find a practical benefit too, I mean really...

[MrToad]

Plus there is another issue: if you use a PCIe raid disk controller, you can no more use the Intel raid controller since the update of Intel Option Rom in the BIOS to version 10.x.

I had the same issues with several boards and RAID/AHCI controllers (first time it happened to me was in a Striker Extreme with an Adaptec 5405), both ROMs try to load on the same address space, resulting in one of them (or both) not loading.

Easily resolved with BIOS update, although the fix might not be "universal" as different manufacturers and models load the ROM to different addresses, so the fix may resolve the conflict with one model of RAID card, but create a conflict with another one...

[spoolindsm127]

Well the QPI PLL I have already answered, so that leaves the OROM updates which will need to be validated before we update. I will ask HQ about that.

-Raja

Hello Raja

I also think it's great Asus is stepping forward with some solid 'in-the-field' support

Okay so we may never have independent QPI PLL control in R3E bios. But can you try to find out what the voltage is set to for QPI PLL?

And regarding the QPI PLL voltage being linked to CPU PLL, I think this may be true. I get drastically varying results when running SPI32M and trying different CPU PLL values, but keeping all other voltages same..

I believe it was a Asus support guy or OCer (LardArse) who said the PLL values were linked.