← All posts 中文版 →

Active vs Passive Cooling: A Commonly Misunderstood Windows Power Setting

You're halfway through a video call. The room goes quiet, and right then your laptop fan roars to life like a tiny hairdryer, loud enough for everyone on the call to hear. You might wonder: does it need to go in for repair?

Usually, it isn't broken. Windows has a setting called "System cooling policy" that makes this call for you: when things heat up, does the fan get loud first, or does the chip slow down first? What this setting does is easy to get backwards.

This post covers three things: what this setting actually controls, which machines it makes a difference on, and whether it overrides the BIOS fan curve you tuned.

Heat has two exits

When a chip heats up, the system has exactly two moves: move the heat away faster (spin fans up), or make less heat (run the chip slower). The cooling policy is the priority order between them:

  • Active: fans first. Windows spins the fans up to keep clock speeds from dropping. Performance holds up better; the cost is fan noise.
  • Passive: slowdown first. Windows lowers CPU speed to produce less heat, and saves the fans for last. It's quieter; the cost is a lower top speed.

In plain terms: Active = "loud before slow", Passive = "slow before loud". Passive suits a PC that's downloading files overnight or sitting next to you during a call, and it's also the better default. Active suits a PC racing to finish a render.

Picture a runner getting too hot. Active cooling is "keep up the pace and crank the fan blowing on you" — you finish fast, but the fan gets loud. Passive cooling is "just jog a bit slower so you stop overheating" — you stay quiet and comfortable, but you arrive later. Either way, the fan still comes into play; the only difference is which you reach for first: the fan or a slower pace.

Where to set it

GUI: Control Panel → Power Options → Change plan settings → Advanced → Processor power management → System cooling policy (separate values for plugged-in and on-battery). Command line: it's the SYSCOOLPOL setting under powercfg's processor subgroup. Or let a power mode carry it — more on that in "The part worth automating".

The fine print: where this setting actually works

The cooling policy only takes full effect where Windows itself manages the fans — which in practice means laptops and OEM prebuilts whose firmware exposes thermal control to the OS through ACPI. On a typical self-built desktop, your fans answer to the motherboard's BIOS fan curve. Windows never touches them, so the policy's "active" option has no fans to control; the part that still works is the throttling side, and you control that more directly with a CPU maximum cap. If you're tuning a self-built desktop for quiet, the cooling policy is a supporting actor — the CPU cap and GPU power limit are the leads.

"Will it fight my BIOS curve or Afterburner?"

A reader testing PowerDoze asked exactly this. They had spent hours tuning a BIOS fan curve and an MSI Afterburner profile and didn't want any setting to overwrite them. Short answer: no, it won't fight either one, for two reasons:

  • BIOS fan curves are never touched. Windows' cooling policy (and PowerDoze) works on the heat-production side: CPU clocks, caps, boost. Your fans keep following the BIOS curve. Because less heat reaches the sensors, the same curve simply spins the fans slower.
  • Afterburner coexists, with one shared knob. Fan curves, core/memory offsets and voltage tuning in Afterburner are never touched by PowerDoze. The only overlap is the GPU power limit: both tools can set it, and the last writer wins. The clean setup: if Afterburner manages your GPU, leave the GPU power field empty in your PowerDoze modes — empty means "don't touch the GPU at all".
Your BIOS fan curve is a thermostat: "if it gets this hot, blow this hard." The cooling policy doesn't touch the thermostat; it just turns down the heater. Less heat reaches the room, so the same thermostat switches the fan on less often by itself.

The part worth automating

The cooling policy is a trade-off, which means the right value changes with context: passive at midnight, active when you're rendering, passive during meetings, active in games. It's not a setting you'll want to switch by hand several times a day. In PowerDoze, cooling policy is one of the settings in a power mode. A "Quiet" mode includes passive cooling plus a CPU cap, and a "Full Power" mode uses active cooling with no limits. The automation (schedule, fullscreen detection, per-app rules) picks the mode, so the policy follows your day without you having to remember it.

The short version

Active = loud before slow. Passive = slow before loud. Fans spin in both. It makes the most difference on laptops and OEM machines; on self-built desktops, the CPU cap is what actually does the work. And the cooling policy won't overwrite your BIOS curve or change your Afterburner profile.

Get PowerDoze from the Microsoft StoreGet PowerDoze from the Microsoft Store

Nisonxi

I'm Nisonxi, the developer behind PowerDoze. I built it because my own Windows desktop idled all day at near-full power and no existing tool could read the situation and switch on its own. This blog is my notebook from the journey.

About the author and PowerDoze →