Home
Download
Guides
Commercial
How does it work?
Add Ons
Support forum
FAQ
Change log
Developers
CPU list
Contact us

Independent resource
Guides and distributed downloads for Windows users.
Core Temp

Home > Guides > Prepare a Useful CPU Temperature Support Report with Core Temp

Prepare a Useful CPU Temperature Support Report with Core Temp

Collect the configuration, workload, sensor labels and event timeline needed for a clear temperature support request.

Direct answer: A useful report combines the exact system configuration with a reproducible symptom and labeled observations. One cropped temperature number rarely explains the problem.

By ALCPU.org editorial resource · Published 2026-10-05 · Documentation reviewed 2026-10-05

On this page

Lead with the actual problem

Describe what the computer does: slows down during a task, stops updating readings after wake, shuts down, or shows a value that differs from another tool. Keep the symptom separate from your proposed explanation. Saying 'the cooler is defective' assumes a cause, while saying 'the system shuts down during this repeatable task' gives support something concrete to investigate. Record when the behavior first appeared and whether it followed a software or hardware change.

Include the configuration that changes the answer

List CPU model, laptop or motherboard model, Windows edition and build, Core Temp version and normal power profile. Mention modifications, but do not publish serial numbers or license information unnecessarily. For laptops, note battery or AC operation and the charger context. For desktops, describe cooling and case placement at a useful level. If a field is unknown, write unknown rather than filling in a guessed value.

Attach evidence with labels

Include the full relevant sensor label, units, observation time and whether the number is current or a session maximum. State the workload and duration. A log should include its coverage and any gaps, plus a short explanation of the event timeline. Redact unrelated usernames, filenames and background windows before sharing a screenshot. Keep the original private copy for the authorized support contact if more detail is needed.

Document what you tried

List troubleshooting actions in order with their actual outcomes. For example, record whether restarting the application restored readings, whether the symptom follows sleep, or whether a matched task behaves differently with an approved default profile. Avoid claiming an action fixed the issue after one unrelated session. Do not disable Windows security features or thermal safeguards just to produce a cleaner report; preserve the warning text for support instead.

Ask a specific question

A clear request might ask which sensor definition to compare, whether a documented software issue matches the symptom, or which manufacturer diagnostic step is appropriate next. This website is an independent information resource and cannot issue warranty decisions or represent the Core Temp developer. Use the relevant developer, processor or system-maker channel. Keep a reference copy of the report so later replies can be tied to the same evidence.

Practical checklist

  1. State the symptom and first occurrence without assuming its cause.
  2. Record system, software and power context.
  3. Attach labeled readings or a log with coverage notes.
  4. List attempted actions and actual outcomes.
  5. Send the minimum necessary information to the appropriate support channel.

Observation worksheet

FieldWhat to enter
System and softwareExact CPU, system model, Windows build and Core Temp version
Observation contextTask, start/end time, sensor label, units and power profile
Evidence limitsMissing samples, changed conditions and unverified assumptions
OutcomeObserved behavior, practical next action and unresolved questions

Questions and answers

Should I send only the highest temperature?

Include its sensor, units, duration and workload context; the peak alone is insufficient.

Does this website provide manufacturer support?

No. Use the original software developer or system manufacturer for their support services.

Sources and verification status

Source pages reviewed on 2026-10-05. This is documentation-based guidance and a proposed observation method. No Windows hardware test, independent performance measurement or verification of the FileDrop payload was performed for this edition. Examples are illustrative. Read the full verification method.

Related reading

Package information · All Core Temp guides