Zitat von @JSebastian im Beitrag #659

---

[quote="POE_UK"|p51494]Thats just the thing though, people should not have to install modded uefi bioses they should just work! but in all fairness, that issue on the biostar board is nothing compared to the myriad of issues gigabyte have, at least it can be reversed, but manufacturers do warn about bios flashing, but theres no way around it on the gigabytes

this is what im getting with vengeance rgb ram at 3400MHz and 3.6GHz cpu, the latency with memtest is 57ns

---

Zitat von matem im Beitrag #660

---

Hi, i've a Gigabyte AX370 Gaming 5 with the new Ryzen 2700X.
The mobo support the new Precision Boost Overdrive but not completely.

This is a screenshot from the Gigabyte X470 Gaming K7
https://i.imgur.com/5eNrGiB.png

Is it possible to enable the second option from this screenshot? The Precision Boost Overdrive Scalar

---

Zitat von CoUsT im Beitrag #657

---

Any way to get all these options on Gigabyte Gaming K7?

https://lime-technology.com/forums/topic...#comment-583547

Are they already present with the modded version you shared? I really miss some options as I recently moved from F7b to F23d and now I can't run my RAM with GearDown on 3200 MHz and higher. There are also no BankGroupSwap settings. Can I find them somewhere and why it doesn't work anymore with GearDown? Any ideas?

---

Zitat von Gigawits im Beitrag #658

---

Got the same problem with >= F10~F23d no geardown else its beep beep beep and thats it
Ive got settled with the idea that i dont upgrade so my 1700 runs fine under F7b , and will try in time a bios upgrade but lost faith in the fact
that GB can (not even try) to fix their shitty 5th grade grap , so for the rest its working but never again GB thats just a waste

---

Zitat von POE_UK im Beitrag #652

---

This is very true with asus, they have very poor bioses on most of their boards, @hereic do you know if i can get a waterblock for an rx580 8gb?

One things for sure i wont be getting a ryzen2 cpu i really cannot see the point

well just took the front panel of my case and that extra pinout header right next to the CPU led header is indeed an extra USB2.0 port, how cool is that, i can fit a permanent secure earse lixux distro in that slot now with an adaptor. what i normally do every 2 months is secure erase my m.2 drive to keep it fresh then reimage from a backup

---

Zitat von redrain85 im Beitrag #663

---

On the Ask GN 77 video (skip ahead to 12:08), Steve from Gamers Nexus was asked if any manufacturers listen to his feedback/criticism. In an example of a company that "listened", he mentioned Gigabyte.

He says that he told them while he felt their hardware was good (he was mentioning the latest Z370/X470 boards specifically), their BIOS is lacking. (Yeah, tell us about it!)

Apparently, when he goes to Computex this year he's going to discuss more in-depth with them what he wants to see improved. And he claims they do want to improve in this area. He also said that the people he's talked to want to make this happen, but the difficulty has been in getting upper management to agree to allow them to devote resources to improving the BIOS. Supposedly.

I wonder if Gigabyte is just telling Steve what they think he (and everyone) wants to hear, to try and keep people buying their boards. When, in fact, they really have no plans of improving.

Regardless, let's hope something good comes out of this discussion between Steve and Gigabyte.

---

Gigabyte blame AMD


http://forum.gigabyte.us/thread/1542/am4...&scrollTo=19083

GIGABYTE - Matt
**********
GIGABYTE Staff Right now I'm Offline
I have made 604 posts
I joined July 2016
I've received 190 likes My gender is Male I currently have no messenger contact information filled out. Facebook Twitter
Hi guys,

Just got back from vacation and was trying to catch up on some of the latest posts. From a quick view it seems people are vacillating between F22 and F22B. The short answer is use whatever works best for your system!

The long answer is one we have gone over but bears repeating. When AMD patches something (new AGESA, or patched AGESA) they give us the final binary code, not the source. This means we cannot see the exact changes they have made. We get a change log, much like the one's I try and supply you guys.... Engineers tend to say things like "Fixed XYZ, updated XYZ". They don't go into exact nitty gritty changes. So what does this mean? Well let's say we make a rule for ABC timings/voltage/whatever to +1 and it seems to help. Next AGESA comes out and perhaps that same setting is changed to +1 on AMD's end. Now we're at +2, which may not work at all! The only way to discover this is guess and check, hence this large BETA BIOS thread.

If I read the posts correctly it seems the biggest issue is F22 is slow with SSD's and won't reboot, but F22B seems to work on both fronts. This is with HEPT on or off. Is this correct?


After it was pointed out that all the other manufacturers get the same code and they can make it work Gigabyte - Matt hasn`t replied to any questions.

Thanks for your help
I understand that we ask you a lot
We can only say thank you for the support you are giving us by improving the bios
If it were possible to activate the "Precision Boost Overdri Scalar" function in the next updates
We can try and say if it works well
Gigabyte should support you for the improvements you are giving

Zitat von Drone69 im Beitrag #666

---

Gigabyte blame AMD


http://forum.gigabyte.us/thread/1542/am4...&scrollTo=19083

GIGABYTE - Matt
**********
GIGABYTE Staff Right now I'm Offline
I have made 604 posts
I joined July 2016
I've received 190 likes My gender is Male I currently have no messenger contact information filled out. Facebook Twitter
Hi guys,

Just got back from vacation and was trying to catch up on some of the latest posts. From a quick view it seems people are vacillating between F22 and F22B. The short answer is use whatever works best for your system!

The long answer is one we have gone over but bears repeating. When AMD patches something (new AGESA, or patched AGESA) they give us the final binary code, not the source. This means we cannot see the exact changes they have made. We get a change log, much like the one's I try and supply you guys.... Engineers tend to say things like "Fixed XYZ, updated XYZ". They don't go into exact nitty gritty changes. So what does this mean? Well let's say we make a rule for ABC timings/voltage/whatever to +1 and it seems to help. Next AGESA comes out and perhaps that same setting is changed to +1 on AMD's end. Now we're at +2, which may not work at all! The only way to discover this is guess and check, hence this large BETA BIOS thread.

If I read the posts correctly it seems the biggest issue is F22 is slow with SSD's and won't reboot, but F22B seems to work on both fronts. This is with HEPT on or off. Is this correct?


After it was pointed out that all the other manufacturers get the same code and they can make it work Gigabyte - Matt hasn`t replied to any questions.

---

Zitat von Mach5 im Beitrag #664

---

Zitat von POE_UK im Beitrag #652

---

This is very true with asus, they have very poor bioses on most of their boards, @hereic do you know if i can get a waterblock for an rx580 8gb?

One things for sure i wont be getting a ryzen2 cpu i really cannot see the point

well just took the front panel of my case and that extra pinout header right next to the CPU led header is indeed an extra USB2.0 port, how cool is that, i can fit a permanent secure erase lixux distro in that slot now with an adaptor. what i normally do every 2 months is secure erase my m.2 drive to keep it fresh then reimage from a backup

---

Does this method work for all SSDs? What does it actually do? Is overprovisioning even necessary?

---

Zitat von ket im Beitrag #668

---

Zitat von Drone69 im Beitrag #666

---

Gigabyte blame AMD


http://forum.gigabyte.us/thread/1542/am4...&scrollTo=19083

GIGABYTE - Matt
**********
GIGABYTE Staff Right now I'm Offline
I have made 604 posts
I joined July 2016
I've received 190 likes My gender is Male I currently have no messenger contact information filled out. Facebook Twitter
Hi guys,

Just got back from vacation and was trying to catch up on some of the latest posts. From a quick view it seems people are vacillating between F22 and F22B. The short answer is use whatever works best for your system!

The long answer is one we have gone over but bears repeating. When AMD patches something (new AGESA, or patched AGESA) they give us the final binary code, not the source. This means we cannot see the exact changes they have made. We get a change log, much like the one's I try and supply you guys.... Engineers tend to say things like "Fixed XYZ, updated XYZ". They don't go into exact nitty gritty changes. So what does this mean? Well let's say we make a rule for ABC timings/voltage/whatever to +1 and it seems to help. Next AGESA comes out and perhaps that same setting is changed to +1 on AMD's end. Now we're at +2, which may not work at all! The only way to discover this is guess and check, hence this large BETA BIOS thread.

If I read the posts correctly it seems the biggest issue is F22 is slow with SSD's and won't reboot, but F22B seems to work on both fronts. This is with HEPT on or off. Is this correct?


After it was pointed out that all the other manufacturers get the same code and they can make it work Gigabyte - Matt hasn`t replied to any questions.

---

Bad workmen always blame something other than themselves. I was also one of the ones to call him out on that BS - see if you can work out which one is me ;) From my testing F23d is better than F22b but F22b is a solid backup if F23d doesn't work out for you. Ironically it wouldn't take much for GB to fix most of the problems the firmware has simply setting one R&D guy aside to address the issues I have personally passed to GB through a contact is all that would need to be done and after perhaps half a day of work 70% - 90% of the problems would go away. The problems I told them about are mostly universal so fix the problem for one board you have fixed it for all applicable boards. The AGESA code now is plenty mature enough where manufacturers don't have to redo their firmware from scratch every time AMD make a new AGESA just major updates now are needed eg; new CPU support added, improved memory compatibility, that kind of thing. During those interim periods manufacturers can fix bugs specific to their products while reporting to AMD any bugs that are specific to the AGESA (and in all honestly that won't be many, if any. Any AMD AGESA option I have tested works flawlessly.) nobody minds waiting for a firmware update as long as the update is worth waiting for, which is to say; thoroughly bug tested and done properly.

F22b and F23d both do not have the HPET bug with F23d also benefitting from having a long, LONG standing SPD data read bug being fixed, I never experienced SSD issues with F22 but I also did not benchmark my SSDs on F22 so cannot say what the problem might be there my guess would be a bad SATA controller driver. I try to only look at the most widely reported problems as those are the ones that should be immediately dealt with issues that are not as widespread are more than likely specific to those systems or a singular specific component in which case the manufacturer of that component, not GB, should be being informed of the problem.

---

I totally agree, I find the fact that only Gigabyte are the ones who blame AMD for all their shortcomings laughable. As you have proven if they actually put some effort into their work it`s not too bad of a board. i`ve not updated to any of the newer BIOS`s, don`t want to screw up my working settings.

I only used an official BIOS for a couple of days before I started using the ones you fixed. I like to think it`s due to me using your improved BIOS versions I`ve been able to run my Hynix M die @3200Mhz and OC my Ryzen 1600x, using P-states to 3.975Ghz

I would like to say thanks for all your hard work.

That being said I`m going to be upgrading to an Asrock board when I`ve some spare cash.

Zitat von POE_UK im Beitrag #670

---

Zitat von ket im Beitrag #668

---

Zitat von Drone69 im Beitrag #666

---

Gigabyte blame AMD


http://forum.gigabyte.us/thread/1542/am4...&scrollTo=19083

GIGABYTE - Matt
**********
GIGABYTE Staff Right now I'm Offline
I have made 604 posts
I joined July 2016
I've received 190 likes My gender is Male I currently have no messenger contact information filled out. Facebook Twitter
Hi guys,

Just got back from vacation and was trying to catch up on some of the latest posts. From a quick view it seems people are vacillating between F22 and F22B. The short answer is use whatever works best for your system!

The long answer is one we have gone over but bears repeating. When AMD patches something (new AGESA, or patched AGESA) they give us the final binary code, not the source. This means we cannot see the exact changes they have made. We get a change log, much like the one's I try and supply you guys.... Engineers tend to say things like "Fixed XYZ, updated XYZ". They don't go into exact nitty gritty changes. So what does this mean? Well let's say we make a rule for ABC timings/voltage/whatever to +1 and it seems to help. Next AGESA comes out and perhaps that same setting is changed to +1 on AMD's end. Now we're at +2, which may not work at all! The only way to discover this is guess and check, hence this large BETA BIOS thread.

If I read the posts correctly it seems the biggest issue is F22 is slow with SSD's and won't reboot, but F22B seems to work on both fronts. This is with HEPT on or off. Is this correct?


After it was pointed out that all the other manufacturers get the same code and they can make it work Gigabyte - Matt hasn`t replied to any questions.

---

Bad workmen always blame something other than themselves. I was also one of the ones to call him out on that BS - see if you can work out which one is me ;) From my testing F23d is better than F22b but F22b is a solid backup if F23d doesn't work out for you. Ironically it wouldn't take much for GB to fix most of the problems the firmware has simply setting one R&D guy aside to address the issues I have personally passed to GB through a contact is all that would need to be done and after perhaps half a day of work 70% - 90% of the problems would go away. The problems I told them about are mostly universal so fix the problem for one board you have fixed it for all applicable boards. The AGESA code now is plenty mature enough where manufacturers don't have to redo their firmware from scratch every time AMD make a new AGESA just major updates now are needed eg; new CPU support added, improved memory compatibility, that kind of thing. During those interim periods manufacturers can fix bugs specific to their products while reporting to AMD any bugs that are specific to the AGESA (and in all honestly that won't be many, if any. Any AMD AGESA option I have tested works flawlessly.) nobody minds waiting for a firmware update as long as the update is worth waiting for, which is to say; thoroughly bug tested and done properly.

F22b and F23d both do not have the HPET bug with F23d also benefitting from having a long, LONG standing SPD data read bug being fixed, I never experienced SSD issues with F22 but I also did not benchmark my SSDs on F22 so cannot say what the problem might be there my guess would be a bad SATA controller driver. I try to only look at the most widely reported problems as those are the ones that should be immediately dealt with issues that are not as widespread are more than likely specific to those systems or a singular specific component in which case the manufacturer of that component, not GB, should be being informed of the problem.

---

Yes and the only way they are ever going to listen is by hitting them in the pocket, this website alone is massive in the gaming community and in itself has the power to totally fuck gigabyte up, HOW DARE gigabyte blame AMD for poor motherboard design, this is ALL gigabytes fault, every single bit, from their shitty vrm's and totally useless rgb implementation to their many design faults and piss poor UEFI, ok then how comes no other x370 board is this bad?

---

Zitat von Drone69 im Beitrag #671

---

I totally agree, I find the fact that only Gigabyte are the ones who blame AMD for all their shortcomings laughable. As you have proven if they actually put some effort into their work it`s not too bad of a board. i`ve not updated to any of the newer BIOS`s, don`t want to screw up my working settings.

I only used an official BIOS for a couple of days before I started using the ones you fixed. I like to think it`s due to me using your improved BIOS versions I`ve been able to run my Hynix M die @3200Mhz and OC my Ryzen 1600x, using P-states to 3.975Ghz

I would like to say thanks for all your hard work.

That being said I`m going to be upgrading to an Asrock board when I`ve some spare cash.

---

Zitat von ket im Beitrag #673

---

Zitat von Drone69 im Beitrag #671

---

I totally agree, I find the fact that only Gigabyte are the ones who blame AMD for all their shortcomings laughable. As you have proven if they actually put some effort into their work it`s not too bad of a board. i`ve not updated to any of the newer BIOS`s, don`t want to screw up my working settings.

I only used an official BIOS for a couple of days before I started using the ones you fixed. I like to think it`s due to me using your improved BIOS versions I`ve been able to run my Hynix M die @3200Mhz and OC my Ryzen 1600x, using P-states to 3.975Ghz

I would like to say thanks for all your hard work.

That being said I`m going to be upgrading to an Asrock board when I`ve some spare cash.

---

No problem, and the Fatal1ty X470 board looks particularly tasty ;)

---

Just had a quick look at the specs of the Fatal1ty X470 and it certainly does.