-
-
Notifications
You must be signed in to change notification settings - Fork 468
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 Freezing and becoming unusable #2959
Comments
Hi, Your log is filled with "System.Windows.Media.Composition.DUCE.Channel.SyncFlush()" errors, which is an infamous WPF render thread bug/crash, most commonly caused by GPU problems/driver issues. What driver version are you running? |
Hi there, Cheers for getting in touch. im currently running Nvidia '560.94', Which i know is quite a far ways back. but the time i wanted to upgrade there was alot of issues with the driver so i had to wait a bit. just forgot to check. So il try get those updated later today. |
I also noticed this after my upgrade to v214. The app would load, but stay in a darkened state that wouldn't respond to user input (almost like the backdrop of when a modal is open, but no modal or popover was visible). To be fair, I had just run a Windows update, but I'm on the most recent Nvidia GeForce GPU drivers (
Here's my log file: |
Seems like a .Net dll missing from the logs |
Yea, which makes sense given the .NET update, so you can likely just ignore my bit. Sorry about that. |
Describe the bug
As of the recent update for some reason the program just outright stops responding to user input. even tho the window is still technically active. i cant click anything and closing the tab does nothing. need to go into tskmgr and forcefully close the app that way and re-launch it. This problem is most commonly occurring right after closing a game.
This is as of the recent update on v214
https://github.com/user-attachments/assets/bf3d794e-7923-4159-94d0-4190a51d6823
Log file
log.txt
Hardware: Desktop
i5 8600k
16gb
RTX2060
The text was updated successfully, but these errors were encountered: