Problems · How to check
How do I check if my Windows laptop is thermal throttling?
Two methods, pick by circumstance. With install rights: HWiNFO's sensor view under load shows core clocks falling, temperatures pinned at the limit, and explicit thermal-throttling flags flipping to yes. Without install rights: a sustained-load browser test, a throughput curve that slides over minutes IS throttling, drawn as a picture.
Either way, the answer is the same shape: full speed while cold, less once hot. What differs is the evidence you take away: sensor numbers, or a measured curve.
First, notice when it happens
The causes, ranked
1. Method 1: HWiNFO sensor view (the full picture)
most commonHow to confirm it
Install HWiNFO (free), open Sensors, run any heavy sustained load. Watch three rows: CPU core clocks, CPU package temperature, and the 'Thermal Throttling' Yes/No flags. Clocks stepping down while temperature holds at ~95–100°C with flags on Yes is throttling, confirmed at the source.
The fix
Note the sustained clock after five minutes. That figure, not the boost number, is your machine's working speed. Repeat after any cooling fix; the delta is the fix's value.
2. Method 2: the browser curve (no install, no rights)
most commonHow to confirm it
On managed or borrowed machines where installing is impossible: a sustained browser test samples throughput continuously across minutes of full load. A slide is throttling; a flat line is a machine holding its speed; the decay percentage is throttling's cost in one number.
The fix
This method also produces a shareable report, useful when the next step is convincing IT, a seller or a repair shop that the slowdown is real.
3. Task Manager alone: the rough check
commonHow to confirm it
Performance tab, CPU: watch the speed figure during minutes of heavy load. Falling well below base clock under load suggests throttling: roughly, since Task Manager averages and hides per-core detail.
The fix
Fine as a first look; graduate to method 1 or 2 before spending money on the answer.
4. Reading the result: slide, step, or sawtooth
commonHow to confirm it
Slide = heat winning gradually (dust, paste, blocked vents). Clean step at a fixed time = power budget expiring, not heat. Sawtooth = cycling at the limit: throttle, cool, boost, repeat, common on laptops with aggressive profiles.
The fix
Each shape has its own fix chapter: slides respond to cleaning, steps to power settings, sawtooths to either. The shape is the diagnosis.
Measure it instead of guessing
Method 2 is this site: the standard run holds 45 seconds of all-core load, the deep run three minutes, throughput sampled throughout, and the report names the shape and the decay percentage. It exists precisely for the machines where HWiNFO is not an option, and as the before/after evidence when you fix what you found.
What software cannot tell you here
- The browser method shows no temperatures, that is physics of the sandbox, and any page claiming degrees is inventing them. For the number in Celsius, HWiNFO is the tool.
- Neither method names the mechanical cause: dust versus paste versus vents takes a screwdriver.
Asked, in people’s own words
- What temperature does thermal throttling start at?
- Most modern mobile processors hold boost until roughly 95–100°C at the core and then regulate there, by design. The number varies by chip and maker's tuning; the behaviour (clocks falling while temperature plateaus) is the universal signature, whatever the threshold.
- Does Windows have a built-in throttling checker?
- Nothing that says it plainly. Task Manager shows the speed figure, and perfmon exposes '% Performance Limit' counters that few people can read. In practice: HWiNFO for sensors, or a sustained measurement for the consequence.
- How long should I run a throttling test?
- Minutes, not seconds, throttling IS a minutes-scale event. Forty-five seconds catches most laptops; three minutes catches nearly all, including heat-soaked and marginal cases. Ten-second benchmarks are how throttling machines get glowing reviews.