Here's a link that might make it easier to keep up with bios updates. I didn't read through the whole thread so if this has been posted before sorry.
http://hwbot.org/forum/showthread.php?t=15952
Printable View
Here's a link that might make it easier to keep up with bios updates. I didn't read through the whole thread so if this has been posted before sorry.
http://hwbot.org/forum/showthread.php?t=15952
MrToad IS OUR CHAMPION AND SAVIOR!!!
Installed the beta BIOS with his infused Marvell update, windows install instantly detects the drive and has no problem addressing it in AHCI! Immediately snappy in installing Windows (still had to get the Marvell driver on thumb drive for the install), and everything installed very quickly to the C300. It's fixed! I can finish!!! Good show, MrToad :clap:
Asus Support: Thanks for dumping your customer. Go eat a d:banana:ck.
Thanks a lot for that link :)Quote:
Originally Posted by pinto
Just to let you guys know we are looking at this thread. I've just started with ASUS this week and Xtreme Systems is one of the places I aim to provide direct proactive support.
Congrats!! I'm so glad that these companies hire guys like you and Tin recently. Kudos to Asus!!Quote:
Originally Posted by Raja@ASUS
Bios 805 for the Rampage III Gene is online now!
ftp://ftp.asus.com.tw/pub/ASUS/mb/LG...page_III_Gene/
**Update Intel Raid Option ROM
:D
Bios 1301 is out for R3E
ftp://ftp.asus.com.tw/pub/ASUS/mb/LG...ge_III_Extreme
Gene 0805 Vanilla
For me:
Better Mem-support (XMP Ripjaw RH in 6x4Gb works)
Lower vCore = Lower temps (2 degrees)
Stable
Gene 0805b (MrToad cooked)
See above +
Better performance Liteon LAT-256M2S
XII, please define stable? i.e. you were able to get higher OCs with the new R3G release? Sorry if I sound dumb but Gene 805 "Vanilla"?Quote:
Originally Posted by XII
With the better mem support, what was occuring with 704 and your memory that is working better now? I've been having a hell of a time with my Dominator GT 7-8-7-20 2000 RAM
What processor and what OC are you running where you could lower your vCore and by how much?
So the top pic of the bench one is the stock R3G 805 ROM using the marvel controller and the bottom is after the updated marvel ROM that MrToad provided?
Also, since the build numbers are the same I'm assuming I don't need to DL the one from Asus?
Stable: Have thrown all my benchmarks en test utility`s at it, and no crash.
Mem @ 1660 7-8-7 24Gb Core ~4G
Spd is working, 0704 was all manually.
GT`s I don`t have, but will test with Hypers, to see if they work, when there is time.
Vanilla: stock Asus 0805, with Marvel 1019
MrToud: Stock Asus 0805, with Marvel 1029
In this case I`d say: Go with MrToad.
As for updating: Flash is double, and don`t turn it off. First bios, reboot, Marvel, reboot.
Quote:
Originally Posted by R37ribution
Preliminary tests with the C300 64GB connected to the Marvell with new BIOS. The drive is also the OS drive, test program run from a thumb drive. 8MB test:
http://img839.imageshack.us/img839/8434/prelimc300.png
32MB test:
http://img40.imageshack.us/img40/375...imc30032mb.png
Pretty darn good, but I'm sure it could be better. Still need to enable write-back, but I have no UPS right now.
ASUS please update Rampage II Extreme bios too.
I checked the latest 1914 bios, it contains:
Intel ROM 8.0.0.1038
JMicron JMB36X ROM 1.07.14
Marvell 88E8056 ROM 6.15.1.3 (not sure about that though)
I believe that these ROMs need update badly.
They didn't even update them in this new beta BIOS, WE had to. :shakes:
Still going strong with the modded BIOS! 3D apps are freaking out right now, but I think it's more of a driver issue or the messed up CF bridge I have on the cards right now. Finished HDD testing over the weekend, will post results soon!
Is there a R3E bios 1301 with the latest Marvell controller firmware on it? Is that possible?
Modified Bios 1301: HERE OR HEREQuote:
Originally Posted by sprayingmango
File: rampageiii-extreme-asus-1301-updated-marvell.rom
1. Updated Marvell 9128 controller Rom/Firmware (Bios: 1.0.0.1029 - F/W: 2.2.0.1113)
File: rampageiii-extreme-asus-1301-updated-marvell-Intel.rom
1. updated-marvell-Intel.rom - Updated Marvell 9128 controller Rom/Firmware (Bios: 1.0.0.1029 - F/W: 2.2.0.1113)
2. Updated Intel ICH10R to 10.5.0.976 (Note: This version is the latest extracted from Intel Z68 board yet to be released. Not many reports on reliability yet - so be careful if you have critical data on your array)
Update Procedure:
1. Load Setup Defaults
2. Update Bios (using QFlash or DOS Flash utility)
3. Reboot when Prompted
4. Load Setup Defaults + Set Marvell Controller to AHCI mode
5. Save Settings and Reboot
You will see a message that Firmware is being Updated. BE PATIENT. You will see a message "Suceessfully Completed" (Approx 2 minutes)
6. Power Down
7. Reboot
8. Apply your custom settings/Overclock profile
9. Save and Reboot
10. Hit <Ctrl-M> to open up Marvell Configuration during boot and verify the updated versions
11. Report back to the forum :)
can't downloan the files and I always don't enable cookies for unknown websites, so if this download site is req. them, please send them in an different way.
R
Updated my post with a download link added to Megaupload. Cannot attach file here due to size.Quote:
Originally Posted by DualCpuUser
I've had a word with HQ about keeping ROMs up to date (assuming they pass our internal validation). As soon as I have an update I'll post back here.
Please update the BIOS for the P6T Deluxe V2 while you are at it.Quote:
Originally Posted by Raja@ASUS
Thanks!
I'll pass the info on.Quote:
Originally Posted by MarkAtHome
Last two bios versions for Rampage Gene III mess up cpu temperature readings on my system, with bios 0602 temps look like this at stock settings:
http://i826.photobucket.com/albums/zz182/mm_67/602.png
And this happens with bios versions 0704 and 0805:
http://i826.photobucket.com/albums/zz182/mm_67/805.png
Cpu temperature reading jumps from 26 C to 74 C. I know that this reading is false and I wouldn't even mind much except that this high reading also messes up fan control. Because of this crazy temperature reading all fans are always running at full speed. For now I have gone back to 0602 version which works but I do hope that next bios version comes without this side effect.
Did a fresh install (had an accident when trying to move my User folder :( ) and still getting the same results. It appears my test is about on par with most of the tests out here, I used this place as my reference http://www.ssdreview.com/review/comp.../hdtachrw.html) I have no idea how/why my burst speed is so high but I'll take it! One thing that I wonder about is the Write Caching, the test gives the same results with or without it on. Wondering if this is the transfer ceiling for the controller?Quote:
Originally Posted by WangChung
My CPU PWM fan control works correctly with both the 704 and 805 revs...Quote:
Originally Posted by mm67
We are not a lot of people, but we wish a little more support on R3E BE BIOS. It is still using first BIOS 0404...An upgrade is due. :)
You can try this in the previous page post #407 ;).Quote:
Originally Posted by Brama
Thanks a lot.
I missed it. :)
I can confirm that the moddet bios for Asus RE3 is working allright... thx for the very good work
Kindly
CB
Thanks very much for the updated 1301 BIOS for R3E.:DQuote:
Originally Posted by p4spooky
Now that both Marvell 9128 controller Rom and Firmware is updated on the R3E, does anyone know if this improves the performance of SSDs on the Marvell controller? and is there any improvements using RAID on the Marvell controller?
Has anyone that has tested this BIOS out on the R3E noticed any improvements on the Marvell 9128 controller?
Thanks for responding.
Wow... You can't read? look at the post right above yours...Quote:
Originally Posted by Sylver123
This is an enthusiast forum. Try it yourself. We are not your guinea pigs.
ok mate, calm down.Quote:
Originally Posted by zoson
zoson, you have become so intolerant lately... :shakes:
I have been answering his questions for the last few weeks. It is people like him with no ambition to test on their own that is bringing the quality of the forum down.Quote:
Originally Posted by donmarkoni
His attitude is easy to see in the R3E thread and this thread. You can simply click his name and look at his posts to see that he wants to do no work and have the community set up his PC in every way for him.
His behavior and his posts are disrespectful to the people like you and I who actually test, explore, and learn about our hardware. I have no tolerance for that kind of disrespect at all.
I see your point. :yepp: Just try to ignore those that annoy you, that's what I do.Quote:
Originally Posted by zoson
Back on thread's topic...
To Officials: Is there going to be any updates with asked stuff implemented (HPET, SATA firmwares, etc...) before we all go to socket 2011?
People here proved almost everything possible, but we never got it from you.
You know, you are such f***ing a idiot.Quote:
Originally Posted by zoson
I am very offended by your comments.
What did I ever do to you?
It wouldn't surprise me at all if you were an administrator here, you would probably ban people like me from the board because of asking for help without going through the hassle of searching or testing myself.
I aint going to change the way I do things on this board for you and there's nothing you can do about it, and if you don't like it, then that's your problem.
Calm down lads and plz skip the F words...
Zoson Eextremsystems already turned into a general help forum a long time ago.... we all have the knowledge and like to share that too. I do agree with you that indeed some better learn the tools of the trade, instead of just copying templates and then cry out : your settings don't work !
I too wonder sometimes why some even bought the high end hardware to get a meazle 4ghz OC and even can't get that one setup properly...
I have been very aggressively adding people to my ignore list now. It is very sad.Quote:
Originally Posted by Leeghoofd
The reason why it turned into a general help forum is because the hostility towards disrespectful people is frowned upon.
This really says it all. They keep coming back because people keep helping them instead of telling them to go elsewhere. If nobody helped them, they wouldn't come here.Quote:
Originally Posted by Sylver123
Has anyone had a problem with the OC Profile Utility?
I was benching my R3G a while back (I think on BIOS 602, but it could have been on rev 501) trying to hit the 4.5Ghz mark and it BS. When I rebooted all my profiles under OC Profile were whiped out and I could not restore any of the CMO files from the OC Profile Utility. This has happened multiple times since, sometimes all the BIOS settings randomly set (i.e. random voltage monitors are set to ignore, fan speed/monitors are randomly set, and even the CPU vcore I've seen set to 1.8v! and of course I have never done this!) - I atribute these abnormailties to an incorrect IOH voltage, but I have never gone above 1.35v...
Ever since this happened the first time, my OC Profile has been acting funny - it will whipe out all my profiles every so often - which really sucks because I can't restore the old CMO profiles with the OC Profile Utility. At first I just ignored it and wrote down the settings in hopes that a new BIOS would remedy the problem restoring the CMO files with the utility, but as of the latest 805 release it hasn't.
Last night I powered up my machine and yet again, all my BIOS settings were whiped and all my profiles were gone. I routinly backup my profiles using the OC Profile Utility (which of course cannot be restored) but failed to write down my settings this time. This is extremely irritating because I just reached my highest 20x Linx stable BCLK ever with this 805 BIOS (224x17) and now everything is gone.
I went so far as downgrading back several revs of the BIOS, overwriting the Profiles each time (I know that some BIOS options were added between revs and due to this fact the profiles are incompatible between different BIOS revs). Until I got down to the shipped 404 BIOS. I am unable to restore any of my older profiles (I saved each profile with the BIOS rev in the filename) or new ones I tested saving as I downgraded BIOS revs. I have also tried different hard drives thinking it might be a problem with my media.
It's important to note that there aren't any other signs of problems with this board. As you can see it is a decent performer with the 224 bclk. I'm wondering if whatever the chip is that the OC Profiles are stored on is simply degrading, and if it is... can I replace it?
Has anyone else had either issues I'm having with any Asus board? 1) All settings in the BIOS getting whiped (including your profiles). 2) OC Profile Utility will not restore any saved CMO file, dispite the fact that the OC Profile Utility says it has successfully done so.
Ok series of beta BIOS updates just landed with me:
The fix-list is as follows (for all BIOSes):
1. Enhance support for Game Port on old audio cards.
2. Enhance SATA compatibility
3. Enhance mouse/keyboard support under UEFI
4. Enhance USB2.0 / 3.0 legacy support
5. Enhance PCIE compatibility
6. Enable support of CAS = 4 DDRIII-1333 modules
BIOSes
P8H67-M-EVO
http://www.mediafire.com/file/3sq6pn...-ASUS-1607.zip
P8P67
http://www.mediafire.com/file/b759m6...-ASUS-1608.zip
P8P67 Deluxe
http://www.mediafire.com/file/ib9xep...-ASUS-1606.zip
P8P67 Evo
http://www.mediafire.com/file/ucm9i3...-ASUS-1606.zip
P8P67 Pro
http://www.mediafire.com/file/qsuatg...-ASUS-1606.zip
P67 SABERTOOTH
http://www.mediafire.com/file/zl2eca...-ASUS-1606.zip
17** series BIOSes are currently being prepared and we hope to have them ready in a few weeks.
-Raja
Any chance of a little more detail on the two "Enhance XXX Compatibility" items please?
Thanks
J
That's all I have and HQ is now off work for the weekend.Quote:
Originally Posted by brammers
-Raja
ability to downflash sir Rajinder ?
Does ASUS update not allow that already if you go into the options?Quote:
Originally Posted by Leeghoofd
One reason I don't like the downflash stuff myself is where OPROMs are updated and users upgrade RST drivers - then roll back BIOS and get issues due to leaving the drivers active = support nightmare.
-Raja
Would you be good enough to get more details on Monday about the changes please?
Thanks
J
Is there any ETA of the flight containing update to ROG MB like R3E and R3BE? :)Quote:
Originally Posted by Raja@ASUS
Is anything coming for P8P67 WS Revolution enhance OCing or so ?
There is a similar beta BIOS being tested for the WS boards - same fix list as above. Does not say anything about OC changes.Quote:
Originally Posted by pr@$r1g
-Raja
Hi,Quote:
Originally Posted by Brama
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
If I may...
When people ask for a new BIOS, it doesn't necessarily mean that there is something wrong or they are having issues. That is for Asus forum.
It is expected from you (not personally you, but Asus) to fix problems and you never fail to do so, if my mind serves me well.
But...
We here (if I'm at liberty to speak for everyone) usually ask for some improvements that we know can be done, cause some other manufacturer did it, or some superuser did.
I remember three things asked, but never got the answer:
1. QPI VTT control
2. HPET deactivation
3. SATA firmwares update
"No" is the answer too, but we never got it.
If something can't be done, like QPI VTT control maybe, cause of HW limitations, we expect to get the answer.
HPET and SATA "issues" were proven possible by BIOS modding and you never did anything or said anything. Again, not you personally, but I'm saying all this to you personally cause I followed your work before you were @Asus and you were always helpful and that didn't change now when you are @Asus.
IMO, people appreciate truth and openness, so if you say something will not be done, everyone will respect you (Asus) for saying so, rather then staying silent or lie.
Lie is the worst thing of all, makes company loose respect and credibility, like creative* did by saying, I'm paraphrasing "no, our old HW can't work on Win7, you must buy our new HW" and a guy proved them wrong - or should I say, caught them in big lie, just with small driver modification.
*no, it is not syntax error (capital first letter), it's disrespect.
Any info on the new updated P8P67-M Pro BIOS? ftp://ftp.asus.com.tw/pub/ASUS/mb/LG...-ASUS-0713.zip
Hi,Quote:
Originally Posted by donmarkoni
Just need the issues not a diatribe, as I cannot read between the lines nor know the outstanding fix requirement for every single product in the wild. If only half of the information is given I need to ask the rest.
What is
1. QPI VTT control?
You need more granularity? The granularity is dependant on the VID table support of the buck controller so what you have now is likely all that can be given.
As for the other two I will ask - that is all I needed.
-Raja
Fix list should be the same as all other P67 updates today but I will confirm.Quote:
Originally Posted by ghost_recon88
-Raja
I believe he meant QPI PLL voltage control. It is currently 'bound' to the CPU PLL control, and we have no reference as to what it set with various CPU PLL settings.Quote:
Originally Posted by Raja@ASUS
Where did you learn it was bound to CPU PLL? As the DC requirements of both are different, which means you'd needs a secondary regulator on-board to provide the step-down (would have to be a pretty good LDO with a high side feed of only 1.8V).Quote:
Originally Posted by zoson
-Raja
Quote:
Originally Posted by Raja@ASUS
Quote:
Originally Posted by zoson
First thing first, zoson is right, I meant QPI PLL, I am just very tired, so I made a mistake.Quote:
Originally Posted by Raja@ASUS
Second, we are making a progress we haven't seen in a long time. You just made some things clearer. :up: Nobody took the time and effort until now to give an explanation. :shakes:
Everybody thought (as zoson and me of course) that QPI PLL is linked to CPU PLL and you are saying that it is not. Please explain us to what is it linked to, if anything.
I could also assume it just might be fixed to default 1.1V and uncontrollable, but that might be wrong as assumption that it's linked to CPU PLL.
So, you get my point? Any answer is a good answer. :yepp: If we know how things work, we'll make the best of it.
Third, and back to the beginning of your post... diatribe...
I didn't even knew what that means, as English is not my mother language. When I looked in the dictionary I was very disappointed at first, cause you see my criticism in the wrong way.
Look around and find my posts, then judge if my posts are bitter or ironical or non-constructive.
But, for the sake of good relations and constructive talk, I'll just accept that as your subjective experience of my post, and I'll try to be more careful how my posts sound like.
It is either going to be using a fixed regulator or possibly linked to IOH voltage (less likely). Either way, if some kind of control were available you'd have had it by now.Quote:
Originally Posted by donmarkoni
-Raja
That is the honest answer that will be respected by everyone I think. :yepp:Quote:
Originally Posted by Raja@ASUS
And thank you for that. :up:Quote:
Originally Posted by Raja@ASUS
Raja, I asked asus tech support:
And got this reply:Quote:
Originally Posted by Zoson
Quote:
Dear Valued Customer,
Thank you for contacting ASUS Customer Service.
My name is Stacey and it's my pleasure to help you with your problem.
Please enter BIOS>Extreme Tweaker>CPU PLL Voltage to adjust it.
You could contact with me if you have any other questions.
Raja is there any possibility of releasing beta bios's to the public as gigabyte does, it somehow feels good playing with different bios.Quote:
Originally Posted by Raja@ASUS
Any time soon will it be there. :)
The BIOSes I posted above are beta. :)Quote:
Originally Posted by pr@$r1g
She misunderstood what you were asking for as CPU PLL - so disregard it.Quote:
Originally Posted by zoson
-Raja
@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,Quote:
Originally Posted by danielkza
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
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.
OK good to know. So do u have anything for P8P67 WS Revolution :)Quote:
Originally Posted by Raja@ASUS
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
No, I have posted everything I was sent.Quote:
Originally Posted by pr@$r1g
-Raja
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.
Code:* 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
Code:* 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
Quote:
Originally Posted by danielkza
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
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.
Code:* 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
Code:* 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
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.
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 :D), 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.
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):Quote:
Originally Posted by amdsempron_xs
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 :(Quote:
Originally Posted by Raja@ASUS
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?Quote:
Originally Posted by amdsempron_xs
-Raja
Quote:
Originally Posted by danielkza
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
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
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.Quote:
Originally Posted by JohnZS
-Raja
I have an R3BE that is a little better than R3E but it has still the issues of R3E that Donmarkoni explained perfectly.Quote:
Originally Posted by Raja@ASUS
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.Quote:
Originally Posted by Brama
-Raja
Which many do..Quote:
Originally Posted by Brama
Can't understand why anyone would find a practical benefit too, I mean really...Quote:
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.Quote:
Originally Posted by Brama
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...
Hello RajaQuote:
Originally Posted by Raja@ASUS
I also think it's great Asus is stepping forward with some solid 'in-the-field' support :up:
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.
Please refer to my previous post about the DC requirements of the CPU PLL rail and the QPI PLL rail. To clarify; the CPU PLL rail needs a minimum of 1.8V at stock, while QPI PLL requires 1.1V and both should be regulated. 32M as an example means nothing as the QPI bus plays no real part in Super Pi. I'd be looking at vIOH first and foremost due to the DC requirements of that rail being similar.Quote:
Originally Posted by spoolindsm127
-Raja
I admit I did not completely understand your previous post regarding the DC requirements, so I appreciate the clarification thank you. I see what you are saying, I will have to see the effect of different IOH voltages.Quote:
Originally Posted by Raja@ASUS
Would you happen to know how to measure QPI PLL voltage on the motherboard? Or is that even possible?
I think I made another bit of progress with my RAM troubles: trying XMP again, I decided to set the the timings to SPD values manually, with an addition, setting CAS Write Latency to 8 instead of the default 7. I got a boot at the rated DDR3-1600 7-8-7-24. Running a round of Prime95 Blend to see if it is actually stable: if it doesn't fail to quickly I'll leave it overnight, and if it is indeed stable, we'll have a clear culprit, tCWL.
Hi, I am currently running 4 x G Skill F3-12800CL7-2GBECO dated 2010Oct in my Asus Sabertooth P67.Quote:
Originally Posted by danielkza
I need to run it at minimum 1.425v to operate at 1600-7-8-7-24-2T.
Here are the sub-timings that AIDA64 reports you need to run it best 7-8-7-24 (CL-RCD-RP-RAS) / 40-88-2-5-12-6-6 (RC-RFC-CR-RRD-WR-WTR-RTP).
I am running Write CAS Latency (tWCL) 7T and everything is great.
Not had great luck with overclocking 100% stable, but will report more if I do.
I have the same memory. It was 100% stable on my x58 Sabertooth at 1.35v.
On my P8P67 EVO it needs 1.45v @ 4.5GB OC. (1600-7-8-7-24-2T)
tWCL does not seem to be a factor.
On my R3E it needed 1.4v, on this board at 1.4v I get BSOD. tWR does seem to effect stability though, at auto at 1600 it sets it at 10, but according to AIDA64 12 is best for the XMP profile, I put 12 in and it helped stability when I was gaming, but still need more testing )))
Oh btw Raja, my ASUS Sabertooth would crash after 15 to 20 minutes of Intel Burn Test when I had 5 or 6 SATA hard drives on the intel ports, but not when I had 4 or less, have had to move things around so am using the marvell controller and no more than 4 intel sata ports, have not tried putting more than 4 on there since I updated to the 1606 BIOS, think it is worth trying or is there a limitation on the chipset?
Quote:
Originally Posted by mjgr33n
There should be no loading limitation on the SATA ports per se. Were you running the system at stock or overclocked?Quote:
Originally Posted by mjgr33n
-Raja
Would it be possible to unlock the MMIO space for the RAM timings for P67 so they can changed in software?
Consider for example this configuration:Quote:
Originally Posted by Ian[Frozen]
- OCZ Revo drive
- 2 HD in raid0 on ICH10r
or
- Adaptec SAS/SATA controller with 2 HD in raid0
- 2 SSD in raid0 on ICH10r
Both configurations can not be used since the Intel OROM was updated to version 10.x
They are not common configurations, but not so rare.;)
Can you please confirm that on R3E and R3BE it is not technically possible to have automatic reduction of cpu voltage from full cpu load to idle when you overclock?
It was a very usefull BIOS setting in R2E which enables RELATIVE Vcpu with an OFFSET regulation, or an ABSOLUTE value which never changes.
This sounds like a problem with your PSU, not your motherboard.Quote:
Originally Posted by mjgr33n
He did confirm this. R3E and R3BE does not do absolute changes. I think it's because R3E and R3BE use digital power circuitry vs analog found on R2E.Quote:
Originally Posted by Brama
There is no problem with my PSU, please read what I posted before commenting, I said I moved them to different ports, so I still have the same amount of hard drives in the system, just now I am using the marvell ports instead of the intel ones and it is fine, also with same psu I did not have this issue with my R3E or R2E, PSU is also a Corsair Gold AX1200, so plenty of power, using different ports does not change power requirements.
I let Prime95 ran for 6h and it was stable at rated 1600 7-8-7-24 with tCWL 8 at 1.35V. Maybe it's worth trying if you want to keep 1.35V. But I had no suck luck with tRCD 9 over 1866, I even tried some weird combinations like 11-9-11-40 but I cannot boot it at all. Can't complain that much considering I can get 2133 9-10-9-28 at 1.6V, and probably still a bit better (I'll find out later today, I hadn't previously tired to mess with tCWL, maybe it'll help me to get CAS 7 or 8).Quote:
Originally Posted by mjgr33n
You can't rule out the PSU as an issue unless you try another, different, psu in the configuration that was causing issues before.Quote:
Originally Posted by mjgr33n
The speed is 5GHz and I'm on water :-)Quote:
Originally Posted by Raja@ASUS
The kit has been returned. I'm gonna get a Ripjaws X BBSE kit :yepp:
Thanks anyway :)