aorus b450m f.50 leads to vga led staying red

[hanswurst]

the latest bios leads to the vga led staying red. i need to remove the pcie power cable pf my graphic card. resetting the bios via jumper or removing the battery doesnt work either. luckyly i have a ryzen 2400g. otherwise i would have been f..... Why do you release such update without testing it before? it costed me hours. not sure yet but i dont think i will buy a gigabyte motherboard again...

[shadowsports]

the latest bios leads to the vga led staying red. i need to remove the pcie power cable pf my graphic card. resetting the bios via jumper or removing the battery doesnt work either. luckyly i have a ryzen 2400g. otherwise i would have been f..... Why do you release such update without testing it before? it costed me hours. not sure yet but i dont think i will buy a gigabyte motherboard again...

Greetings,
Not sure if you are here to express dissatisfaction or are seeking assistance?

If you want help...

What BIOS did you come from?
F32 is a pre-reg for F40
Did you apply the EC FW Update tool - you wouldn't want to go to F40 or > without it regardless of the CPU you were using? (memory compatibility)

F41 was last non-beta release

And you upgraded to F50a (a beta BIOS) from your system which was stable? Running a RavenRidge CPU supported with any BIOS F1~F40 (all non beta) in order to address what?

Because the fixes above F40 appear to be related to AGESA updates for CPU's you don't own, RAID compatibility, enhanced Destiny 2 support, video issues (for CPUs) you don't own, improved m.2 compatibility or decreased boot times which I doubt you are affected by or you would have said something?

If something is now broken, I'd revert to F40, stay away from anything beta and enjoy my computer.  If there is another issue, I or someone else would be happy to try and help.

[hanswurst]

Not sure if you are here to express dissatisfaction or are seeking assistance?

both.

i was and currently again am on F42g

f50a isnt labeled as beta:

https://www.aorus.com/product-detail.php?p=796#pd_download


it was stable but why not to update? boottimes are slow, so i wanted to give it a shot.

[shadowsports]

Not sure if you are here to express dissatisfaction or are seeking assistance?

both.

i was and currently again am on F42g

f50a isnt labeled as beta:

https://www.aorus.com/product-detail.php?p=796#pd_download


it was stable but why not to update? boottimes are slow, so i wanted to give it a shot.

Greetings,
Well, you gave it a shot.  Many times, BIOS' are optimized for the generation of CPU's they are targeted to support.  While backwards compatibility is expected, its not always guaranteed, or it might work, but not as well as an earlier revision.

I normally suggest staying with the BIOS written for the Generation of CPU you are running, and only upgrade when indicated.  Address a security issue, add support / hardware compatibility, correct a specific problem or behavior.  Not sure how "slow' your boot was but I guess enough to warrant you trying F50a.  BIOS' with a (letter) designation are beta's.  Some are very stable, while others are not.  No manufacturer guarantees another release, but newer hardware typically sees regular BIOS releases for at least 18 months.  If you are stable again, I'd stay where I'm at.  You already know F50a does not appear t work correctly with your CPU and system config.     

[AgentFXA]

.. Why do you release such update without testing it before? it costed me hours. not sure yet but i dont think i will buy a gigabyte motherboard again...

All depending on hardware configuration (and possibly overclock) it works or fails - I had no problems with F50a ..