Printable View
Yeah, I read it somewhere, but just can't find it now. :confused:Quote:
Originally Posted by zoson
Anyway, DFI UT X58 has Digital VRM and it can do relative voltage changes.
If Asus can't make it, then it must be cause of Hybrid (digital-analog) VRM.
Thank you,Quote:
Originally Posted by Raja@ASUS
I think you will not have much luck with Intel White Papers as a lot of these were conceived before 4GB DIMM production was even around.
Theoretically X48 can address upto 16GB of RAM (and some users have already provided proof of 12GB and 16GB running on their Maximus Extreme and Rampage formula Boards).
The issue lays in that ASUS' Memory QVL for the Rampage Extreme is woefully old and needs a radical update.
Also BITS (www.biosbits.org) MSR errors have been reported by myself and at least 4 other forum members, any ideas as to if/when these will be fixed for ultimate platform stability?
Thanks
John
I have tried both, also when it is not at load it can be on all week with no problems. Is there a fault with the board possibly? I am going to try some more testing with the new BIOS later.Quote:
Originally Posted by Raja@ASUS
Also would like to elaborate, it is not normal crashing per say, it is stuttering/freezing/locking up, sometimes it lets me shut intel burn test down, but cannot shut task manager down or close AIDA64 and it will definitely not let me shut the pc down without hard reboot, but can still move mouse around and open internet and some other programs. Just seems like everything has got bottlenecked but more extreme.
Initially when I first got this problem I did think it was PSU, CPU, Memory, MB, maybe one of my PCI cards or even the backplate on my EK waterblock, so I tested everything by swapping PSU to a Corsair HX750 which is with my R2E board in my other pc, tried a Sandybridge core i5 2400 from my HTPC, tried some spare Corsair memory, removed my ASUS pci sound card which needs a molex power feed, also got the new EK 115x true backplate and the new easy mount system for my waterblock.Quote:
Originally Posted by zoson
Nothing made any difference, it still started freezing/stuttering at the same point every time, I probably could have timed it, but it was roughly 15 minutes into load testing, made no difference whether I was at stock (or with the i5-2400) or overclocked to 4.8Ghz.
At least at the moment, by moving 2 drives off the Intel ports onto the Marvell ports it works perfectly without crashing, have load tested it for an hour straight with no issues, also gamed all night and not a single stuttering episode.
Currently got, 1 SSD and 3 SATA HD's on the Intel ports and got 1 SATA HD and 1 SATA DVD drive on the Marvell ports.
Is that a B2 or B3 revision Sabertooth with the problem?
The symptoms sound a lot like the SATA issue that the B3 was meant to resolve.
J
Currently running it now at 1866 at 1.5v with the following settings completely stable, basically 8-9-8-24-2T and everything else set to auto except tWR which have set to 14.Quote:
Originally Posted by danielkza
Quote:
Memory Timings
CAS Latency (CL) 8T
RAS To CAS Delay (tRCD) 9T
RAS Precharge (tRP) 8T
RAS Active Time (tRAS) 24T
Row Refresh Cycle Time (tRFC) 103T
Command Rate (CR) 2T
RAS To RAS Delay (tRRD) 6T
Write Recovery Time (tWR) 14T
Write To Read Delay (tWTR) 7T
Read To Precharge Delay (tRTP) 7T
Four Activate Window Delay (tFAW) 28T
Write CAS Latency (tWCL) 8T
B3 RevisionQuote:
Originally Posted by brammers
Quote:
Originally Posted by mjgr33n
Drop me a PM listing your parts and settings again (as I can't find yuour earlier post here for some reason) - and I'll get someone to take a closer look if need be. List driver versions and RST drivers used if any.
-Raja
CheersQuote:
Originally Posted by Raja@ASUS
EDIT: Finally got around to testing with 1606 BIOS and 5 sata drives on the intel array and so far soo good, ran intel burn test for over 30 minutes with no issues, going to try with 6 next, see what happens.
EDIT2: Ok, I have tested with 6 drives on the Intel Array with 1606 BIOS and all is working great, over 30 minutes of Very High on Intel Burn Test, so looks like the SATA fixes for 1606 fix my issue as well ))))
Happy now ))
Why are you even here asking then? It sounds pretty obvious that the board is defective... ;)Quote:
Originally Posted by mjgr33n
Cool beans :)Quote:
Originally Posted by mjgr33n
Good settings you got there, I'll give them a try latter today. I tried 2133 8-10-8-28 with XMP subtimings and got an almost-instant (3 minutes) Prime fail, so here goes my hope of keeping the secondary timings quiet.Quote:
Originally Posted by mjgr33n
Hey Raja, do you have any comment for this post from earlier of mine?
I'm getting the run around at Asus support. At first they said they needed to ship me a new BIOS chip. Now they are talking about RMAing my board. I really just want this resolved. A failing BIOS chip seems more logical to me but I just wanted to get another opinion. I'd rather not RMA the board if I don't have to, it seems to OC VERY nicely.
Thanks in advance, Aaron
Quote:
Originally Posted by R37ribution
Wow, you failed again, BIOS 1606 fixed the issue, you do not bother reading all the information people write, you give awful advice and you attack people with no provocation questioning there validity to post, my issue was related to BIOS and I correctly put it in the beta BIOS section, I had thoroughly tested before doing so (I am not some technical noob, I have been working in IT industry for nearly 15 years now and I get paid a lot of money for my advice and technical knowledge) leaving BIOS as my last option and the beta BIOS (which is no longer beta) fixed the issue, I am pretty sure that qualifies me to post here.Quote:
Originally Posted by zoson
Also, the only thing I asked of anybody when I came here, was the opinion of whether or not it was worth doing another round of exhaustive tests with the new BIOS (which it turned out it was), as I had already spent several days finding what the issue was, also I addressed this to Raja@ASUS as he would have been one of very few people that would have been qualified to answer the question.
Anyway, the issue is fixed now and I am very happy, although it would be nice to know what the enhance SATA compatibility did or whether there was anything else in the new BIOS that helped fix the issue?
^_^
Quote:
Originally Posted by R37ribution
Hi Aaron, they may have decided it is best to get the board back to test and see what caused the issue. In which case I would go with what they say.
Where are you based?
-Raja
A big +1000 on this!Quote:
Originally Posted by spoolindsm127
@Raja can you help on this mate ?
EDIT:
Sorry for offtopic
I'm out of Ann Arbor, Michigan.Quote:
Originally Posted by Raja@ASUS
The origional guy I talked to hadn't heard of the problem before and consulted someone named Sunny said he saw the problem with the chip degrading before and it needed to be replaced. I was pretty happy with this solution because it fit everything I had hoped for (no taking the PC apart and I get to keep a known good OCing mobo). He said I had to call back before 5:30pm when the "BIOS" department is open. I called back and got a woman who told me I had to pay $5 for the chip (even tho my board is under warranty) and $15 for shipping this coupled with her snobby attitude made me pretty irritated and I asked to speak with a "supervisor". I've worked in a call center before I know how these things go, its not really a "supervisor" you talk to.
This person started doubting Sunny's solution would fix the problem and said there is another chip on the board that could be bad.
Basically I've been waiting for a call back for over a week now. I just want to know if the OC profiles are stored in the BIOS chip or not or if there is even the possibility of another chip on the board causing this as this guy suggested. Otherwise, I guess I'll shell out the $20 and just buy another chip because the OC profile Utility save to media utility on my board cannot restore the profiles to this area of the chip.
Hi,Quote:
Originally Posted by R37ribution
From a distance I doubt it can be answered absolutely, so I'd say its best to RMA it - even though it's going to be a pain for you. If you want to proceed with that I can help, just drop me a PM.
-Raja
The only person making attacks here is you, and you've been reported for it.Quote:
Originally Posted by mjgr33n
You provided incomplete information, which is why I suggested the things I did.
You only outlined your testing of things after I suggested you do them. You can't blame me for your own failure to disclose relevant knowledge.
You admit that you didn't test 1606 because you didn't think it was worth it. Guess what, you came to the forum without testing and your issue was already resolved. I'm sure Raja doesn't mind dealing with you because he gets paid for it, but thanks for wasting everyone else's time.
LOL, I never admitted anything of the sort about not thinking it was worth it, I said I had fixed the issue myself by moving around the hard drives to different ports, I asked an opinion of whether or not Raja thought it was worth testing again now that I had the new BIOS given the fixes that was in it after I had 'already' done days of testing (I never tested anything because you asked, I had already done it), also in case anybody had heard of a similar issue.Quote:
Originally Posted by zoson
You failed to read what I had wrote about moving ports and because of your failure you thought I had removed drives and gave bad advice about power supply.
Because of the response I got from Raja telling me that there should be no issue with the chipset or any types of bottlenecks, that prompted me to try again with the new BIOS and do exhaustive testing again which proved that the sata fixes in the BIOS fixed the issue, which was great ))
While I was testing you started saying I had a faulty motherboard, which was obviously wrong, I do not remotely understand why you are posting in this section of the forum if you have nothing useful or helpful to say or if you are going to keep being wrong.
Also one only has to look back a few pages to see you attacking other people, in those posts you attacked people for not being willing to test things themselves which I obviously have tested myself, I not only test things as part of my job I also love experimenting with IT.
I can take apart AMI BIOS's, I used to hack them with custom memory tables, OROMS and cpu updates, even bricked a board in attempt to learn things and further the helping of others on other forums.
Yet I come here posting help to one other member who has been having issues with the same memory as me and while I was here I figured I would ask a simple piece of advice, which was not greatly important due to the fact I had a temporary fix, also I figured if at least I posted the issue and then the BIOS update fixed the issue or it did not and something else did, if somebody else ever came on this forum and asked the same issue people could point them at this post and it would help them.
In IT if you have a strange issue you make sure it is documented somewhere and the fix too so that others can learn, but from your responses you do not seem to care about helping anybody, just having a go at people and making mistakes.
Feel free to report me, I directed my question to Raja initially not you and you where the one who made the mistakes, I am only guilty of laughing at you and pointing out said mistakes, you are the one getting annoyed at people and I am here sat behind my desk smiling because my issue is fixed, I have helped somebody with there memory issue and given a fix for anybody that comes looking for help with the same issue and lets ASUS know so that if somebody logs a call with them that BIOS 1606 fixes the issue, so win win for me and everybody except you.
Oh and I just got news this morning that I have got a new contract for even more money with one of the top IT companies in the world and get to see my girlfriend in a few weeks who I have not seen for a few months, so yeah in the grand scheme of things reporting me has to be on the very bottom of my list of remotely important things in life I have ever remotely heard of :P
Raja@ASUS m8 can you provide recent Beta Bios for Gene-Z please ?
We got some noise problem with it tho c3/c6 has been disabled.
Hi,Quote:
Originally Posted by IronAge
I don't have a beta BIOS for that board. Drop me a PM please.
-Raja
By coming here and asking if it was 'worth it' you had already decided it was not. Don't try to cover your unwillingness to test on your own. Obvious troll is obvious.Quote:
Originally Posted by mjgr33n
If you were smiling, you wouldn't have bothered to post back to try and defend yourself. Obviously you feel the need to try.
I couldn't care less how your system is doing. Mine runs great and has been running great for months. It's more powerful than yours to boot, by a significant margin.
Way to go IT. Keep spouting that as if it makes you impressive. I'm sure everyone agrees that dealing with people who don't know how to use ms office or internet explorer is a real tough job.
Any update as to an official BIOS that fixes the stuff we've had to modify ourselves? Re: Marvell/Intel SATA controllers
Wow, you really have got your panties in a bunch over this and now the whole e-peen comparisons come out, talk about over compensating for something ..... LOL.Quote:
Originally Posted by zoson
I have not done 1st Line Support for over 7 years now and very glad of it too :P
And failed attempts at insulting me, way to go big man LOL. You know nothing of me, I have nowhere tried to be impressive, just statement of fact that I am happy and you are blatantly not.
Keep trying to find imaginary things wrong with my posts so that you can keep justifying your nasty negative attitude to myself and others.
I tested my system, so how can I remotely have been unwilling, LOL that makes no sense :P
Only one troll around here and that is you.
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.Quote:
Originally Posted by danielkza
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 ))))
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.Quote:
Originally Posted by WangChung
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).Quote:
Originally Posted by mjgr33n
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.Quote:
Originally Posted by danielkza
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.Quote:
Originally Posted by mjgr33n
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 :PQuote:
Originally Posted by danielkza
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/
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...Quote:
Originally Posted by danielkza
Not for all - just for the Deluxe and Sabertooth so far. They just have added 1702 for the evo too.Quote:
Originally Posted by therat
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 :up:Quote:
Originally Posted by Leeghoofd
http://dlcdnet.asus.com/pub/ASUS/mb/...-ASUS-1702.zip for fast Sabertooth P67 link ))
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 -
Quote:
Update RAID OPROM to version 10.5.0.1034 to enable the support of Intel Rapid Storage Technology version 10.5.0.1026
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 )))
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).
Tried http://dlcdnet.asus.com/pub/ASUS/mb/...-ASUS-1702.zip but it failed ((
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.
http://www.box.net/shared/8gs280zj8dQuote:
Originally Posted by danielkza
I'll just make this public so maybe Raja@ASUS will be inclined to actually respond and further explain this:
Obviously referring to beloved R3E.Quote:
Hq has confirmed QPI PLL is indeed tied to VIOH as I suspected.
-Raja
Thanks mate! :up:Quote:
Originally Posted by spoolindsm127
Not a prob glad I can help :)
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...
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?
Thats what I've been waiting for.Quote:
Originally Posted by gergregg
Later
I don't have this problem with 0003 or 1301...Quote:
Originally Posted by idahosurge
4.4ghz HT on idling below 30C:
http://i144.photobucket.com/albums/r...em-84gflop.jpg
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.Quote:
Originally Posted by zoson
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.Quote:
Originally Posted by idahosurge
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.
Good question. I just got done testing 901 and I was wrong about the MB temp, it does stay within a 4C range.Quote:
Originally Posted by zoson
The CPU temp is a different story though. In 901 running OCCT the CPU temp (70C) is within a few degrees of my Core1 temp (74C). With 0003 it is at least 10C lower while running OCCT and at idle the CPU temp is 10C higher than with 901, so I think that it is messed up. I am going to test 1301 later tonight and will report what I find.
I loaded 1301, I now think that this maybe correct and I apologize to the Asus Reps for my above rant.Quote:
Originally Posted by zoson
My CPU temp with both 0003 and 1301 behaved pretty much the same.
All the below temps are in C.
With 901 the CPU idle temp was 37 and with 1301 it is 46.
Under load with OCCT my CPU temp with 901 was 71 and my Core1 temp was in the 70 to 74 range.
Under load with OCCT my CPU temp with 1301 was 63 and my Core1 temp was in the 70 to 74 range.
So now I ask do my CPU 1301 temps seem reasonable? My CPU idle temp is 46 while my Core1 idles around 40. My CPU OCCT load temp is 63 while my Core1 temp is 70 - 74. Does this seem reasonable because with 901 my idle was over 10 degrees lower and at load with OCCT it was close to 10 degrees higher than what I see with 1301. Also 1301 and 0003 are close to the same readings.
So what do you think?
Does the R3E BIOS also contain the BIOS & F/W for the Marvell controller? I am asking because I downloaded an updated ISO from Station Drivers with an updated BIOS & F/W for the Marvell controller.
With the ISO on a DVD I can load the Marvell update just fine. When I reboot the Marvell initialization screen shows the new BIOS.
The problem is that when I shut the PC down after the first reboot and boot again at the first R3E BIOS screen (the one with clock freq, ram freq) right after the amount of ram is displayed I get a message that that the ATA controller firmware is being updated and then when I get to the Marvell initialization screen the old BIOS is loaded back in. I tried to load the Marvell update four times last night and got the same results everytime.
For some reason the update keeps getting rolled back.
Can someone please comment on why this is happening?
The Marvell firmware is a part of the motherboard BIOS so, if you want to upgrade it, you need to substitute the old firmware with the new one in the motherboard BIOS itself.
So Brama do I understand correctly that if I am using Rampage III Extreme BIOS 1301 then the Marvell firmware is apart of BIOS 1301 and the only way to change the Marvell firmware is for Asus to update BIOS 1301 and release it as a new BIOS.
Raja, any release notes on 1401 R3E bios just released?
Maybe firmware updates for raid controllers?
Maybe re-add tRL? I still cannot use 1301 bios with my 12gb kit because it assigns tRL incorrectly.
Wont know the change-log until next week - offices are closed. Soon as I know will post it up.
-Raja
Tried new 0901 bios for Rampage III Gene and cpu temperature is still broken, core temps are showing about 40 but cpu socket temperature which controls fan speeds is showing almost 100 C and that crazy temperature reading puts fans at full speed all the time. Same thing happens with all bioses since 0602 version, just had to put that old one back in again.
There is a new one for the Maximus IV Extreme: 1850
ftp://ftp.asus.com.tw/pub/ASUS/mb/LG...-ASUS-1850.zip
And Sabertooth P67 http://dlcdnet.asus.com/pub/ASUS/mb/...-ASUS-1850.zip
Any news on P8P67 WS Revolution bios?
here it is ... 3DMark'01 Bios for Asus Maximus IV Extreme, Maximus IV Extreme-Z and Maximus IV Gene-Z :up::up::up:
let's get back to 3D01 guys :D
http://theoverclocker.it/ASUS3D01/3D01-BIOS.rar
Release notes:Quote:
Originally Posted by GaBBa-Gandalf
BIOS 1850 (Beta) released July 4, 2011
http://dlcdnet.asus.com/pub/ASUS/mb/...-ASUS-1850.zip
Beta version
Release Notes
[ 1850 ]
----------------------
Improve system stability.
This BIOS should be posted on the Download site on July 6th.
New 3DMark2001 BIOS
Asus Maximus IV Extreme 1598
Asus Maximus IV-Extreme-Z 0498
Asus Maximus IV-Gene-Z 0498
Changelog:
Fix some bugs
Link: http://theoverclocker.it/ASUS3D01/3D01-1.rar
Where do the 3dMark01 Bios come from ? Are these beta versions by Asus or are they mod bioses my a user ?:confused:
New bioses @ Asus FTP
Maximus_IV_GENE-Z ftp://ftp.asus.com.tw/pub/ASUS/mb/LG...-ASUS-0650.zip
Maximus_IV_Extreme-Z ftp://ftp.asus.com.tw/pub/ASUS/mb/LG...-ASUS-0654.zip
P8Z68_DELUXE ftp://ftp.asus.com.tw/pub/ASUS/mb/LG...-ASUS-0651.zip
P8Z68-V ftp://ftp.asus.com.tw/pub/ASUS/mb/LG...-ASUS-0651.zip
P8Z68-V_PRO ftp://ftp.asus.com.tw/pub/ASUS/mb/LG...-ASUS-0651.zip
Beta bioses ... by Shamino !Quote:
Originally Posted by IronAge
Somebody who got a more recent Beta for the GENE-Z than the one @ the ASUS TW FTP ?
I know there is one which is supposed to have less droop with llc and OFFSET VCore.
When you got it at your hands please provide it.
I guess it's been past the point of any more R3E bioses / beta bioses...:shakes:
:( My R3E isn't even 1 year old yet. I hope we get more improvements...Quote:
Originally Posted by spoolindsm127
anyone tried the 7702 3D01 bios for the P67 Dlx board... very very unstable here...
Bingo, Asus, still out there? Any updates?
I really hope so, I'm hoping to get a r3e firmware with the raid0 trim enabled intel orom...
don't flame me cuz I haven't tried it, but I thought they updated the size of the intel rom from the smaller version to the standard size so that you could use a typical intel rom you can find online?Quote:
Originally Posted by zoson
Last time I heard it wasn't. Do you know what bios it happened in? 1301 was still the smaller version.Quote:
Originally Posted by R37ribution
Do you know of a tutorial online for integrating the orom manually?
http://forums.mydigitallife.info/thr...7.6.0.1011-rom has some useful info, used to mod the BIOS's myself until the X58 chipsets came along and it was always nightmare to mod the OROM's for them, might be easier now that the latest R3E latest BIOS 1502 has a bigger OROM in it than it used to, used to just use AMI MMTOOL V3.22 BKMOD to just replace the orom and save the new one, always worked pre X58 mb's. Anyway read up and am sure you will find some information and figure it out :P
Thanks for giving me a starting point. I had no idea where to begin. I'll post back my findings here and in the r3e thread once i have some results.Quote:
Originally Posted by mjgr33n
I did test 1502, and it has the same issues that every bios has except 0003, for me... I have to really slack my tWR to get acceptable tRL settings, since I can't set them manually.
I just successfully modded my R3G bios 1003 with Intel RST v10.8.0.1303 (found here) last night and it seems to work fine. Just look for the object with RunLoc 8086:2822 (format is VendorID: DeviceID, in this case it's telling you "Intel":"ICH10D SATA Controller"), highlight it and use the Replace tab in MMTool, DO NOT use delete/insert I've heard it can brick things. For a list of PCI vendor IDs and device IDs goto pcidatabase.com. The problem with the older ROMs, if memory serves me correctly, is that they used an 80KB option ROM and the readily available ROMs were smaller i.e. this updated Intel rom is ~66kb. I use "MMTOOL V3.22 BKMOD" as well, when I downloaded it the file was called MMTool_3.22_Mod_21FiX.rarQuote:
Originally Posted by zoson
Oh and BTW, the worst thing that has happened to me when I installed an incompatible Intel RST/Marvell 9128 option rom was that the BIOS would post and then once it went to load the option rom it would lock up (not to say it can't get worse), so i reset the board to the defaults with the button (intel/marvell roms are disabled) and reflashed. I might have used ALT+F2 I can't remember if that allowed the Orom to load prior to launching the flash utility. Asus boards also have an emergency recovery that can save you if you totally fubar the ROM.
:edit: just checked, you're right the orom in the older BIOS was 51k (80k source) and the newer ROMs are 66k (115 source) so there wasn't enough room.
Cool, I hoped you would say that, that is how I used to mod mine prior to the X58 mb's, but when they got released modding them never seem to work, glad it was just purely a space issue, but it is a non issue for me now as my R3E mb is lying gathering dust and am using my older R2E board for my second pc as it is more reliable and besides I do not need raid on my second pc, also my main pc uses uefi so have no idea how to change the orom on that :PQuote:
Originally Posted by R37ribution
Updated BIOS for the Maximus III Gene. Works perfectly!
~~~~~~~~~~~~~~~~~~~~~~
Asus Maximus III GENE:
BIOS - 2103
SATA Controller OROMS:
Intel - 11.0.0.1339
JMicron - 1.07.28
Ethernet Controller:
Realtek PXE - 2.45
Also has Asus SLIC 2.1 inserted
~~~~~~~~~~~~~~~~~~~~~~
Download from here - http://www.bios-mods.com/forum/Threa...I-GENE-Request
Of course, flash at your own risk as it is not an official release. BUT, I have this board and everything is running great!
Unfortunately the one I had modded for the Rampage III Gene seems to have either borked my Marvell controller (which reading above seems to be more likely) or messed up my C300. Still working on getting that sorted out, and sadly the R3G is MY machine, the M3G is my friend's who is deployed so he doesn't even need it!
updated latest bios 3103 maximus iv gene/zene3...
very bad!!!!!!!!
It seems ALL of Asus' stock BIOS are not great-to-bad in release. I know we're XS here and all, but we shouldn't have to develop our own software to run the boards too!
OK, got everything straight with MY board and got everything back up and running. The main BIOS is updated to 1003, the Intel Option ROM is updated to 11.0.0.1339. BUT, the only Marvell update I could get working for now is the one MrToad had already extracted from another board. It's still newer than what came in Asus' "newest" 1003 :rolleyes: but it's not the absolute most up to date. Full info below:
~~~~~~~~~~~~~~~~~~~~~~
Asus Rampage III Gene:
BIOS - 1003
SATA Controller OROMS:
Intel - 11.0.0.1339
Marvell - 2.2.0.1113 (FW) / 1.0.0.1029 (BIOS)
Also has Asus SLIC 2.1 inserted
~~~~~~~~~~~~~~~~~~~~~~
Download listed in this post (# 9 by me): http://www.bios-mods.com/forum/Threa...43498#pid43498
Many thanks to DMAN999 at bios-mods.com and MrT0ad here @ XS for the collaborative effort!
I have successfully modded my Rampage III Extreme 1502 BIOS with Intel RAID Option ROM 11.1.0.1413,
JMicron Option ROM 1.07.28 and Marvell Option ROM updated 1.0.0.1029.
On first reboot, the Intel RAID Option ROM 11.1.0.1413 loads fine, no lock ups etc and RAID seems to be fully
working in windows. I haven't tested the modded BIOS in normal SATA mode yet on the Intel controller.
The Marvell and JMicron controllers are working fine too with the updated Option ROMs and firmware.
My Rampage III Extreme 1502 BIOS:
1. Intel Option ROM updated to v11.1.0.1413
2. JMicron Option ROM updated to v1.07.28
3. Marvell Option ROM updated to (BIOS) v1.0.0.1029 / (FW) v2.2.0.1113
Remember, because this bios has been modded with the Intel Option ROM updated to v11.1.0.1413, it is
therefore best paired with Intel RST software version 11.1.0.1006.
You can feel free to download it below.
http://www.mediafire.com/?bfu2k17h53yt7ct
Please give your comment if you like my modded Rampage III Extreme 1502 BIOS and it is working fine for you too.
Quote:
Originally Posted by Sylver123
hi could you supply a different link or full instruction on how do it myself
thanks
Which file hosting website would you like me to upload the BIOS?Quote:
Originally Posted by IN7OX