Quote Originally Posted by Terlcartman View Post
Yep I loaded F6e with Q-Flash and went straight to the BIOS after reboot and loaded optimized defaults, saved, rebooted and started overclocking from there. Thanks for the heads up about the variability of BIOS settings as I did not know that, but I have never used profiles as I do it the hard way and just go change every setting manually.

So it sounds like I could have used @ BIOS to fix this issue? I thought about that but due to your warnings on tweaktown I have never used that application. Also is there a way to force the MB to use the backup Bios that is stored in the second Bios chip or will it only do that if the primary is corrupted?

I have never updated my secondary BIOS with Alt +F12 so I was trying to find a way to force the MB to read from that one as it should be F3 which came with the MB.

Interesting that you say it was a problem with pre 3/11 beta's as I have been running beta's off of tweaktown since a few days after I got the UD5 and I have been flashing the BIOS regularly forward and backwards with no issues. I noticed the drops in temps with the F5 Series and I played with the 21X200 Bclk seetings with F6a but have always come back to F5e for my best LinX stable setting at 4.095. I need to get on one night and get some help from the experts to break 4.2 one of these nights.
ya, do keep that in mind. All BIOS's will differ for sure, some more then others. Of course some may feel like all works just the same as another, but not often.

Yes, you could have used @BIOS, but I do not suggest Windows based flashing when there is many other methods available.

Ya, you can short out the Main BIOS chip, if you wanted to do so. >>>
http://www.xtremesystems.org/forums/...&postcount=520

But other then that or corruption you can't choose to boot from the backup. You may or may not have F3 in there, the BIOS will backup itself without you using ALT+F12, I am not sure when or what invokes this or how often it happens but it will be done for sure without you manually doing it. So you could have any in between F3 and what you are using now in your secondary chip.

The Qflash issue, that you came upon today, has not always been around but just in the last few sets of Beta's here the past week or three. The issue is just as you described it, once flashed with a Problematic BIOS the user could no longer use Qflash to flash to a previous BIOS and had to use DOS based flash or otherwise to go back to a older BIOS.

It has not been a constant thing either, I had been advised to pass along warnings that the Qflash issues may or may not be resolved. That is until a few days ago I was informed that they believed all BIOS after 3/11 should be good to go.

So hopefully your issue was just a quirk maybe? Care to run a check to see if it happens again still with F6e? No worries if you don't want to, I understand fully. If you do please post your results.

Anyone else please advise as well if you have Qflash issues after using a Beta dated after 3/11 so that I may pass it along