[OFFER] Gigabyte GA-AX370-Aorus Gaming 5 BIOS mod



all ryzens run at 2133 fella, any faster is actually overclocking.

i know that, but i though ket say the subtiming displayed correctly for this bios (on the right side column in bios)

edit : i set my RAM on 2933 MHz 14-14-14-14-34-48 but the subtiming on the right side show 15-15-15-15-35-50

Ive just been looking at the aourus x470 board, lol they never learn do they, for people that watercool with hardline tubing putting the m.2 slot right next to the gpu slot is the dumbest thing ever, it means you have to strip your whole system down to change it. agreed others are guilty of this as well but damn gigabyte, have you learned nothing? and the vrm sinks look real cheap and nasty



You need to go to "Advanced Memory Settings" then set "eXtreme Memory Profile" to Enabled. The XMP profile on your memory will then be loaded and applied when you save and exit. Your system might also reboot itself the first time after enabling XMP, this is normal.




The SPD data is read correctly, by which I mean all timings that have a SPD value are now read and displayed correctly. They are not dynamic and will not change when you manually change the values, the information displayed is just what is contained in the SPD data on the memory.



Correct, while the x470 taichi will be every bit as good as the x370 theres absolutely no reason to get one, the topology is almost identical, asrock added bios support for ryzen2 cpuā€™s ages ago, in fact i really cannot see the point in getting an x470 board if you own a good x370

Ket,

Thanks for the updated bios for the K-3. Made a few changes and running at 3.2 GHz and 3200 on Ram. Hope the board lasts as long as my Asus Rampage formula with the Qx9650. It is still running strong after all the years of 24/7 service.

MAK



Almost certainly but Iā€™m already at capacity with the number of firmwares Iā€™m modding, drivers being modded, and compiling packages with the latest drivers. Someone else would need to step in and agree to pick up on what I donā€™t have the time for.




How bout showing a guide and the tools your using I think most of us are willing to learn and try it ourselves.


This is what I was hoping for . . . and what I was afraid of, at the same time.

I figured that if Gigabyte was actually going to take the AM4 platform seriously in any way, theyā€™d finally make an effort with the UEFI when X470 debuted. And this might trickle down to X370/B350.

If the UEFI didnā€™t improve now: then weā€™d know it would never, ever improve.


That being said, a couple of folks on the Gigabyte forum are claiming P-state overclocking might be broken again on F23d.

http://forum.gigabyte.us/post/19378
http://forum.gigabyte.us/post/19388


Huh! I didnā€™t know, until now, that the AMD chipset drivers package doesnā€™t install an AMD AHCI driver. They leave it to the generic Microsoft drivers to do the job.

Tempted to give the AMD AHCI driver a try, but does it really make much of a difference in performance? According to this post, the MS and AMD drivers are about equal:

Recommended AHCI/RAID and NVMe Drivers (63)


If you choose to believe CanardPC (and I do, in this case): the X470 chipset is really just a rebrand of the X370 chipset. There is no difference between them, whatsoever.

All the differences are in the new Ryzen 2000 series CPUs (IMC, for improved memory support), the new X470 PCBs (better VRMs, and improved memory trace layouts in some cases), and the updated UEFIs.

So if your board already has decent VRMs, good memory overclocking results, and really good UEFI support from the manufacturer: simply replacing your Ryzen 1000 series CPU with a 2000 one will get you almost all the benefits of X470 without needing to replace your board.


If you choose to believe CanardPC (and I do, in this case): the X470 chipset is really just a rebrand of the X370 chipset. There is no difference between them, whatsoever.

All the differences are in the new Ryzen 2000 series CPUs (IMC, for improved memory support), the new X470 PCBs (better VRMs, and improved memory trace layouts in some cases), and the updated UEFIs.

So if your board already has decent VRMs, good memory overclocking results, and really good UEFI support from the manufacturer: simply replacing your Ryzen 1000 series CPU with a 2000 one will get you almost all the benefits of X470 without needing to replace your board.[/quote]

This pretty much ties in with my thoughts for x470, by all means get one if you dont have a good x370 board otherwise its just pointless.

Also sniffing around on gigabyte forums and other places a shit ton of people are still have major bios issues with the gaming5 and k7, wtf

Well for me its GB presenting the middle finger , the F23d bios just brings in more crap
cant go over 3200Mhz with memory even different sets rated 3200, 3600, 4200Mhz , place it in a different mobo (not Gb) no problem
Geardownmode should be working on 2666 (does also on F7b and yes the above mentioned mem ratings )
But the crapness is the the softbrick is back (or atleast by mine GB-K7) lucky i dont have a battery seated so 5min powerof and dustoff and try again but nomore with this F23 or whats to come
For now i stick with F7b , no problems i cant handle
And to be honest its working great , so thxz ket for trying to fix things (f22d-m bios i believe) but still the bugs are infested deep
So i say stay away from Gigab


This is what I was hoping for . . . and what I was afraid of, at the same time.

I figured that if Gigabyte was actually going to take the AM4 platform seriously in any way, theyā€™d finally make an effort with the UEFI when X470 debuted. And this might trickle down to X370/B350.

If the UEFI didnā€™t improve now: then weā€™d know it would never, ever improve.


That being said, a couple of folks on the Gigabyte forum are claiming P-state overclocking might be broken again on F23d.

http://forum.gigabyte.us/post/19378
http://forum.gigabyte.us/post/19388


Huh! I didnā€™t know, until now, that the AMD chipset drivers package doesnā€™t install an AMD AHCI driver. They leave it to the generic Microsoft drivers to do the job.

Tempted to give the AMD AHCI driver a try, but does it really make much of a difference in performance? According to this post, the MS and AMD drivers are about equal:

Recommended AHCI/RAID and NVMe Drivers (63)


If you choose to believe CanardPC (and I do, in this case): the X470 chipset is really just a rebrand of the X370 chipset. There is no difference between them, whatsoever.

All the differences are in the new Ryzen 2000 series CPUs (IMC, for improved memory support), the new X470 PCBs (better VRMs, and improved memory trace layouts in some cases), and the updated UEFIs.

So if your board already has decent VRMs, good memory overclocking results, and really good UEFI support from the manufacturer: simply replacing your Ryzen 1000 series CPU with a 2000 one will get you almost all the benefits of X470 without needing to replace your board.




P-States are always going to be a fickle thing and I donā€™t know the situation with other manufacturers regarding P-States so I donā€™t see the point in always complaining P-States are broken in some way they are there at least just avoid using the setting that is broken in their case there are many other bugs and problems with the firmware a lot more severe than a P-State setting not working. The X470 for some time has been known will be marginally different at best compared to X370 unless you have a turd like an Aorus board I think any other board is completely fine, and lets be honest, Iā€™ve reviewed enough X370 boards to be able to say that with certainty :stuck_out_tongue:



Almost certainly but Iā€™m already at capacity with the number of firmwares Iā€™m modding, drivers being modded, and compiling packages with the latest drivers. Someone else would need to step in and agree to pick up on what I donā€™t have the time for.




How bout showing a guide and the tools your using I think most of us are willing to learn and try it ourselves.


I have considered that but it would also take time for me to write. Iā€™ll try to find the time but there are a lot of guides on this forum that will tell you the tools you need to use and how to do a lot of things already.



I really canā€™t say why my thermal performance might be lacking. I hear the pump change speed if I change profiles, so it is running. The fans are running. Even after taking it off (was installed with the default thermal paste that was pre-applied) when I sent the motherboard away, and then using my own paste when I re-mounted it, it was performing more or less the sameā€¦ What else should I check? My ambient temperatures arenā€™t THAT high, sometimes upper 20s (Celsius) I guess. What does that setting throttle, and if it does throttle, would it not decrease performance and the temperature it produces?




Great to hear confirmation that the SBZ works on it! I guess I went for the Creative and not the Asus sound cards, because my previous PCI Sound Card was Creative so I was more familiar with the brand. Apart from this seemingly random compatibility issue I have been happy with it (apart from the bright red LEDs. Thatā€™s I painted the whole thing black and put in blue LEDs). If I ever have to buy a new one, Iā€™ll consider the Asus ones then too.



I just hope that the X470 chipset will support the first-generation Ryzen CPUs as good as the X370 chipset does, since I donā€™t see the point on upgrading to Zen+ from Zen. If I get 3.8GHz out of my 1700x, great. If I get more with reasonable temperatures, even better.

Check that the pump is at 100% they are inaudible so theres no reason not to let them run 100% really. Iā€™d also consider tipping the rad a few times there might be a trapped air bubble impeding the flow.



The fan header is set to 100%/maximum. Because the rest of my system is normally rather quiet, I can hear the pump when I put it in non-Quiet profile (whatever it is called), so I normally keep it in Quiet profile unless I stress test or encode videos. I have a 200mm and 120mm intake, and a 120mm exhaust fan other than the two on the H100i, so I think it is getting enough air. Also, it is on the exhaust side, so it is drawing (probably warmer) air from inside the case. Would it make such a huge difference? I donā€™t think I can mount it anywhere else though.



The fan header is set to 100%/maximum. Because the rest of my system is normally rather quiet, I can hear the pump when I put it in non-Quiet profile (whatever it is called), so I normally keep it in Quiet profile unless I stress test or encode videos. I have a 200mm and 120mm intake, and a 120mm exhaust fan other than the two on the H100i, so I think it is getting enough air. Also, it is on the exhaust side, so it is drawing (probably warmer) air from inside the case. Would it make such a huge difference? I donā€™t think I can mount it anywhere else though.




Iā€™d need to see a few pics of your system with the panel off to offer some good airflow suggestions for your specific setup. If you can hear the pump the pump bearings might be wearing out even if I disable all of the fans in my system I still canā€™t hear the pump from my 240mm MasterLiquid and the pump on that I run 100% all the time. If you are considering a new AIO I would definitely recommend CoolerMaster AIOs Iā€™ve reviewed a few of them and looked at just about every AIO in existence and the AIOs you can get from CM or NZXT (if you are willing to pay the prices of the Kraken models) really are the best.

Is anyone else having problems with F23d firmwares on AX370 K7 boards? After one reboot or two, my machine wonā€™t POST.

Official gets stuck with debug code 78, and ketā€™s one with F2 code.

Clear CMOS helps, but I set up stuff, and after one or two reboots, wonā€™t POST again.

That looks like you are overclocking with P-States. GB keep breaking that feature so general consensus is just donā€™t use it OC with multipliers instead.

Actually I donā€™t use P-states. I use fixed 39x multiplier and thatā€™s it.

What I usually do is:

1) Cpu multiplier to 39X
2) Enable XMP (3200Mhz CL16)
3) Disable geardown mode (CR2)
4) Loadline calibration to High
5) Vcore at 1.38750v
6) Vcore SOC at 1.10v
7) Enable SVM
8) Enable Fast boot
9) Disable CSM
10) Disable HPET (in GBā€™s firmware)

Anything else remain as-is.

Iā€™ll try to test settings one by one, hopefully I find the culprit.



Well after looking at this problem further I can tell you code 78 is an ACPI initialisation issue, seems like my modded firmware fixes that problem and kicks out an F2 which is the board putting itself in recovery mode. You might have a compatibility issue with your memory kit but before suspecting that try this;

1. Look for the two dip switches at the bottom of the board, the bottom most switch is for dual or single BIOS operation mode.
2. Flip the very bottom switch to single BIOS mode operation, boot up, flash to my modded F23d.
3. After the system restarts shut it down and flip the top dip switch to the alternate position to set the other BIOS ROM chip as the active one.
4. Wait for the system to POST then enter Q-Flash and flash my modded F23d to that ROM chip as well.

Long story short, it sounds like your board likes to either soft brick itself or is randomly trying to restore to a different firmware image because there are mismatching firmwares on the ROM chips causing the system to have a weird kind of conflict between the newer and older firmware images. In my testing at least switching the board to single ROM operation mode has completely stopped any and all soft bricking issues. I didnā€™t have many problems of this nature and the one time I did I suspect the problem was not a soft brick perse but a bad AGESA code update as I had the same problem on both the Gaming 5 and GT7 at the time but to play it safe I switched to single ROM mode on the Gaming 5 and have had no problems of that nature ever since.

Well, I just had the most bizarre experience.

Long ago, I flashed ketā€™s modded F7b to the Main BIOS and left the Backup BIOS on the factory default of F3. I also left the BIOS mode switch in Dual BIOS mode, again the factory default.

When the Main BIOS decided to corrupt itself several months ago, the board automatically switched to the Backup BIOS. Then, just to make sure I was flashing the correct BIOS, I toggled the BIOS switch back and forth between Backup and Main. I made sure the LED indicator showed Main before I re-flashed F7b.


Not too long ago, I decided to set the BIOS mode switch on the K7 to Single BIOS mode in position 2 as a safety precaution. (At least I hope thatā€™s right, because I question whether or not the manual is actually correct.) And Iā€™ve always had the Main BIOS selected for boot, in BIOS switch position 1.

A few days ago, I flashed the Main BIOS with ketā€™s modded F22b. Then, I thought, Iā€™d switch to the Backup BIOS and flash F7b as a safe BIOS to fall back on. To my surprise, the Backup already contained F7b. Hmm. So I guess back when I re-flashed F7b to the Main, and still had Dual BIOS mode enabled, at some point it copied F7b to the Backup and replaced the factory F3. Not happy about that, but okay. Whatever.


Then, yesterday, I noticed the board was suddenly booting up with BIOS F7b. WTF?!

I decided to flick the BIOS switch from position 1 (Main BIOS) to position 2 (Backup BIOS). And what did I get? F22b!

In other words, the board randomly decided to swap BIOSes. I checked the BIOS LED indicator and, yes, it showed Main BIOS was active with F7b. I flicked the switch to Backup, and it was active with F22b.

So I switched back to Main, and flashed it with ketā€™s modded F23d. The Backup still contains F22b, when it should have been F7b.


Iā€™m at a loss for words, here. This should never, ever happen. NEVER! Iā€™m really regretting buying this board. This will be my first, and last, Gigabyte motherboard.

So, bottom line, is that the board seems to have arbitrarily decided to reverse the behaviour of the BIOS selection switch. Selecting Main now sets Backup, and selecting Backup now sets Main. Even though the LED indicators show otherwise.


P.S. On this F23d BIOS, the POST code indicator is frequently changing codes after boot. It usually shows 33, but sometimes 35, and sometimes D3. With prior BIOSes, it would always be a steady 40 unless you restarted, and then it would change to 24. Donā€™t know what to make of this, but itā€™s strange behaviour.

Oh, and just to make it clear: I know these issues have nothing to do with you, ket. Youā€™re doing your best to fix Gigabyteā€™s fuck-ups, and we all appreciate it! Your modded BIOSes are far better than the originals.