GA-Z270 Gaming K3 rev1.0 vcore gets stuck sometimes

[mhanor]

Hello,

I have this motherboard and an i5-6600K. Has anyone noticed that vcore gets stuck to a value, as indicated by the voltage sensor? I've tried to optimize my overclock, by incrementally increasing the vcore value from the MIT settings, using the smallest steps (0.005V at a time), starting from the default vcore value (1.185V). At some point I noticed that during stress test, the CPU still wasn't stable, then I noticed the vcore sensor readout. I selected the default voltage, rebooted, but the vcore readout was unchanged (see the attached screenshot). I've tried more changes, but only after a PC shutdown the vcore readout returned the expected default value. I've made some more vcore selections, with reboots, it seems that vcore gets stuck to some value, regardless of what's selected.

Has anyone noticed this? I have some more screeshots, but the forum doesn't allow me to attach more files. My motherboard has the latest BIOS (F5). Before upgrading to F5, I wasn't even aware that the previous version (F4) was overvolting the CPU (the sensor readout was >1.3V), which is why my previous overclock was stable (4.4GHz through the CPU upgrade BIOS option) with F4, but was unbootable with F5 and the correct default vcore voltage.


Thanks,

[wh173]

Yes that happens to me with a z170 board with bios F7, and auto voltage also doesnt work, it gets stuck on whatever voltage i had manually set before.

Ive been waiting for the newer bios to get out of BETA in order to try it to see if there are less bugs in it.

[mhanor]

You should try the latest BIOS and open a ticket on esupport.gigabyte.com if it's still buggy, before the board becomes EOL.

[wh173]

You should try the latest BIOS and open a ticket on esupport.gigabyte.com if it's still buggy, before the board becomes EOL.

I asked gigabyte's support if the beta BIOS was reliable and safe and they pretty much said no, and to wait for the stable one.

Problem is, gigabyte is apparently only worried about z270 and the X300's boards for AMD, z170 riddled with bugs, broken and they dont care.

[mhanor]

I suspect that Z270 boards will follow in the footsteps of the previous generation, if users don't flood Gigabyte with reports.

[wh173]

I suspect that Z270 boards will follow in the footsteps of the previous generation, if users don't flood Gigabyte with reports.

Except that is exactly what they want by releasing beta bioses, for consumers to be the beta testers.

[mhanor]

After waiting for week to get a response, this is what I got:

Dear Sir,

Thank you for your message and inquiry. We suggest that you use a dedicated volt-meter for the most precise measurement, or measure the vCore under load. The erroneous  reading might have something to do with the Power Saving features of the CPU/MB or the Vdroop.

Please try to check the settings under load and also check the Load Line Calibration settings. It could be useful in your attempt to stabilize your overclock.

What a bulls*** response.

[Maikill]

Hi, I'm having the same issues, i have the MOBO for 2 days, The motherboard came out of the box with a Vcore of 1.3, I OC to 4.8GHz using 1.290v, i was using only 1.275 did Cinebench and it was ok, but on game blue screen came, so I moved from 1.275 to 1.290, but honestly using HWMonitor and CPU-Z the Voltages are unstable. I hope they get that fixed...

[mhanor]

I've just received a message from Gigabyte, they are working on a fix for this vcore issue.
Btw, I'm not talking about vcore variation. It's normal to have vdrop and it can vary, depending on the LLC setting and how much work is the CPU doing.

I've also realised that the screenshots I uploaded the first time were not showing the actual issue, it's only vdrop.