Curves randomly disappearing after some time

[Jonny11bonk]

I noticed that my set curves for my GPU and chassis fans went missing. (That's why I was getting 90°C on my GPU while in the game)

I had to set them back manually. It didn't set back from the config after restarting the Fan Control.
When the Curves were set to None, they were controlled by the default BIOS set fan curves. The GPU fans are connected to the motherboard instead of the GPU's fan connector. (There was no PWM control on the GPU's fan header)

It happened again while I was writing this.

I noticed this issue since V111 was released. I had no problems with the V109.

[Rem0o]

Can you try and elaborate steps to reproduce this?

[Jonny11bonk]

Can you try and elaborate steps to reproduce this?

I start the Fan Control as normal every time my PC boots. It automatically loads the configs. Everything works as usual. After "9 hours" of PC being idle or downloading some stuff, I noticed the curves I've set in the Controls were set to None for some reason.

My solution: assign the curves back or load the config again.

It's been the 3rd time I noticed that the Curves were gone.
I can put here my configs if needed. This started happening since the update. I don't think it's because I've set my fans as PWM in the BIOS settings. (As Gigabyte has a weird glitch that the system freezes for a second every few minutes, I think the cause is that it checks the fan control type whether it's a DC or a PWM speed control)

Quiet.json.txt
I hope the link to the file works, ben using the Github for just 6 months.

The "Back" and "Front" didn't have any Curve assigned. Same for the "GPU", it happened only one time, when my card almost melted along with its Low Profile heatsink. Poor GTX 1650 😭.

[Rem0o]

After "9 hours" of PC being idle or downloading some stuff, I noticed the curves I've set in the Controls were set to None for some reason.

That's not really what I meant for "steps to reproduce" 😅. I meant steps I can do myself and try to get the same issue locally. There is nothing wrong or weird about your config. By the way, the curves gets cleared off WHILE fancontrol is running in the backgroup? No sleep?

Do you have a log.txt file?

[Jonny11bonk]

After "9 hours" of PC being idle or downloading some stuff, I noticed the curves I've set in the Controls were set to None for some reason.

That's not really what I meant for "steps to reproduce" 😅. I meant steps I can do myself and try to get the same issue locally. There is nothing wrong or weird about your config. By the way, the curves gets cleared off WHILE fancontrol is running in the backgroup? No sleep?

Do you have a log.txt file?

I have the Fan Control in the Program Files, but the Read/Write works as normal. Here is the image after running my PC for 10 hours today. I just noticed the Curves have disappeared. I tried to look into the log.txt, but the newest log was from 4.3.2022. When closing the Fan Control, It even asked me if I want to save changes. I didn't make any changes to my config at all.

[Rem0o]

I know the effect. What I want is stuff to help me diagnose the cause of the problem. Same 2 questions:

1. Do you have a log.txt file in your fan control directory that you can share here.
2. During that 9h/10h, does your computer goes to sleep/wake?

[Jonny11bonk]

I know the effect. What I want is stuff to help me diagnose the cause of the problem. Same 2 questions:

1. Do you have a log.txt file in your fan control directory that you can share here.
2. During that 9h/10h, does your computer goes to sleep/wake?
   log.txt

1. the log file
2. No, my motherboard doesn't even support the sleep function. It's just idle at a locked screen (Win + L)

and a file just created in the folder while I restarted the Fan Control called CACHE, has something saying about disabling the pop-ups in my Quiet.json config file

[Jonny11bonk]

After updating to the V119, it started happening again.

[Jonny11bonk]

Update: It's still happening even after putting the Fan Control folder somewhere else like on a desktop. Version 120.

[Rem0o]

My guess is that it's the same issue as #1008 which has been fixed.

[Jonny11bonk]

I hope so.

…

On Tue, Aug 23, 2022, 15:04 Rem0o ***@***.***> wrote: My guess is that it's the same issue as which has been fixed. #1008 <#1008> — Reply to this email directly, view it on GitHub <#845 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATVFHXXL6LIEVYODY4T6EQLV2TD7FANCNFSM5XVNS7NQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>