Fiery

Thank you for the test runs, we've fixed a couple of issues around the DirectX module to fix the memory leaks. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3011kwx5st2bvczip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Try to use the search field of Windows Explorer to find the file AIDA64.EXE. Once you found that file, just remove it, and any other AIDA64-related files you may find via the Windows Search facility.

What do you want to do exactly? Do you want to completely remove AIDA64 from your system?

Any software that wants to interact with AIDA64, e.g. its External Applications features. We only know of Logitech LCD Manager, but there could be others out there.

If you cannot find the AIDA64 auto-start task in Task Scheduler, then AIDA64 hasn't set itself to load up at Windows bootup. It means some other software starts AIDA64 at Windows bootup, but I'm not sure what software would want to do that.

Thanks a lot! But I'm afraid we cannot find the registers responsible for holding the fan RPM readout It's either at some other place, or the readouts are only available via Dell SMI calls. Problem is: AIDA64 is no longer able to use the Dell SMI interface. It could be because either Dell revamped their SMI interface, or discontinued using it. But since Dell doesn't reveal their secrets, so far we're stuck with that issue We'll try to get (borrow) such a new Dell system, to see how it works, but it may take a while. I'll post a message into this topic once we have an update to this.

I've sent you the email address in private message. Thank you.

Then maybe the problem is that AIDA64 auto-start entry is still active in the Windows Task Scheduler. Once AIDA64 starts up automatically at Windows boot, go to main menu / File / Preferences / General, and disable (clear the checkbox) the option Load AIDA64 at Windows startup. Close AIDA64, and if you want, you can verify if the scheduled task entry is actually removed by using the Task Scheduler: push the Windows key, and type in: Task Scheduler, then click on the icon of the Task Scheduler in the Programs group. Then, in the Task Scheduler, select the Task Scheduler Library group in the left pane to see all scheduled tasks. AIDA64 shouldn't be there. If it's still there, then maybe some other programs created the task (could be a malware that imitates AIDA64). In such case make sure to perform a full system check via a security/anti-virus software.

Thank you for posting the cleaner

Thank you. Please let me know what video adapter(s) do you have in your system. We'll build a similar configuration and try to reproduce the issue. I suppose the problem would be in the DirectX video memory measurement module. If you disable the Used Local Video Memory and other such video memory related items in Logging, the memory leak may go away with Build 2954+. BTW, have you tried it with the latest AIDA64 beta release? http://www.aida64.com/downloads/aida64extremebuild3006q7kg9jxrptzip

Do you have any BitDefender security software installed? BitDefender seems to collide with thread creation by AIDA64, and we're already investigating it to find a resolution or workaround. Thanks, Fiery

Do you have a Logitech keyboard with LCD screen? E.g. G15, G19. Their software (Logitech LCD Manager) may auto-load AIDA64 even if you didn't enable it specifically.

Please note that even after uninstallation, AI Suite tends to leave behind its NT services that are still running after Windows restart, and still collide with hardware monitoring applications like AIDA64. You have to manually remove those services. Regards, Fiery

The mentioned values (CPU core temperatures, CPU utilization, fan duty cycles) aren't related to AI Suite at all. You can verify what values AIDA64 exports to other applications if you enable the Registry exporting as well (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications), open the Registry Editor (REGEDIT.EXE), and navigate to HKEY_CURRENT_USER\Software\FinalWire\AIDA64\SensorValues.

Sometimes loading AIDA64 at Windows startup could take a while. It is because Windows' driver subsystem prefers statically loaded (installed) kernel drivers over dynamically loaded kernel drivers. AIDA64 uses dynamically loaded kernel drivers to assure it is 100% portable between Windows installations and different computers as well, and also it makes it easier to update the software automatically.

Thank you for the data and the photo. I'm afraid so far we cannot find the registers responsible for the fan speeds Would it be possible to create 2 more ISA Sensor Dumps, one when the fans are definitely stopped (not spinning), and the other while the fans are definitely spinning? That would help us to find the registers by comparing the dumps to each other. Thanks, Fiery

1) AIDA64 exports all core temperatures via WMI. It all depends on the other application (that takes and displays those readings from WMI) which values does it read from there. 2) AIDA64 exports fan duty cycle settings as well. See #1 3) Units are not exported to WMI, but the type and ID fields can be used (by the other application) to figure out the unit and display it. With temperatures, voltages and fan RPMs it's easy, since you only have to use the type field. With system readings (like CPU utilization, CPU clock, CPU multiplier, etc) you have to make the other application a bit more clever by checking the ID field as well.

AIDA64 (regardless of whether you're running the trial version or the unlocked licensed version) can publish those values that are listed on the External Applications page in the Preferences. Please note that the list there is only applicable to the current underlying system you're using. So if you take AIDA64 to another computer, running another operating system, the list of values may be longer or shorter, depending on the number of sensor items that particular computer supports. Regards, Fiery

Their SDK evolves a bit slower than we'd expected

I'm not sure what you're talking about. First of all, it's not possible to configure a 60 seconds update frequency for the SensorPanel. And even if you configure a very long update frequency (of e.g. 30 seconds), when you hide and show the SensorPanel using the right-click menu of the System Tray icon, it will disappear/appear immediately, regardless of the update frequency setting.

Yes, but Direct3D does some very odd things AIDA64 doesn't show a lot of information on Direct3D video adapters, simply because those values do not seem to make any sense. Microsoft keeps revamping and tweaking Direct3D, but it's still not there yet to reflect the proper hardware capabilities. It's best to rely on the directly measured/detected values.

Quite frankly, only nVIDIA knows what those values represent exactly. AIDA64 only reads those values, it doesn't do any conversion or other modification to the values ForceWare provides. Regards, Fiery

GPU temperature may be measured as zero when the GPU goes to sleep, that's normal

Try to enable the option Wake GPUs up at AIDA64 startup in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64. If it still doesn't bring the GPU temperature readout back, then it could be a driver (ForceWare) issue that we won't be able to fix on our end Regards, Fiery

Please also create a new ISA Sensor Dump using the latest AIDA64 Extreme beta release available at: http://www.aida64.com/downloads/aida64extremebuild3006q7kg9jxrptzip In this beta we've added a new section to the ISA Sensor Dump that dumps a special Embedded Controller MMIO region that may help us to understand where and how your notebook stores the sensor readings.