Home > Support > Troubleshooting

Core Temp Troubleshooting

Almost every report that reaches the support forum falls into one of a handful of categories. Work through the one that matches your symptom; if none of it helps, the support forum is the place to post, and a note of your processor model and Windows version saves a round trip.

Before anything else: run the current version

A large share of the issues people describe were fixed in a later build. The release notes on the home page list what changed, including fixes for temperatures that stopped updating after a restart or sleep on Ryzen systems, and for the program appearing not to respond around start-up. Update first, then re-test.

No temperatures at all

• The driver was not allowed to load. The sensor is read in kernel mode. Start the program with administrator rights and approve the prompt.
• Another monitoring tool is holding the sensor. Vendor utilities, overclocking suites and RGB software often talk to the same interface. Close them and try again with only Core Temp running.
• The processor is very old or very new. Chips without a digital thermal sensor cannot report per-core values at all, and a brand-new platform may need a newer build.

Readings freeze after sleep or a reboot

This was a known defect on Ryzen systems and is addressed in the current release. If it still happens after updating, note whether it follows hibernation, sleep or a full restart — that distinction is the most useful thing you can include in a report.

The program stops responding at start-up

Update to the latest build, which contains a fix for exactly that behaviour. If it persists, start Windows with third-party services disabled and add them back in groups; crashes traced back over the years have usually come from another tool poking at the same hardware interface.

Nothing in the notification area

Windows hides tray icons by default. Open the taskbar settings and set Core Temp to always show. If the icon is present but empty, check inside the program which sensors are selected for display — the tray configuration was reworked recently and existing colour settings were reset when that happened.

The numbers look wrong

One core much hotter than the others

Normal. A single-threaded task loads one core; the rest idle. Watch it under an all-core workload before concluding anything.

Values that are implausibly low or high

Some processor families report an offset rather than an absolute temperature, and a few early models were specified inconsistently by their own manufacturer. If your model is affected, treat the trend as reliable and the absolute figure as approximate.

A different tool shows a different number

Expected. Other programs often show a board-level package sensor, not the per-core digital sensor, and they poll at different moments. Compare like with like — the temperature guide explains what the per-core value represents.

Install and security warnings

Verify the checksum published on the download page against the file you saved. A match means the file is the one that was published; a heuristic warning from a scanner is a reaction to the driver, not evidence of tampering.

Uninstalling

Remove it like any other program, from Programs and Features in Windows. The portable build leaves nothing behind — deleting its folder is enough.