Fiery

Unfortunately WIndows doesn't allow precise positioning of TabControl tabs, so we cannot arrange them in a way that would form a similar layout to Razer dynamic keys But, in the next AIDA64 beta release we'll widen the TabControl so you wouldn't have to use horizontal scrolling to switch between tabs.

I'm afraid it's not possible to schedule the logging facility of AIDA64. So you cannot start it at a given time and stop it at a given time, automatically. You have to manually start and stop the logging. You can however take the CSV logging output, have a date/time stamp column in it, and process the file after the logging by getting rid of the unnecessary lines.

It seems the crash is due to a bug in the Strike7 SDK that AIDA64 uses to communicate with the LCD screen. We've implemented a workaround to fix it from our end: http://www.aida64.com/downloads/latesta64xebeta But it will have an unfortunate side-effect: AIDA64 can no longer switch between LCD pages instantly. The page switch will only take place at the next LCD update, so it is best if you use the lowest update frequency possible, which is 500 milliseconds (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency). Hopefully Mad Catz will fix their SDK soon.

That shouldn't be a problem. However, please note that you can upgrade the installed version by extracting the portable ZIP package files into the installation folder of AIDA64. Let it overwrite any existing files. Your settings (AIDA64.INI) and your entered license will be retained.

Such things might happen when the system time gets updated in the background, e.g. roll it back to a previous date than before. If you experience the issue multiple times, please let me know. Thanks, Fiery

Your Windows user doesn't seem to have the right privileges (administrator rights) to let AIDA64 load its kernel drivers and so access the sensor chip of your motherboard. Make sure to provide the necessary privileges to let AIDA64 use its low-level hardware features. Regards, Fiery

Thank you for the feedback, it looks awesome

Under Windows 8 and Windows 8.1 it's best to use the libusb-based Windows driver we've created. You can download it from: http://download.aida64.com/resources/lcd/samsung_spf_lcd_driver.zip You have to first start AIDA64, and enable Samsung SPF LCD support from the Preferences. Then, once the LCD is switched to Mini Monitor Mode, install the driver via Device Manager. Then restart AIDA64 and it should work.

Thank you for the feedback, it looks great

Under heavy load AMD iGPUs consume quite a lot of power, so unless you unlock APM to let the TDP loose, loading the iGPU will heavily cut back the CPU Turbo clock headroom. Regular 95W and 100W APUs are less affected, since with them there's 35W more headroom for Turbo.

1) Your CPU uses a Richland core that supports APM (Application Power Management). APM keeps the CPU below its 65 Watts TDP limit by lowering the CPU and/or iGPU clock if necessary. AIDA64 puts a lot of pressure (load) on the CPU and/or the iGPU, so it's no surprise if APM has to scale the clocks back quite a lot to keep the CPU under the 65 Watts limit. 2) 145W: That's what your CPU reports In case APM is active, the package power will never exceed 65 Watts, so you can simply ignore that value. Regards, Fiery

Hash: that is due to a Catalyst video driver bug. Update your Catalyst to the latest version. 24-bit IOPS: AIDA64 uses the same benchmark on CPUs for both 24-bit IOPS and 32-bit IOPS. So if one fails, but the other one works, then it could be a temporary issue. Try to run the benchmarks again Regards, 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?