Skip to content
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

Closed
thegame4craft opened this issue Jul 18, 2024 · 4 comments
Closed

Fancontrol chrashes with "Not Responding" #2614

thegame4craft opened this issue Jul 18, 2024 · 4 comments

Comments

@thegame4craft
Copy link

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.]

@thegame4craft thegame4craft changed the title Fancontrol chrashes with "No Responding" Fancontrol chrashes with "Not Responding" Jul 18, 2024
@Rem0o
Copy link
Owner

Rem0o commented 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?

@thegame4craft
Copy link
Author

thegame4craft commented Jul 26, 2024 via email

@Rem0o
Copy link
Owner

Rem0o commented Jul 26, 2024

Polaris (RX 500) gpus are not supported by ADLX. However you shouldn't get a "hard crash". Anything in EventViewer?

@thegame4craft
Copy link
Author

thegame4craft commented Jul 26, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants