When HWInfo64 was started after FanControl, it would cause issues with FanControl's ability to, well, control fans. When I had the issue, yes, the start order of FanControl and HWInfo64 did matter in my case. So from my perspective the issue is not clear-cut. The problem PP2012 describes is something that I was able to observe on my system as well (but was fixed for me by updating both HWInfo64 and FanControl, or by magic I don't understand). I have observed LHM clashing with other hardware monitoring tools in the past intermittently, but I never observed HWInfo clashing with others. To clarify: I'm not affiliated with FanControl but am following the issue thread on github. They will return to 0% if the temperature is 65 C or less.First of all: Thanks Martin for responding and even showing interest in this issue at all, because it is quite obscure and only shows up for a small portion of users. For example, in my curves, the fans will always spin at 100% speed if the temperature is 95 C. When the minimum or maximum temperature is reached for both of these cards, their corresponding speed will trigger. Next, you need to set a minimum speed and a maximum speed. Basically, you're telling the app, "I want my temperature to never exceed X, but it's okay if it never goes below Y." Both cards require you to set a minimum and a maximum temperature. First, let's focus on the Target and Linear cards since they're very similar to each other. I've already configured these cards to my personal preference. For case fans, you can use the hottest motherboard, CPU, or GPU sensor as it doesn't matter too much. Before you do anything, you need to select a temperature source.įor CPU fans, use one of your CPUrelated sensors (pick the one with the highest temperature to be safe).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |