How To Get Aida64 For Free

[Rosella Bowlan]

Ive used Aida64 for the Sensor Panel for many years. But after upgrading my PC*, I've noticed that Aida64 uses a relatively high amount of CPU (often hovering around 5%, sometimes hitting 10+%. Perhaps it always used so much but I've only noticed now.

Anyway, the CPU usage seems unrelated to what's actually on the sensor panel: it behaves the same whether it has 0 items on it or 100. Though it does improve if I set transparency to 0%. And it does dip below 1% if the sensor panel is turned off completely by unchecking "show sensor panel" (as opposed to just hidden by setting all items to "hide"). It also seems to be pretty much unaffected by whether the polling rate is 100ms or 2000ms.

1. Are there certain settings I can change in Aida64 that would reduce CPU usage? I only use the sensor panel and logitech g510s lcd panel (I don't even use the main aida64 window). So I'd be happy to disable anything that doesn't relate to those. Could I disable something in the stability section perhaps?

2. Is the 5-10% cpu usage actually a problem if I don't max out my CPU to 100%? I'm a photoshop power-user, which frequently works my CPU and RAM hard, but it usually only maxes out one or two cores (my CPU has 8 physical cores). My understanding is that, in theory at least, if Photoshop maxes out, say, cores 1 and 2, then the CPU will just shift Aida64's workload to core 3, and Photoshop's performance would remain unharmed. Is this how it works in reality?

1) It would be best to first check what might cause the high CPU usage. Try to right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first.

Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Generally speaking, certain Asus motherboards could operate with a very high EC (Embedded Controller) latency that would cause AIDA64 sensor module to load the CPU for several milliseconds. You can check if your motherboard is affected by that anomaly by disabling EC support in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option. Also note that by disabling EC support you will lose a few sensor readings like CPU OPT fan RPM.

2) It's not really a huge issue, especially if you almost never max out the CPU usage across all cores. If you only load the first 2 or 3 CPU cores using Photoshop, Windows will automatically switch AIDA64 to use one of the other cores to update the sensor readings and the SensorPanel.

Asus motherboards could operate with a very high EC (Embedded Controller) latency that would cause AIDA64 sensor module to load the CPU for several milliseconds. You can check if your motherboard is affected by that anomaly by disabling EC support in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option. Also note that by disabling EC support you will lose a few sensor readings like CPU OPT fan RPM.

My sensor panel did have CPU Opt RPM on it, which has now stopped working as you said (it's no big deal). I can't see any other changes in the sensor panel. Can I assume that, apart from CPU Opt RPM, disabling EC support will have negligible impact for me in AIDA64?

EC latency is only a problem if you're running a software that polls EC registers. And those are typically hardware monitoring tools like HWiNFO, HWMonitor, SIV, SpeedFan, etc. Other kind of software would never go as deep as to talk to the EC, since they have no information to gather from the EC at all.

In my case, AIDA64 was constantly using about 1.5% CPU (hard to do, since this is a 32 core, 64 thread system). This after slowing down the update frequency quite a bit.

Changing the EC support did not change anything at all, but I then started experimenting with the other stability selections.

In my case, the culprit was the selection for RAID SMART Support.

30+ drives, a good portion of them controlled by an Adaptec RAID card. Apparently asking them all for SMART info every few seconds (which my sensor panel does not use anyway) is not a good idea.

RAID Member enumeration, and Adaptec Card support turned on/off made no/little difference, but RAID SMART support apparently takes a lot out of it.

After turning off SMART support, AIDA64 consistently runs at only 0.1-0.2%. Now I can raise the update frequency again. Hurray..

Hello, sorry to revive and old thread but i had the same problem, CPU usage was 4%-5%, after disabling EC CPU usage went down between 0.1% and 06%, thats good but i want to ask something as i didnt understood what you meant in the post i quoted. Will my HWiNFO and HWMonitor apps be affected because disabling that option in Aida64? Is that option just for Aida64 or something globally on my PC? Thank you for your information!

So my problem, I like the look of these little 5" displays that people use as stat screens. I have installed aida64 and made up a sensor panel. Problem is that when I run aida with icue my fans lighting stutters, then after a while aida will freeze and my fans go back to normal.

I want to put a 7" Sensor Panel in the Rear Exhaust Fan location of my O11 Dynamic XL case but also want to run an ICUE Nexus on a K100 KB I have ordered for some Touchscreen control of RGB/Fan Profiles and At a Glance Temp/Speed monitoring. I mean if I have to choose, iCUE wins because I have a Capellix H150i, Vengeance RGB Pro, LS100, ST100, Polaris Pad, MM700 Extended Pad, about 24x Corsair RGB Strips, 15x QL120 Fans across two PC's......LOL.

Corsair can you please fix your application so that it works with 3rd party software. I love your hardware and the software is great, but it can not do everything that other software can do. Can you PLEASE allow you consumers to use 3rd party software on out own machines.

I want the 'SensorPanel' to start on the 7 "monitor with a resultion of 1024x600, so that the AIDA64 starts with the correct scaling, unfortunately the program opens on my main monitor and the scaling is wrong with 1536x900 the fonts become bigger but the pictures does not scales, no changes when i drop the SensorPanel to my 7" Monitor with Windows scaling 100%.

Try to enable SensorPanel, set its size to some small value, like 300x200 pixels, and move it to the 7" monitor of yours. Then close AIDA64 and open it again. In case it opens on the 7" monitor, then it should be possible to configure it from then on.

I have an issue with the sensor panel also. I tried to make it work correctly and I still cannot make it display correctly. Changing the compatibility option to system or system (enhanced) does stop it from changing the values in the display panel settings but it still starts on my main display and is about 4x larger than it needs to be to fit on the display panel. I tried to set it to the low settings (480x320) but it doesn't start on the secondary display.

I am recently having something similar problem. I tried solutions given above but nothing is working. My sensor panel monitor is 1024*600. I created sensor panel to match this resolution a year before. My computer was packed away for few months. When I tried to start again i am getting problems. Recently updated the Aida 64 software as well.

When i load my old sensor panel it loads on some weird resolution as first ( like 200*300), all the text and logo gets cramped on one area. When I go to preferences and change the resolution to 1024*600, sensor panel moves back to 1024*600 but all the icons, graphs and texts stays on same place without moving. I tried the solution provided above but doesn't work.

3a8082e126