I think 13 is either left by mistake or for legacy reasons, has anyone found 13 in use over 14?
In the R5E manual it says that the X99 chipset provides 10 x 6Gb/s SATA ports, but that âdue to chipset behaviorâ ports 7, 8, 9, and 10 âdo not support IRST including RAID configuration.â We see this in the BIOS as two SATA controllers, the first of which lists 6 ports and has RAID as a selectable setting and the second of which has 4 ports and does not.
UBU identifies two OROMs âIRST RAID for SATAâ - 13.1.0.2126 and 14.8.0.2377. Extracting the OROM GUIDs and comparing them with those versions shows that GUID E095AFFE-D4CD-4289-9B48-28F64E3D781D is IRST version 13.1.0.2126 and GUID 20FEEBDE-E739-420E-AE31-77E2876508C0 is IRST version 14.8.0.2377.
MMTool shows GUID E095AFFE-D4CD-4289-9B48-28F64E3D781D with DevicePath HB0-0:0-0:0-11:4 and GUID 20FEEBDE-E739-420E-AE31-77E2876508C0 with DevicePath HB0-0:0-0:0-1f:2. Both have VendorID 8086 (Intel) and DeviceID 2822 (RAID Controller).
In Windows device manager, with view set to âDevices by connectionâ I see âACPI x64-based PC\Microsoft ACPI-Compliant System\PCI Express Root Complex\Intel Chipset SATA RAID Controllerâ which contains the disk drives I have plugged in to SATA ports 1 through 4. Examining the property details on this RAID controller show an attribute named âLocation pathsâ which contains âPCI(1F02)â in it. This matches the â1f:2â in MMToolâs DevicePath for GUID 20FEEBDE-E739-420E-AE31-77E2876508C0. I also see âACPI x64-based PC\Microsoft ACPI-Compliant System\PCI Express Root Complex\Standard SATA AHCI Controllerâ which contains the disk drive I have plugged into SATA port 7. The âLocation pathsâ for this device contains âPCI(1104)â which matches the â11:4â in MMToolâs DevicePath for GUID E095AFFE-D4CD-4289-9B48-28F64E3D781D.
So my conclusion is that in legacy mode BIOS 3101 is using IRST 14.8.0.2377 for SATA ports 1 through 6 and IRST 13.1.0.2126 for SATA ports 7 through 10.
I flashed the modded 3101 BIOS and it took many reboots until I could get into the BIOS. Unfortunatelly, it was completely unstable, I could not even enable the XMP profile / overclock 10% and successfully boot - in fact, almost any change in the BIOS would boot to a blank screen and then switch off until CMOS was cleared.
I tried rolling back to the last rock solid working for me BIOS, the 2001 (modded and original) and I am getting an infinite boot loop and a lit up blank screen, I cannot get into the BIOS nor see the "BIOS is updatingâŚ" message. The same is happening with the 2101 (modded and original), while the original and modded 3101 boots into BIOS (after many tries) in an unstable manner. BIOS 2 from the BIOS switch is also not working for some reason, although I never used it before.
Is it bricked?
Try extracting battery and clearing cmos and if you have the choice to enter bios, flash with ezflash, then use flashback to go to one original.
Well, after many tests, I can only boot to Windows with 3101 BIOS and only after I hard reset BIOS or remove the battery and try booting multiple times (at some point it will work). Also, restarting Windows will freeze on boot and I need to either hard reset BIOS or cut power for about 20 seconds and then I can boot to Windows. Again, this may take a couple of tries.
No other BIOS works.
I do not know what is wrong but even after multiple flashes, nothing can make it work properly.
Any chance we can fix it?
Via an eeprom programmer. It is the only useful tool able to recovery bios chips
or corrupted flashes.
hello guys, I ordered a Xeon E5 2698 V4 ES (stepping QHUZ) from Ebay for rendering of a 3D animation Im working and I need to know if this is compatible with my motherboard Rampage V or can make it compatible with a custom bios. If there is no solution I will need to buy as soon as possible another motherboard like the Asrock X99E-ITX/AC that states its compatible with V4 xeons.
I tried with Xeon E5-2683 v4 ES. Bios 3101 boots to windows only if I clear CMOS - discard changes. R5E_MOD2_3101 canât even get to bios.
Thatâs strange. AFAIK they all have the same microcodes(archs, IDs), only versions updated.
Hey, @Sylar76 maybe itâs a good idea to fix FIT? Tried it on my system with fixed and stock(wrong) records and everything booted fine, but it looks like someone has some problems with XeonsâŚ
So I guess right now the Rampage V is not usable with v4 Xeons, or I have to clear cmos every time I boot.
Maybe bios needs to have the CPU Microcodes updated as well. Iâll check this later today.
Iâve checked bios again but I do not know why Xeon CPU are causing some issues.
New CPU microcode 38 for Haswell-E
Sylar76, you could add to your MOD (I use the MOD 2101 LOGO, all updated except "Uncore module) 
Thanks so much
I tested R5E_MOD2_3101 again with Xeon E5-2683 v4 ES and it stops on q code 91 "testing nvram". After a while it just shuts down. Non modded 3101 goes to bios fine first but if I save any settings, it halts on q code 19 "cpu init" (discard changes gets me to windows).
Not sure I am posting in the right spot.
the 2001 Bios is the only bios I can run my memory stable at 2800 settings. The 2001 Bios is the only that will set the Cpu Strap to 100 Automatically?
I guess I was wondering if anyone could tell me why this bios runs stable and is the only one to set the strap correctly. I apologize if this in wrong spot.
Im running a 5960x and Gskill 2800 64 gig
Thanks
EDIT by pluto: merged with proper thread.
@tuckerr200 :
Welcome at Win-RAID Forum!
If you donât want to offer any already modded BIOS, you have posted into a wrong Sub-Subforum.
You should better ask ASUS than us.
Regards
Dieter (alias Fernando)
SoâŚwe are not allowed to discus the various differences between the R5E modded BIOS versions?
That post was at a separate thread of itâs own. Not that itâs merged, itâs ok.
I have the same thing using BIOS 401 or 602 with a brand new ASUS X99A-II that was released about a week ago. Code 19 if I reboot or donât exit BIOS.
To get around this I have been running without a CMOS battery so I donât have to pop it out each time or mess with the JP1 jumper.