New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update broke sensor detection. #2465
Comments
With my 7900XT, after update (187) for gpu sensors it only shows the VRSoC temp, where before it showed core and hot spot. Reverted (to 186) and it was fixed. Windows 11, Powercolor Hellhound 7900XT, 24.3.1 drivers. |
I lost all my custom fan names and paired sensors with update 187. |
After digging around a bit, I saw your repo for LibreHardwareMonitor had a resent commit 2 days ago and you added that update to v187, I suspect something went wrong in the d22cd1d commit. |
Similar issue, RX 6800, gpu core and liquid showing temps >3000°, gpu hot spot showing a sensible value. Happy to do more to diagnose/whatever, but for now I've just changed the sensor used to the hot spot. |
Yeah there is a new method implemented to get sensor values, but there might be a bug in there. I compiled this: https://github.com/GPUOpen-LibrariesAndSDKs/display-library/blob/master/Sample/PMLog/PMLog.cpp If anyone here is willing to run it and show the output, might be of some help. |
I've compiled a test build of LibreHardwareMonitor with a possible fix for the issue. If the users with RX 6000 cards can test, will be useful (LibreHardwareMonitorLib.dll included in zip). The temps should be shown correctly with this build. A test copying the new |
@Rem0o
@epinter I swapped the LibreHardwareMonitorLib.dll file from LHM to Fan Control v187 folder and ran the software again, and it seems to be working fine now. |
@iDumle Anyway, if the test build shows the values correctly, some boards of RX 6000 series doesn't work with pmlog feature. I will send a PR to LibreHardwareMonitor excluding these boards and use the old method. It's weird that pmlog worked for me with a RX 6750 XT. Thanks for the test and feedback! |
The saying "If it ain't broken, don't fix it" comes to mind :) that said if you at some point decide to give the new method a once over again I'd be happy to test it out. |
I'm having the same kind of issue with my 7800 XT, sensors value are corrupted, so fancontrol looses its mind and ramps the fans all the way up. Went back to 186 and no more issue. |
7800 XT doesn't have problems with the build LibreHardwareMonitor fancontrol 187 is based, actually the sensors of 7800 was fixed by that build. Try the build I posted above. |
@iDumle |
@epinter So something seems to gets missaligned from LHM to Fan Control. |
Thanks for the test! So LHM is working. |
The downloadable LHM is not the most up to date version. I'm using the latest commit since I'm compiling it myself. |
I'll try and make a detailed timeline of my use of the software, maybe it can shine some light on something.
What the actual root course for the odd behaviour I experienced is, I can only speculated on, It could be a windows thing, or maybe related to the fact my first version was v146 and all updated was done in software and never redownloaded from repo, or it might be that I was just unlucky. What I do know is that I have done a new install from a newly download zip of v187 from the Github repo and unpacked it to its own folder on my desktop and loaded up my old config file, and it's working fine. I don't know if this is helpful at all but now you have it. |
Something is still wonky on the v187 release for me, I just had a cold boot with the new fresh install that I though was working, and now the temp are frozen and incorrect. |
|
I don't understand... I'm running on 7800 xt for 2 weeks, no problems. I will look the code again, but I don't know why there's invalid data with some cards. What I see in common on @iDumle and @axel-lebourhis screenshots is the "GPU Memory" temperature added. The only temperature sensors on these cards are "GPU Core" and "GPU Hot Spot", as far as I know. |
@axel-lebourhis When you have time, can you try to run and tell me what happens ? I'm trying to isolate some code path. |
Can you try this ? |
@epinter I tested the LHM and I have two results for you. This one I did right after downloading your LHM, and it's clearly broken, the computer had been running for about 2 hours. I then did a reboot and had LHM boot with window, and I got a different result, ran overwatch and it responded fine. I then did a third reboot with start with windows disabled and it mirrored the 2nd test and was working fine too (I didn't screenshot it). I hope this is informative enough, please tell me if you want additional data. |
|
@iDumle |
You're welcome I'm happy to help, I do hope this will be it for this issue, and thank you for doing the work, your contribution enable us amd users to keep enjoying the software. |
Latest LHMLib is in V189 |
I think this could be something in LHM yet. If you want to help, I can send you a build of LHM for you to collect the report. I see you have a RX 5700, we didn't test with series 5000 yet, maybe there's some adjust to make. |
Sure, send it but I will need instructions :D not as well versed in this as the other guy |
:) |
WhenItsNOTWorking.Report.txt |
Great, thanks for the reports. Everything looks ok on both reports, the sensors found are consistent, also the data in each of the sensors. I don't see problem in LHM, let's way @Rem0o update FanControl. I was looking specially two things: |
FanControl V189 uses the latest commit |
md5 of V188 and V189 are the same:
EDIT: By the file properties, the commit is the LibreHardwareMonitor/LibreHardwareMonitor@331d334. After this commit, I've sent 3 updates. |
@Rem0o @epinter |
V190 lost my GPU sensors. Swapping in LHM files from V189 fixed it. |
What gpu you have ? Users tested AMD RX series 5000, 6000 and 7000, all of them worked as far as I know. Test the latest nightly build of LHM: https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/actions/runs/8958653644/artifacts/1474376834 |
My card is an AMD R9 280x. Adding that latest LHM to Fan Control had the same problem as v190. Got the same could not find expected sensors error again. The ADLX plugin didn't help either. |
Must be the same problem of RX 400 and RX 500 series. Try this build of LHM, tell me if it works. Download links at the end of the page, LibreHardwareMonitor-net472 is full LHM, others are the libraries for other .net versions. https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/actions/runs/9085676231 |
That LHM works again! |
Nice , good to hear that! |
As far as I'm considered my issue has been resolved with v190, and if the new ones in this issue have made their own, I will close this. |
Describe the bug
Update V187 broke sensor detection for GPU Core for my AMD Radeon 6650 XT graphics card and it's now showing an incorrect/frozen value.
On version 186 the setup was working fine, and the software had no problem detecting the GPU Core sensor, I'm now using GPU Hot Spot instead as that seems to be updating its values.
Right after update the value was stuck at 468 'c, I then tried restarting twice after the update and the error persisted after reboot though GPU core showed a value of 0 'c and then subsequently 8 'c.
I have tried Refresh sensors detection, but it didn't change a thing it's still stuck on the same value.
Is there a log.txt file next to FanControl.exe with recent date entries?
The Error log show no resent entry, though there is one from back in January I suspect it's unrelated, but just in case I'll post it.
log.txt
Relevant hardware specs and setup
The graphics card is a ASUS Radeon RX 6650 XT DUAL OC - 8GB, and I am running window 10, and the newest graphics drivers 24.3.1.
And here is a picture of the whole Fan Control Setup.
The text was updated successfully, but these errors were encountered: