"UEFI Boot" is in green, so it means it is enabled, if we should trust the software. The "Not capable" message is definitely a bug, probably related to the fact that your BIOS is more than two years old. But it is still UEFI. More than that, how could you have UEFI Boot without an UEFI firmware? Even my old laptop is seen as "UEFI Capable" (but not UEFI Boot) and its last release was in 2010. You can report this bug in their forums, they should fix it fast. Every BIOS released after 2012 should be in fact UEFI, unless it was a bugfix of a very old release.

Did you guys know that it's possible on the P8Z68 to disable CSM through AMIBCP as 'CSM Support' is a hidden menu option so theoretically you could disable CSM by hard coding it into the bios optimized settings. If only there was a way to unhide that menu option?!

Edit: Can someone test this rom to see if it has a uefi gop?

https://www.dropbox.com/s/eggv04exrs10yoe/GK110.rom?dl=0

Thanks

Interesting. I hope you can work on the CSM support more.

By the way, ASUS gave me a new BIOS for my ASUS P8Z68-V/GEN3 board that works when "EFI compatible" is chosen in the BIOS. Apparently, they fixed the problem but I'm not sure what the changelogs are.

If I post the BIOS in this thread, can you guys look at the difference in code?

Great!

Here's the BIOS:

https://www.dropbox.com/s/hn531kwm4w87rn...S-9903.ROM?dl=0

These are the changes:



To be fair, there were many files that had a different CRC, but after removing the date stamp with a script, this is the result. In green you have the files that had only cosmetic changes, like new version and a new compilation date. In blue I have selected the files that have little chances to be related to the topic's problem. Only those in red could be related, where AMITSE and CORE_DXE come first, while CSMCORE and BIOSBLKIO are less likely to fix the problem.

Zitat von lordkag im Beitrag #128

---

These are the changes:



To be fair, there were many files that had a different CRC, but after removing the date stamp with a script, this is the result. In green you have the files that had only cosmetic changes, like new version and a new compilation date. In blue I have selected the files that have little chances to be related to the topic's problem. Only those in red could be related, where AMITSE and CORE_DXE come first, while CSMCORE and BIOSBLKIO are less likely to fix the problem.

---

Hi,

I did a little trouble shooting and found on one of my systems having more than one gpu installed in a pci-e slot causes a failure in pure efi boot mode with CSM disabled.
This is a Gigabye Z87X-UD5h motherboard with a EVGA 770GTX videocard that according to nvflash --version has a UEFI compatible GOP. I also had a second 740GT video
card with UEFI firmware. Swapping each card or booting with the onboard gpu was as easy as can be unless I plugged in more than one video card where the system
would hang on the boot logo. This is remarkably similar to my P8Z68 Deluxe gen 1 board with two 780GTX's in there. Unfortunately that board doesn't have an dGpu
port though I am willing to bet it would post if I had only one video card in there!

I mean I have no trouble booting with just one video card.

Thanks

Zitat von kevindd992002 im Beitrag #129

---

So to sum it all up, what do you think they really did in this BIOS? Just more on cosmetic changes that "led me to believe" that they fixed it? I'm not sure if using this beta BIOS would be better than using the latest published one.

---

Great! I'll do that. How about overclocking potential? Since there are OC'in-related changes, is it safe to assume that the OC'ing potential would be affected either positively or negatively? I'm not sure if I need to re-do my overclock to get a better one.

I don't see the changes so important as to affect the overclocking, neither in good nor in bad. But it is always a safety measure to reset to defaults before flashing, again reset after flashing, shutdown and only after that re-apply your settings. If you were talking about testing for new overclocking potential, I wouldn't do that, unless you have problems with current settings or have the time to do it.

Hi kevindd992002,

I had the exact same problem as you described in your first post and I'm curious if we have the same mobo. If they are the same I'm thinking of trying out the BIOS you posted.
Is your board an ASUS P8Z68-V Pro/Gen3?

Zitat von lordkag im Beitrag #133

---

I don't see the changes so important as to affect the overclocking, neither in good nor in bad. But it is always a safety measure to reset to defaults before flashing, again reset after flashing, shutdown and only after that re-apply your settings. If you were talking about testing for new overclocking potential, I wouldn't do that, unless you have problems with current settings or have the time to do it.

---

Zitat von JohnM im Beitrag #134

---

Hi kevindd992002,

I had the exact same problem as you described in your first post and I'm curious if we have the same mobo. If they are the same I'm thinking of trying out the BIOS you posted.
Is your board an ASUS P8Z68-V Pro/Gen3?

---