Fiery

That is due to a bug in the latest Saitek X52Pro drivers (Version 7.0.47.1). When you install those drivers, the driver installer fails to copy the 32-bit DirectOutput.dll file into the folder under \Program Files (x86)\Saitek. We've checked it, and it seems both the latest driver (7.0.47.1) and also the previous driver (7.0.40.9) have this bug. The last driver that works fine is 7.0.39.0. You can either revert back to the last working v7.0.39.0 driver, or I can send you the 32-bit DirectOutput.dll file that we extracted from 7.0.39.0 driver. But I cannot guarantee the DLL from the old driver would work properly with the newer driver as well.

Thank you for letting us and other users know about the resolution.

I'm afraid we don't have any contact at HP

Thank you. Are you using a 32-bit Windows or 64-bit?

We've never noticed that as an issue on our test systems so far. Please let me know what video card do you have, which Windows version do you have installed, and the video driver version you've got installed.

I'm afraid we don't have any idea about what could prevent your system from providing drive activity statistics to AIDA64 We've done test runs on various Win8.1 systems, but on every system we could monitor drive activity without any quirks. There must be a special configuration setting or a background service/process that causes the issues on your system, but I have no idea what could it be.

AIDA64 doesn't support setting the number of decimal digits per sensor item, and we don't have plans to enable that. Regards, Fiery

Thank you for your feedback. The mapping of misc temperatures on your board are: Temperature #1 = T_Sensor1 Temperature #2 = EXT_Sensor1 Temperature #3 = EXT_Sensor2 Temperature #4 = EXT_Sensor3 I'm not sure why they show bogus values sometimes. The only issue I can think of that may cause that is a background process or service that concurrently monitors sensors. The most infamous of those is Asus AI Suite that is still not synchronized with 3rd party monitoring software like AIDA64, HWMonitor, SpeedFan, CoreTemp, HWiNFO, SIV, etc. While those listed software are all synchronized with each other to avoid such collisions due to concurrent sensor access. As for the extension fans, I'm afraid those are only available via EC banked access. And switching EC banks is dangerous, since when a collision (with e.g. AI Suite) occurs during an EC bank switch operation, the system could lock up or the CPU might get overvolted

Yes, that's to prevent you from losing a column If you set one to zero width, it will revert back to the default width the next time you open the System Stability Test.

It is not an option, but a small new feature. AIDA64 will now remember the column widths of the statistics list on the Statistics page of the System Stability Test.

Thank you for the feedback

We've implemented advanced support for Samsung 950 Pro SSDs with the factory default Windows NVMe driver (StorNvme) installed in the latest AIDA64 Extreme beta update: http://www.aida64.com/downloads/latesta64xebeta In case you haven't installed the Samsung NVMe driver yet, please let me know how it works

The above mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta

The above mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta

The above mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta

High variation between various CPU readings is absolutely normal, and you shouldn't worry about it that much.

Thanks a lot! The pictures confirmed my theory about your motherboard having an EC chip. It's an ITE IT8528E. The motherboard is labelled as "IPM99-VK" which means it was manufactured by Pegatron. Sadly I cannot seem to find a sensor chip on the motherboard PCB, so even though those information are interesting, we cannot step further without HP helping us out.

Modern processors have multiple temperature diodes. There's a good chance Speccy reads a different sensor and shows it as "CPU". It could be the CPU temperature as measured by the motherboard sensor chip, one of the CPU Core sensors, the CPU Package sensor, etc. Make sure to check all CPU-related temperatures on the Computer / Sensor page in AIDA64, and compare the values against HWMonitor and the factory monitoring software came with your motherboard (e.g. Asus AI Suite for Asus motherboards).

Thank you for your suggestion. I've sent you a private message

There's a 30-day trial period. Make sure to try everything during that month, and only purchase a license if you're fully satisfied with AIDA64.

What you're talking about is the built-in Logitech Arx sensor applet, which is developed by Logitech and not us. With AIDA64 you can have a lot more flexibility than with the built-in applet. With AIDA64 you can adjust font size, font style, and of course display all GPUs on a single page. Regards, Fiery

Thank you for the data. The issue will be fixed in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.

No problem, it's not something trivial It is possible only because of the flexibility of the Sensor Item

Thank you for the data. The issue will be fixed in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.

This cannot be done right now, simply because the AIDA64 hardware monitor module doesn't manage a history of values. So it's not possible to indicate the maximum value for the session. We would need to completely revamp the hardware monitor module to make it possible. We'll see when can we get there, since nowadays we're rather busy with a lot of ongoing projects... Regards, Fiery