I doubt there is true support for Fast Boot from that board. It is missing EFI RAID drivers, EFI UNDI driver, basically the firmware feels like a hybrid between EFI and legacy.



If you don't get a fix from BIOSTAR, I wouldn't try to insert the EFI drivers on your own. Just work with the maximum you can get at full stability.

Fernando and lordkag,

Thank you both for replying and investigating the issue with this bios. I just wrote to Biostar support, lets see what will get from them, not much hope though :)
Meanwhile after my modification of bios 97XAD807.BSS with UBU tools (kudos to Sonix for make this nice piece of software) the following modules are detected.

1 AMD OROM and EFI Nodules
OROM AMD AHCI 4391 - 3.3.0.0
OROM AMD RAID MISC 4392 - 3.3.1540.19
OROM AMD RAID MISC 4393 - 3.3.1540.19
EFI AMD RAID - Not present
3 LAN OROM PXE and EFI UNDI - Intel, Realtek, BCM, QCA
OROM Realtek Boot Agent - 2.63
AMD AGESA CPU Support
EFI AMD AGESA OrochiPI - 1.5.0.5

As lordkag suggested probably it is kind of crippled UEFI bios without some functionalities.
Will keep you guys posted for any further development, meanwhile if u come up with ideas - you are most welcome.

Regards

UBU is not written by me, Sonix is the author. And I believe the AHCI ROM was not in the original BIOS, it was added by you with MMTool/UEFITool? You can see from the various missing pieces that the board is not decided between Legacy and UEFI. I hope BIOSTAR is more supportive than Asus.

@lordkag

Thanks for clarification for UBU tools, corrected my previous post. I used your Gop update software for modding EVGA rom, so kudos to you are still valid :)
Now to the point - I did inserted the AHCI ROM with MMTool, hoping it should solve my problem with Option ROM set to EFI compatible but obviously it didn't work. Thought that was the problem for system not finding efi compatible module, but obviously this is not the case. Could you elaborate what supposedly am I missing here?

The AHCI ROM is legacy only, it had nothing to do with your issue. All EFI systems have an EFI AHCI driver that is not OEM dependent. In fact, you will have an impossible task of finding EFI AHCI drivers provided by Intel or AMD. For your issue, there are two options: either you have RAID or PXE/UNDI boot activated - no such EFI drivers in your system, or there is a problem in the Biostar code. The first one can be tested by simply switching to AHCI and disabling any Lan/PXE/UNDI Boot option. If the problem is still there, only Biostar can fix it.

Understood. Obviously got the second case - since my Boot from LAN option was set to DISABLED from the beginning and the system is running in AHCI.
Meanwhile I received surprisingly quick answer from Biostar support team regarding my question about fast boot option and the missing efi modules in the bios of the TA970 motherboard. Not so surprisingly it contained the the following ridiculous statement:

---------------------
Dear Sir,
Regarding to your question,
sorry that this model support Support Windows XP / Vista / 7 / 8 OS,does not support Windows 10 OS as your request.
Here is TA970 V5.0 specification link for your reference,
http://www.biostar.com.tw/app/en/mb/intr...p?S_ID=623#spec
--------------------

Left me silently wondering what am I missing here :)

The classic answer wrapped in middle finger paper. What Win10 has to do with this, I don't know. If the OS supports UEFI and its boot configurations, it makes no difference what version it is. If you want to make them a case, try to install Win8/Win8.1 and repeat the test.

@lordkag I don't really want to go off topic here, so I'm not sure where to post this. However, reviewing this whole tread trying to figure out my issues has been endless. I have a P8P67 which I have successfully modded my Firmware to boot UEFI, however, the problem I am having is exactly the issues that you @kevindd992002 was having, where the machine will POST to ASUS splash screen and hang. Since kevindd992002 indicated he got a beta BIOS that works, is there a chance that I can export some of the modules from his BIOS and import them to my P67 to update the EFI modules that fixed his issue? Also, I already contacted ASUS who promptly pointed the middle finger at EVGA saying it was their problem. However, after testing my 780GTX on my supermicro server board in EFI only mode I was able to successfully post and boot to a UEFI usb. Contacting EVGA they tried their best, by giving me an updated VBIOS which updates the GOP I'm guessing but it didn't help. I will dump my GOP using your script in the other thread so that we have that data available.

@Fernando would you be the one to ask this question?

*Edit* I am able to get everything to work if I run Legacy mode which I'm guessing is a mixture of EFI and Legacy because I'm booting off the NVME PCIE card. If I set EFI compatibility the machine will post and hang with the 780GTX. Squarely pointing the finger at the UEFI firmware on the P8P67. I'm still curious if I can harvest some of the newer roms form the later UEFI updates to allow this to post and boot normally on full blown UEFI.

Zitat von kevindd992002 im Beitrag #135

---

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.

---

That's exactly the process I'm performing when flashing new BIOS revisions, so no problem with that. Regarding the vBIOSes of my GTX 670 cards though, are the ones you edited still the latest GOP's?

Zitat von JohnM im Beitrag #134

---

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?

---

Mine is the non-PRO version, sorry, but I'm sure you can request one from ASUS.

---

I believe he's asking me that question.

@zazzn

The BIOS version given to me was 9903. Please take note that this is for the ASUS P8Z68-V/GEN3 board. The latest publicly-released BIOS for this board is STILL 3603 and I doubt will ever be going updated in the future as this board is already EOL.

Hello everyone,

I see that I'm very late to this thread, but I may have some info that could help. I am running an ASUS P8Z68-V PRO/Gen3 Board and like all of you the POST process freezes at the logo screen if I use the EFI Boot option. However A few years ago I was using a Gigabyte GV-R797OC-3GD video card and that card WOULD boot using the EFI Boot option! There was a noticeable boot speed-up too!

The card worked this way until Gigabyte updated the card BIOS to the F3 version. But the F1 and F2 vbios worked just fine with EFI enabled.

I have attached all three vbios below for your inspection. Perhaps this will provide an insight into why the EFI option doesn't work anymore. Maybe the GOP section needs to be removed entirely or modified in the F1/F2 style.

@Cyberia,

I have the P8Z68 Deluxe Gen 1 board and also have the same issue with Efi boot freezing on the logo. Have never been able to fix this and your report is interesting in that points to the vbios being the culprit. I suppose you could try flashing different vbios roms till you find one that works or use the gop update tool.

Thanks

The problem is definitely in the vbios. Read the included changelog for the F3 vbios:

Gigabyte.R797O3GD.F3.rom

1. ATI Source BIOS Version:015.032.000.004
2. ECLK/MCLK: 1000/1375 Mhz
3. Release For HYNIX Memory
4. UEFI BIOS


Unfortunately I don't have that card anymore....and have been forced to use the LEGACY BOOT option since.

I'm aware of the GOP Updater tool, but AFAIK it hasn't produced a single variant that works on the ASUS P8Z68-V PRO/Gen3 Board w/ EFI BOOT enabled. Correct me if I'm wrong.

But I thought the modders (I'm not one) here would be interested in comparing those vbioses