F37 non beta is out finally
F38 for the Aorus Elite.
They fixed the LogoFail vulnerability so perhaps it's something to do with that. It is an odd issue.I found out what the issue was, kind of. I have raised a ticket with Gigabyte to see if they can help at all...
After the upgrade, I found that my monitor connected via Display Port would no longer show during POST. This was using identical BIOS configuration. Even so, I tried changing CSM, I ensured the correct PCIE was selected for POST etc. but nothing helped. I reverted back to F36 to double-check, and it worked fine again. Moved back to F37, and there is no display signal during POST. My display comes back to life as soon as Windows boots. I am also able to boot into the BIOS configuration via "del". It's just the POST screen no longer shows. As a workaround, I can use a different HDMI monitor and it works fine.This appears to be related to: https://www.nvidia.com/en-us/drivers/nv-uefi-update-x64/. But, my VGA BIOS is up-to-date and the issue only occurs on the newer F37 BIOS. It seems like either Gigabyte need to update something re VGA/CSM etc. or maybe EVGA need to update their VGA BIOS if it is no longer compatible for some reason.
I'll update if Gigabyte provide any guidance. Considering how 'old' this board is, I fully expect them to tell me to bugger off
This was exactly my thought.They fixed the LogoFail vulnerability so perhaps it's something to do with that. It is an odd issue.
This has been removed nowF38 for the Aorus Elite.
- Update AMD AGESA V2 1.2.0.B
- Fix AMD processor vulnerabilities security
- Addresses potential UEFI vulnerabilities. (LogoFAIL)
Might look at updating from F21. I'm 7 versions behind but everything is stable!
F37 was removed.Hey community, I updated my bios from F36 to F37 and now I have a 0d error with the F37 and F36 bios, has somebody the same issue and was able to solve it?
My PC ryzen 5800x, gigabyte 6900xt, gigabyte x570 master, 4x8G GB 3200 CL16 Corsair Vengeance
I know, but how I get rid of the 0d error?F37 was removed.
Have you tried 'Reset CMOS' ?I know, but how I get rid of the 0d error?
The error occurs now with the old drivers too.
It fixes the LogoFAIL security bug:I am currently on F36f - any point updating to F38?
Thanks