Latest Gigabyte X370 K7 Motherboard BIOS Broken Dynamic vCore, up to 1.7v

[Raevenlord]

Update: It seems that the vCore voltage can go up to 1.7v, which has resulted in at least one claim of a fried Ryzen CPU on Gigabyte's forums. Multiple users are reporting this issue, and apparently the problem isn't limited to Gigabyte's K7 motherboard: users on the Gaming K5 motherboard are also reporting similar issues with the latest BIOS for their respective motherboard.

A warning to users of Gigabyte's X370 K7 motherboard: the most recent F5 BIOS version, which was posted as a stable release on the company's BIOS support page, has been originating reports from users as having increased the dynamic voltage applied towards stratospheric values (from a "healthy CPU vCore baseline.) The problem appears to be related to the usage of Gigabyte's Dynamic vCore functionality, where users that were seeing vCore values of around 1.2v started seeing those dynamic values, as set by the motherboard, being set to a crispy 1.55v instead, at the same clocks as before the BIOS update. If you have such a motherboard, and have recently updated your BIOS to revision F5 or planned on doing so, please do yourself a favor and set vCore manually to your value of choice, compensating with LLC (Load Line Calibration) so that your CPU isn't shocked to death with additional vCore.





There are some reports of Ryzen CPUs going the way of fries due to this issue, although at the time of writing, it wasn't possible to confirm this through multiple sources. Should any more information turn up on this issue, expect this space to be updated. Other than that, it seems that this is a good BIOS release for the K7 motherboard, shoring up some weaknesses that still resided on Gigabyte's BIOS. Apparently, VRM temperatures are down, and issues of soft bricks on PC shutdown cycles have been corrected.



View at TechPowerUp Main Site

 

[Daven]

I happened to be on the website at just the right moment and noticed that I can see the author typing the 'Coming Up' headline in real-time. While I was watching I noticed the headline first read 'Fries CPUs' but then the author quickly erased the text and wrote 'up to 1.55v' instead.

I thought that was funny.

 

[Raevenlord]

I happened to be on the website at just the right moment and noticed that I can see the author typing the 'Coming Up' headline in real-time. While I was watching I noticed the headline first read 'Fries CPUs' but then the author quickly erased the text and wrote 'up to 1.55v' instead.

I thought that was funny.

It is it's the real time we have.

The fries CPUs stood there for quite a bit of time, actually; I was trying to confirm that information through multiple sources. For now, I haven't been able to find other users reporting the same as having happened, so one isolated case does not a pattern make =) however, the vCore issue is real and was reported by multiple users, so, here's the heads-up.

 

[Daven]

It is it's the real time we have.

The fries CPUs stood there for quite a bit of time, actually; I was trying to confirm that information through multiple sources. For now, I haven't been able to find other users reporting the same as having happened, so one isolated case does not a pattern make =) however, the vCore issue is real and was reported by multiple users, so, here's the heads-up.

Sorry about the not quite so true recount. I couldn't remember if I saw the first part typed and then erased right afterwards or just erased after some time. Thanks for clearing that up.

 

[psyko12]

Wow! 1st time I got my name mentioned in a contribution post @Raevenlord Thanks!

Aside from the offset voltage issue. So far golden here. System seems more "reliable" hahaha

 

[R0H1T]

Sabotage*

*sells tin foil

 

[R-T-B]

Looks like Gigabyte needs me to mess with their bios again at the rate they are breaking things... too bad my hands are full.

 

[Asuredawn]

I haven't seen any reports from K5 users, and my own board doesn't exhibit this behavior. Are you not confusing the gaming 5 with the gaming k5?

That said, I have noticed that bclk about 1mhz higher than I set it to, which isn't very comforting...

 

[Riffraff]

I have been using bios ver. F5C. For some time and the cpu vid has always been 1.55v when xfr and turbo is active. It only spikes up there now and then.

If the multiplier is set to any value over stock the cpu vid stays at 1.55v so its important to set voltage manually when o.c.

I have now moved to the f5 release and up to now very happy seems i can now get 3.95ghz on the same voltage that i reached 3.9.

 

[Indurain]

In my testing it appears that setting it to Normal is what guarantees you will be at 1.55V +-OFFSET. Auto will work most of the time, details later. So on Normal you can go down to a 1.40V actual and over 1.7V depending on the offset. An offset of 0V results in 1.55V. Also in my testing if you change back from Normal to a fixed voltage (one you type in) and do not set Dynamic Vcore back to Auto beforehand the actual Vcore is higher than reported in BIOS.

Not a single word from Gigabyte nor have they removed the F5 BIOS from their website as of 1900 UTC.

And yes VID reports 1.55V in a number of circumstances but in this particular case the other sensors also report 1.55V+OFFSET. This is the K7 other boards may react differently and people that are not reporting issues may not be using Normal with an OFFSET. if they use Auto or type in a voltage the board seems to react as it always has.

 

[Riffraff]

In my testing it appears that setting it to Normal is what guarantees you will be at 1.55V +-OFFSET. Auto will work most of the time, details later. So on Normal you can go down to a 1.40V actual and over 1.7V depending on the offset. An offset of 0V results in 1.55V. Also in my testing if you change back from Normal to a fixed voltage (one you type in) and do not set Dynamic Vcore back to Auto beforehand the actual Vcore is higher than reported in BIOS.

Not a single word from Gigabyte nor have they removed the F5 BIOS from their website as of 1900 UTC.

I would like to see a iittle more negative offset available, as you say 1.4 is still a little high

 

[Indurain]

@Riffraff, the maximum negative offset your can set is 0.150V so it stands to reason that Vcore minimum in that case is 1.40V in actuality most of the Windows hardware monitoring programs will report closer to 1.42V (HWInfo, Aida64, CPU-Z, etc). Even BIOS will report higher than 1.4 set at -0.150V if you go back into BIOS after saving and rebooting.

I may have confused the K5 and Gaming 5 when I posted this to overclock.net. The posts are in the Gigabyte AM4 BIOS thread on their forum.

 

[toilet pepper]

I also made a post about it. It also affects x370 gaming 5. (Tested by me) And other AM4 boards as well. Thia ia not isolated to the K7.

 

[R-T-B]

I haven't seen any reports from K5 users, and my own board doesn't exhibit this behavior. Are you not confusing the gaming 5 with the gaming k5?

That said, I have noticed that bclk about 1mhz higher than I set it to, which isn't very comforting...

Good I use a static voltage then. I'm wary not to try a dynamic voltage now.

 

[Dave65]

Gaming 5 here and my board is reporting 1.55 also.

 

[Indurain]

@Dave65 Make sure you look at something other than Ryzen Master, it will show 1.55V even if you specify Vcore directly. If you use HWInfo and look at Core VID it may show 1.55V but down further in the section showing CPU [#0] CPU Core Voltage (SVI2 TFN) shows the actual Vcore. In Auto and when a Vcore is specified that number should be very close if not exactly what you requested. If you use Normal even that sensor will report 1.55+Dynamic Vcore. The section below that for the ITE Sensor has another Vcore measurement and it should be close to the SVI2 TFN number. Again if you choose Normal and a Dynamic Vcore Offset it will jump to 1.55V+Dynamic Vcore.

@R-T-B You should be good with F5, one thing to be careful of, If you want to test Dynamic Vcore and set an offset, when you go back to Auto or a specific voltage make sure you set the Offset back to Auto first or you could get unexpected results. I did not write down exactly what I got but I do recall it has much higher than the number I typed into CPU Vcore.

 

[Dave65]

I switched back to the F6 bios from F7 and it solved my problem on the gaming 5.

 

[Dave65]

@Dave65 Make sure you look at something other than Ryzen Master, it will show 1.55V even if you specify Vcore directly. If you use HWInfo and look at Core VID it may show 1.55V but down further in the section showing CPU [#0] CPU Core Voltage (SVI2 TFN) shows the actual Vcore. In Auto and when a Vcore is specified that number should be very close if not exactly what you requested. If you use Normal even that sensor will report 1.55+Dynamic Vcore. The section below that for the ITE Sensor has another Vcore measurement and it should be close to the SVI2 TFN number. Again if you choose Normal and a Dynamic Vcore Offset it will jump to 1.55V+Dynamic Vcore.

@R-T-B You should be good with F5, one thing to be careful of, If you want to test Dynamic Vcore and set an offset, when you go back to Auto or a specific voltage make sure you set the Offset back to Auto first or you could get unexpected results. I did not write down exactly what I got but I do recall it has much higher than the number I typed into CPU Vcore.

With HWinfo it shows 1.131 on them all...SVI2 TFN shows my exact input for my vcore, the ITE shows very close what my inputs for vcore is..

 

[Indurain]

Another report on overclock.net about a possibly damaged 1700 on a Gaming 5 with their new BIOS. Operator was using Dynamic Vcore and when he booted he saw 1.77 then 1.78V before he shut it down.

Still no word from Gigabyte?

No word still, but the Gaming 5 F7 links are all dead, and the F5 for the Gaming K7 has been completely removed.

 

[psyko12]

They've sent out a new bios!!!
This is one for the k7
http://www.gigabyte.eu/Motherboard/GA-AX370-Gaming-K7-rev-10#support-dl

1. Fix P2-state hanged issue while adjusting CPU Vcore of Ryzen 3
2. Improve DDR compatibility
3. Fix CPU Vcore caused high voltage issue while adjusting the Dynamic Vcore option

 

[Indurain]

Link currently doesn't work

 

[newtekie1]

It's Gigabyte, so I'd expect something like this. I can assure you, they aren't going to be of any help to the people with fried chips either.

 

[Asuredawn]

It's Gigabyte, so I'd expect something like this. I can assure you, they aren't going to be of any help to the people with fried chips either.

Seems pretty disingenuous, as it was their fault and released as stable, but it certainly wouldn't surprise me. Most motherboard manufacturers have a policy of upgrade at your own risk, after all. :/

 

[Riffraff]

Has anybody managed to get the f6 bios yet?

 

[Hoaca388]

I was meet this issue yesterday affer updated F5 bios for my K7 mainboard. The Vcore voltage was up to more than 1,7 vol . S. H. I. T