Fiery

I guess it means your motherboards cannot stand AIDA64 System Stability Test -- which is an extremely demanding task, but all computers (theoretically) should be able to stand it and run it without issues. The test apparently raises a false alarm or some other sort of electrical warning that your BIOS misreports as a PSU surge. I guess if in all other tasks your computer is 100% stable, you just need to avoid running the AIDA64 System Stability Test.

Thank you for the data. I'm afraid that means those voltage rails cannot be monitored, but only their voltage levels can be adjusted. Hence a monitoring software cannot monitor those voltages.

We did implement support for Endpoint Security v12 in AIDA64, but apparently it doesn't work in all cases. We'll check it again on different configurations, in a hope that we can catch the bug and fix it up.

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 right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. 3) Do you have a software that can show those values under Windows? Like MSI Core Center or MSI Control Center? 4) Can you see the mentioned voltage values on the H/W Monitor page of the BIOS Setup? Thanks, Fiery

What kind of anti-virus software do you have installed on your computers? Please indicate software name and full version number. Thanks, Fiery

Please note that in the BIOS Setup your processor cannot use its power saving techniques (like C1E and SpeedStep), hence it's quite normal that both motherboard and CPU temperature are higher in the BIOS Setup than while running a monitoring software under Windows. You can try stressing your system to see how they move under heavy load. Go to AIDA64 / main menu / Tools / System Stability Test. Only have the FPU subtest enabled, then press the Start button. Watch how motherboard and CPU temperature changes, while running the test. CPU temperature should rise more than motherboard temperature, and it should take several minutes to see a considerable change in motherboard temperature. If the measured CPU and motherboard temperature act weird, please let me know. You can also try comparing AIDA64 sensor readings against MSI's own monitoring software called Control Center II: http://www.msi.com/service/download/utility-15496.html

You can find the mentioned new & improved AIDA64 beta release at: http://www.aida64.com/downloads/aida64extremebuild2320tjb6lpwyzxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

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...