ASUS Official X79 Motherboards Support Thread

Latest from HQ on the IRSTe situation:

1) Avoid using IRST Driver 11.6. There is a bug that prevents the building of a RAID array, which is why we have not updated to it. For that reason the current build will stay defacto.

2) A future BIOS (no ETA) will include a UEFI IRST driver instead of a separate OROM. That means RAID options will be accessed from within UEFI instead of needing to press CTRL-I to access the OROM. The first driver to be phased in will be the current one on the ASUS site, as 11.6 has a serious bug.

That's all the info I have at present.

-Raja

Thanks for the update Raja. Just finished my new build and it went without a hitch. Used all the drivers from Asus website. Installed OS onto Vertex4 and then installed the two RAID0 HD from my old build. The system recongized the RAID array without doing anything. I was surprised that I could have used it as is, but I deleted the array and reinstalled it for a fresh array on this system.

Having a problem with my R4E. :(

I have been out of the loop for awhile and I was having some issues and figured it was time for a bios upgrade. I was on 1001 or something before not 100% sure.

I grabed an archive from the R4E thread and flashed it. It had both the R4E.ROM and the R4E.cap in it. It was a 2105 bios with a modded intel fw. I used the USB flashback to flash it, comp would not boot. It will just spin the fans for a second then shut off and repeat about every 10s. I tried flashing the following though usb flashback with no luck in order listed:

2105 stock (.cap)
cap converter (.rom)
1404 stock (.rom)

After every one of these I tried booting, tried reseting the cmos but, I still get the same issue where it powers on for a second and then shuts right back off.

Another thing I noticed, is the led would flash for about 2 minutes and then it would go solid, instead of shut off like the USB flashback guide said. I found this a bit strange.

Anyone have any ideas? I thought these things had dual flash chips to prevent this, I do see them in the board. Do I just need to swap the flash chips in their sockets? I have the capability to program the flash chips if necessary...

Just use the "bios switch"button to change from bios 1 to bios 2,bottom right hand corner of mobo.The bios chip led is supposed to be solid.Can i ask why you used the bios "flashback"procedure to flash,this is used to flash your bios to older bios's,not newer ones. ???

@ASUS

Where is AISUITE for Windows 8? You've only had a year get it 98% "there" and its been RTM now for months with the WHQL complete to back up logo testing. So???????? Where is it?????????

Quote:

---

Originally Posted by moorhen2

Just use the "bios switch"button to change from bios 1 to bios 2,bottom right hand corner of mobo.The bios chip led is supposed to be solid.Can i ask why you used the bios "flashback"procedure to flash,this is used to flash your bios to older bios's,not newer ones. ???

---

Ah that did the trick, thanks! You have to use the flashback feature in order to flash a modified bios after some 2XXX version.

Hi

I am trying to determine if I have a faulty X79 Sabertooth motherboard. I was hoping if someone out there with the same board could confirm if they are experiencing the same symptom?

Basically if I make any BCLK adjustment above 100.5 when I power off the power supply completely (draining all power to board), when I next turn on the board starts briefly/stops/starts again (almost as though it was going to produce an overclock failure) but then proceed to run normally at my designated overclock. This only occurs when I increase the BCLK above 100.5 AND power off supply completely, a standard shut down does not produce this.

My highest stable overclock of 4.6ghz using BCLK 121.75/CPU STRAP 125/Multiplier:38 runs fine but continues to have this symptom. However if I bump the BCLK up to 125/CPU STRAP 125/Multiplier: 37 (to produce a similar clock speed of 4.6ghz), I have the same problem but this time the board DOES produce a overclock failure when booting after a power supply turn off. No amount of bios adjustments or tweaks seem to get this one stable.

As I understand it the bclk is a little sensitive with this x79 chipset but I was curious if perhaps I have a bad board. I dont remember having any of these issues with my old X58.

Any input from other sabertooth users? I have posted on another forum but did not get any response from sabertooth owners. One guy with a MSI board reported something similar.

Motherboard: ASUS X79 Sabertooth Processor: i7 3820 @ 4.6ghz Memory: 16gb (4x4GB Samsung MV-3V4G3D/US

Depending on your OC adjustments a double boot after power loss is normal. The system might completing some sort of training, then require a power down in order to apply settings.

As Cx-ray said, this is normal.

I was running BIOS 1203.ROM and upgraded to the 2104 using the CAP converter. All seemed to go well, the machine rebooted a number of times and then into the BIOS. It showed 2104 so I thought all was good. I then saved and exited and the machined re-booted and I got a message "Bad Disk". I tried to reboot into BIOS but it kept coming back to the error message.

Luckily I am paranoid, so I had already purchased a 2104 BIOS chip from the ASUS eStore. So I pulled the chip and replaced it with my ASUS pre-flashed chip. Same thing happened again! Got the bad disk error and could not get back to BIOS screen.

So, I pressed the Clear CMOS button and the machine booted normally. I was able to enter the BIOS screen and make some changes and the machine rebooted normally into Windows 7.

One problem: the Q-Code display is permanently stuck on "04" - but this cannot be a real Q-Code because the machine is fully functional and runs normally. I contacted ASUS tech support and they said not to worry about --LOL!

It appears the Q-Code display is locked up and no longer functions. Any ideas on how to fix it? I am reluctant to do anything because it is not causing any problems. Has anyone seen this behavior?

Thanks...

Rampage 4 Gene - dead after bios flashback

Guys, I just received my long awaited 3960X so I assembled a rig based around a Gene I bought used. At first attempt to boot the Debug display showed 62 so I did some research, asked some questions and decided to update the bios. I downloaded the latest bios and cap converter but the flash won't start, if I change the bios suffix to .rom then it appeared to go through the flash procedure but it will not post. The fans spin up for about half a second then it shuts down and tries again in an endless loop. I tried to flash it again, tried different bios versions and another USB stick but the symptoms do not change. I also tried different ram and video card but they make no difference, even having no ram in the mobo gives the same symptom, so what is wrong and how do I fix it?

Any help would be great.

:(

Has anyone tested the new Dominator Patinum sticks on their X79?

2666C10 does 2400C9-11-11 at 1.6Vdimm, my crap 3960X IMC can't handle +2500MHz clocks

After sitting idle for three months my R4E will not post, the fans spin up for a second it then shuts down and tries again. Also BIOS chip number one is extremely hot even when it is not activated.

I have tried different RAM and graphic card configurations and flashed both BIOS chips using USB flashback.

Quote:

---

the fans spin up for a second it then shuts down and tries again

---

That is my symptom also, I hope we find a solution.

:(

Any help anyone? Is it worthwhile trying a new bios chip? Only $16.39 off ebay ....

Aussie, test the power supply if you haven't yet. I had this issue due to a PSU that went mental.

I think its fine but I will try another one anyway.

:)

I tried another PSU but it didn't help with my problem.

@Raja, does Asus do cross shipment RMA's on the R4E?

Quote:

---

Originally Posted by MetalRacer

I tried another PSU but it didn't help with my problem.

@Raja, does Asus do cross shipment RMA's on the R4E?

---

In North America yes (if in stock).

-Raja

Quote:

---

Originally Posted by aussie-revhead

Rampage 4 Gene - dead after bios flashback

Guys, I just received my long awaited 3960X so I assembled a rig based around a Gene I bought used. At first attempt to boot the Debug display showed 62 so I did some research, asked some questions and decided to update the bios. I downloaded the latest bios and cap converter but the flash won't start, if I change the bios suffix to .rom then it appeared to go through the flash procedure but it will not post. The fans spin up for about half a second then it shuts down and tries again in an endless loop. I tried to flash it again, tried different bios versions and another USB stick but the symptoms do not change. I also tried different ram and video card but they make no difference, even having no ram in the mobo gives the same symptom, so what is wrong and how do I fix it?

Any help would be great.

:(

---

@Raja - any advice for me please?

:)

Is the flash drive FAT formatted? If not, it needs to be (FAT, FAT32 etc).

If not that try older BIOS renamed accordingly.

Hard to say what else the issue could be - with it being a "used" board and all...

Yes Fat formatted, I tried three bios versions already and used shouldn't matter as it got worse after I attempted bios flashback. I did find afterwards that for some reason the bios chip was not fully seated, does that mean someone has touched it already? Even then shouldn't it still accept a flashback?

:(

Quote:

---

Originally Posted by aussie-revhead

Yes Fat formatted, I tried three bios versions already and used shouldn't matter as it got worse after I attempted bios flashback. I did find afterwards that for some reason the bios chip was not fully seated, does that mean someone has touched it already? Even then shouldn't it still accept a flashback?

:(

---

If it's "used" anything is possible.

I'm having trouble with my RIVE after updating the bios from 1404 to 3101, on cold boot and reboot it stops for 30 sec on postcode 65 and for 60+ sec on postcode 67, both of these postcodes are memory related if I'm not mistaken.
I've tried three different CPU's and two sets of memory also tried three different GPU's all with the same result, stock or OC'ed makes no difference.

Any ideas?

http://img87.imageshack.us/img87/863/linxt.jpg