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!