Fiery

Please note that we've revamped the Logitech G15/G19 DLL scanning module in AIDA64 v5.00, so if you're using a previous AIDA64 version, you may get into troubles about that, but with AIDA64 v5.00 and v5.20 it should work just fine.

Thank you, we'll fix the issue in the next AIDA64 beta update due to be rolled out in a few days from now.

Just a quick guide, please let me know if you have difficulties with this, and at which point do you have issues: 1) Connect the AlphaCool LCD to the USB port of your computer 2) Download and install the latest version of AlphaLCD: AlphaLCD 1.0.4.48 Beta 3) Start AIDA64 (latest version: v5.20), go to main menu / File / Preferences / Hardware Monitoring / LCD, select the AlphaCool tab, and tick the checkbox to enable the AlphaCool LCD support 4) It should say "AlphaCool Init OK" with green colour once you've enabled the checkbox 5) Keep the Preferences open, and go to the next page called LCD Items. Press the New button or double-click in the empty list of items to add a new item to your LCD layout. If you have difficulties building your layout, refer to the following video: Note that the 2 most popular AIDA64 visual monitoring modules, SensorPanel and LCD both use the same layout building solution and the same rendering engine. So whatever you read or watch about SensorPanel, will also apply to the LCD module.

Are you using the latest version of AIDA64, v5.20?

That is one of the new improvements of AIDA64 v5.20, but I'm not sure in what way would it be related to your computer.

Thank you. Is it 64-bit Win8.1 with Update 1 and all the other updates installed? SensorPanel should be able to work with 500 millisec update rate, just like other modules. The only constraint is that the update rate is measured between the end of the last update and the beginning of the next update. So in case polling all the sensors and other system values on your computer takes let's say 450 millisec, then the effective update rate will be 950 millisec.

Thank you for the feedback. We'll fix that glitch in the next AIDA64 beta update.

I'm afraid that's not the information we would need to implement support for your hardware

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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic.

We'll try to reproduce the issue on our test systems. Please let me know what Windows version do you have installed. Thanks, Fiery

We would need a bit more information on that issue to fix it up What is the actual problem? Which values are reported incorrectly? Thanks, Fiery

We don't have a list of those devices, simply because we don't manage a list of those. Last year we've started to compile a guide for LCD devices, that is in a beta stage. I can send that to you in email. Just drop me a private message if you're interested

Thank you for the feedback

The new AIDA64 release implements optimized benchmarks for AMD "Carrizo" and Intel "Broadwell" processors, SensorPanel and external LCD improvements, and supports the latest nVIDIA GeForce and Quadro graphics accelerators. New features & improvements - 64-bit benchmarks optimized for AMD "Carrizo" APUs - AVX2 and FMA accelerated 64-bit benchmarks for Intel "Broadwell" CPUs - Improved support for Intel "Braswell", "Broadwell-H", "Cherry Trail", "Skylake" CPUs - Preliminary support for AMD "Nolan" APU - Support for the sensors of the AquaStream XT, MPS, PowerAdjust 2, PowerAdjust 3 water-cooling parts - Support for the sensors of Thermaltake DPS-G power supplies - SensorPanel and LCD: right-to-left bars, control strings for static labels - 0.01 Celsius temperature measurement for select sensor items - Support for Odospace LCDs - CUDA 7.0, OpenCL 2.1 support - Corsair Neutron XT, Crucial BX100, Crucial MX200, SanDisk Ultra II SSD support - GPU details for NVIDIA GeForce GTX 960, GeForce GTX Titan X What's new since AIDA64 v5.00 - RemoteSensor smartphone and tablet LCD integration - Logitech Arx Control smartphone and tablet LCD integration - System certificates information - Support for Gravitech, LCD Smartie Hardware, Leo Bodnar LCD devices - Microsoft Windows 10 Technical Preview Build 9888 support - Improved support for Intel "Skylake" CPU - Preliminary support for Intel "Braswell" SoC - Aquaero and Aquaduct sensor devices support - Improved support for Crucial SSDs [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v5.20 ] [ Download ]

To me it sounds like an overheating issue. Maybe your system only gets excessively hot when all components are stressed in the same time. Regards, Fiery

If you move the SensorPanel out of the visible Windows Desktop area, AIDA64 will automatically place it back to the visible area.

I'm afraid AIDA64 doesn't offer an exclusion list to let you "whitelist" those drives with issues about SMART reporting. I still believe your drives (or something related to your drives) have an issue. It could be a common issue that plagues all systems that have such a drive in your enterprise, like a similar PC configurations with similar compatibility or hardware issue. The author of HD Sentinel stated this on a similar issue about End-to-End Error: http://www.hdsentinel.com/forum/viewtopic.php?f=32&t=1829 Based on what he said -- and let's face it, he's an expert about these things -- I'd say in your case there could be an issue about SATA cable, SATA controller, SATA controller driver, or perhaps a one-time failure that somehow happened to all your ST1000DM003 drives. If I were you, I'd try to get to the bottom of this, because it's really not the best practice to ignore SMART errors, no matter how serious they are. Gambling with user data is a big no-no in my book

We'll add the requested new items in the next AIDA64 update due in a few days from now. Thanks, Fiery

Yes, we'll see what we can do about it

It's not possible, but it is there on the Statistics tab of the AIDA64 System Stability Test. It's also possible to log the min/max/average values to a HTML or CSV log file (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging). Regards, Fiery

Using transparent color key is an old thing that looks terrible in most cases. Unless of course you use a square object on your SensorPanel, and everything around that object would need to be transparent. But then it would be much like having no transparency at all, since the SensorPanel is also a square object and everything around it is transparent Trust me, we've put a lot of thought into those things, and whatever we could try, we've tried already. What we've got in AIDA64 v5.00 (latest version) is what we can do about those issues.

On your particular system I don't think disabling any of the Stability options would make a difference, system most of them are manufacturer specific ones. You can of course try to disable those that you deem unrelated to your system, like the Apple, Dell, Koolance, T-Balancer, Toshiba, Volterra ones, but I doubt it would fix anything.

You're right about that. It'll be fixed in the next AIDA64 update due in a few days from now. Thanks, Fiery

We'll add the requested Mbps unit conversion in the next AIDA64 beta. Using Mb/s would be a bad idea, since AIDA64 ignores the case, so Mb/s and MB/s and MB/S are all treated equally as MegaBytes Per Second

We've tried that, but it didn't help to prevent minimizing SensorPanel with Windows key + D. AIDA64 Preferences already implements a Prevent SensorPanel from being minimized option. That's all we could do about this issue. As I've explained before, transparency for the SensorPanel is not possible. You can however take the wallpaper, slice out a portion of it and put it as the SensorPanel background image, to imitate a transparency effect. Many users went down that path and use SensorPanel with good results.