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

Switching off ADLXWrapper crashes FanControl #2717

Closed
JN848433 opened this issue Sep 8, 2024 · 14 comments
Closed

Switching off ADLXWrapper crashes FanControl #2717

JN848433 opened this issue Sep 8, 2024 · 14 comments

Comments

@JN848433
Copy link

JN848433 commented Sep 8, 2024

I thought I'd open a separate ticket for this as it is a separate bug. Not a big issue as restarting FanControl solves the issue.

Switching ADLXWrapper OFF in settings throws the following error when the refresh of the sensors is done afterwards in Windows Event log.

Anwendung: FanControl.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: System.AccessViolationException
bei ADLXWrapper.Bindings.ADLXPINVOKE.delete_ADLXHelper(System.Runtime.InteropServices.HandleRef)
bei ADLXWrapper.Bindings.ADLXHelper.Dispose(Boolean)
bei ADLXWrapper.Bindings.ADLXHelper.Finalize()

@Rem0o
Copy link
Owner

Rem0o commented Sep 9, 2024

Update to V201 and see if this still happens?

@Rem0o
Copy link
Owner

Rem0o commented Sep 12, 2024

@StainlessSteele
This doesn't look like an EventViewer crash report.

@JN848433 Did you update to V201?

@jilherme
Copy link

from event viewer:

Application: FanControl.exe
CoreCLR Version: 8.0.824.36612
.NET Version: 8.0.8
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Stack:
at ADLXWrapper.Bindings.ADLXPINVOKE.delete_ADLXHelper(System.Runtime.InteropServices.HandleRef)
at ADLXWrapper.Bindings.ADLXPINVOKE.delete_ADLXHelper(System.Runtime.InteropServices.HandleRef)
at ADLXWrapper.Bindings.ADLXHelper.Dispose(Boolean)
at ADLXWrapper.Bindings.ADLXHelper.Finalize()

image

portable version just crashes, but the installed version (v202) gives me the error from the image

@Rem0o
Copy link
Owner

Rem0o commented Sep 15, 2024

@jilherme do you have an AMD GPU at all with Adrenaline installed?

@jilherme
Copy link

@jilherme do you have an AMD GPU at all with Adrenaline installed?

I have an AMD iGPU, with latest adrenalin drivers installed. ryzen 7 7700x.

@Rem0o
Copy link
Owner

Rem0o commented Sep 15, 2024

Right, but from 202, do you get the hard crash still or just the popup error? If you only have an iGPU you can disable ADLX all together, it's meant for dedicated gpus.

@jilherme
Copy link

Right, but from 202, do you get the hard crash still or just the popup error? If you only have an iGPU you can disable ADLX all together, it's meant for dedicated gpus.

I'm in bed right now, but I think I can't adjust any settings. If I remember correctly the app crashes after a couple of seconds

@TheSangral
Copy link

Right, but from 202, do you get the hard crash still or just the popup error? If you only have an iGPU you can disable ADLX all together, it's meant for dedicated gpus.

I only got the popup in 201 and now in 202 I get hard crashes with this error of the app. I don't know what the heck happens here, I didn't change any settings, I don't have an AMD GPU at all, this just appeared after updating to 201 and I don't know where to disable this, I looked everywhere and I have zero plugins installed. It's driving me mad.

@Senaxx
Copy link

Senaxx commented Sep 16, 2024

Same issue here.

Clean windows install - AMD chipset drivers installed. I'm getting a crash on startup with ADLXWrapper message shown here. It's the same screen as @jilherme posted.

Log just says:

9/17/2024 1:34:50 AM: Initialization failed. Retry count (2) exceeded.
9/17/2024 1:35:09 AM: Initialization failed. Retry count (2) exceeded.
9/17/2024 1:36:10 AM: Initialization failed. Retry count (2) exceeded.
9/17/2024 1:36:56 AM: Initialization failed. Retry count (2) exceeded.

Downgraded to v200 and it works.

AMD 7800x3d
4090

@DrBoiko
Copy link

DrBoiko commented Sep 17, 2024

Same issue, started to occur after I updated to 202 just now. Log just says:

9/17/2024 7:34:43 PM: Initialization failed. Retry count (2) exceeded.

@etherealremnant
Copy link

Same issue here.

Clean windows install - AMD chipset drivers installed. I'm getting a crash on startup with ADLXWrapper message shown here. It's the same screen as @jilherme posted.

Log just says:

9/17/2024 1:34:50 AM: Initialization failed. Retry count (2) exceeded.
9/17/2024 1:35:09 AM: Initialization failed. Retry count (2) exceeded.
9/17/2024 1:36:10 AM: Initialization failed. Retry count (2) exceeded.
9/17/2024 1:36:56 AM: Initialization failed. Retry count (2) exceeded.

Downgraded to v200 and it works.

AMD 7800x3d 4090

Thanks. V200 worked for me with my Ryzen 7 9700X that was crashing too.

@Rem0o
Copy link
Owner

Rem0o commented Sep 19, 2024

See V203

@JN848433
Copy link
Author

JN848433 commented Sep 19, 2024

V203

Yes and for me it all works on V203. Thank you for your dedication!
I was in vacation - sorry for the late reply.

@JN848433
Copy link
Author

Issue closed as error is fixed.

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

7 participants