Rampage V Extreme. Instructions for updating the BIOS file CPU microcode.

[CMDRZOD]

After reading about the latest zombie load attack on Intel CPU's I decided to see if there is a new microcode. Sure enough there is. Thanks again for having these instructions, once again they worked flawlessly. If you guys really want I can just post a link to the R5E.CAP I produced, which has the microcode 36h.

Here's links to the microcode and R5E.CAP if you don't feel like patching yourself. Note: My CPU is 6950X. If you do not have this CPU then this BIOS will not help you. You will have to build it yourself using the instructions on the first page and the new mCode from the link below.

Microcode:
https://github.com/intel/Intel-Linux...0190514.tar.gz

R5E.CAP I produced from building this myself for 6950X:
https://drive.google.com/open?id=1iW...HXFdz46I2Pvw-_

Just booted it up and using it now. Seems no different from before, but I'm eagerly awaiting benchmarks and more news of what kind of performance may be lost due to mitigating this new vulnerability.

[Axle Grease]

After reading about the latest zombie load attack on Intel CPU's I decided to see if there is a new microcode. Sure enough there is. Thanks again for having these instructions, once again they worked flawlessly. If you guys really want I can just post a link to the R5E.CAP I produced, which has the microcode 36h.

Here's links to the microcode and R5E.CAP if you don't feel like patching yourself. Note: My CPU is 6950X. If you do not have this CPU then this BIOS will not help you. You will have to build it yourself using the instructions on the first page and the new mCode from the link below.

Microcode:
https://github.com/intel/Intel-Linux...0190514.tar.gz

R5E.CAP I produced from building this myself for 6950X:
https://drive.google.com/open?id=1iW...HXFdz46I2Pvw-_

Just booted it up and using it now. Seems no different from before, but I'm eagerly awaiting benchmarks and more news of what kind of performance may be lost due to mitigating this new vulnerability.

Man, I read about the exploit only a few hours ago. Thank you very much for bringing this to our attention. I'll try the patch for the i7-5960X tomorrow.

Update: I tried flashing both modded and non-modded BIOSes using the USB BIOS Flashback method. For some reason that method no longer works.

[CMDRZOD]

Man, I read about the exploit only a few hours ago. Thank you very much for bringing this to our attention. I'll try the patch for the i7-5960X tomorrow.

Update: I tried flashing both modded and non-modded BIOSes using the USB BIOS Flashback method. For some reason that method no longer works.

I had a 2GB stick. I formatted it to FAT16 and put the R5E.cap file there. USB flashback port is one closest to motherboard. At first I was pressing the Bios reset button, till I realized I was supposed to be holding the bluetooth ROG connect button. Worked fine then.

Pretty sure an NTFS drive will not work.

[Axle Grease]

I had a 2GB stick. I formatted it to FAT16 and put the R5E.cap file there. USB flashback port is one closest to motherboard. At first I was pressing the Bios reset button, till I realized I was supposed to be holding the bluetooth ROG connect button. Worked fine then.

Pretty sure an NTFS drive will not work.

I've been through the process dozens of times over the years, but now flashback just ceases to work on my R5E. The 16GB USB stick is formatted FAT32 and has an an image named R5E.CAP on it. Pressing the ROG Connect button 3secs or longer, until the LED indicator on the stick lights up, and the image would normally start loading. The LED indicator on the USB stick pulses quickly when it is being accessed. Now the USB stick LED flashes briefly. Nothing loads; not even a non modded BIOS downloaded from the ASUS website. All I have is the EZ Flash 2 utility in cmos setup which accepts only non modded BIOSes.

I tried using another USB stick but it solved nothing. I also flashed an earlier BIOS using EZ Flash 2, then attempted to flash the same BIOS using USB Flashback and it failed again. Oh, well. 3902 is the latest BIOS for the R5E so I guess I'm going to be stuck with that for the foreseeable future.

[Axle Grease]

So USB Flashback happily loads the BIOS image off my flatmate's USB stick...... but not mine. I compared the two sticks in Disk Manager. They're both formatted FAT32 "Healthy Primary partition", only his is also set active so he could boot off it. I don't get it.

Version 3902 modded with Intel's latest microcode patch is now up and running.

[Vlada011]

Looks like now and mine computer is fixed without my intention against Spectre and Meltdown.
I didn't do nothing except last Motherboard BIOS 1903 for RVE10, last Win_10_64bit_1809 is installed from iso file and Widows is Updated.
Probably only that it's necessary for Spectre-Meltdown.
I think even 1902 BIOS for RVE10 is with Updated Microcode, 1903 is improved system performance.

I like when ASUS update BIOS for more than 4 years old chipset.

[huppra]

Windows 10's May update complete breaks this bios for me. My system (X99 Asus Deluxe II) just get stuck in a boot loop until I downgrade to the previous one (1902). Prior to the May update I was running the custom bios with no issues.

[CMDRZOD]

Windows 10's May update complete breaks this bios for me. My system (X99 Asus Deluxe II) just get stuck in a boot loop until I downgrade to the previous one (1902). Prior to the May update I was running the custom bios with no issues.

No issues here with the 1903 update. Just did a manual install of Win 10 x64 1903 with my custom Rampage V Extreme BIOS modded from the latest for this mobo

[Dalnoboi]

bios 3902 ASUS Rampage V Extreme (CPU Microcodes updated)
https://drive.google.com/file/d/1ybK...ew?usp=sharing

[huppra]

No issues here with the 1903 update. Just did a manual install of Win 10 x64 1903 with my custom Rampage V Extreme BIOS modded from the latest for this mobo

Did it auto install the update that included mcupdate_GenuineIntel.dll in the windows\system32 folder for you? Because when I don't rename that file my multiplier goes from 42 to 38 in windows.