Gigabyte Z97MX-Gaming 5 sensor issues.

[d6d1]

Hello!

 

I just upgraded my system to this board, ran AIDA64 on it... and saw a couple of quirks:

 

A fan speed info is wrong...
SYS_FAN1 shows up as "CPU OPT" when I have CPU_OPT unused.
I would assume plugging a fan into CPU_OPT would make AIDA64 show it up under "Chassis #1"... but I haven't tested it.

CPU_FAN and SYS_FAN2 show the proper values, didn't test SYS_FAN3.

 

Vcore value is wrong. It says 0.060-0.384v at idle, CPU-Z reports it as 0.929-0.953v.
However the value is correct (same as CPU-Z) if I check it on the "Overclock" tab. (I guess this is VID info)

 

Memory temperature is missing (This shows up in HWINFO) Found the setting in Preferences... silly me.

 

CPU temp is 23 degrees, when CPU package shows 31 and Cores are at 30/31 (maybe I only need to manually compensate?)

 

Also, I see on HWINFO two temperature readings that are unidentified... is possible to add those, if whatever they're measuring is identified?

[Fiery]

1) We'll fix the fan labels in the next AIDA64 beta update.

2) AIDA64 reports the actual Vcore, while CPU-Z reports the CPU VID.

3) CPU temperature and CPU Package temperature may or may not match. It's due to the difference in measurement methodology, you don't have to adjust any of those values.

4) Unidentified temperature readings can only be added if your motherboard also shows those values in the UEFI Setup or Gigabyte's own monitoring software. Otherwise, those values could well be just bogus readings, invalid values, or unconnected sensor chip wires.

Regards,

Fiery

[d6d1]

Hi Fiery

Good to read that fans will get fixed for next release, just what I wanted to read.

 

And yeah, I was new to Haswell so I didn't know the "odd" Vcore values of this processors when idling.

 

Also, now that I've thought about it more, I understand that CPU is the temperature at the socket whereas CPU package is temperature on-die.
My previous build (i3 560) only had "CPU" so this dual reading is new to me too.

 

In regards to the unidentified readings, there's just one. Temp5 is totally bogus/unconnected sensor, since it shows 0 and 159 degrees, without any sort of logic, so it's quite easy to discard it.

However Temp3 & 4 do show "proper" temperatures... actually now that I'm checking, temp3 is "CPU temp" (same values as in AIDA64).
The only "missing" temperature is temp4, which is at 29º at idle now but goes up a little when CPU is at 100% (at 31 after a 3min 100% load).
I wonder if this could be PWM's temperature...

Installed Gigabyte's EasyTune to see the HW temps but all I get is overclocking options. UEFI doesn't show any special temperatures besides those that you already show in AIDA64... so it's just speculation for now.
Maybe I'll remove the heatsink from the VRMs and see if the sensor temp rises heh... would this be a definite proof for you?

Regards

Steven

[Fiery]

In case the missing temperature was something meaningful and important when overclocking or tuning your system, Gigabyte would show it as a PWM or VRM temperature in the UEFI Setup and in their software as well. To me it doesn't make much sense to go to lengths in implementing a hardware temperature sensing logic, to assign valuable space on the motherboard PCB for connecting an external temperature sensor to the sensor chip, and then not showing he measured value on the user interface.

[d6d1]

Hello again.
It's me, coming to annoy you for more sensor readings again!

I've run HWiNFO v5.06 and noticed it shows Voltage Regulator temperatures, Currents and Powers. Also VR Vout and VR VIn but that's "a detail".

Would be possible to add this info to AIDA64?
Sensor is IRF IR3564B...

In regards to your last reply, I'd say VR temperatures are important when overclocking/tuning... :wink:

[Fiery]

Generally speaking, we're not so keen on implementing support for motherboard PWM/VRM chips. Because many of those chips are quite sensitive to frequent polling, so it could well cause a system instability just to read the temperature, current and power values from such chips. We however can add support for such boards on a case by case basis, and we just did that about your motherboard in the latest AIDA64 Extreme beta update available at:

http://www.aida64.com/downloads/latesta64xebeta

Please let me know how it works

[ApcyBut]

Hi just a question,

What do you use to control xbmc on the gigabyte BRIX? It doesnt have a IR Port.

[d6d1]

VRM chip monitoring has been stellar on this board! (lol forgot to reply!)
Now I come with another "detail" about this MB...

DIMM positions are mislabeled!
i.e. now I have memories installed in slot 1 & 2 (according to silkscreening on MB, they're in dual channel), but software reports they're on 2 & 4.
Positioning on this MB is like this:   (CPU)   4 2 3 1
(Yes, I'm still using the exactly same board)

Using Aida64 5.98.4800 at this moment.

PM if you would want me to test each slot individually to get their correct number... (according to MB silkscreen).

[Fiery]

On ‎10‎/‎14‎/‎2018 at 5:25 PM, d6d1 said:

VRM chip monitoring has been stellar on this board! (lol forgot to reply!)
Now I come with another "detail" about this MB...

DIMM positions are mislabeled!
i.e. now I have memories installed in slot 1 & 2 (according to silkscreening on MB, they're in dual channel), but software reports they're on 2 & 4.
Positioning on this MB is like this:   (CPU)   4 2 3 1
(Yes, I'm still using the exactly same board)

Using Aida64 5.98.4800 at this moment.

PM if you would want me to test each slot individually to get their correct number... (according to MB silkscreen).

DIMM slot numbering depends on the actual motherboard.  Many motherboards have them mixed up.  It's only a minor cosmetic issue that doesn't need a fix.