Blog

Thermal Canary Pro blog

Real product mechanics, real thresholds, no generic thermal tips.

Gaming headphones glowing red on a dark desk, lit by a blue monitor glow in the background

We built a silent alert for your GPU. Then PyQt6 made it actually silent.

July 30, 2026

Qt's own audio API reported perfect playback: no errors, full lifecycle, isPlaying flipped true then false. Nothing came out of the speakers. Here's the actual bug and why we shell out to pw-play instead.

A real CPU die and a real GPU die side by side, labeled CPU hwmon and RAPL, GPU amdgpu and NVML, with their real exposure gaps listed underneath each

What Linux actually tells you about your hardware, and what it flatly won't

July 24, 2026

hwmon, amdgpu, NVML, RAPL: a plain-English map of what's actually readable on Linux versus Windows and macOS, where the real gaps are, and why some of them exist on purpose.

A GPU die and package next to a decoded clock-throttle-reasons readout, with POWER_BRAKE highlighted as the active flag

Your GPU already knows why your FPS dropped. NVIDIA just never shows you.

July 17, 2026

NVIDIA's driver exposes a full bitmask of clock-throttle reasons over NVML, thermal, power, or the motherboard itself limiting delivery. Here's what each bit actually means, and the one almost nobody checks.

$A gaming monitor showing a dead black screen with a dramatic red fracture across it, PC case fans still lit blue in the background, dark room$

Your GPU crashed on Linux. Here's every piece of evidence that survives, and the one that doesn't.

July 10, 2026

The kernel log records that your GPU driver died. It never records how hot the card was when it happened. What journalctl actually gives you after a hard lock, and the gap that's left.