Fiery

Thank you for your feedback

Please send me your old email address and full name in private message, and I'll send you your AIDA64 product key.

Thank you. We've fixed it up in the latest AIDA64 Extreme beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

Thank you. We've fixed it up in the latest AIDA64 Extreme beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

We've implemented sensor support for ASRock H270M Performance, H270M Pro4 and Z270M Pro4 motherboards in the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

The above mentioned AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Thank you. Is it buggy no matter if you're trying to play video or audio files?

Thank you! What was the value of the 2 missing voltages when you created those dumps? What label can you see displayed for those values in the BIOS Setup? Are you sure the values can be monitored, not just configured/adjusted? Can you please submit a photo of the BIOS Setup screen where you can see those 2 voltages monitored?

It's not possible right now. We may enable that in the near future though, along with RTSS OSD label styling.

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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. 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, or attach the results as a TXT file to your post.. Thanks, Fiery

I think the issue may be the limitations of RTSS, which is 256 characters for the whole text to be displayed on the RTSS OSD.

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Please post in English on this forum Meanwhile, we've fixed the issue in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta

Thank you, I'm glad things are going in the right direction

External LCDs with small colour graphical screen and an interface that can be directly handled by AIDA64 with no special API are quite rare actually. AX206 hacked firmware picture frames come to mind, but I'm not sure if you can still buy one on eBay. Then there's Digital Devices USB SideshowTouchDisplay, but that may also be a thing of the past. LCDInfo may still produce USBD480, it's a great display, but it may be too large (it's 4.3") and too expensive for your project: http://www.lcdinfo.com/products/usbd480-wq43.html I think you can still order Odroid-Show: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G139781817221 But it's quite slow: it takes cca. 9 seconds to update the whole screen, so it's 1/9 FPS. The most interesting one is probably the Saitek Pro Flight Instrument Panel: http://www.saitek.com/uk/prod/fip.html But it's again, quite expensive, and requires Saitek's own drivers to work, with their own API. And of course there're large picture frames by Samsung (SPF Series), but several users have issues with them, and they're quite large too: And I guess that's about it.

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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Please use the latest AIDA64 beta version to produce that output. Thanks, Fiery

Thank you. The issue will be fixed in the next AIDA64 beta update due in a few days from now.

I'm afraid I have no idea what could be wrong WIth the same BSPlayer build it works properly for us. Are you using Windows 10 64-bit?

In case the north bridge clock fluctuates, it's normal that sometimes AIDA64 cannot capture the highest value in the power states. Or is it consistently lower on the Cache & Memory Benchmark panel than the value displayed on the Overclock page?

1) Try to use the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta Because we've recently added extended labels for the Computer / Sensor page. Those labels will help you identify which reading comes from which source, much easier than the current way of purely guessing 2) It depends on the actual motherboard model. So there's no universal truth about that. Usually we just recommend that you should be watching the core temperatures, and take the highest value of them as a reference for your processor's "well-being".

We're working together with Corsair, NZXT and Asus right now, in order to improve the synchronization (interlocking) between their respective monitoring software and AIDA64. We're glad if you guys can notice the progress

No, it doesn't work like that. The LCDsysinfo and LCDsysinfo for GOverlay LCD devices do not support direct addressing. In other words, you cannot just render a nice colourful bitmap and send it over to the display via the USB connection. So they cannot be used in AIDA64 directly. What you can do is activate External Applications support in AIDA64, and pass along the measured sensor values to the LCDsysinfo software. And that software (developed by the same folks who're selling those displays on the 'Bay) will handle the LCD, and display the values in a way that you set it up in that software.

That may be due to CPU fan multiplexing that makes it difficult for AIDA64 to measure CPU fan speeds in all cases on ASRock motherboards. Try to connect the fan to the other CPU fan header, it should help

Due to the enermous number of requests we've been receiving since the Ryzen market launch, concerning various confusions about AIDA64 and Ryzen, hereby we post a clarification. AIDA64 is currently not 100% compatible with the recently unveiled AMD Ryzen high-performance x86 processors. It's because AIDA64 still has a few issues that we need to fix. However, in order to fix those issues, we first need to run a series of very long benchmark tests on Ryzen, and that -- among with the bug fixes themselves -- will take several days to complete. As for the bugs and limitations we so far discovered: UPDATE: We have fixed #3, #4, #5 and #7 in the latest AIDA64 v5.90.4200 stable update, which is now 100% compatible with AMD Ryzen processors: https://www.aida64.com/downloads/latesta64xe 1) A number of minor hardware detection issues were already fixed in the latest AIDA64 beta update. 2) The list of Turbo and XFR PStates are invisible on Ryzen, so it's not possible to properly enumerate or track them using a software. When a core of the AMD Ryzen processor goes into idle, the core will report the clockspeed of the P2 power state (e.g. 2200MHz on the Ryzen 7 1800X) and enter into the core-c1 (CC1) or core-c6 (CC6) sleep state. While the VID remains detectable in these states, the states are power gated and the true frequency is not known to the OS or monitoring utilities. As indicated from the “fine-grained Pstate” commentary released at Ryzen Tech Day, the AMD Ryzen’s processor true frequencies in these modes are significantly lower than reported via the “last known” P2 reading. AMD engineering tells us that V/f changes can be executed at 1ms intervals, indicating that the act of monitoring the states with the resolution necessary to accurately capture this behavior would also prevent cores from entering into the ultra low-power CC1 or CC6 states. 3) L1 cache bandwidth and latency scores, as well as memory bandwidth and latency scores are already accurately measured. 4) L2 cache and L3 cache scores indicate a lower performance than the peak performance of Ryzen. The scores AIDA64 measure are actually not incorrect, they just show the average performance of the L2 and L3 caches rather than the peak performance. It will of course be fixed soon. 5) Even though AIDA64 warns about a potential lack of optimization, the CPU and FPU benchmarks should be indicative of the full potential of Ryzen. We may be able to tweak e.g. the FPU Julia benchmark to squeeze even more performance out of Ryzen, but we don't expect the improvement to be substantial. 6) The CPU Hash benchmark provides an exceptionally great score on Ryzen due to the hardware accelerated SHA instructions capability of Ryzen. It's absolutely normal that hardware acceleration boosts CPU computing performance by such a margin. 7) AM4 motherboards are not yet supported by the latest AIDA64 stable build of v5.80.4000. Make sure to use the latest AIDA64 beta build to have accurate sensor measurements on ASRock, Asus, Biostar, Gigabyte, and MSI AM4 motherboards. We will post further updates to this topic as we progress with our bug fixing efforts on our Ryzen test systems.

You cannot achieve that, unless you disable UAC prompt or UAC completely on your workstations.