Zitat von lordkag im Beitrag #10

---

The file looks like this:



You can let UBU replace the EFI drivers, you just have to replace the ROMs in A032---. You must use UEFITool, as MMTool will break when replacing more than one ROM in that GUID. For the microcodes there is a workaround, but it takes some writing and I suppose you are not that interested.

---

(Blaenant copy and paste from @voodoo as it is so well worded & huge thanks to @sinders for the guide and holding my hand throughout!)
Note: Like all modded BIOS', must be flashed via USB Flashback. To do this, load file "R5E.cap" (do NOT rename) onto a usb drive, insert it into the LOWER USB port on the PS/2 Mouse/KB hub, and then press and hold the ROG Connect button (below BIOS reset button / green circle arrow) for a few seconds. Corresponding BIOS light at the bottom of the motherboard will then start to flash (at which point you can release the button), and will blink faster and faster as it progresses. BIOS flash is complete when light stops blinking. At this point you can turn the motherboard power on and enjoy (note that you might have to press the power reset button on the board just once after a BIOS flash).

This contains the option replaced in both modules allowing traditional Ctrl + I setup and the EZtuning (F11 in Bios) option, also the EFI Sata driver so you have 2 ways to setup raid. My personal favorite is EZtuning as this stops the Raid option rom page during POST and seems to POST a lot faster.

Modded 1701.CAP

150903090844 by Gareth Holland, on Flickr

You don't have to update the CPU microcode because like I said to you over on the ROG forums, ASUS updated this in the latest BIOS 1701 to MU063F022E which is the latest version as far as I am aware.

Zitat von Fernando im Beitrag #2

---

Question: Why did you start a new thread?
It would be much better for users with a similar problem, if your final report would be added to >this< thread after having changed the title to something like "[Solved] How to mod an ASUS Rampage V Extreme BIOS?".
If you should agree, but do not know how to manage it, I will do it for you.

---

Zitat von sinders im Beitrag #19

---

... ASUS updated this in the latest BIOS 1701 to MU063F022E which is the latest version as far as I am aware.

---

Zitat von lordkag im Beitrag #21

---

Zitat von sinders im Beitrag #19

---

... ASUS updated this in the latest BIOS 1701 to MU063F022E which is the latest version as far as I am aware.

---

Not true, they provided cpu000306F2_plat6F_ver0000002D_date#21-11-2014 and the last version is cpu000306F2_plat6F_ver00000032_date#09-06-2015 (with credits to Plutomaniac for finding it). But for being able to replace it without doing manual hex edit, you need to read this and bellow. You would still do some hex editing, but at least you don't have to know the format of a microcode.

---

MU063F022E is cpu000306F2_plat6F_ver0000002E_date#23-02-2015 in fact. Intel is sending the patch in human readable form. MU063F022E = MU + 06 + 3F + 02 + 2E or Microcode Update for Family 06, Model 3F, Stepping 02, Patch 2E. The bin file has the CPUID in a packed form as 0306F2, from where you take 1 + 4 and 2 + 5 and 3 + 6 to obtain the human form. Unless you are the OEM working with the hex string file or publishing the release note, use the packed form, as that one is always used in apps. The last version is cpu000306F2_plat6F_ver00000032_date#09-06-2015 and Asus is double wrong, you can see from my screen that they used 2D and not 2E as they said.

Edit: from MU to CPUID use 135 + 246 == MU 063F02 -> 06 + 3F + 02 -> 030 + 6F2 -> CPUID 0306F2. From CPUID to MU use 14 + 25 + 36 == CPUID 0306F2 -> 03 + 06 + F2 -> 06 + 3F + 02 -> MU 063F02.

Both HWiNFO and SiSoftware Sandra suggests BIOS 1701 has CPU Microcode MU063F022E. SiSoftware Sandra says I have CPU Microcode MU063F022E and HWiNFO says I am using CPU Microcode 2E.




I haven't modded the BIOS CPU Microcode in any way.

If you check my screen or open the file in MMTool, you will see the patch 2D. If you open the attached file from this post, you will see that patch 2E is provided by Microsoft in Windows -> system32 -> mcupdate_GenuineIntel.dll (or mcupdate_AuthenticAMD.dll for AMD). You can try to rename that dll to a temp file and reboot to check if the microcode is still 2E, but I'm not responsible for any damage to your OS. There is also a backup in Windows -> WinSxS -> amd64_microsoft-windows-m..update-genuineintel_xxxxxxxxxxxxxxxxxx, so renaming that as well might be needed.

I don't know if the Asus representatives tried to cut it short or if they are truly unaware of this matter, but their version is simply false, there is no patch 2E provided by Asus in 1701 release.

Hey, everyone! Got my Rampage V today and my habit of updating everything kicked in=) There were no problems to update RST with UEFITool (thank you guys for guides in this thread!), also there were no problems updating MEI firmware and ASMedia USB controller's too. And after that great start I got some troubles) While searching for new modules and OROMs for Intel NIC, I stumbled to a thread with UBU tool. I had no luck in injecting it's Intel PRO modules(devices won't be detected in EFI shell), also there is a weird EFI module for Realtek NIC in GUID 2EAA04AA-5EED-4C27-B9EE-26916EC25A8F (I think we don't have any realtek network controllers at all on Rampage V). So I have some questions: Are there any updated Intel PRO/1000 OROMs and modules, compatible with I218-V(15a1) device? Have anyone tried to make such mod? Is it safe to remove RealTekLan module completely? Aaand, one more thing,- while searching for updated microcodes I came up to a thread with 31 microcode, which is not mentioned here, so it would be great to have some kind of guide to try to update it too... Thanks!

It would be nice if you wouldn't mind sharing the BIOS when you have it all working :)

Looking for a version 1401 Bios with modded oroms for raid controller etc. for some reason 1401 is only version that runs stable with my memory set to xmp 3200 any other vesion bios equals hang.

only 15 and 17 versions so you will need to use the guide and mod your own.