How to Read HWiNFO Indicators
HWiNFO shows hundreds of sensors. Here's what actually matters for diagnosing gaming performance issues and how to interpret each key metric.
Temperature Indicators
Temperatures are crucial - high temps cause throttling which leads to stuttering.
CPU Package Temperature
The overall CPU temperature - most important CPU temp to watch.
✅ Great
✅ Normal
⚠️ Warm
🔥 Throttling!
GPU Temperature
Graphics card core temperature - affects gaming most directly.
✅ Great
✅ Normal
⚠️ Warm
🔥 Throttling risk
GPU Hot Spot / Junction Temperature
The hottest point on the GPU die. Usually 10-15°C higher than core temp.
Throttling Indicators (Critical!)
These Yes/No flags tell you exactly when your hardware is slowing down.
Thermal Throttling: Yes
Meaning: CPU/GPU is too hot and is reducing performance to cool down
Impact: Sudden FPS drops and stuttering during load
Power Limit Throttling: Yes
Meaning: GPU has reached its power limit (TDP)
Impact: GPU can't boost higher, may cause slight FPS variance
Fix: Increase power limit in GPU control panel (if cooling allows)
Voltage Limit: Yes
Meaning: GPU can't get enough voltage to clock higher
Impact: Usually minor - GPU is at safe operating limits
Fix: Often okay, but check power supply if unstable
All Flags: No
Meaning: Your hardware is running within limits
Impact: No throttling-related performance loss
Clock Speeds & Usage
GPU Clock (MHz)
Current GPU core frequency. Should be stable during gaming.
- Stable ~1800-2200 MHz: Normal for modern GPUs
- Drops suddenly: Indicates throttling
- Very low (<500 MHz): GPU not being used (CPU bottleneck?)
GPU Usage (%)
How much of the GPU is being utilized.
- 95-100%: GPU is the limiting factor (normal for GPU-bound games)
- 50-90%: CPU bottleneck or frame cap active
- <50%: Likely CPU bottleneck or in-game fps limit
CPU Usage (%)
Watch both overall and per-core usage.
- One core at 100%: Single-threaded bottleneck
- All cores high: Multi-threaded CPU limit
- Low CPU + low GPU usage: Frame limit or issue
Advanced CPU Indicators
Effective Clock vs Reported Clock
HWiNFO shows multiple clock readings. Know the difference:
- Core Clock (reported): What the CPU says it's running at — can be misleading during C-state transitions
- Core Effective Clock: The ACTUAL average frequency including idle time. This is the true performance number.
C-State Residency
Shows how much time the CPU spends in power-saving states during gaming. High C-state residency while gaming = CPU not being fully utilized. This often indicates a single-thread bottleneck where most cores are idle.
VRM Temperature (Motherboard)
The Voltage Regulator Module powers your CPU. Cheap motherboards with weak VRMs can overheat:
✅ Safe
⚠️ Check airflow
🔴 VRM throttling
Memory Metrics
Physical Memory Used
RAM usage in GB or %
- <80%: ✅ Healthy
- 80-95%: ⚠️ Getting tight
- >95%: 🔴 May cause stuttering (paging)
GPU Memory Used (VRAM)
Video memory on graphics card
- <80%: ✅ Plenty of room
- 80-95%: ⚠️ Near limit
- 100%: 🔴 Texture streaming stutters likely
Page File Usage
Disk being used as RAM overflow
- Low/Zero: ✅ RAM is sufficient
- High spikes: 🔴 RAM is full, causes stuttering
Power Metrics
GPU Power (W)
How much power your GPU is drawing.
What to look for:
- Stable at/near TDP: Normal under load
- Sudden drops: Power limit throttling
- Way below TDP: GPU not fully utilized
Example TDPs:
- RTX 4070: ~200W
- RTX 4080: ~320W
- RX 7800 XT: ~263W
Frame Time (The Stutter Metric)
FPS tells you how many frames per second. Frame Time tells you how long each individual frame takes. This is far more important for detecting stutter.
Why Frame Time Matters More Than FPS
Example at "60 FPS":
- Smooth: Every frame takes ~16.7ms (consistent)
- Stuttery: Most frames take 10ms, but every 30th frame takes 80ms (still averages "60 FPS" but feels terrible)
FPS averages hide the stutter. Frame Time reveals it.
How to See Frame Time in HWiNFO
Frame Time isn't a hardware sensor — it comes from the rendering pipeline:
- HWiNFO + PresentMon integration (built-in since 2024): Enable in sensor settings
- MSI Afterburner + RTSS: Shows "Frametime" in overlay and logs
- In-game: Some games show frame time in their built-in benchmarks
What Frame Time Values Mean
| Frame Time | Equivalent FPS | Feel |
|---|---|---|
| <8ms | 120+ FPS | Butter smooth |
| 8-16ms | 60-120 FPS | Smooth |
| 16-33ms | 30-60 FPS | Acceptable |
| 33-50ms | 20-30 FPS | Sluggish |
| 50-100ms | 10-20 FPS | Stuttery |
| >100ms | <10 FPS | Freeze/hitch |
- Consistent frame times = smooth gameplay (even at lower FPS)
- Frame time spikes = stutter (even at high average FPS)
- Gradually increasing = thermal throttling building up
- Periodic spikes every X seconds = background process or polling interference
Quick Reference: Problem Signs
| If you see... | The problem is... | Guide |
|---|---|---|
| Thermal Throttling: Yes | Overheating | Thermal Guide |
| GPU Usage <80%, CPU core at 100% | CPU Bottleneck | CPU Guide |
| RAM >95% + Page file active | Memory shortage | Need more RAM |
| VRAM at 100% | VRAM limit | Lower texture quality |
| Power Limit: Yes + clock drops | Power throttling | Raise power limit or check PSU |
Real-World Diagnostic Scenarios
Here's what different combinations of readings actually mean in practice:
Scenario 1: "FPS drops after 10-20 minutes of playing"
- CPU Temp: Starts 75°C → climbs to 95°C
- Thermal Throttling: Changes from No → Yes
- Core Clock: Drops from 4.5 GHz → 3.2 GHz
Fix: Thermal Throttling Guide →
Scenario 2: "GPU usage bouncing 40-99% constantly"
- GPU Usage: 40% → 99% → 45% → 99% (oscillating)
- CPU Usage (one core): 100% constantly
- GPU Temp: Low (50-60°C) — GPU is waiting
Fix: CPU Bottleneck Guide →
Scenario 3: "Micro-stutters every few seconds during cutscenes"
- GPU Memory: 100% (8GB VRAM maxed)
- GPU Clock: Drops exactly when stutter happens
- Everything else normal
Fix: Lower texture quality to High or Medium.
Scenario 4: "Everything looks normal but still stuttering"
- GPU Usage: 99%
- Temps: All good (60-70°C)
- No throttling flags
- RAM: Plenty free
Fix: Shader Stutter Guide →
Frequently Asked Questions
GPU Temperature is the average across the chip. Hot Spot is the single hottest point — usually 10-20°C higher and the real danger number.
Classic CPU bottleneck. Check per-core CPU usage — one core at 100% while others are idle confirms it.
Yes. Click the clock icon to reset readings before launching your game. This ensures Min/Max values reflect your gaming session only.
Hardware isn't everything. Check shader compilation, driver issues, background apps, or DPC latency. See our Shader Stutter guide.
GPU can't get enough stable voltage to boost higher. Often normal at stock settings. Only a concern if clocks are dropping significantly.
Let AI Analyze Your Logs
Don't want to analyze manually? Upload your HWiNFO CSV and get instant diagnosis!
Upload for Analysis