Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Fiery

  1. On 3/18/2021 at 5:53 AM, kombi said:

    Hello everyone, I am trying to write a small tool that reads hardware information from the shared memory of AIDA64. I use python's MMAP library to operate.I found that mmap can obtain the target XML text when reading, but errors often occur during the XML parsing in the subsequent steps.The manifestation of this error is that the XML parser often cannot find a properly closed tag.In manual inspection, I found that this kind of error can be manifested as follows:

    1.<pwr>**********</pwr> wr>



    These errors look like I am reading while AIDA64 is writing to the shared memory area. The data read in this way is not a complete frame(Therefore, the structure of the data as XML may not be complete due to misalignment and other reasons).

    The test code I used for reading is as follows:

            with mmap.mmap(fileno=-1, length=12288, tagname="AIDA64_SensorValues") as AIDA64data:
                string = AIDA64data.read().strip(b"\0").decode(encoding="gbk")
                string = f"<AIDA64>{string}</AIDA64>"
                dict_xml = xmltodict.parse(string)
        except Exception as e:

    Does AIDA64 provide a function that shows a locked state when it accesses shared memory?Or is there a way to avoid reading while writing?

    I am a rookie programmer, maybe this problem can be realized by using some advanced functions of the program, please help me, thanks! :)

    We don't use locking for our shared memory, but we also haven't got any complaints about it working incorrectly.  When we use OpenFileMapping / MapViewOfFile, no such anomaly occurs at all.

  2. On 3/19/2021 at 9:44 AM, Bjoern_GMX said:

    Please add the CPU readings of:

    Fclk, Uclk, Mclk 

    and makes us able to add them to the sensor panel.

    As well as:

    Gpu memory Temperature

    Of AMD Radeon RX6000 series.


    With HWinfo i can read/log them.

    But why not with AIDA?




    We're working on it.  Meanwhile, please avoid posting a single issue into multiple topics.  I've removed your other topic.

  3. On 3/21/2021 at 4:07 PM, paradox37 said:

    I just noticed a little strange behavior of sensors panel. It seems displaying of temperature of my disks is order dependent. I keep two disks in my PC, one M2 and one SSD.

    SensorPanel is configured to display temperature of those disks.

    Samsung 960 EVO - label Samsung

    Crucial CT500MX - label Crucial

    But, from time to time, I hot-plug my HDD since my PC case supports it. And then SensorPanel starts to show the temperature of the disk I just plugged in.

    Labels stays the same, but source of temperature changes. So, label Samsung starts to show temperature of HDD I just plugged in, and Crucial label start to show temperature of Samsung label. When I unplug the HDD, temperature sources are back to normal.

    Can this be fixed? It is strange that this SensorPanel does not use some ID for device and not order.

    It's quite complicated, since the order is determined by the type of device first and then the order (index) inside a particular device group.  Usually external drives appear in the last group to avoid the issues you've described.  Maybe your drive appears as an internal drive even though it's an external one?  We'd need to have a better understanding of what's going on about that in order to fix this.  Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART 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.

    Please create 2 dumps, one with the HDD hot-plugged and another one when it's missing (disconnected) from your system.


  4. 11 hours ago, S41nT said:

    Hey there, 

    aida is messing my framtimes up. I run now the newest version. Same problem exist in the old version. So the problem is not fixed yet.

    My System:

    ROG Maximus Formula XI 
    Intel 9900k 
    32 GB Trident Z Royal 
    ROG RTX 3090 Strix OC 

    Please 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.


  5. 8 hours ago, Nereus said:

    Questions regarding AIDA64 Extreme and Corsair Commander Pro compatibility:

    1. It appears that AIDA64 *will* see fan RPMs for fans that are plugged into Commander Pro fan headers, providing Corsair Link Sensor Support is enabled in AIDA64, is that correct?
    2. Unclear on the following question: Will AIDA64 continue to read fan RPMs plugged into Commander Pro if Corsair iCue software is on - it seems kind of pointless having a Commander Pro unit if iCue isn't on to make use of it, particularly when some RGB components depend on iCue being on in order to display as intended (and for fan curves too obviously).
    3. Also unclear if AIDA64 will see thermal temp readings (like water temp) that are plugged into Commander Pro - and the same compatibility issues above about iCue being on/off?

    I asked in an old existing thread but no response. Amazed if Corsair still aren't providing a hook after years of this being an issue.

    Appreciate any help on this.


    1) Yes, correct.

    2) iCUE and 3rd party monitoring software don't work together, but it depends on the actual situation and devices in question whether the issue is minor or major.  You need to exploit the 30-day trial period that we provide for AIDA64 in order to find out that on your particular configuration how deep the synchronization issue is.  We'd be happy to work on it, but as I've explained in other forum threads, the ball is now rolling at Corsair's and they don't seem to want to play the game with anyone :(

    3) Without iCUE AIDA64 can read up to 4 thermal measurements from Commander Pro.  With iCUE, well, you gotta see and test it out.  Such complicated situations are why we offer a trial period so you can verify if AIDA64 suits your needs on your actual system.

  6. 8 hours ago, Static said:

    I checked the hide senor panel box when I locked my panel in place on my 7'' LED screen. Now my senor panel is hidden on my 7'' LED screen how do I get back the display of all my gauges and such?

    In the latest AIDA64 version of 6.33, there's a Reset Position button in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel.  When you press it, AIDA64 will move the SensorPanel to the center of its Preferences window.

  7. On 3/27/2021 at 5:54 PM, HeMan91 said:

    Hello, I updated to the latest version and still experience the same problem. To reiterate, this PWM problem started with the BETA version that fixed the GPU temperature.

    I don't use Precision X1 but here's a similar screenshot.

    When it's an EVGA video card, I'd trust Precision X1 over 3rd party software.  So it'd be important to verify what PWM setting is indicated by Precision X1.

  8. On 3/28/2021 at 12:18 AM, osborn2009 said:

    Okay so I recently acquired a MSI 3070 Suprim X and had to get a new case for the brand new computer I built. I bought the Lian Li O11 Dynamic. Here is my build. I noticed that my CPU was running about 10-15 degrees warmer while idle than it was in my old smaller case. That didn't feel right, so I figured maybe I had the fans running wrong or I needed a bigger cooler. After watching several videos, this one explained the "best fan configuration" for this case, to which the video maker and most of the commenters agreed. That configuration is 3 exhaust fans on the "back/side", 3 intake fans on the bottom blowing up, 3 intake fans on the CPU radiator at the top. So I went out and bought some more fans and a bigger 360mm AIO and swapped everything out. It has not made even the tiniest bit of difference. In my old case, it was running at 28-32 degrees when idle, now it is running at 48-54 degrees when idle. Can anyone help me figure out what I am doing wrong? or what I am missing?

    iCUE is using like 8% of the CPU and AIDA64/other programs have been using between 0-1.2% of the CPU for a grand total of between 12-15% while idle.

    The room my set up is in is pretty cold. I like to keep my apartment really cool in general, so it does not fluctuate much at all.

    When I check MSI Afterburner and Corsair iCUE, the CPU Temp says 28 degrees. Meanwhile CPUID HWMonitor and AIDA64 both say its fluctuating between 46-52.... What is going on?

    There are several different CPU temps I can select in AIDA64: CPU, CPU Package, CPU IA Cores, CPU GT Cores. I've noticed that the first three all show the previously mentioned high temperatures. But the CPU GT Cores shows the same temp as MSI Afterburner.

    It's hard to tell since we have no technical information on how CPU temperature is measured by Afterburner or iCUE.  Modern processors implement several methods to measure CPU temperature, and you need to decide which one you take into account.  The highest temp, lowest temp, the average of them, it's up to you.  BTW, even on top of the ones you've listed there are the CPU core temperature readings too -- just to make it even more complicated :)

    I'd personally trust HWMonitor in this case, but it may be worth checking HWiNFO64 too.

  9. On 4/3/2021 at 12:53 AM, Robert McKee said:

    AIDA64 seems to be stealing focus every few seconds (3-5), which is very annoying.  If AIDA is running for example, and I try to rename something on my desktop, AIDA steals focus before I finish renaming the file.  If I tell AIDA to quit, then the problem stops happening.  Very repeatable.

    Seems to be related to the SensorPanel, and only if you choose the option to always keep it on top.

    Using AIDA64 Exteme version 6.33.5700

    That's how Windows reacts to AIDA64 forcing the SensorPanel (and OSD Panel) windows to always on top.  A behavior that was recently appeared in one of the Windows 10 updates.  All we could do to mitigate it is to make it less frequent that AIDA64 reclaims the always on top setting for SensorPanel and OSD Panel.  It seems everytime you press a right-click on the Desktop, Windows disables (takes away) the always on top setting from SensorPanel and OSD Panel.  AIDA64 will then detects that and tries to claim back the setting.

  10. On 4/4/2021 at 7:02 AM, Arne said:

    Hey everyone, My goal is to open my rom drives remotely with a stream deck. So far i can open the drive by execute a shortcut remotely, but now i need a way to achieve that by a button press or a simple command that i can run as a shortcut on my main pc. Is there any way to achive that?

    Thank you in adavance!

    Maybe a full graphical remote control solution could do that for you?  Remote Desktop, TeamViewer or VNC?

  11. On 4/4/2021 at 8:59 AM, Crashtest said:

    After installing my Radeon RX 6900XT there are some new PCI devices but AIDA64 cant identify them...

    1002-73A4 - AMD UCM-UCSI Device [1002-73A4] [NoDB]

    1002-73A6 - ATI/AMD USB 3.10 eXtensible-Hostcontroller – 1.10 (Microsoft) [1002-73A6] [NoDB]

    Thank you, we've added those devices to our PCI device database.

    • Like 1
  12. On 4/5/2021 at 2:47 AM, Techsniffer said:

    I am having an issue with my OSD after updating recently and I was hoping someone might have an answer, when I open AIDA64 my OSD doesn't show up, so I go into Prefs and click on OSD > OSD Items it and it just sits and spins. Here is the LowLevel log:


    I am having the same issue, OSD Panel just hangs at detecting sensor information, this was working fine until I updated AIDA64, here is my log:

    [2021-03-31 07:18:21.804]      TO_HWMonitor: --- Start ---
    [2021-03-31 07:18:21.814]      TO_HWMonitor: SensorInfo
    [2021-03-31 07:18:21.822]        SensorInfo: --- Start ---
    [2021-03-31 07:18:21.830]  MotherboardModel: "Asus ROG Maximus X Hero Wi-Fi AC;S11512-100330001110ATX2430Z370,*M22*DDR4-4*GBL*WIF*"
    [2021-03-31 07:18:21.839]  Software Version: AIDA64 v6.33.5700
    [2021-03-31 07:18:21.847]        SensorInfo: --- CPU VID / NB VID ---
    [2021-03-31 07:18:21.912]        SensorInfo: --- GPUSensorInfo ---
    [2021-03-31 07:18:21.920]   nVIDIA GPU Info: --- Start ---
    [2021-03-31 07:18:21.929]   nVIDIA GPU Info: --- reg_0 ---
    [2021-03-31 07:18:21.935]   nVIDIA GPU Info: --- nVIDIADriver_GetClocksOld ---
    [2021-03-31 07:18:21.940]   nVIDIA GPU Info: --- nVIDIABIOSInfo ---
    [2021-03-31 07:18:22.059]   nVIDIA GPU Info: --- Memory Size ---
    [2021-03-31 07:18:22.069]   nVIDIA GPU Info: --- Memory Size (TurboCache) ---
    [2021-03-31 07:18:22.076]   nVIDIA GPU Info: --- Memory Type ---
    [2021-03-31 07:18:22.083]   nVIDIA GPU Info: --- Memory Bus Width ---
    [2021-03-31 07:18:22.090]   nVIDIA GPU Info: --- Base Clock ---
    [2021-03-31 07:18:22.097]   nVIDIA GPU Info: --- GPU Clock ---
    [2021-03-31 07:18:22.121]   nVIDIA GPU Info: --- nVIDIADriver_GetClocksNew ---
    [2021-03-31 07:18:22.127]   nVIDIA GPU Info: --- nVIDIADriver_GetClocksOld ---
    [2021-03-31 07:18:22.134]   nVIDIA GPU Info: --- Memory Clock ---
    [2021-03-31 07:18:22.140]   nVIDIA GPU Info: --- Pipes, Shaders (G80+) ---
    [2021-03-31 07:18:22.148]   nVIDIA GPU Info: --- GPU Usage #1 ---
    [2021-03-31 07:18:22.154] nVIDIADriver_GetLoad: --- Start ---
    [2021-03-31 07:18:22.161] nVIDIADriver_GetLoad: --- NVAPI Init ---
    [2021-03-31 07:18:22.168] nVIDIADriver_GetLoad: --- NVAPI Get GPU Count ---
    [2021-03-31 07:18:22.175] nVIDIADriver_GetLoad: --- NVAPI GetDynamicPstatesInfoEx ---
    [2021-03-31 07:18:22.184] nVIDIADriver_GetLoad: --- 1 ---
    [2021-03-31 07:18:22.190] nVIDIADriver_GetLoad: --- Finish ---
    [2021-03-31 07:18:22.196]   nVIDIA GPU Info: --- GPU Usage #2 ---
    [2021-03-31 07:18:22.203]   nVIDIA GPU Info: --- Compute Perf #1 ---
    [2021-03-31 07:18:22.210]   nVIDIA GPU Info: --- Compute Perf #2 ---
    [2021-03-31 07:18:22.219]   nVIDIA GPU Info: --- Compute Perf #3 ---
    [2021-03-31 07:18:22.226]   nVIDIA GPU Info: --- Compute Perf #4 ---
    [2021-03-31 07:18:22.232]   nVIDIA GPU Info: --- Compute Perf #5 ---
    [2021-03-31 07:18:22.241]   nVIDIA GPU Info: --- Compute Perf #6 ---
    [2021-03-31 07:18:22.247]   nVIDIA GPU Info: --- Die Size ---
    [2021-03-31 07:18:22.256]   nVIDIA GPU Info: --- reg_0 chk ---
    [2021-03-31 07:18:22.263]   nVIDIA GPU Info: --- gpu_id Loop End ---
    [2021-03-31 07:18:22.270]   nVIDIA GPU Info: --- i Loop End ---
    [2021-03-31 07:18:22.281]   nVIDIA GPU Info: --- Finish ---
    [2021-03-31 07:18:22.865]        SensorInfo: --- HDDSensorInfo ---
    [2021-03-31 07:18:22.992]        SensorInfo: --- SPDSensorInfo ---
    [2021-03-31 07:18:29.185]        SensorInfo: --- Start ---
    [2021-03-31 07:18:29.192]  MotherboardModel: "Asus ROG Maximus X Hero Wi-Fi AC;S11512-100330001110ATX2430Z370,*M22*DDR4-4*GBL*WIF*"
    [2021-03-31 07:18:29.199]  Software Version: AIDA64 v6.33.5700
    [2021-03-31 07:18:29.206]        SensorInfo: --- CPU VID / NB VID ---
    [2021-03-31 07:18:29.246]        SensorInfo: --- Start ---
    [2021-03-31 07:18:29.253]  MotherboardModel: "Asus ROG Maximus X Hero Wi-Fi AC;S11512-100330001110ATX2430Z370,*M22*DDR4-4*GBL*WIF*"
    [2021-03-31 07:18:29.260]  Software Version: AIDA64 v6.33.5700
    [2021-03-31 07:18:29.266]        SensorInfo: --- CPU VID / NB VID ---
    [2021-03-31 07:18:29.277]        SensorInfo: --- GPUSensorInfo ---
    [2021-03-31 07:18:29.304]        SensorInfo: --- HDDSensorInfo ---
    [2021-03-31 07:18:29.310]        SensorInfo: --- SPDSensorInfo ---
    [2021-03-31 07:18:29.338]        SensorInfo: --- GPUSensorInfo ---
    [2021-03-31 07:18:29.362]        SensorInfo: --- HDDSensorInfo ---
    [2021-03-31 07:18:29.369]        SensorInfo: --- SPDSensorInfo ---
    [2021-03-31 07:18:30.245]        SensorInfo: --- Start ---
    [2021-03-31 07:18:30.252]  MotherboardModel: "Asus ROG Maximus X Hero Wi-Fi AC;S11512-100330001110ATX2430Z370,*M22*DDR4-4*GBL*WIF*"
    [2021-03-31 07:18:30.259]  Software Version: AIDA64 v6.33.5700
    [2021-03-31 07:18:30.268]        SensorInfo: --- CPU VID / NB VID ---
    [2021-03-31 07:18:30.338]        SensorInfo: --- GPUSensorInfo ---
    [2021-03-31 07:18:30.367]        SensorInfo: --- HDDSensorInfo ---
    [2021-03-31 07:18:30.374]        SensorInfo: --- SPDSensorInfo ---
    [2021-03-31 07:18:31.968]        SensorInfo: --- Start ---
    [2021-03-31 07:18:31.974]  MotherboardModel: "Asus ROG Maximus X Hero Wi-Fi AC;S11512-100330001110ATX2430Z370,*M22*DDR4-4*GBL*WIF*"
    [2021-03-31 07:18:31.980]  Software Version: AIDA64 v6.33.5700
    [2021-03-31 07:18:31.987]        SensorInfo: --- CPU VID / NB VID ---
    [2021-03-31 07:18:32.044]        SensorInfo: --- GPUSensorInfo ---
    [2021-03-31 07:18:32.071]        SensorInfo: --- HDDSensorInfo ---
    [2021-03-31 07:18:32.078]        SensorInfo: --- SPDSensorInfo ---

    Make sure to have the option called SMBus access through ACPI disabled (unchecked) in AIDA64 / main menu / File / Preferences / Stability.

  13. 17 hours ago, zolotoy said:

    Is it possible to monitor specific CPU activities? For example, IIS threads only?


    AIDA64 can only monitor the starting and stopping of processes in the Logging module.  It doesn't have any deeper facility to monitor processes or their activity specifically.

  14. 2 hours ago, Ralendil said:

    ok... RAM temperature are showing in the sensor panel now....

    I don’t understand how and why... but it works now.

    Maybe that’s because I initied icue...

    I suppose the issue came up because you previously had the option SMBus access through ACPI enabled in AIDA64 / main menu / File / Preferences / Stability.  On your system that option should be left at its default value of disabled (unchecked).

  15. On 3/18/2021 at 2:39 PM, Amer Atya Alnomany said:

    really hope this is something you guys are working on, cant wait to have that information display for me on my dashboard @Fiery hope i am not being such a bother by pinging you about this, just want to know if there are any updates on this subject please.

    We're working on it... Hopefully it will be ready in a week or two.

    • Like 1
  16. On 4/1/2021 at 8:56 AM, Fabiomaster said:

    There is 2 add sensor in HWinfo.

    1. GPU Memory Junction Temperature

    2. GPU Hot Spot Temperature

    There is possible to switch this on aida sensor panel ?

    We're working on adding those measurements to AIDA64...

    • Like 2
  17. On 4/2/2021 at 2:11 AM, pasgener said:

    I also would like to GPU VRAM temperature to be included in Aida64.  In HWInfo64 it is called the GPU Memory Junction Temperature, and is distinct (and much higher) than the GPU diode.  I have an MSI 3090 Gaming X Trio, and would find this a really useful addition to my Aida64 SensorPanel.

    I have attached my GPU Register and SMBus Dump text files, but I can't find the VRAM temp in them.

    HWInfo64 can read that data, as can NiceHash.nvidiagpureg.txtnvidiasmbusdump.txt

    We're working on it...

  18. 2 minutes ago, Kilumnati said:

    now my sensor panel on my gpu temperature showing N/A value, before upgrading it was fine and showing all the stats

    You may need to change GPU to GPU Diode or vice versa, depending on the video card model you've got.

  19. On 4/1/2021 at 1:35 AM, d3cayrip said:

    I've posted onthe EK FB goup page ... when will companies learn that integration expands their markets... 

    They contacted us directly, so huge thanks to you!  Let's hope things will accelerate from here immensely.

  • Create New...