Fiery

Thank you for the feedback.

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2320tjb6lpwyzxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Supporting UEFI BIOSes can sometimes be tricky. If the UEFI BIOS wouldn't emulate the old system BIOS (at least the F000 segment), AIDA64 won't be able to read BIOS details, including AGESA version. We'll need to come up with a workaround for that, but so far we haven't found a method that would be reliable and stable on all systems. We'll work on it.

AI Suite II may collide with the sensor features of AIDA64, so it would be best if you could completely uninstall it, and try running the AIDA64 System Stability Test again.

Do you have Asus AI Suite installed on either system?

Thank you. Your motherboard features a new Fintek sensor chip that is currently unknown to AIDA64, and so not supported. We've contacted Fintek to help us implement support for this new sensor chip. I'll let you know in this forum topic once we have an update on this issue.

1) 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. 2) Also copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. Thanks, Fiery

AFAIK reading sensor information by AIDA64 should still let Radeon HD 7000 family video adapters use their zero core function. When you leave your computer running, and the display enters into power saving mode (turns off), does AIDA64 still show meaningful GPU temperature readings and other GPU related values? You can verify that by enabling Logging to HTML file in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging. Regards, Fiery

In the reference benchmarks list we indicate the base clock for every processors, without taking CPB or Turbo Boost into consideration. Every reference processors were running with stock (default) configuration, so if they support CPB/Turbo, we leave it enabled to maximize their performance. Regards, Fiery

Thank you. It means AIDA64 shows the right value managed by ADL, but the video adapter might use a different (higher) value when it is overclocked. MSI Afterburner may show the higher value because it uses specific code for MSI video adapters. I'm not sure about Trixx though, I'd need to see an ATI SMBus Dump of such a Sapphire card to tell you more

It's the last item in the System category. Please note that you need to have Fraps running in the background to make the item appear in the list.

Thank you, but we can only add the listed devices if there's publicly available device specifications for them. And WD800JD is already in the HDD database of AIDA64 Regards, Fiery

Have you tried to scroll down to the bottom of the list of values?

AMD Trinity processors are impacted by a hardware issue that results in incorrect (unrealistic) CPU diode temperature readings. AIDA64 shows the values directly read from the processor, while HWMonitor uses a different method. We've tested HWMonitor on our Trinity system, and found that it measured over 110 Celsius (!) temperature at heavy system load. Quite frankly, that's just as incorrect reading as the regular (= very low) readings can be directly read from the processor. Judging by the incorrectness of the CPU diode temperature measured by HWMonitor, I wouldn't be surprised if the power and current values would also be just as off As for fan speeds, several ASRock motherboards use a fan mux logic that cannot be properly handled by AIDA64. It means that in the end the 2 muxed fans cannot both be measured, but only one of them, or none of them (in rare cases). Unfortunately the mux solution ASRock designed is not something we can properly implement in AIDA64, due to its slowness and unreliability On your motherboard CPU Fan1 and CPU Fan2 are muxed together, so it'd be best if you used the rest of the fan headers, to make sure AIDA64 can read the fan RPM from them. However, in the next AIDA64 beta we'll try to implement a trick about the fan mux, to make sure you get more fan RPMs on your current configuration than now. Regards, Fiery

Does GPU-Z measure a different Vcore on AMD GPUs than AIDA64?

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!