Fiery

Thank you for the feedback

Thank you, I've replied you in email.

We'll do that in the next AIDA64 beta Thanks, Fiery

Thank you. We're planning to implement Fraps support sometime in February.

Thank you for the feedback.

Thank you for the feedback

Yes. Let it overwrite any existing files.

We've switched the Vcore and VTT readings on GA-Z77X-UP7 motherboard. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2306gchywsm6nkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Thank you. We believe we've managed to find a way to initalize the fan mux on your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2306gchywsm6nkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Thank you both for the screen shots. We've fixed the BIOS version detection bug that affected ASRock motherboards. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2306gchywsm6nkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Thank you for the detailed bug report. If it's possible, please manually submit a report to us (in AIDA64 / main menu / Report / Submit Report To FinalWire), and in the report submit window make sure to have all 3 debug dump options enabled (checked). Also, it would be best if you could do the report submit while having the SMBus and kernel driver stability options enabled, and so the brightness control interface is "mixed up". We need those, because it may be possible to filter out a single SMBus device address where the brightness control interface is found. If we could see the full SMBus dump, that may give us an idea on where to find the brightness control interface. Alternatively, you can make a new AIDA64 report, a full SMBus Dump (right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full) ), and an ISA Sensor Dump (right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump), compress the files using ZIP, 7Zip or RAR, and attach it to your post in this forum. Before attaching the compressed file, please rename it to attach.txt. Thanks, Fiery

PCH Diode is a temperature diode that is integrated in the motherboard chipset (also known as PCH for modern Intel platforms). Some motherboards have no such diode connected, and some other motherboards may have the diode improperly implemented. In the latter case the temperature readout may be stuck at a fixed value. If that's the case, just ignore the reading

Thank you for the test. It seems this mux is a bit tougher to crack than we anticipated If it's possible, please do one more test for us: 1) Restart your system, and make sure F-Stream is not auto-started when Windows loads up. 2) Start AIDA64, check if both CPU fans are missing from the Sensor page 3) Right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Super I/O Dump. Copy-paste the full results into this topic. 4) Close AIDA64 5) Start F-Stream, check if both CPU fans are properly measured 6) Close F-Stream 7) Start AIDA64, check if any of the CPU fans is properly measured on the Sensor page 8) Repeat step 3 Thanks, Fiery

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

You can try, but I don't think that would help.

Exactly.

AIDA64 LCD module only supports Logitech gaming keyboards. Regards, Fiery

Clearing up fan mapping is another case, and the 4 dump files requested above may also help to clear that up too. But if you could send a screen shot (after the 9-step test) that shows AIDA64 Sensor page and all F-Stream fan RPM readings side-by-side on a single screen shot, that would be very helpful as well.

Thanks for the dump. If you would like us to improve AIDA64 to better support your motherboard, then please run the test for us. Even if you don't upgrade to a newer AIDA64 release now, you may do that in the future, and by then you would have an AIDA64 release that has better support for your current hardware. Of course by then you may have an even newer hardware, but that's another issue :) I've also sent you a private message.

Then please try to do the following: 1) Restart your system, and make sure F-Stream is not auto-started when Windows loads up. 2) Start AIDA64, check if both CPU fans are missing from the Sensor page 3) Right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results into this topic. 4) Right-click on the bottom status bar of AIDA64 main window --> System Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. 5) Close AIDA64 6) Start F-Stream, check if both CPU fans are properly measured 7) Close F-Stream 8) Start AIDA64, check if any of the CPU fans is properly measured on the Sensor page 9) Repeat steps 3 and 4 Based on those dumps, we may be able to figure out how to set the mux into a state that allows you to at least monitor one of the CPU fans. Thanks, 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.