Fiery

That is a common issue of modern AMD processors. It is due to a hardware pecularity that cannot be fixed from software. The temperature diode of such processors provide a reliable and sort-of-accurate reading when the processor is under load. Regards, Fiery

We've just rolled out a new AIDA64 beta that supports Aquaero 5 and Aquaero 6 displays, as well as Matrix Orbital RS232 LCDs: http://forums.aida64.com/topic/2458-new-lcd-device-support-aquaero/

We've just added support for RS232 (serial) port Matrix Orbital LCDs in the latest AIDA64 beta: http://www.aida64.com/downloads/latesta64xebeta

We've added support for Aquaero 4, Aquaero 5 and Aquaero 6 devices, as well as compatible Aquaduct products (Mark 2, Mark 3, Mark 4 and Mark 5). You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is having the Aquaero/Aquaduct unit connected to a USB port. You can verify if your device is compatible with AIDA64 by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be one of the following IDs: 0C70-F0B0 (Aquaero 4) 0C70-F0B8 (Aquaduct Mark 2 or Aquaduct Mark 3) 0C70-F001 (Aquaero 5 or Aquaero 6) 0C70-F002 (Aquaduct Mark 4 or Aquaduct Mark 5) It is recommended to use the latest firmware for your unit. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD or VFD device that is currently unsupported by AIDA64. BTW, Crystalfontz LCD, LCDInfo, POS VFD (customer display, pole display, table display), and Trefon LCD devices are also supported now by the latest AIDA64 beta. Regards, Fiery

We've just added 4 new POS protocols (ADM787/788, CD5220, DSP800, ICD2002) to AIDA64: http://www.aida64.com/downloads/latesta64xebeta

We've implemented the requested feature (scale right-alignment) 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

We've extended the Razer LCD pages count from 4 to 9. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3129md9rnvbs5jzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

I'm not sure what you mean by "limit the record period". Can you please explain what you would exactly try to do with AIDA64? Please note that CPU throttling activity can be monitored using the AIDA64 System Stability Test, OSD Panel, SensorPanel and LCD facilities, and also can be logged to CSV or HTML file. Regards, Fiery

You need to initiate the refund process at cleverbridge: http://www.cleverbridge.com/?scope=cuseco&id=IxRlJytbEg&progress=customersupportform But please note that the license doesn't need to be renewed every year. You only need to renew the license (after its support & maintenance period expired) in case you've got any issues with the AIDA64 version you're using, and you want to upgrade to a newer release. Regards, Fiery

Thank you, we've tested it, and apparently Samsung's SODI driver isn't 100% compatible with Windows 8.x The SODI driver somehow prevents the AIDA64 main process from exiting, that's why you cannot start AIDA64 again after closing it. So under Windows 8.1 it's best to use the LibUsb0 drivers.

Yes, we'll do that soon. As usual, I'll post a download link to a new AIDA64 beta update once the requested feature is implemented. I'm not sure what kind of items do you want to have right aligned. If you use the "Simple Sensor Item", then right-align option is already there. However, when precise positioning is crucial, it's best to use "Sensor Item", which you can define the total item width for, and precisely position the value and unit fields inside the dedicated sensor item space. We'll check that issue. Please let me know which driver are you using currently (Samsung's or LibUsb0). Reordering pages is already possible with the latest AIDA64 beta: just use drag&drop on the "Page 1 / Page 2 / Page 3 / Page 4" headers http://www.aida64.com/downloads/latesta64xebeta

I appreciate your attention to this issue, and the proposed ideas on how to improve the existing Logging feature of AIDA64. However, you have to understand a few things: 1) The logging facility was originally designed without an entry in the System Tray icon right-click menu. It wasn't meant to be stopped or suspended and then restarted again with a user interaction. And we haven't had complaints on the way it was implemented. Later on, a few users wanted us to make it suspendable and restartable via the System Tray icon. The current solution is in place for a few years now already, and it was only you, a single user who posted any complaints on the Logging feature. Most users simply find it clear and easy to follow, easy to use. While I do understand that you want to make it more clear for you, for most guys it is simply "good enough" currently, they can use it without issues. 2) If you check other Preferences options, related to other features of AIDA64, you can see that the way the logging options are implemented is completely consistent with other related features of AIDA64. For example, if you enable the OSD Panel or SensorPanel, they will automatically open once you start AIDA64, and they will close when you close AIDA64. You can open and close the SensorPanel from the System Tray icon right-click menu, but that wasn't found with criticism by other users as well. So, once you enable a specific Hardware Monitoring facility of AIDA64, they will always start once you start AIDA64, that's just the way they are supposed to work. 3) We'll fine-tune the "Logging Finished" tags at the end of the log files. It's not quite easy to swap an already written line there, simply because currently logging is implemented in an incremental way, so only appending the files is possible. That policy saves a lot of unnecessary writing to disks, which is quite important in the days of SSD drives. And when you suspend logging and AIDA64 would write a "Logging Suspended at XXXX" time stamp there, and you restart the logging, the file should be completely recreated in order to remove the "Logging Suspended at XXXX" line from there. Unless of course you would leave those lines there, which would make the log file quite ugly IMHO.

Did you change any hardware in your computer recently? Or have you updated any drivers like ForceWare or Catalyst or the Strike7 drivers?

We've just rolled out a new AIDA64 beta that supports LCDInfo and Aquaero 4 displays: http://forums.aida64.com/topic/2449-new-lcd-device-support-lcdinfo-usb13700-and-usbd480/

We've added support for both LCDInfo LCD protocols, as described at: LCDInfo USB13700 LCDInfo USBD480 You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is having the LCD drivers (libusb0) installed, and the display to be connected to a USB port. You can verify if your device is compatible with AIDA64 by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be one of the following IDs: 16C0-08A2 (USB13700) 16C0-08A6 (USBD480) It is recommended to use the latest firmware for your display. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD or VFD device that is currently unsupported by AIDA64. BTW, Crystalfontz LCD, POS VFD (customer display, pole display, table display), and Trefon LCD devices are also supported now by the latest AIDA64 beta. Regards, Fiery

AIDA64 uses CPU MSR register to detect throttling activity. It is per core, so #1 from your list. I'm not sure if there's a register that one could use to detect throttling activity for other parts of the CPU package. Much quicker, typically just tens of milliseconds. AFAIK throttling kicks in when the CPU is overheating for 20 milliseconds (or more), so the whole thing is very sensitive and very sharp. It has to be, or else it wouldn't be able to prevent a critical overheating situation damaging the processor.

There's a native method to read PCH Diode temperature, directly from the PCH. That's a different reading And it's not supported by many Intel systems.

Thank you for the shot, it looks great. I'm glad you could make it work We'll try to get a SPF-87H that failed to work out for you, because there's a slim chance that particular DPF has some other tricks that AIDA64 doesn't handle properly yet. Although my gut instinct says that your particular SPF-87H part may just have some hardware flaw that isn't related to AIDA64 at all.

Please note that AMD processors will not throttle, throttling is used by Intel processors. AMD processors use a different mechanism to protect themselves from overheating. As for the spikes, they could be because the CPU temporarily failed to provide the right CPU multiplier reading, or that the motherboard temporarily failed to provide the BCLK (FSB) clock speed via APIC. Such things could happen when the system is under extreme load (stress). You don't have to worry about such things as long as your processor isn't overheating while running the stress test. Regards, Fiery

AIDA64 will not stress or load the system when you only use it for monitoring purposes. I'm afraid you haven't provided enough details on the issue to discuss it further. For example, it would be important to know what kind of computers are they, and whether you could see any actual CPU load (via e.g. Task Manager) when your processors were throttling while you were using AIDA64. And if you saw any actual CPU load, it would be important to know whether they were caused by the AIDA64 main process (aida64.exe) or some other process or service. Regards, Fiery

No adjustment is necessary about TJMax on Intel Nehalem and Silvermont family processors. TJMax adjustment was only necessary in the LGA775-era. As for throttling, it may or may not kick in at TJMax. Please note that the on-die CPU temperature sensors aren't that accurate that one may expect them to be. Also, when any of the CPU cores momentarily hits TJMax, the CPU will start throttling immediately, and the reported DTS temperature will quickly drop down a few degrees Celsius. The whole thing overheating protection mechanism works very quickly, and the measured temperatures will fluctuate a lot.

Thank you for the feedback

Thank you for the feedback

I'm sorry, that is just a pecularity of our implementation of the log closing. It doesn't put the footer there if you manually stop logging, since it treats the situation as you just suspend logging and may restart it again with the same log files. It will only put the footer there when AIDA64 itself stops the logging and closes the log file. We'll try to come up with a solution soon, although it's not easy, since there are many different issues colliding with each other in this case.

Such things could happen when AIDA64 enables a certain chipset PCI device that is otherwise disabled by the BIOS at system bootup. Once the new device appears in Device Manager, try to reinstall Intel Chipset Device Software. It should take care of installing the drivers for the enabled device.