Recent Gigabyte x370 Bios Killing CPU's

[Neokolzia]

Big PSA for users of these boards to avoid this firmware update until a fix is announced, so there's no chance of becoming a victim to it.

Its reported that basically inside the bios menu voltages on the vcore are fluctuating between 1.5-1.7 which is very very high, where as usual voltage is closer to 1.2 or 1.35-1.45 when OC'd, and the max you can even set in the bios is 1.55

 

F8 (Gaming 5) & F6 (x370 K7) bios has also been uploaded by Gigabyte today allegedly fixing the Vcore issue

F7 (Gaming 5),F5 (x370 K7) are no longer available to download and should be avoided

 

Quote

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(Or as high as 1.7v) instead, at the same clocks as before the BIOS update.

 

Source's: 

http://wccftech.com/amd-ryzen-cpu-gigabyte-x370-damage-burning-bios-update/

https://www.techpowerup.com/236659/latest-gigabyte-x370-k7-motherboard-bios-broken-dynamic-vcore-up-to-1-7v

[Matu20]

Do you know how many were actually affected?

[Neokolzia]

4 minutes ago, Matu20 said:

Do you know how many were actually affected?

The article said there are 2 cases reported of dead chips, I know one on overclock.net reported that he believed his chip was damaged as cpu-z was showing 1.78vcore on desktop apparently

 

The tech powerup article I posted on the OP, has a few of I'm sure more to come examples of this.  

[Jito463]

Well, I was just about to install the F5 BIOS (running F4 beta at the moment) on my Gaming K7, now I'm glad I didn't.  Thanks for posting this.

[Neokolzia]

1 minute ago, Jito463 said:

Well, I was just about to install the F5 BIOS (running F4 beta at the moment) on my Gaming K7, now I'm glad I didn't.  Thanks for posting this.

Ya I'm on F4 (Also a K7) without much complaint and gonna wait a bit before touching F6 make sure its all guuchi even though they said its fixed.

There's a very active thread on this motherboard on overclock.net if you want to keep tabs on bio's information.

 

http://www.overclock.net/t/1625822/gigabyte-ga-ax370-gaming-k7-discussion/2530

[Doobeedoo]

Great it got fixed quick. 

[MoonlightSylv]

Did they not validate it before releasing it?

[Jito463]

1 minute ago, ShadowTechXTS said:

Did they not validate it before releasing it?

If so, it obviously wasn't validated well enough.

[NumLock21]

So it burns oc and stock chips?

[RagnarokDel]

regardless of if the chip is dead or not currently, any chip that ran this, has assuredly lost a lot of longevity.

[Neokolzia]

4 minutes ago, NumLock21 said:

So it burns oc and stock chips?

i'm not 100% sure, its related to the offset voltage in the bios, but its pumping 1.7v into chips so, unexpecting users might get completely wrecked by this and have their chip/motherboard damaged

 

[W-L]

@Neokolzia Plese do remember to add a quote in the OP from the sources related to the article, as of currently it has been moved to the CPUs, Motherboards, and Memory section. 

 

 

[Zodiark1593]

3 hours ago, RagnarokDel said:

regardless of if the chip is dead or not currently, any chip that ran this, has assuredly lost a lot of longevity.

If one's CPU has been damaged by this update, is there any recourse as far as CPU replacement (and potentially lost time for workstation users) go?

[Neokolzia]

59 minutes ago, W-L said:

@Neokolzia Plese do remember to add a quote in the OP from the sources related to the article, as of currently it has been moved to the CPUs, Motherboards, and Memory section. 

 

 

apologizes its been corrected, I saw some other large news threads that didn't have this and followed suite, since I essentially regurgitated in more direct words the pretty simple topic.  

[RagnarokDel]

20 minutes ago, Zodiark1593 said:

If one's CPU has been damaged by this update, is there any recourse as far as CPU replacement (and potentially lost time for workstation users) go?

I'm sure it'd be in Gigabyte's best interest to fork the cost of a replacement chip. Worst case scenario, you can always take them to small claims and win by default.