Fiery

Thank you for the feedback

Results may be different in AS SSD Benchmark, but: 1) AS SSD Benchmark performs high-level (file based) benchmarks, while AIDA64 uses low-level benchmarks (directly reading/writing disk sectors). With AIDA64 performance limitations and configuration issues may look more apparent, more "dramatic". 2) Even in AS SSD Benchmark the values are much lower than what one could expect from an Agility 3 SSD, so there must be some serious issue with either your SSD, or with your system configuration.

I'm afraid we don't know of a better method to read AMD GPU Vcore than ADL...

Thanks for the feedback and your kind words

We've implemented optional labels for RTSS. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2313tdm7b6ykvxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. You can enable the labels in AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications.

We've implemented Fraps support in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2313tdm7b6ykvxzip 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 renamed Temperature #1 reading to VRM1 temperature, and Temperature #2 to VRM2. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2313tdm7b6ykvxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

What we have on our this year's roadmap is a service that would allow you to submit (upload) your sensor readings to our servers, and then let you log into there and monitor your temperatures, voltages and fan speeds in a web browser. After a generic web based solution we may add native iOS and Android apps as well. Regards, Fiery

That access time is way too high. It should be well under 1 (one) milliseconds. I guess there's a background process, driver or service that causes latency issues in the Windows kernel. Not easy to diagnose such issues though...

Thanks for the feedback!

If you have any USB, FireWire or eSATA storage devices (e.g. flash drives, external HDD boxes, card readers) connected, then please try to disconnect them before starting AIDA64. If that helps to launch AIDA64, then please let me know what device caused the troubles. Thanks, Fiery

What version+build of AIDA64 are you running? Thanks, 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