Fiery

There are no SMBus devices in the range where DIMM TS capable modules would be found. It is between SMBus device 0x18 and 0x1B (if you have 4 DIMM slots). Your SMBus dump has no device under SMBus device 0x40.

We're planning to implement that feature in one of the upcoming beta updates to AIDA64. I'll drop a message into this topic once you can try it out

I'm glad you like our progress so far. We'll make sure to improve on the Arx module in the near future. 1) We'll add that in one of the upcoming beta updates to AIDA64. 2) You can already use vertical bar graphs if you specify a bar width smaller than the bar height As for bar direction, we'll work on that 3) Conditional formatting would add one more layer of complexity on the already quite complicated LCD item configuration panel But, maybe we can come up with something that is easy to follow by less experienced users. We'll also have to make sure the panel doesn't get even more crowded. What kind of text properties would you like to update based on the item state? Only the text colour? Would you like to use the conditional formatting for Simple Sensor Items?

It may be a bug about GPU dynamic memory measurement in AIDA64. What sort of operating system are you using? Windows 8.1 64-bit? Thanks, Fiery

I'm glad you've managed to figure it out. Note that in some cases, when the system gets suddenly unstable with no hardware change or hardware configuration change, it turns out to be a driver or software related issue. So you cannot always blame it on the hardware Regards, Fiery

Your memory modules do not seem to have a DIMM TS temperature sensing logic. Regards, Fiery

Since your motherboard reports "M11BB" as both motherboard model and system model, that's what AIDA64 can use to identify the motherboard model and activate the necessary sensor adjustments. And since your motherboard doesn't report its model as "F2A55-M", AIDA64 cannot use the F2A55-M sensor adjustments. We'll fix that in the next AIDA64 update due in 2 days from now

CPU power issue: I suppose the problem behind all that may be that the CPU power measurement is done by the Turbo Boost logic of your CPU. And when Turbo Boost is fully unlocked or disabled, power measurement isn't done in the default fashion anymore. Sensor issue: I think ultimately the logic driving the SensorPanel and LCD rendering module is at fault. We've designed them in a way that they should hide such sensor items from the rendering engine that fail to produce a certain "good value" output. So e.g. when an electrical current or power measurement item measures an invalid or "N/A" value, the rendering engine hides the complete sensor item from the output image. We've done that in order to avoid displaying nonsense values, or render weird looking graphs or gauges. And even though in most cases it's quite convenient and user-friendly, it turned out to be an obstacle for Aquaero owners like you. We'll revamp that logic in the next AIDA64 update, to display "N/A" or simply zero value when the sensor reading is invalid. I hope it will be suitable for your needs, and help to fully exploit the Logitech Arx integration. If it still wouldn't be 100% suitable for your needs, please give us more feedbacks, and we'll continue fine-tuning the whole thing to match the requirements of power-users like you

1) The next AIDA64 update will fix the missing gauges for fan speeds. However, the missing sensors cannot be fixed for the voltages and currents, since those values are measured as "N/A" (instead of zero) on your Aquaero sensor device. And when a value is measured as "N/A", AIDA64 will not display the value anymore. The major problem behind that issue is that no sensor device has such a facility that would provide monitoring software the ability to detect physical fan header connection status. So a stopped fan and an unconnected fan header appears exactly the same to monitoring software. If AIDA64 was able to detect the physical fan presence, it would be able to provide fan voltages and fan currents as 0.0V and 0.0A, instead of "N/A". 4) We've checked it with our Core i7-5820K (stock settings), and on that processor AIDA64 measures cca. 10W at idle, and 100W under heavy load. Maybe on your CPU the package power measurement goes crazy due to the excess overclocking. Can you please check what HWMonitor reports?

The issue is related to decoding DDR4 XMP 2.0 memory profiles. It will be fixed in the next AIDA64 update due in 3 days from now.

I've just sent your a private message about this issue.

1) Please explain it using a bit more details. What kind of sensor item is that, and why doesn't it provide any data? 2) That is a pecularity of the HTML based layout AIDA64 has to use for Logitech Arx. With HTML layouts the preview cannot be 100% accurate in all cases. 3) It's a limitation of the operating system of your mobile device. You have to pick a font that exists on both your main computer (PC) and your mobile device. From your PC it's not possible to detect what fonts does your mobile device support. 4) What Intel processor do you have? Thanks, Fiery

Thank you for the feedback. Measurement units are fixed, they cannot be changed I'm afraid.

Are you sure you've got an Asus F2A55-M motherboard? 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.

I think the problem is that you're using an old AIDA64 version. Your motherboard is fully supported by the latest AIDA64 release available at: http://www.aida64.com/downloads/latesta64xebeta Regards, Fiery

1) It's a great idea, we'll add that to the Arc Gauge configuration panel. 2) I'm not sure why such a triangle would be useful. Can you please explain? 3) You can already use vertical bars. Just configure the bar in a way that its width is less than its height Thanks, Fiery

On your system you should focus on the CPU temperature (Processador). Core temperatures (Nucleo) are in many cases inaccurate on AMD CPUs and APUs, so it's best to avoid using them as a reference. In order to challenge the stability of your stock or oveclocked system, you can use the AIDA64 System Stability Test (AIDA64 / main menu / Tools / System Stability Test). To use the maximum thermal stress, only enable FPU and GPU subtests there. Regards, Fiery

Thank you for the feedback. Water Quality is not there yet, but pumps should be there, albeit not as frequencies but as RPM. Stopped fans disappear only from the Computer / Sensor page, but their RPM is still shown as zero on the LCD. Same goes for pumps. Flow sensors indicating zero flow are still displayed both on the Sensor page and LCD. If it doesn't work the way you wish, please let me know what exactly happens vs. what would you expect to happen.

We've implemented a trick in the latest AIDA64 beta to let you avoid AIDA64 writing values to the Registry. Please do the following: 1) Close AIDA64 (if it is running) 2) Download the latest AIDA64 beta from: http://www.aida64.com/downloads/latesta64xebeta 3) Extract it to your existing AIDA64 installation folder (or a new empty folder) 4) Start AIDA64.EXE 5) Go to main menu / File / Preferences 6) Press the OK button on the Preferences window 7) Close AIDA64 8) Go to AIDA64 folder and open AIDA64.INI file (in e.g. Notepad) 9) The 4th line of the AIDA64.INI file should read: NoRegistry=0 Change it to: NoRegistry=1 Save the AIDA64.INI file. That's it From now on AIDA64 should write no values to the Registry, except for the Desktop Gadget and External Applications: Registry features that depend on the Registry to pass values. I hope it works in a way you expected it Regards, Fiery

FYI, we've renamed the AIDA64 Web Server feature to RemoteSensor. You can still use your existing layout, you just have to look for a different LCD device in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD.

We've fixed the issue in the latest beta version of AIDA64 Extreme available at: http://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

I think EVGA E-LEET software supports your motherboard, including sensors measurement. Since it is made by the manufacturer of your motherboard, it's safe to assume that it can be used as a reliable reference to verify whether PWM temperatures are measured properly by AIDA64. Please let me know how it goes Regards, Fiery

Thank you for letting us know about the resolution That is not an official feature of AIDA64. It is there to help us diagnose various issues during the development.

Are you using the latest AIDA64 beta build of 3244? The previous build (3242) had a bug that we've fixed in 3244.

Such issue may occur when the Arx app fails to refresh the web page after you changed the layout. Is it an iOS or Android device?