Fiery

You can alter the scale of each graph by that way easier and more dynamically than going to the System Stability Test Preferences and changing the graph minimum/maximum values there.

Yes, we had to remove the trackbars there to support both light and dark mode properly. There's still a hidden trackbar there, just try to move the mouse while you have the left mouse button pressed An Easter Egg of sorts to provide the same functionality than with the visible trackbar before.

A frozen window will not consume any real-time resources. However, hiding and then showing the SensorPanel may cause other issues when the system transitions between screen resolutions for example.

We've checked, and it's best to keep the SensorPanel visible but frozen.

RTSS is a different kinda beast, it's not tied to the SensorPanel module. Alright, it's pause then We'll implement it soon, and will let you know in this topic once you can check it out.

While your system is in full-screen mode, would you prefer to hide the SensorPanel or just pause its updates?

Meanwhile, we've implemented native pinning the SensorPanel to any monitor. Just check the new option called Pin SensorPanel to monitor in AIDA64 / Preferences / Hardware Monitoring / SensorPanel. https://www.aida64.com/downloads/latesta64xebeta

The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

Meanwhile, AIDA64 v7.20 is already out with full Dark Mode support:

We've checked, and unfortunately your motherboard is not capable of monitoring chipset (PCH) temperature.

What version of AIDA64 are you using?

If you cannot reduce update rate, it means AIDA64 doesn't have low-level hardware access due to it having no use of its kernel driver. In most cases it's because of a virtualized environment, lack of administrator privileges, or improper AIDA64 installation -- whereby the kernel driver files are not installed or extracted from the ZIP package.

1) The current Queen benchmark scales quite bad on many-core systems. It typically stops performing any better at around 30 cores. We're already working on a new Queen benchmark that would replace the current out-dated one in the next AIDA64 stable update. 2) Our suspicion is that there may be cooling issues about the 7975WX test system. We'll make sure to improve on that and re-measure the Mandel benchmark result.

According the updated dump the refresh should take 1 second. It is still quite long, but the Aquaero USB protocol is quite slow, and we cannot get around that

Thank you! The Corsair RMi module causes the extreme high latency. If you can let it go, just disable that module in AIDA64 / Preferences / Stability / Corsair HXi/RMi sensor support.

In AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> Sensor Profiling Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

I've checked the link and it still works.

Please send me your product key in private message, and I will check it out for you. Please also let me know where did you purchase your key from.

It's not relative to the main monitor. It simply has a fixed X,Y coordinate on the Windows Desktop. The Windows Desktop may span across multiple monitors, and the Windows Desktop arrangement may change in case Windows shuffles monitors around or when resolution of one ore more monitors change. It's best if you could assure that the monitor where your SensorPanel is placed gets fixed coordinates on the whole Windows Desktop. Try to make that monitor to be left and top of everything else.

Thank you for your continued support.

I suppose it's because when AIDA64 is restarted during the automatic update process, the RemoteSensor module may not be properly closed and de-initialized. We will tweak that in the next AIDA64 beta update.

Thank you, we'll order a unit and check it out.

Custom Variables is a feature that is designed for a different purpose, it's geared towards assisting network audits in corporate environments. AIDA64 currently supports reading strings and DWORD values from the Registry, and put them on external displays (or SensorPanel, OSD Panel, etc). You need to find a way to write the Registry values into the following path: HKEY_CURRENT_USER\Software\FinalWire\AIDA64\ImportValues And name them as: Str1 Str2 ... Str10 for string values, or: DW1 DW2 ... DW10 for DWORD values. As you keep updating those values in the Registry, the values get updated on your external display.

I suppose in your case we'd need to focus on the Razer 8-port hub you've mentioned. That's the device that we need to natively support in AIDA64. Please let us know what's the model name or part number of that Razer device. I assume it is connected via USB to your motherboard, is it the case?

I've sent you a private message about this.