On the taichi you can go up to 113Mhz on the clock generator before the pcie-bus switches to 2x mode, but as i say 3333Mhz will yield the fastest results as ryzen prefers tight latencies over speed, memtest confirms this, the latency will go down to 57ns and at 3600 that goes up to 61ns, ryzen also does not like odd cas timings, you can do 14 16 or 18 on the cas but 13 15 and 17 will never work. Also note the clock chip is also there for the new ryzen cpus that are coming out that will take even more advantage of it. The voltage problems of this board cause various issues from random reboots to bios lockups, the problems also are at the stages of delivery way before the bios switch hence the bios switch is actually useless. you must have been real lucky to get a working board ket, i know at least 5 people myself included that got hit by this board, i was blaming the psu at first (corsair corsair 750x) but nope, nothing to do with it at all, its rectifiers are rock solid. gigabyte has tried to fix these problems with software but it aint happening, there was loads of batches sold with various hardware faults that caused anything from random shutdowns to cpus being destroyed. of course i cant diagnose everyones board without looking at it and people that say they can over the internet are fools.

Im looking at the whole picture here not just this boards many faults, >

I used to love gigabyte man, at one point it was only gigabyte and abit i would ever buy, but these boards are all style over substance, they have the pretty lights, they have the rgbw, but do they work properly? people get sucked in by looks, great if you want a flashing paperweight. They also promised users a place to buy etched name plates, did that happen? did it fuck, and the m.2 is in the most stupid place imaginable, meaning if your machine is hard tube watercooled and the m.2 fails you have to completely strip your whole machine down to replace it. there is no wifi, there is no temp cpu led readout, there is no standard pci slot (which a lot of people still use btw) and there are U2 ports which are near as makes no difference useless my taichi has one of these ports i wish they hadnt bothered tbh but at least theres only 1 of em. on arrival of the gaming5 one of the crystal oscillators was loose meaning i had to solder it back on, from the word go i knew i was in for a world of pain. remembering back if i remember right the waveforms were bloody terrible with spikes all over the shop, of course i dont own this thing now and it was way off frequency. In the last 30 years no board has given me so many headaches as this thing i felt like throwing it through the window, disappointment no1 was when the leds didnt work properly, although its not an important feature it should at least work properly, they have also used the cheapest diodes they could find, the colour separation was just horrible, simple 3mm diffused rgb leds would have been so much better, this is another issue i could have fixed myself but i really couldnt be arsed to get my hot air station out. macbook air laptop motherboards have give me less problems although they can be just as bad with everything being bloody glued down (i urge anyone not to buy on of those either) asrock were once a budget brand, a spinoff from asus using their spare factory parts to build motherboards, but with ryzen its safe to say the taichi and the msi are the only two i will ever buy or recommend and there are no exceptions here not even asus cut the mustard. I know ill probably never use 10 sata3 ports but its nice to have them there im using 5 of them atm with 4x1tb western digital blacks and a lg buray writer, we all know m.2 nvme are fast as hell already but also having the ability to raid them is a feature id take over any onboard led gimmick, and we have to remember here that the taichi in some stores is actually cheaper now that the gaming5 was!

So in a nutshell ket if i get hold of my findings with this board ill post them here, before i go there was another fault i found and that was in the front panel audio section i cant remember what it was off hand but i know it rendered it completely useless, it was the worst sounding implementation of the alc1220 i have ever heard, of course they tried to correct it with the use of creatives 3rd party software but it still didnt work right. Although anyone serious about audio wouldnt use any onboard sound chip no matter how good they claim they are, all these things should at least work properly and they do not, the motherboards overall instability caused the front panel audio to completely crap out at random intervals and/or cause major distortion of the output signal. so as you can see this is just for starters, theres really nothing i like about these motherboards, but whether i like it or not personally is irrelevant, they are faulty enough said. I told gigabyte about all this many months ago, you know what their answer was? "we are working on a bios to fix this" haha what a joke.

The BCLK value you can attain is highly, HIGHLY, reliant on other hardware in the system very few people will make it anywhere near 113MHz before a device becomes unstable due to the higher bus frequencies. Zen likes low latency, but there is always a balance each person needs to find for their system. Case in point; I can run 3200 CL14 or 3466 CL16, the latter has the same latencies as 3200 CL14 but quite a bit higher bandwidth. What is applicable to one system may not be true for another even with identical hardware. You can also use odd CAS numbers but you need to switch to 2T, don't know what the outcome would be on every board I just happen to notice on one of the boards I was testing that switching to 2T allowed for the use of odd CAS latency numbers. I'll state again that the point in switching to single ROM mode is to protect one of them so the board doesn't end up bricking both if it tries to recover a corrupt image automatically. I'd also argue GB have done precisely fuck all to fix this board all of the bugs with it I logged over a year ago are still there today or worse and GB have somehow managed to add a few more to that bug log with their most recent firmware, all of them are utter crap its why I'm weeding through them picking out the firmware for each board that seems to be the least buggy. I'd forget updating the firmware to anything newer than whats in the old modified firmware section until GB can sort their shit out.

I don't like the M.2 placement either but thats one thing you can't hold against GB a lot of manufacturers have boards with the M.2 slot in the same place, your MSI Titanium does, for example. Most boards don't come with WiFi either and the ones that do are over £200 so again not something I'd hold against GB, LED CPU temp readout I've always found pointless who seriously pokes their head in a PC to check CPU temp rather than just check some software or use a temp gun? :p PCI slots don't belong on enthusiast boards, or any boards for that matter, anymore. If you still have a PCI device its well overdue upgrading, not sure I know why you are moaning about U.2 slots either tech moves forward no need to bemoan an extra feature such as a U.2 even if you don't think you'll use it at least its there for more futureproofing. One thing I can say I've never had issues with is the audio which might be due to me using rubber washers, but if that is the reason it just shows GB are not grounding and isolating circuitry properly.

End of the day the Gaming5 is not a good board, at all. I have to suffer with it more than anyone for sake of developing modified firmware and I'd dare say I've made more progress than GB have as my modded firmware does actually fix some problems, attempts to fix some others, and exposes a lot of options the firmware should already have accessible to the user as well as makes attempts at improving compatibility without breaking anything. Based on reports I have for that latter point would suggest I succeeded at that as well. Anyway as I have said before there is a lot that can be fixed if GB actually get their head down and start working on and testing fixes because the only thing GB are giving the impression of with so many bugs being present for a whole year is that they are incompetent and arrogant believing they can do no wrong. They will sink fast in the MB arena if they keep that mentality and I will be the first to turn around and say to GB "I told you so. If only you had listened to me and all of the user complaints. I tried warning you.".

That pci slot, its nice to have fella, i have old soundcards/gpus/capture cards etc that run perfect on windows 10, and U.2 slots? its dead jim, same as intels thunderbolt. That led cpu/chipset temp readout on the taichi is bloody handy i tell ya, ket im not having a dig at you at all fella, youre doing a wonderful job of reviving this turd of a board, i just hope more people around the globe are reading all this what we are all posting here. as for the audio theres nothing wrong with the I/O shield outputs, its the front panel outputs that are faulty, the board is supposed to be grounded. what really pisses me off is how much money this company has made out of these boards and intels equivalents. theres not one single thing, nothing i can find to say thats good about the gaming5 or k7.

Zitat von AndreDVJ im Beitrag #492

---

I flashed back F7a (with AGESA: SummitPI-AM4 1.0.0.6) on my K7 board

- HPET OFF works fine
- Fast Boot works as intended, with HiberBoot enabled.
- UEFI GOP works correctly (not falling back and having UI elements streched while Windows is booting)

Windows 10 options aren't exposed from F10 and onwards. I believe "Other OS" gets defaulted and Fast Boot cannot work properly.

About LEDs, I have three RGB fans from Coolermaster (Air Balance) and colors from onboard LEDs and fans are mostly in sync. I don't have much to complain regarding this one.

About voltages, SoC voltage was always overvolting if left on Auto. Gigabyte says it's normal, but it's actually pretty abusive, and 1.1v should be more than sufficient for 3.9Ghz CPU and 3200Mhz DDR4 CL16.

Looks like AMD published a new AGESA, so let's hope with a grain of salt that Gigabyte will attempt to fix these obvious issues.

---

Guys,

Any idea on when the K3 bios will be posted again. Just an old timer looking to re-flash while building the PC.

MAK

My GF's getting tired of me sighing, lol.

I'm still on F21 so I figured I'd try 2t commandrate. Odd timings don't work and are upped to the next even value.

Went back to the settings before and the different monitoring software would pick and choose which DIMMs to read. HWiNFO would find only DIMM2 and 3, CPUID typically 0-2 and never the 4th (i.e. "3"). Thaiphoon Burner would take ages to load, even longer to read SPD and would basically produce zeroes, thus reading nothing from the SPD chip.


Reset the BIOS and started testing voltages while OCing.



Everything Auto:

VCore maxed out at 1.380V with short spikes to 1.416V and went as low as 0.400V
SOC Voltage was anywhere from 0.8-1.104V.


Everything Auto at 40x multiplier:
The same as above

Everything Auto at 40.25x multiplier:
VCore spikes to 1.446V, floats between 1.390-1.416V
SOC Voltage stuck at 1.248V

Everything Auto, SOC Voltage 1.10625V and 40,25x:
VCore spikes around 1.355-1.380V, depending on workload, and switches between 0,400-0,887-1.325-1,369V (pr. core)
SOC Voltage at 1.100-1.104V

Now I'm back at my stable OC and everything is running perfectly stable. All DIMMs are read correctly and all else is well. My next restart will be to lower VCore a tad, 1.3125V seems to work fine.


A part of me is considering either going for the X470 motherboards once they arrive unless the MSI X370 Pro Carbon gets even cheaper.

Zitat von POE_UK im Beitrag #498

---

That pci slot, its nice to have fella, i have old soundcards/gpus/capture cards etc that run perfect on windows 10, and U.2 slots? its dead jim, same as intels thunderbolt. That led cpu/chipset temp readout on the taichi is bloody handy i tell ya, ket im not having a dig at you at all fella, youre doing a wonderful job of reviving this turd of a board, i just hope more people around the globe are reading all this what we are all posting here. as for the audio theres nothing wrong with the I/O shield outputs, its the front panel outputs that are faulty, the board is supposed to be grounded. what really pisses me off is how much money this company has made out of these boards and intels equivalents. theres not one single thing, nothing i can find to say thats good about the gaming5 or k7.

---

F21 (still) on my K7.

LLC does make a difference.


VCore set to 1.31875V, 40.25x multi, Prime95 load:

Extreme: 1.368-1.380V, a few dips to 1.356V. Settles at 1.368V.
Turbo: 1.356-1.368V, a few spikes to 1.380V, a few dips to 1.344V, settles between 1.356-1.368V
High: Unstable, drops all the way down to 1.320V, tris to live with 1.332V and locks up. A few spikes to 1.344V but to no avail.


VCore dropped to 1.3125V, same multi and load:

Extreme: 1.356-1.368V with frequent spikes to 1.380V, still settles at 1.368V
Turbo: 1.332-1.356V with occasional spikes to 1.368V. Settles at 1.344V


As a whole, I've shaved 3-4 degrees off the CPU die-temperature and the VRM has dropped from 72-75 degrees to 67-70.

SOC stays between 1.104-1.116V


Still, it's weird behaviour. Basically I'm using LLC to "overvolt" when compared to the VCore I'm setting up. Keeping a stable voltage seems unlikely but I'll keep messing with it. I'm prepared to buy a new motherboard and even CPU, should both call it quits, so I'm just punching in numbers for the hell of it, now.


Edit/addition:

At least I can admit my mistakes, lol!

I've been looking at what the VRM's send to the CPU, so screw my readings. Knowing this I raised the voltage further did let me OC to a stable 41xxMhz with no other issues than pushing higher temps.

LLC @ Extreme mereley reduces Vdroop to a minimum. VCore in BIOS is set at 1.3125V, VRM output registers as 1.320V and registers as 1.306 at the CPU. The latter drops to 1.294V under load.


Whether this is the board's fault or not, I'm unsure of.

At least LLC works on the K7, definitely doesn't on the Gaming 5 I have so GB seem to have broken something there. If anyone is looking for a good cheap replacement for their GB garbage the Biostar GT7 really is very good, its a bit lacking in some areas but I'm also working on a modified firmware which will expose some handy options and fix easily one of the biggest flaws the board has - the crappy 70c fan limit before all of the fans kick up to 100%. In fact I've already fixed that problem I have increased the maximum limit to 85c for proper fan control without the board just completely taking over whenever that old limit was hit. Zen doesn't have an overly high recommended operating temp but up to 75-80c shouldn't hurt it even long term.

LLC defintely works. I have no base of comparison so I can't tell if a loss of 0,05-0,06V from the VRM reading to the CPU is normal. For reasons unknown, I now get a VRM-reading of 1.356V but CPU stays around 1.306 with unchanged VCore and LLC @ Extreme. Erratic behaviour to say the least, eh?

I've not experienced loss of fan control apart from the secondary CPU fan which upon restarting and during *some* cold-boots kicks up to 100%. This has been across all BIOS, so far.

Zitat von hansen_DK im Beitrag #505

---

LLC defintely works. I have no base of comparison so I can't tell if a loss of 0,05-0,06V from the VRM reading to the CPU is normal. For reasons unknown, I now get a VRM-reading of 1.356V but CPU stays around 1.306 with unchanged VCore and LLC @ Extreme. Erratic behaviour to say the least, eh?

I've not experienced loss of fan control apart from the secondary CPU fan which upon restarting and during *some* cold-boots kicks up to 100%. This has been across all BIOS, so far.

---

Hey ket do you think you could change the boot logo on my taichi?

As long as the 0.060V isn't part of a stability issue or something worse ... still not good enough, though. This is supposed to be a top tier card.


I've been playing around with the RGB-settings. My issue with the (lack of) synchronisation with Corsair's RGB RAM seems to be as simple as timing related. Choosing solid colours, the colours sync up. If I choose any sort of lighting effect, be it flash, pulse or colour cycle the RAM un-sync within a few seconds. The RAM won't flash, they instead start a pulse sequence. Apart from red, every colour is out of sync, where orange sticks out the most.

Basically, GB has designed and built a top tier motherboard with a quite capable VRM design, good looks and a nice feature set with lots of LEDs and a custom element. The problem is that most of the fun stuff doesn't work very well, let alone as advertised, and in general the firmware hardly improves over time. Add to that the way the voltages behave which makes me question whether there may be a hardware issue of sorts, if not many.

I'm starting to sound like POE_UK ... :)

I'll jump on X470 if something good launches. At the moment the MSI X370 Gaming M7 is on my short list, should my AX self-destruct.

ket, of the newer Raven Ridge/Pinnacle Ridge ready BIOSes (starting with F10, I think) have you looked at F22b yet?

The consensus on the Gigabyte forum seems to be that it's the least buggy and most stable. (For example, the HPET bug isn't there and supposedly P-States still work.)


For some reason Gigabyte removed it from all the motherboard product pages. Maybe because it was a beta version of F22?

Regardless, pretty much everyone is saying it's better than the final F22 version. And it can still be downloaded from here: http://download.gigabyte.cn/FileList/BIOS/?C=M;O=D


I'm just thinking that if you base your custom BIOSes on older versions, you'll be limiting yourself to Ryzen 1000 series users only. Owners of the Raven Ridge APUs and upcoming 2000 series won't be able to use your custom BIOSes on Gigabyte B350/X370 boards at all. Which would be a shame, as they'd be missing out on your great work.

All that being said: there are, of course, inevitably going to be more BIOS releases from Gigabyte in the very near future. What with the B450/X470 boards launching, and patches for the flaws discovered by CTS-Labs.

So I guess it's best to wait a few more weeks and see how things go? Maybe with the release of B450/X470, Gigabyte will overhaul their AM4 platform BIOS code, and it will filter back down to the older B350/X370 boards?

Zitat von redrain85 im Beitrag #509

---

ket, of the newer Raven Ridge/Pinnacle Ridge ready BIOSes (starting with F10, I think) have you looked at F22b yet?

The consensus on the Gigabyte forum seems to be that it's the least buggy and most stable. (For example, the HPET bug isn't there and supposedly P-States still work.)


For some reason Gigabyte removed it from all the motherboard product pages. Maybe because it was a beta version of F22?

Regardless, pretty much everyone is saying it's better than the final F22 version. And it can still be downloaded from here: http://download.gigabyte.cn/FileList/BIOS/?C=M;O=D


I'm just thinking that if you base your custom BIOSes on older versions, you'll be limiting yourself to Ryzen 1000 series users only. Owners of the Raven Ridge APUs and upcoming 2000 series won't be able to use your custom BIOSes on Gigabyte B350/X370 boards at all. Which would be a shame, as they'd be missing out on your great work.

All that being said: there are, of course, inevitably going to be more BIOS releases from Gigabyte in the very near future. What with the B450/X470 boards launching, and patches for the flaws discovered by CTS-Labs.

So I guess it's best to wait a few more weeks and see how things go? Maybe with the release of B450/X470, Gigabyte will overhaul their AM4 platform BIOS code, and it will filter back down to the older B350/X370 boards?

---