[Request] Fully updated BIOS for ASUS Rampage IV Black Edition

Looking for an updated BIOS for this board including nVME, ReBAR, Above 4G Decoding, updated microcode, and updated BIOS modules. Attempted this myself in the past and ran into compression issues.

Unmodified BIOS attached.

RAMPAGE-IV-BLACK-EDITION-ASUS-0801.zip (4.8 MB)

@pantsaregood Please flash this using bios flashback: R4BE_Complete.rar (4.4 MB)

To enable rebar, you can refer to this post. Also for the updated modules, they’re updated with the version i did with the Sabertooth X79 in the post, and added nvme boot capability. In addition to the modded bios, i replaced the old ROG logo with Modern ROG one, also increased the MMIOH Size to 128GiB from stock 64GiB.

If bios is succesfully flashed, you could boot to bios, and when you disable CSM and enable Above 4G Decoding, the bios have no quirks whatsoever (XMP and OC you did working as-is stock bios), and ReBar working (just set rebarstate at 32 and reboot), could you please take a scrrenshot similiar to this:

BIOS works, and can get a screen shot. Is it possible you can also unlock the “Trusted Computing” menu under Advanced? This motherboard supports TPM 1.2, but it looks like the menu isn’t exposed.

1 Like

I think trusted computing will unhid by itself once the tpm module is inserted and detected by the bios. But if you did connect it and it didn’t appear, i’ll try to unhid it.

I did connect a known-working TPM 1.2 module without it showing up. I don’t recall the M5F or the C5FZ ever hiding the option, so I thought it was strange.

Also, wanted to say thank you. I really appreciate the time.

All right, i’ll check it later if you’re still interested in it. But youu should cross check if the tpm module is actually compatible/doable on other similiar generation board, just to be sure :slight_smile:

Hello! Thank you very much for this modified bios! I wanted to ask a few questions, if you ok with this. I saw that you did many modified bioses, so I assume that you are knowledgeable and know what you are doing, so I’m sorry if this message feels like I’m doubting your skills, I’m just very careful with hardware and firmware and always want to double-check things. I got my hand on this mb with 4960x and 32gb of 2933 trident (literally garage find) and intended to use it for foreseeable future as daily-driver so this bios looks must-have for games and not needing to have flash drive for booting from nvme in pci, so thanks again!

So I wanted to check your image with Codex to be sure that it comes out okay, but it highlighted 3 things and so I thought it would be okay to ask the author.

  1. It referred to this part in DSDT patching: “Please make sure you use MMTool 4.50.0.23 to replace the AmiBoardInfo module when doing this on X79, there have been reports of newer MMTool versions and UEFITool causing high voltages when using overclocking” and it said that there is no way to determine what version you used so I just wanted to check if you are aware of this and used right version. I’m now very afraid of voltage and everything surrounding it because my brothers 12900k died because of stupid board overdrive “lvlup” setting.

  2. NvStrapsReBar 0.4-rc1 having this documented bug where the driver configuration can not be read from the EFI variable. If I understand correctly this driver won’t work on my system because my 3080 Ti will utilize ReBarUEFI. I just wanted to ask if this means I can’t encounter this bug and how this bug will make itself know if it happens.

  3. The most strange one - it thinks that this change can give bad behavior on this motherboard and could be genuine local code mistake, so this is mostly why I even wrote this message

{
Firmware module - PciBus
Module GUID - 3C1DE39F-D207-408A-AACC-731CFB7F1DD7
Firmware-file start in the complete modified CAP, including its capsule wrapper - 0x26FEB0
Comparison instruction within the decompressed executable - 0x1E5D
Two executable bytes that differ from official 0801 - 0x1E5F and 0x1E60

Official 0801
cmp rax, 0xFF
jbe allowed

Modified image
cmp rax, 0x1000
jbe allowed
}

If you read this, thank you so much! Sorry again if this is a big yap, I just prefer to be very careful with hardware. If you could answer about this things, that would be awesome! Thanks again.

Edit
P.S. If all this turns out okay, I would be glad to contribute to this thread for future visitors via flashing, testing and providing screenshot from hwinfo and cpugpuz as you requested