Q Code AE (Legacy Event) on P9X79 Pro after 1104 BIOS upgrade attempt

nixd2012

nixd2012

nixd2012

Associate
Joined
29 Apr 2012
Posts
19
System (from OCUK ofc :))

P9X79 Pro Mobo
i7-3820 3.6 GHz Sandy Bridge-E LGA-2011
G.Skill RipJawz 8x4GB DDR3 PC3-17000C9 2133 MHz
Asus GeForce GTX 560 DirectCU 1024MB
Antec 300 case
OcUK H2Flo liquid single fan cooler
OCZ ZS Series 750W PSU
Crucial RealSSD M4 128GB SSD
Win 7 Pro

Everything was working just fine.

Tried to use USB BIOS flashback to go from the 0906 that it came installed with to the latest 1104 from asus.com. And then problems began.

Have tried working backwards through the BIOS versions back to 0906, and even double checking against the BIOS ROM image on the install DVD.

Stops with Q Code AE (legacy event). The Mem OK! LED is illuminated. Have tried the CMOS reset button - no change. Have tried the Mem OK! button. Goes through cycles of reboots and quicker flashing illumination of the Mem OK! LED. But gets back to the LED being constantly on.

Earlier, it was illuminating the CPU LED constantly. But that changed to the Mem OK! LED. I can't remember precisely what changed this I'm afraid.

What does "legacy event" mean (Q Code AE)?

And what might cause the Mem OK! LED to turn on? Various searches give posts about people seeing this LED when initially building their system. But I could find nothing about it starting to occur on a working system after an attempted BIOS upgrade.

As you can guess, any help or suggestions would be very much appreciated.
 
If everything was working fine and you did not need the features offered by a new bios why would you update??? I am still on 1005 as my main bios on R4E as new bios offer me nothing I need.

If this problem was me I would disconnect all hardware apart from VGA, One stick of RAM in socket furthest from CPU and CPU. Reset CMOS including removing the battery and try boot the board again.

Post back your results.
 
Hmm, after a few cycles around upgrading the different BIOS versions (0906, 1010 and 1104), finally the 1104 "took" and the system booted into BIOS recovery mode. No idea why it took so much effort. But seems back and working. Does seem the level of detailed advice against the specific Q Codes is pretty lacking around the internet unfortunately.

Somewhat ironic to see a new thread above mine today with someone asking whether they should upgrade their BIOS if everything is working fine.I guess I should add my weight to the general view expressed of, if it's working, don't change it!
 
Basically if your system is stable and the fixes offered by a new bios are not applicable to you why upgrade?? I see no reason at all. People think the latset is teh best but this certainly does not apply to all systems. I am still on 1005 as my main Bios for R4E. Ok it has two bios chips and I mess with the other one but thats about it.
 
did you rename the file correctly?
the file name for your mobo(when flashing from usb) is on the asus site
 
@8 Pack: maybe naive - the auto OC didn't get much and I hoped for maybe more with later. But maybe that is separate and I should do more reading on how to OC.

@niko: yes - the filenames were correct. If the upgrader is not happy the button light goes solid on and stays there - it did all the described flashing and then going off. And I reformatted the USB stick in case. So the only file was the upgrade file. So continues to be a bit of a mystery - but at least I seem to have a working system again.
 
You must log in or register to reply here.
Back
Top Bottom