Every modern processor has a survival reflex: when it gets too hot, it cuts its own clock speed to avoid cooking itself. The PC does not crash - it just quietly becomes a much slower computer, often exactly ten minutes into real work. This page is the test that catches it in the act, with two numbers moving together as the only witness you need.
The symptom pattern is your first clue, and it is oddly specific: fast from a cold start, slow after sustained work, fine again after a rest. Software faults do not care about temperature; this one does. The test needs Task Manager's Performance tab for clock speed and a free hardware monitor such as HWiNFO for temperature - then one honest workload and five patient minutes, as the example reading shows.
Open Task Manager (Ctrl + Shift + Esc), Performance tab, CPU page. Note the Base speed printed there - that is the speed your processor promises. Beside it, the live speed figure moves constantly; that is normal. Also open your temperature monitor and find the CPU package temperature.
Take a cold reading first: start the PC, let it idle five minutes and note idle temperature and idle clock. Every verdict in this test is a comparison - cold versus hot, idle versus load.
Start the workload that makes the PC feel slow - the game, the export, the heavy spreadsheet, or simply many programs at once - and keep it running for at least five minutes. Watch the pair:
That synchronised pair is the proof. High temperature alone, with the clock holding at or above base speed, is a hard-working PC coping fine - no conviction.
On a laptop, run the test twice: once on a hard desk, once where the user actually works - a bed, a lap, a stand that blocks the vents. Thin machines throttle by design when their air is choked, and the test often re-convicts the furniture instead of the hardware. Also compare plugged in versus battery, since many laptops cap power hard on battery - that is a power limit, a cousin of throttling with a different fix, and honest testing names it correctly.
On a desktop, note the fan behaviour through the test: roaring at full speed with temperatures still climbing points at dust, dead airflow or dried thermal paste working against it - but naming the exact cooling failure is the fixer's job after this test hands over its verdict.
In the video the clock speed collapses live under load - watch it happen before you believe any forum thread about it.
Watch Full VideoFor most modern CPUs, no - many are designed to work in the 80s and even low 90s under full load, and they hold their clock speed there. Heat becomes your diagnosis only when the clock speed falls well below base speed at the same time. Read the pair, not the thermometer alone.
Likely a power limit rather than a thermal one: a laptop on battery, an aggressive power-saving plan, or VRM limits on the motherboard. The symptom feels identical - the PC slows itself - which is exactly why the temperature half of this test matters before choosing a fix.
That daily rhythm is the classic throttling story: cool room and cold machine in the morning, heat soaked in by afternoon. Run the five-minute load test in the afternoon, when the complaint is real, and compare against a cold morning reading.