-
-
Notifications
You must be signed in to change notification settings - Fork 442
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
Fancontrol chrashes with "Not Responding" #2614
Comments
thegame4craft
changed the title
Fancontrol chrashes with "No Responding"
Fancontrol chrashes with "Not Responding"
Jul 18, 2024
Built-in ADLX support is new. It is meant for AMD RDNA GPUs. Those throws should never happen in normal operation. There's a problem with the program in your system. What's the setup, parts, OS? |
Hi,I missed to answer you. My pc setup:- AMD Ryzen 5 3600- asus radeon rx 570 oc 8gb I think the rest is irrelevant.
|
Polaris (RX 500) gpus are not supported by ADLX. However you shouldn't get a "hard crash". Anything in EventViewer? |
I don't know if there is anything in the event viewer. Im not at home for about two weeks. But what I noticed is that windows doesn't put "Not Responding" in the window title. The app just doesn't do anything
-------- Ursprüngliche Nachricht --------Von: Rem0o ***@***.***> Datum: 26.07.24 16:40 (GMT+01:00) An: "Rem0o/FanControl.Releases" ***@***.***> Cc: thegame4craft ***@***.***>, Author ***@***.***> Betreff: Re: [Rem0o/FanControl.Releases] Fancontrol chrashes with "Not Responding" (Issue #2614)
Polaris (RX 500) gpus are not supported by ADLX. However you shouldn't get a "hard crash". Anything in EventViewer?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Changing A setting (for me ADLX enable) causes Fancontrol to Chrash. I'm also a .Net developer. I interpret from the log that you are throwing an exception when a sensor isn't found. I dont know how it was in the past, but about half a year ago, fancontrol didn't chrash everytime i open it after changing a setting. I think thats the reason why it chrashes
Is there a log.txt file next to FanControl.exe with recent date entries?
log.txt
Relevant hardware specs and setup
[Laptops and most proprietary pre-built desktops are not supported.]
The text was updated successfully, but these errors were encountered: