Fiery

Can you please copy-paste the full content of the Motherboard / BIOS page of AIDA64 into this topic, using both AIDA64 v2.70 stable and v2.80 stable, so we could compare the output? Thanks, Fiery

Please note that AIDA64 requires the driver of the Asetek/Antec water cooling system to be installed on the system. So try to reinstall the ChillControl software (that also installs the drivers), but not have it running while you use AIDA64. Regards, Fiery

I suppose the only reliable temperature measurement would be getting an external thermal diode that you could attach to the processor die.

Please note that AMD Trinity processors implement a flawed temperature diode that is unable to provide correct temperature readings, especially when the CPU is at idle. HWMonitor apparently implements a trick to correct the invalid temperature readings, but it's definitely not right even that way, since for example on our test system of Gigabyte F2A85X-UP4 + A10-5800K we get over 110 Celsius values using HWMonitor v1.21 while running the AIDA64 System Stability Test with FPU+GPU subtests enabled. The processor would simply fry at such exceedingly high temperature, so the reading must definitely be incorrect. BTW, AIDA64 also implements a manual correction facility, so if you believe you know a formula to correct the core temperature readings on your system, to make them more realistic, you can try applying it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.

Apparently Steam does not accept submittals right now, but they only accept community greenlighting: http://steamcommunity.com/greenlight We'll try to submit AIDA64 for greenlighting, as soon as we ensure that there would be definitive community backing up our submittal.

Not at all. A lot of systems have such corrupt ACPI tables, and those tables never cause issues fortunately.

Does one of those missing fans appear in AIDA64 after your start ASRock F-Stream application? Maybe the mux logic requires some sort of initialization to let any of the fans be monitored.

We'll work on it

Currently such type of disk performance measurement is not supported by AIDA64. We may implement it sometime later this year.

Thank you. Since the sensor chip's fan register corresponding to the muxed CPU_FAN1 and CPU_FAN2 headers indicates an invalid RPM reading, I suppose your motherboard by default would monitor CPU_FAN2 instead of CPU_FAN1. Try to connect your fan to CPU_FAN2, and check if it appears in AIDA64 that way. As for Antec water cooling systems, unfortunately the way ChillControl software is designed, it's not possible to monitor the water cooling system from two or more different software In other words, the access to the water cooling device is exclusive: either ChillControl accesses it, or AIDA64, but they cannot access it simultaneously.

Then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Please also indicate in your post which fans are connected and spinning. Thanks, Fiery

Certain video adapters use power management tricks that lower PCI-E speeds when the card is at idle. Try to run a 3D application, and look at the bus speeds while that is running. Alternatively, you can try using the GPU subtest of the AIDA64 System Stability Test (AIDA64 / main menu / Tools / System Stability Test). Regards, Fiery

Thank you, we'll check those links and the IDK out Regards, Fiery

We've updated the GPU utilization measurement code of AIDA64 to better suit Radeon HD 7xxx cards. Make sure to upgrade to the latest stable version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/a64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Thank you. We've updated the fan measurement code of AIDA64 to better suit the newer BIOS releases of Maximus V Extreme. Make sure to upgrade to the latest stable version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/a64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

It's definitely not a virus. BIOSes tend to use incorrect table signatures or completely corrupted tables to hide specific ACPI tables when you select such behavior in the BIOS Setup. For example, if you disable the HPET table -- although in your case HPET is enabled Of course it could also be due to a BIOS bug, but such bugs fortunately doesn't cause any actual issues. Regards, Fiery

As I've explained above, you can monitor either CPU_FAN1 or CPU_FAN2 with AIDA64, but not both I'm afraid.

Make sure to upgrade to the latest stable version (v2.80.2300) of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/a64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it makes a difference. Thanks, Fiery

This is an English language forum. Please post your questions in English. Regards, Fiery

On your motherboard CPU Fan1 and CPU Fan2 headers are muxed together, and connected to a single sensor chip register. Due to the way the mux is implemented (which is not very clever) AIDA64 cannot properly handle the mux. Hence you can only monitor one of those fan headers, but not both. If you connect your fan to another of the rest of the 4 fan headers, you won't have such issues. Regards, Fiery

In a few days Make sure to subscribe to our newsletter, so you get a notification on the new releases: http://www.aida64.com/news (in the right column)

Thank you. There's definitely a special chip on your video card that may be responsible for providing the correct voltage readings. We'll try to find out what that chip might be, and implement support for it if possible.

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Also, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Thanks, Fiery

If it crashes the Device Manager, that sounds like a slight issue in Marvell drivers to me...

We already did everything we could on our end...