What is the difference between Active and Passive cooling policy in Windows?

Windows offers two cooling policies in its power plan settings. Active cooling ramps up fan speed first to keep the CPU cool, prioritising low temperatures over noise. Passive cooling throttles the CPU's clock speed first before spinning up fans, trading a small amount of peak performance for significantly less fan noise. Switching to Passive is one of the quickest software changes you can make to quiet your PC at idle without buying any new hardware.

How do CPU power limits reduce fan noise without hurting performance?

Modern CPUs are allowed to boost far above their base TDP for short bursts, generating sudden spikes of heat that trigger fan ramp-ups. By capping the processor maximum state (e.g. from 100% to 80–90%) or setting a sustained power limit, you reduce the peak wattage the CPU ever reaches. In practice, lightly-threaded tasks like browsing and video calls are barely affected because they rarely saturate the CPU, while fan noise drops noticeably since the heat spikes that triggered the fans are gone.

Can I limit GPU power to make my PC quieter?

Yes. NVIDIA cards expose a power limit via nvidia-smi, and AMD cards have a similar cap in their driver settings. Reducing GPU power by 10–20% typically cuts temperatures and fan noise substantially at idle and during light workloads, while losing only a few percent of peak frame rate in games. For everyday desktop use where the GPU is mostly idle, this is an easy win: the GPU barely notices the cap, but the fans stay quiet.

Does lowering the processor maximum state affect game performance?

It depends on how low you go and what you are playing. Dropping from 100% to 90% usually has negligible impact on most games because they do not fully saturate all CPU cores. Going below 80% can start to cause frame-rate drops in CPU-bound titles. The practical approach is to set a lower limit in a quiet power plan for everyday use, and switch back to an unrestricted plan when gaming — something PowerDoze can automate by switching profiles based on detected activity.

Screaming Fans Aren't a Cooling Problem — They're Unmanaged Watts: Quiet Your PC with Software

You're on a video call, sitting still, doing nothing demanding — and your PC's fans suddenly spin up loud, like a hairdryer. Same thing all summer: loud while you read a webpage, then quiet, then loud again for no obvious reason.

So you start pricing coolers. But here's the twist: the fan isn't the problem, and you probably don't need new hardware. That noise is heat, the heat is watts, and the watts are just a setting Windows is happy to push to the maximum — until you tell it not to.

This post shows you the three switches that quiet a PC at the source, then how to make them turn on by themselves so you never babysit them again.

Why your fans are loud

Your CPU and GPU convert electricity into computation, and almost all of it ends up as heat. Fan controllers react to temperature — more watts, more heat, more RPM, more noise. The chain runs in one direction, which means you can intervene at the start of it instead of the end:

Hardware route: same watts, same heat, carried away more efficiently (and more quietly, if you buy well).
Software route: fewer watts, less heat, less for the fans to do — at the cost of some peak performance you may not have been using anyway.

A loud fan is like a kitchen range hood: the bigger the flame and the more smoke, the harder and louder it has to run. Most people reach for a stronger hood (better cooling), but the simpler move is to turn the flame down first — less smoke, and the extractor stops straining. The fan was never the source of the noise; it's just cleaning up the heat the watts created.

The three settings that quiet a PC

Cooling policy → passive. Windows' system cooling policy (SYSCOOLPOL under powercfg, or "System cooling policy" in advanced power options) decides whether Windows spins fans up first (active) or slows the CPU down first (passive). Passive is the most direct "be quiet" switch the OS has — on machines where Windows actually manages cooling, which mostly means laptops and OEM prebuilts. On a typical self-built desktop, fans follow the motherboard's BIOS fan curve and this setting does little; there, the CPU and GPU caps below are what move the needle.
Cap the CPU's maximum state. powercfg /setacvalueindex scheme_current sub_processor PROCTHROTTLEMAX 70 + powercfg /setactive scheme_current caps the CPU at 70% — anything below 100% kills turbo boost, and 70% trims sustained clocks a bit further on top. (On a laptop, repeat with /setdcvalueindex for the on-battery profile.) Turbo is where the disproportionate heat lives: the last 20% of performance costs far more than 20% of the watts. Browsing, video, and office work won't notice.
Power-limit the GPU. nvidia-smi -pl 150 (admin shell) caps an NVIDIA card's draw — check your card's allowed range with nvidia-smi -q -d POWER. Resets at reboot, so it needs a startup task.

Turbo boost is like flooring it from 110 to 130 km/h at the end of a drive: barely any faster, but the fuel use spikes and the engine roars loudest. That's exactly where a CPU's disproportionate heat hides — the last 20% of performance costs far more than 20% of the watts and noise. Cap that slice off (set it to 70%) and browsing, video, and typing feel identical, but the fans go quiet.

Bonus in summer: every watt you don't burn is heat your room — and your air conditioner — doesn't have to deal with, so each watt you cut comes off your AC's workload too.

The problem you'll hit within a week

These settings are static, and your life isn't. The cap that makes the machine blissfully silent during a meeting makes it sluggish when you render video at 4 PM and infuriating when you game at 9 PM. So you toggle settings back and forth for a few days, then give up and leave it loud. The settings were never the problem — the switching was.

Quiet when it should be, fast when it must be

This is the exact problem shape PowerDoze handles. You bundle the three knobs above (plus screen timeout) into power modes — say, a "Quiet" mode with passive cooling and capped CPU/GPU, and a "Full Power" mode with everything open — then let the automation pick the right one:

Schedule — Quiet overnight and during meeting-heavy mornings; Full Power for your afternoon work block.
Away mode — you leave the desk, it goes quiet; you come back, it restores instantly.
Fullscreen and per-app detection — a game or render job in the foreground gets Full Power without you touching anything, regardless of what the schedule says it's time for.

The result is a machine that's silent in the moments you care about silence and fast in the moments you care about speed — without you ever opening Control Panel again. (Schedules, two power modes, fullscreen detection, and the GPU power-limit knob are free; away mode and per-app rules are part of Pro.)

When software can't help

Honesty corner: if your fans roar at idle with low temperatures, your problem is mechanical — dust-clogged heatsinks, a dying fan bearing, or a badly configured BIOS fan curve. No setting fixes physics; clean it or replace the part. Likewise, a thin laptop under sustained 100% load will always need its fans. Software tuning shines in the most common case: a machine that's louder than its actual workload justifies, because nothing ever told it to calm down.

Download PowerDoze free →

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 →