Qwinn

Hi Fiery. Great news! Far as I can tell, 6.85.6318 6.85.6323 does fix the problem. I can run sensorpanel now without locking CPU Package temp. I did not check the other temps others have remarked on, but the most important temp that controls the fans seems to be okay now. (Edited to correct version number that fixes the issue)

Hi Fiery. Appreciate the attention to the problem, but still getting stuck CPU Package temp when starting sensorpanel on Aida64 beta 6.85.6318 on X670E Crosshair Extreme as well.

For the record and to save folks time, the new beta release does not stop the CPU package temp lock, at least not on a x670e Crossfire Extreme running bios 0705. I haven't updated to 0805 because it apparently doesn't fix the issue either. Fiery, has there been any communication from Aida to Asus on the nature of the problem so they're aware they need to resolve it? If so, did they acknowledge the problem is theirs?

You can actually start up Aida and use a lot of its features without locking the temp, you just can't activate the sensors, either via the regular UI or by starting up a Sensorpanel. If you have Sensorpanel enabled in Aida, disable it and reboot. Then you can at least use Aida to view regular system info, run benchmarks, etc.

Yes. I will add that the problem seems a bit more severe for me. Others are saying that other apps are reading temperature correctly, but in my case, my Asus Ryojin II 360 Eva Edition CPU cooler, and the motherboard LED on my Crossfire Extreme mobo, are showing the locked temperature. And that temperature drives the fans. Once that temperature gets locked I don't dare do anything except reboot.

Something else occurs to me. On the latest BIOS version for my ASUS Crosshair X670e Extreme, BIOS 0705, they modified the BIOS such that the 2 character LED that normally displays Q-Codes (POST status) on Asus boards now displays CPU temperature by default instead. As I am already displaying CPU Temp both elsewhere on the motherboard and on my CPU cooler, I personally immediately changed that BIOS setting to "Show POST codes only", which was the default behavior before this latest BIOS version. There does seem to currently be a bug in BIOS 0705 where, if you set it to "Show POST codes only", the LED shows the normal and expected "AA" code only briefly while Windows is loading, only to permanently change to "81" in the middle of the load. This does not happen when running Ubuntu off a USB, it stays "AA" in that case, so it's definitely something in Windows triggering it. No one knows what that means or why, but it's probably just a bug. I mention this because I don't think AIDA was causing this issue until I updated my BIOS to 0705, and the implementation of something directly tied to CPU temp monitoring seems to be a bit buggy, so it seems like it'd be worth investigating. EDIT: So I decided to experiment, and set that BIOS setting back to "Auto" so that it displays temp, and verified that Aida still locks the CPU package temp when sensors are turned on. However, it's also true that the temp being displayed where the POST codes normally go is *not* CPU package temp. Not sure what temp it is honestly, I saw at one point that I had 70c package temp and only showed 38c on that led. So maybe it's just a single core temp? Or motherboard temp? Not sure. At any rate, that temperature being displayed does not completely lock when I start the sensorpanel (unlike CPU package temp) but it does seem to be much less likely to change over time.

Out of curiosity, I disabled the display of the temps on both the Asus cooler and the onboard motherboard LED. Just have them displaying animations instead. Changed nothing, CPU temp still locking. Not surprising though, as the temps would still have to be monitored by those devices to properly drive the fans.

Uninstalled RM, set eco mode via BIOS instead. CPU package temp still locking upon activating sensorpanel. As noted before, shutting down Aida64 completely does not unlock the temp. Reboot is required. I would look at a possible conflict with Asus Ryujin II 360 Cooler EVA edition, as I am using that and it does also read package temp (I also have the built-in LED on a Crosshair x670e Extreme monitoring that temp).

Interesting. I do have Ryzen Master installed, but I was thinking of switching to setting eco mode in the BIOS anyway. I'll uninstall it, do it via BIOS, and give it another try. I still do not see the issue using HWInfo64 though. Running it now with RM installed and package temp still works fine.

Hi Fiery, I'm afraid not. Still locks CPU Package Temp when I activate sensor panel. Thanks for acknowledging the issue anyway.

Just saw that someone else reported the same thing under Hardware Monitoring. I added my 2 cents there.

Just adding that I am experiencing the same issue. CPU package temp gets locked as soon as Aida reads the sensors. I had it lock at 82c once, fans went full and stayed on full despite my going back to idle. This is quite dangerous - if someone were to have their package temp locked at a low reading and then they ran something that drove the temps over 95c, I don't think it would increase the fans or throttle at all. This is on a 7950x and Crosshair x670e Extreme running on Windows 10. Aida Extreme version 6.75.6142 Beta. Oh, incidentally, my GPU is a 1080TI and it doesn't seem to be locking that particular reading. But it may not be limited to just CPU package temp either. EDIT: For the record, I tried the sensors on HWInfo64, and it is not causing this issue. It can monitor the CPU package temp correctly without locking it.

Additional information: The CPU package temp locking only occurs once I actually trigger Sensors, either by clicking on the Sensor option under Computer, or by activating the SensorPanel. If I start up Aida without triggering the sensors, CPU package temp seems to stay correct. Needless to say, this is a serious issue, as the fans and temperature control won't adjust for whatever the actual heat is. Windows 10 Pro, by the way. Asus Crosshair x670e Extreme and AMD 7950x.

Hello. Thank you! I have good news and bad news. The good news is that your advice worked, and I now have a version of Aida 64 that allows me to update from within Aida itself. The bad news - it did an update today, in fact, and the update release notes indicate only one piece of hardware was added, and I happen to have that hardware - the Asus Riujin II CPU Cooler EVA edition. Thing is, now, when I start Aida, it seems to lock the CPU Package Temp reading. After that, it never varies. In a couple of cases it got locked at 82c meaning my fans went on hard and stayed on hard, despite the fact that that definitely wasn't the real current temp for more than a moment (as I was able to see in Armoury Crate, I believe). I can't be certain if it is the update that caused the Temp freeze, or just a consequence of me updating today per your instructions and configuring my sensorpanel. I have had to disable Aida because of this issue for now. I guess I will try it every so often and see if this issue is resolved, but if it happens, it pretty much necessitates a reboot, because shutting down Aida once it happens doesn't resolve it, the package temp as reported by the cooler, and the resultant fan speeds, stay locked.

Hello, I recently bought an Asus Crosshair x670e Extreme, which comes with an Aida64 Extreme subscription, and indeed it pretty much installed itself. My problem is that it is version 6.60.5901, from back in December 2021, and it doesn't fully recognize my hardware. Using the Check for Updates function in the About screen doesn't work (there is a "No variants found" error), then says it's up to date. I would just download the newer version from the website, but it calls it a "Trial version", and I am afraid that if I install that over this Asus-installed version I'll lose the license. If I had a product key I'd go ahead, but without it I'm not willing to take the risk. What can I do? Thanks for any help.