Speedfan problem

How rude, you have a serious attitude problem.

Bye!

Sexy isn't rude, he's blunt and to the point.

Perhaps a little older than most on here too, and I don't mean that insultingly. I can be too at times, perhaps offer a little grace there as you clearly seem invested in the forum and I think by and large you're a good addition.
 
I've not seen this behaviour. Whenever I've deliberately killed the app in Task Manager to simulate a crash the fans always immediately ramped up to full speed (this was true of SpeedFan as well as Fan Control).

What fan control programs were you using? Did you have the BIOS fan controls disabled/set to full speed?
Speedfan is my main one. It's too long ago to remember much else I experimented with before settling on that TBH. I'm not sure terminating in Task Manager represents a proper crash really, but haven't exactly researched!

Maybe it's when the app gets unresponsive but doesn't close, rather than crashes and exits. That's ringing a bell.
 
Last edited:
Fan control is by far better than speedfan. this is due to speedfan not having been updated for some years and likely won't see the new controllers in newer motherboards
 
Since these recent issues with FanControl and Windows Defender I've resorted back to using the BIOS to control my fans and it's awful. I have no idea what sensor it's using to control the fan temps but it seems to be unrelated to the CPU temperature...
 
the sudden defender seeing winring0 as a trojan due to it's security risk sucks. never been an issue before until the issue was pointed out by microsoft. now everyone is using bios as its the only thing that works but it only works for cpu and mobo temps and limited control for speeds and ramp up and down intervals. just hope microsoft either allow winring0 or the new driver is implemented and passed via microsoft for future use.
 
Back
Top Bottom