Fiery

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.

As long as you feature AIDA64 -- as a software running on your computer -- in your video, we have no problem if you use the AIDA64 logo in your video. Regards, Fiery

Thank you, but please also try the latest AIDA64 beta build, that should fix this up: https://www.aida64.com/downloads/latesta64xebeta

Thank you! I've sent you an email about this issue.

AIDA64 has no control over, or insight into the placement of those sensors. You need to use aquasuite to better understand the layout of the thermal sensors. Regards, Fiery

Please create an ISA Sensor Dump and also a Super I/O Dump before and after launching ASRock's A-Tuning Utility. Maybe it reconfigures the Super I/O chip in order to enable sensor readings. You can create those dumps by right-clicking on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump or Super I/O Dump. Copy-paste the full results into this topic, or attach the results as TXT files to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

Is the video card fan spinning when you try to add it?

Thank you for your feedback

Thank you. That's rather weird then. Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Since they both will be displayed on the Sensor page, I don't think we need to replace anything Whichever you don't like, just ignore it

What version of BSPlayer are you using? BTW, we've checked it with BSPlayer 2.70 Free, and it displays the media title properly in AIDA64.

That look odd. Do you happen to have Low-level PCI bus operations or Low-level SMBus operations or Low-level sensor operations disabled in AIDA64 / main menu / File / Preferences / Stability?

Processes: We of course have the code to enumerate running processes. I just find it quite complicated to configure it that way. E.g. if you want to configure it for a particular game, you need to launch the game, go back to AIDA64, find the process in the list of processes, etc. To do that with all the games and applications you use on your computer is quite a task. Not to mention you need to do that in the future with newly installed games/applications. Let's just say it's not a feature we would see implemented in AIDA64, unless there's a very easy way of detecting the computer state. Duty cycle: Fan duty cycle is quite misleading, since when the duty cycle is configured and then detected at e.g. 30%, it doesn't mean the fan is actually spinning. Focusing on the RPM is a lot better, since that way you can be aware of a stopped or clogged fan. VLC: I'm sorry, but both HTTP and Telnet protocol is way too overkill to be used in the AIDA64 hardware monitoring module. And DBus is not supported by Windows.

Thank you

It seems on your particular motherboard model the Vcore reading has to be multiplied by 1.2. We'll implement that in the next AIDA64 beta update

Thank you for your feedback, I'm glad you like the way we steer the development of AIDA64

Those temperatures are reported by AIDA64 too.

There seems to be no classic sensor chips in your system, or they're connected to an IPMI BMC. Have you tried to check the Computer / IPMI page? Maybe sensor values are reported via IPMI on your system. Regards, Fiery