BIOSTAR B660GTN WRONG VOLTAGE READINGS

[Freestate]

A recent motherboard, all the voltage readings are messed up. Zero acuracy. In other reading apps happens the same, no readings or wrong data.

AMI BIOS.

 

[Martin]

Please attach the HWiNFO Debug File and a screenshot of BIOS health menu showing correct values.
I will try to match the sensor values with BIOS, but Biostar boards are rather uncommon and no one knows the exact sensor layout.

 

[Freestate]

Please attach the HWiNFO Debug File and a screenshot of BIOS health menu showing correct values.
I will try to match the sensor values with BIOS, but Biostar boards are rather uncommon and no one knows the exact sensor layout.

some extra info here https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/pull/690

 

[Martin]

Thank you. I will try to fix this in the next (Beta) build of HWiNFO.

 

[Freestate]

Thank you. I will try to fix this in the next (Beta) build of HWiNFO.

LAST BETA Working, but i can't see info from +3.3v

 

[Martin]

AVCC3

 

[Freestate]

@Martin With the last versions i'm having extremely wrong readings sometimes. Today an alert on 3.3v readings reported 0.0 value, it also happens with 12v a 5v rails with similar strange values.

 

[Martin]

Are you maybe running some other monitoring tool along with HWiNFO?

 

[Freestate]

Are you maybe running some other monitoring tool along with HWiNFO?

I just looked at it and an application bundled with the motherboard with small reading characteristics (12v readings and core-ram clocks) was open. RACING GT EVO is the name of the app.

 

[Martin]

Then try to run HWiNFO without that application as it might be colliding with HWiNFO.

 

[Freestate]

Then try to run HWiNFO without that application as it might be colliding with HWiNFO.

hwinfo was working perfectly after my last message. Today with the last update 8.20-5640 , wrong readings are back. See image:

 

[Freestate]

Are you maybe running some other monitoring tool along with HWiNFO?

Right now nope. Was solved until last versions. I'm stuck on 8.16 version, the later ones had the same issues back.

 

[Martin]

Are only voltages affected?
Would you be able to capture the invalid value in DBG file and then provide it?

 

[Freestate]

Are only voltages affected?
Would you be able to capture the invalid value in DBG file and then provide it?

I also have strange values in one ACPI thermal zone, with previous working version 8.16 i get around 70 degrees in tz.thrm, with last one is 121.1 C!!!, affected ones are 5.5v rail, 3.3v rail ,12v rail, Vcore

dram voltage also DBG FILE HERE ( TOO BIG TO ATTACH UNTIL I GET THE VALUES) https://drive.google.com/file/d/1hmLfA2q19Tc7YA9Z9AI5uFFttwlT-1YV/view?usp=drive_link

 

[Martin]

Hm, that's interesting. Try to disable monitoring of the ACPI sensor (press Del over the sensor heading) and let me know if the problem still happens.

 

[Freestate]

Hm, that's interesting. Try to disable monitoring of the ACPI sensor (press Del over the sensor heading) and let me know if the problem still happens.

mmm done. It appears that with the ACPI thermal zone disabled, the voltages are now consistent. See screenshot.

 

[Freestate]

shit, fucked up again

 

[Martin]

You didn't disable both ACPI sensor values. Best would be todisable the heading.
But anyway, I have an idea what could be causing this and will try to fix this in the next (Beta) build.

 

[Martin]

Please try the new v8.25-5705 Beta and let me know the result. It should work also with the ACPI sensor enabled.

 

[Freestate]

Please try the new v8.25-5705 Beta and let me know the result. It should work also with the ACPI sensor enabled.

It seems solved. After an hour, all the values appear correct, with no zero or strange values. What speed! You're a genius, Martin. Thanks a million.