ASUS RAMPAGE III EXTREME BIOS - V1601 - Updated OROM MOD

[Miklsoft]

Start system 0 port (sata3) - SSD 240GB (win 10, Install w10 after Bios update )
1 port (sata3) - HDD 500GB
2&3 ports (sata2) - 1500GB HDD x 2; RAID 0 (No used TRIM)
5 port (sata2) - DVDrom (ODD) (When start BIOS - "Port 5 - error" and "Press F1 to resume"- start win10 if pressed )
Jmicron no tested, but see on device info win 10
All devices ON in BIOS, fireware - off.

[pir8man]

yea, never mind the TRIM question. your raid is HDD, not SSD.

I can run through some tests here, but I may not be able to reproduce the issue.
What diagnostic steps have you attempted?

Try turning off the Jmicron controller as well as the Marvell controller. to see if that has an effect.

[Miklsoft]

yea, never mind the TRIM question. your raid is HDD, not SSD.

I can run through some tests here, but I may not be able to reproduce the issue.
What diagnostic steps have you attempted?

Try turning off the Jmicron controller as well as the Marvell controller. to see if that has an effect.

The error is not displayed every time, but when I boot with the disk. Or after without a disk. It helps only turn off the power. The 10 always works, regardless of the BIOS boot error.

Maybe this is due to the ODD itself?

[pir8man]

yea, never mind the TRIM question. your raid is HDD, not SSD.

I can run through some tests here, but I may not be able to reproduce the issue.
What diagnostic steps have you attempted?

Try turning off the Jmicron controller as well as the Marvell controller. to see if that has an effect.

The error is not displayed every time, but when I boot with the disk. Or after without a disk. It helps only turn off the power. The 10 always works, regardless of the BIOS boot error.

Maybe this is due to the ODD itself?

do you have (or can borrow) another ODD to test with ?

Also try another sata cable.   that could always be the case, or even a poor/loose connection.

I just successfully booted a Linux live cd and Win10 installer dvd.   So I can't reproduce your problem here either.

EDIT: Does your ODD operate correctly on standard 1502/1601 BIOS?

[Cyberdyne]

Hi! Does your modified BIOS support for NVMe? If not, how do I support M. 2 drives?

[pir8man]

Hi! Does your modified BIOS support for NVMe?  If not, how do I support M. 2 drives?

This is why we use search AND read through a thread before we post.  This is clearly detailed in post 51.

[Stahab]

I was happily and flawlessly running S19i and S19t (on BIOS1 and BIOS2 respectively, testing both) on my R3E (XEON X5690 stock / 12GB / SSD on Intel AHCI / Win10 Pro x64 ver.1709) until 3 days ago, when Win10 ver.1803 update showed up on my windows updates.

The update kept freezing at first boot after every installation attempted.

I tried to clean install Win10 v.1803 x64 from bootable usb but the machine would freeze while in the boot process. Strangely enough, the 32bit Win10 installer booted normally.

Switching from S19i to S19t didn't change anything. Also both Marvell and JMicron controllers were disabled, so there was no issue with BIOS memory. 

After some internet searching, I found out that Intel VT-d has caused similar problems in other platforms, so I disabled VT-d from BIOS (Advanced -> Chipset -> Intel VT-d configuration) and Bingo! Everything worked fine and Win10 1803 installation completed with no troubles.

Disabling VT-d also cured another problem that I've had for about a year and could not troubleshoot: My machine would not recover from S3 sleep (BSOD) while it would normally recover from S1 sleep and hibernation. Now it works fine.

Not sure if this VT-d issue is related to our old chipset/CPU, our BIOS, or the spectre/meltdown related updates in ver.1803.

I just thought I'd share this here for people that are facing the same problem with S19 and 64bit Win10 ver.1803.

[RPro]

I was happily and flawlessly running S19i and S19t (on BIOS1 and BIOS2 respectively, testing both) on my R3E (XEON X5690 stock / 12GB / SSD on Intel AHCI / Win10 Pro x64 ver.1709) until 3 days ago, when Win10 ver.1803 update showed up on my windows updates.

The update kept freezing at first boot after every installation attempted.

I tried to clean install Win10 v.1803 x64 from bootable usb but the machine would freeze while in the boot process. Strangely enough, the 32bit Win10 installer booted normally.

Switching from S19i to S19t didn't change anything. Also both Marvell and JMicron controllers were disabled, so there was no issue with BIOS memory. 

After some internet searching, I found out that Intel VT-d has caused similar problems in other platforms, so I disabled VT-d from BIOS (Advanced -> Chipset -> Intel VT-d configuration) and Bingo! Everything worked fine and Win10 1803 installation completed with no troubles.

Disabling VT-d also cured another problem that I've had for about a year and could not troubleshoot: My machine would not recover from S3 sleep (BSOD) while it would normally recover from S1 sleep and hibernation. Now it works fine.

Not sure if this VT-d issue is related to our old chipset/CPU, our BIOS, or the spectre/meltdown related updates in ver.1803.

I just thought I'd share this here for people that are facing the same problem with S19 and 64bit Win10 ver.1803.

Stahab,  Thank you very much for your post.  I’m still running the stock 1502 bios and was going to give S19 a try to see if that would resolve having VT-d enabled with Windows 10 ver. 1803 resulting in a stuck at reboot on the windows logo.  Per your testing it does not fix it.  - only resolution being to disable VT-d and take a big hit with running virtual machines.

What’s interesting is on the following Microsoft thread Link Here xTr1 posted that he has a X58 based Asus Sabertooth that he updated the bios to Version 1402 12/08/29 (sabertooth X58 BIOS 1402 which was listed to ‘improve VT-d compatibility issue’) Bios Link Here  and he is now able to have VT-d enabled with windows 10 1803 – all on a x58 based board.  I’m wondering if there is any way we could figure out the change in that bios and apply it to the Rampage III Extreme bios.  

Also to note is that Intel released microcode updates in April 2018 that addresses meltdown/Spectre for our Intel X5690 CPUs – MCU rev 0x1E - Intel Microcode update guidance link   I’m curious if the 0x1E microcode was updated in our bios if the VT-d issue might be resolved as well.

Thanks again!

My current setup – Rampage III Extreme – Intel X5690, 12GB RAM – using only the ntel SATA – Intel Rapid Storage software 13.2.8.1002 with driver 13.44.0.1026 (2 x 8TB RAID1, 2 x 3TB RAID1, 1TB SSD), Win10 1709 until I can upgrade to 1803 with VT-d.  Note the reason why I have held off using the mod bios’s is the SLIC tables included with them, concern I would lose my Windows or Office 2016 activation.

[rattyto]

Hello, i have install the S19t_Final BIOS Version and if i enable the Boot on LAN Option in BIOS then i receive the error message : "PXE-E01 PCI Vendor and Device IDs do not match!" what is wrong in my doing? I have try other versions and the error message is the same.

Another Question: Is it normal with this Version not seeing the JMicron boot text?

[Stahab]

@ RPro,

Thank you very much for the enlightening on the VT-d issue!

Sorry for my late reply, I've recently relocated and still no phone/internet connection :-(

I'm not sure exactly when my issue with S3 resume developed, but I have the feeling it started back when I first used the ZioMod BIOS. At that time I was playing a lot with the system, so I blamed a driver and as a workaround I disabled sleep and used hibernate instead. It was not until I clean-reinstalled windows when I realized that the issue was deeper than I thought. Other people with X58 platforms appeared to experience the same problem but at that time no one (including me) could spot the cause (VT-d).

I am now suspecting that VT-d was causing booting issues long ago before Win10 1803 but not as critical. I also suspect that there may be a glitch with one of the updated modules of our modded BIOS (probably inhered from ZioMod).

My search for a new 06C2 microcode led me here. It is MCU 0x1E.
Maybe pir8man would want to create a new BIOS for testing.