Fiery

We've just released AIDA64 Beta Build 1651. It's available for auto-update, or can be downloaded from: http://www.aida64.com/downloads/aida64extremebuild1651ctmw8qszdnzip It implements the requested new option in AIDA64 / main menu / File / Preferences / General. During the auto-update process AIDA64 will place not only the ZIP package in that folder, but also the changelog in a TXT file. The changlog can also be seen as a list item hint in the NetUpdate window. The hint will appear while you hover the mouse cursor over the bottom part of the window, where AIDA64 lists the available updates with their corresponding version, date and file size info. We've also added more tricks about the auto-update, e.g. from the next update it will pop up a bubble over the System Tray icon after a successful update stating how many new devices have we added to the AIDA64 Hardware Database.

Sounds a bit weird, but I'm glad you managed to resolve it.

It looks like AIDA64 is unable to use its kernel driver. We've completely revamped the kernel driver in Build 1635. It means the current kernel driver cannot be loaded by an old AIDA64 version, and vice versa. Maybe while performing the upgrade you didn't overwrite the old KERNELD.* files with the new ones? Or maybe some other issue occured during the upgrade process. Please try to completely remove any AIDA64 installations you may have on your system, and restart your computer. You can keep your AIDA64.INI files of course, to keep your Preferences settings. Then manually download beta 1649, extract it into an empty folder, enter your license, and check if it works now. Let me know how it goes

1) Exactly which XPS model do you have? 2) Do you have Win7 64-bit installed? 3) Which version of ForceWare driver do you have installed? Thanks, Fiery

Have you tried to restart your computer after upgrading to the new release?

That's normal. SMART data field for temperature values may or may not be a direct temperature readout (in Celsius). For some drives the lowest byte holds the temperature, and the rest of the bytes of the double-word value may hold minimum or maximum values too. In your case the data value is 2C0A0015 in hexadecimal, which would make it hold 3 temperatures: 44 Celsius, 10 Celsius and 21 Celsius. The lowest byte (21 Celsius) should be the current temperature value. Regards, Fiery

1) Are you using AIDA64 v1.85? (latest version) 2) What version of Windows are you running? 32-bit or 64-bit? Thanks, Fiery

I think it is simply a matter of column width. Double-click on the vertical line separating the cell headers for "A" and "B" columns to adjust column "A" width. Do the same with column "B" to adjust its width as well.

AIDA64 has a complex hardware monitoring module that was designed to monitor temperatures, voltages, fan speeds and power draw. It was not intended to be used as a generic monitoring layer to monitor any sorts of system values. Recently we've enhanced it to cover special values like network download and upload rate, but it's still not capable of monitoring any kind of values. BTW, AIDA64 already monitors disk drive temperatures and alerts you when they exceed a preconfigured value. As for HDD health monitoring via SMART... We don't pursue that feature mainly because we don't trust in SMART. Most of the hard disk failures we suffered here in our labs were not predicted by SMART at all. On the other hand, we have a handful of hard disk drives where SMART says there's an imminent failure, but the drives happily continue working fine. There's a single Matrox IDE drive that's been in use for over 10 years already, with over 8 years of SMART predicted failure And it's still working fine today. But in case you want to constantly monitor the SMART values of your drives, and receive an alert when SMART predicts failure, I recommend you to try specialized HDD SMART monitoring applications like HD Sentinel: http://hdsentinel.com/

Make sure to let Franck know about this issue. If he contacts us for assistance, we'll help him to fix CPU-Z.

AIDA64 doesn't expose SMART values currently. We may implement that feature next year. I'm sorry, but we don't work in C#, so we don't have a sample code. Regards, Fiery

I think your motherboard simply doesn't utilize the sensor features of the VT1211 chip, so all readings should be ignored In case you can ask HP directly about that, please let us know if there's a trick we should use in AIDA64 to make the readings work. Regards, Fiery

In case Asus PC Probe II (part of Asus AI Suite 2) reports different values than AIDA64 latest beta (Build 1647), then please create a screen shot that shows PC Probe II and AIDA64 values side-by-side on the same screen shot. That would let us compare the values measured "head-to-head".

Thank you for the feedback

We've just released the first AIDA64 beta that implements the Automatic Online Update feature: http://www.aida64.co...47r2mcblkz7fzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that the fully automated online update will only work if you have a valid AIDA64 license. With illegal license keys only the web download link will be offered, and the user will have to manually perform the upgrade by downloading the new ZIP package and extracting it to the existing AIDA64 installation folder.

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1647r2mcblkz7fzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1647r2mcblkz7fzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you for the feedback

Please try to disable Dell SMI sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. Thanks, Fiery

It's already there Just enable the first 2 items in the Logging items list. They are named "Date" and "Time" Regards, Fiery

We've had to revamp the kernel driver of AIDA64 to implement preliminary support for Windows 8. When we change the kernel driver, a one time system restart is necessary.

Please reinstall Build 1641 (latest beta), and restart your computer. If it doesn't work, then remove all copies of AIDA64 you may have on your system, restart your computer, and install Build 1641. Regards, Fiery

Both Catalyst 11.8 and 11.9 suffer from the OpenGL issue. AIDA64 v1.85 will not work with them. But the latest AIDA64 beta will work fine since it uses static linking for the OPENGL32.DLL module: http://www.aida64.com/downloads/aida64extremebuild1641xc8yz5fwkpzip

Thank you for the feedback

Thank you for the suggestions. 1) Virtual cores cannot be ignored, because it would make the CPU utilization measurement completely false. Even when the virtual cores are only working at 1-digit percentage load most of the time, such small load will still count. And with proper benchmarks and proper stress test modules (like what AIDA64 implements) it's quite easy to stress all cores -- incl. virtual ones -- to 100%. If you're bothered having your virtual cores sleeping all the time, then you may want to disable HyperThreading in the BIOS Setup 2) Less than a second polling time may be handled by your processor quite easily -- and in fact most multi-core processors could do that --, but the problem is not there. AIDA64 has a hardware monitoring module that has a set of sub-modules to handle various tasks. One of those sub-modules is for core temperature monitoring, another is for motherboard sensor chips, a third is for GPU monitoring, etc. etc. A few of those sub-modules use HID or COM (serial) port sensor devices like T-Balancer and Koolance. Such communication protocols tend to be very slow compared to other modules, which effectively means reading sensor values could last 200 to 800 msec (!), regardless of how fast CPU you have in your system. On top of that, when you have a high-end desktop system with 6 or 12 cores (1 or 2 CPU sockets), 3 or 4 GPUs (e.g. two HD6990 cards) with multiple sensor chips connected, the regular sensor readouts can also take more than 500 msec combined. Hence using a more rapid update rate could well mean a constant sensors polling or a deadlock. 3) We'll check the LCD screen drag&drop ability, IMHO it's a good idea. Regards, Fiery