Elderdeekey

Case resolved. I have no clue why v.8.00 had troubles reading RAM temp while v. 7.65 hadn't, but as soon as I delayed Aquasuite services start by 10 seconds problem gone...

Checked. No other version of Aida64 present on my system. When testing I move the entire Aida64 directory into zip file, delete that directory, create new one and unpack another version into there. So it is still very strange - v.8 doesn't show RAM temperature after initial boot and requires exit and restart Aida64.exe file to restore RAM temp reading while v.7.65 works just fine...

UPDATE: from my understanding dump file is empty, no SMBus reading at all... I've spent quite some time testing and I found the following: - after 1st PC start there is no RAM temp reading in Aida64 v.8 - if I exit Aida64 v.8 and then restart it manually w/o rebooting PC RAM temperature appears just fine. Something is blocking that SMBus reading on initial PC boot... At the same token v. 7.6 doesn't have that problem... RAM temp is in place after 1st PC start. Would be happy to provide any additional info if needed. Thanks!

Here we go and thanks for the fast reaction! smbusdump_full.txt

v. 7.65 was OK. After upgrading to v. 8.0 DIMM temperature gone. Nothing was changed in Windows 11 or HW, no updates, patches whatsoever... RAM Team Group T-Force Delta RGB 32GB (2x16GB) DDR5 running @ 7000MHz @Fiery - what debug should I send to you? Thanks!

X.58 resolved the problem, no more Aida64 (I'm using v.6.75.61.00) readings delay.

What is your Windows (version and edition)? Thanks!

Appreciate your extensive reply. In fact, I did use Google translate to read that forum, just don't feel comfortable to post "inking unit" and alike text I share your thoughts on AQ attitude. I did have bad experience even talking to their support when my OCTO blew off because of early microcode bug (that is definitely another story). Could you please tell me what is your update frequency setting in AIDA64 - I'd like to use yours and double check what happens with reading under X.57. Thank you!

Interesting! Could you please ask Aqua folks via forum (I do not know German) - WHY everything goes smoothly with Aida64 sensor reading when Aquasuite X.53 is installed and as soon as it is updated to version X.57 Aida64 reading becomes extremely slow?! (Indeed it is the same PC/OS/Aida64 version with the same settings.) In my humble opinion something has been changed by Aquasuite programmers in between (could be in v. 54, 55, 56 or 57). Thank you!

Gotcha! It is sad that they "behave" that way... Well, thanks for your time and efforts to help resolve this issue...

Fiery, I'm a bit lost... Does Aqua message mean that they've changed update rate in X.57 (or at least after X.53 as I didn't install 54-56)? The reason to be lost is that with the same AIDA64 update frequency - 5000ms - I have no troubles with sensors reading with X.53 installed. Immediately after X.57 installation AIDA64 (even your latest beta) with the same settings (I do not change even a single bit in settings) becomes extremely slow and barely reads sensors (it looks to me like once every 15-30 seconds or alike)...

It doesn't and my reply with dump file is hidden...

Nope :((( As soon as I applied X.57 update to Aquasuite and installed AIDA64 6115 beta its sensor updates (via gadget) again became very slow... Attached dump is from such system... aquacomputerdump6115.txt

Fiery, in my attempt to help with resolution of this issue I'm attaching 2 dump files here - one with Aquasuite X.53 installed (where there is no troubles with AIDA64 sensor readings) and with Aquasuite X.57 installed (where there is substantial delay between sensors readings). Simple comparison these 2 files with WinMerge program clearly shows there are difference in MPS, OCTO and QUADRO areas. Thanks again! aquacomputerdump-X53.txt aquacomputerdump-X57.txt

Sometime ago, after yet another aquasuite update (with some microcode update, at least for my QUADRO and OCTO) AIDA64 stopped its reading for some Aqua sensors. It has been fixed by AIDA64 great team by updating this wonderful program. I would suggest you start another thread and attach your sensor debug information to your post. Good luck!

As title says... At certain day I've noticed that even at 5000 ms (500 ms was a typo) sensors update frequency settings AIDA64 (I'm using 6.75.6100) did update reading like once a minute and even initial load after Windows start takes much more time than usual. It took me a few hours to find out that it has happened after I've updated Aquasuite from version X.53 to X.57. It has been confirmed by myself a few times by restoring Windows 11 from the image with version X.53 installed (where reading updates are done according to the settings) and applying the update to X.57 which immediately slows it down substantially. I guess not many people use this combination (AIDA64 and Aquasuite) but still this is an issue. Fierry, I guess you have contacts at Aqua Computer - could you please check what has changed from 53 to 57. As a side note - I skip X.54, X.55 and X.56, there is a chance the changes were done prior to X.57... Thanks!

Case closed! After playing with AIDA64 Stability settings I've managed to find the reason why SMBus Dump (full) had no information. The reason was enabled "SMBus acess through ACPI (Asus motherboard)": As soon as I uncheck it: 1. SMBus Dump (full) started to produce full results (attached) AND 2. I see all 4 DIMMs temperature now: I do not know is it a bug or a feature of this setting but enabling it on my ASUS ROG Maximus X Formula blocks DIMMs temp. reading. smbusdump_full_new.txt

Not sure debug worked as intended, see no info in the file except MB info. Anyway, please find attache that file. Thank you! smbusdump_full.txt

I've lost Corsair's Vengeance RGB Pro modules temperature reading - Corsair made microcode update just recently to those modules to firmware 1.02.64. Temperature reading of those modules works just fine inside Corsair's ICUE software. Version: 6.50.5806 beta (Oct 28, 2021) fixed the problem with all OCTO sensors after aqua computer updated its microcode but not with Corsair RAM. DIMM thermal sensor support enabled: Attaching 2 debug files, please let me know if I should debug something else. Fiery, many thanks in advance, as usual! aquacomputerdump.txt sensorprof.txt

Opened a new thread to make sure it is not forgotten...

Same here with STRIX Z390-E_Gaming with the latest stable AND beta versions. HWMonitor started once with sensor enabled fix the problem... Dear Fiery, could you please look into this, thank you!

same here with STRIX Z390-E_Gaming

Clean reinstall of AIDA64 and redo new .ini file resolved the glitch. Case closed, thanks Fiery!

How do you enumerate thermal sensors? I have 11 sensors in total: T_Sensor from ASUS MB Ext_1 and Ext_2 from ASUS Fan Extension Card (3rd port isn't in use) 4 temperature sensors from 2 Aqua computer MPS flow meters (2 internals and 2 externals) 4 temperature sensors from Aqua computer OCTO fan controller (all externals) All Aqua computer sensors enumerated as Temperature #1 - #8. Thank you.

Thanks Fiery, attached. smbusdump_full.txt