⌘K
Logging Guide

How to Record HWiNFO Logs While Gaming

To diagnose gaming stuttering with HWiNFO, launch it in Sensors-Only mode, set polling to 500ms, enable CPU/GPU temperature, clock speed, usage, and power sensors, then start CSV logging before launching your game. Play for 10-15 minutes to capture the issue, then stop logging. The resulting CSV file reveals exactly what your hardware was doing when stuttering occurred — thermal throttling, power limits, clock drops, or CPU saturation.

This method has helped diagnose over 1,000 stutter cases on SmoothFPS. Most issues become obvious within the first 5 minutes of a properly configured log.

Before You Start

You'll Need

HWiNFO64 (free download), ~50MB free disk space, 5-15 minutes to play with logging

Time Required

Setup: 2-3 minutes. Logging: 5-15 minutes. Total: ~10-20 minutes

Prefer screenshots? Our visual walkthrough shows every step with 24 annotated images.

View Walkthrough

Step 1: Download HWiNFO64

  1. Go to hwinfo.com/download
  2. Choose Portable version (no installation needed)
  3. Download the ZIP file
  4. Extract to a folder (e.g., Desktop)
  5. Run HWiNFO64.exe
Tip: Use the 64-bit version (HWiNFO64) for modern systems

Step 2: Launch in Sensors-Only Mode

When HWiNFO starts, you'll see a dialog with options:

  1. ✅ Check "Sensors-only"
  2. ❌ Leave "Summary-only" unchecked
  3. Click Start
Why Sensors-only?
It skips the full hardware scan and loads faster. We only need the sensor monitoring for gaming logs.

Step 3: Configure Settings (Important!)

Default settings work, but these tweaks improve log quality:

  1. Right-click anywhere in the sensor window → Settings
  2. In "General/User Interface":
    • Set Polling Interval to 500ms (or 1000ms for longer sessions)
  3. In "Safety":
    • ✅ Enable "Minimize to tray on startup" (optional)
  4. Click OK

500ms Polling

Better detail, larger files (~5MB per 10 min)

1000ms Polling

Good balance, smaller files (~2MB per 10 min)

2000ms Polling

For long sessions, may miss quick spikes

Step 3.5: Enable the Right Sensors (Critical for Gaming)

HWiNFO shows hundreds of sensors. You don't need most of them. Here are the essential ones for diagnosing gaming issues:

✅ Must-Have Sensors (Always Enable)

CPU Section:
  • CPU Package Temperature → detects overheating
  • CPU Package Power → detects power throttling
  • Core Clocks (all cores) → detects clock drops
  • CPU Usage (total) → detects CPU bottleneck
  • Core Usage (per-core) → detects single-thread bottleneck
GPU Section:
  • GPU Temperature → detects GPU overheating
  • GPU Hot Spot / Junction Temperature → the real danger number
  • GPU Clock → detects throttling-related clock drops
  • GPU Usage (%) → the #1 indicator of CPU vs GPU bottleneck (watch for sudden GPU usage drops)
  • GPU Power → detects power limit throttling
  • GPU Memory Usage → detects VRAM exhaustion
🚨 Throttling Flags (MOST IMPORTANT!):
  • Thermal Throttling [Yes/No]
  • Power Limit Throttling [Yes/No]
  • Performance Limit — tells you EXACTLY why performance dropped
Memory:
  • Physical Memory Used (%) → detects RAM shortage
  • Page File Usage → if this spikes, RAM is full
  • GPU Memory Used → VRAM monitoring

How to Disable Unnecessary Sensors

  1. In the sensor window, find sensors you don't need
  2. Select them (Shift+click for multiple)
  3. Press Delete key → hides them from view AND logging
  4. To restore later: Settings → Layout tab → click "Show"
Recommended to disable: Individual voltage rails, SMART disk sensors (can cause stutter), Motherboard auxiliary temps.
Important: HWiNFO Can Cause Stutter

Yes, the tool you're using to diagnose stuttering can itself cause stuttering:

!

ASUS EC Sensors: On ASUS motherboards, EC sensor polling can cause micro-stutters. Fix: Right-click "ASUS EC" section → Disable monitoring.

!

SMART Disk Sensors: Polling disk health can cause brief freezes. Fix: Settings → SMARTx → uncheck "Enable SMART for drives".

!

Too-frequent polling: 250ms polling on older systems can impact performance. Stick with 500ms-1000ms.

How to test if HWiNFO is causing YOUR stutter:
  1. Play WITHOUT HWiNFO running — note if stutter exists
  2. Play WITH HWiNFO running — compare
  3. If stutter only happens with HWiNFO: disable sensor groups one by one

Step 4: Start Logging

  1. In the HWiNFO sensor window, click the 📝 button (or go to File → Sensor Logging)
  2. Choose where to save the CSV file (Desktop is easy to find)
  3. Give it a descriptive name like gaming_log_fortnite.csv
  4. Click Save - logging starts immediately
Important: Start logging BEFORE you launch your game!

Step 5: Play Your Game

  1. Launch your game normally
  2. Play for 5-15 minutes
  3. Try to trigger the stuttering/issue you're experiencing
  4. Note the time when problems occur (helps with analysis)
Tips for Good Logs
  • Play the game mode where stuttering usually happens
  • If stuttering is random, play longer (15-20 min)
  • Don't alt-tab constantly - stay in game
  • Note timestamps when issues occur

Step 6: Stop Logging & Analyze

  1. Exit your game
  2. Return to HWiNFO
  3. Click the 📝 button again to stop logging
  4. Your CSV file is ready!

Upload for AI Analysis — Let our AI analyze your log and identify issues automatically!

Upload Log File

How to Read Your Log File

Your CSV log is a goldmine — but it needs interpretation. Here's the quick workflow:

Option 1: Upload for AI Analysis (Fastest)

Upload your CSV to our analysis tool and get an instant diagnosis with specific fixes.

Option 2: Manual Analysis with GenericLogViewer

  1. Download GenericLogViewer (free, no install needed)
  2. Open your CSV file → select "HWINFO" as file type
  3. Pick sensors to graph (start with GPU Usage, CPU Temp, GPU Temp)
  4. Look for correlations: when GPU usage drops, does CPU temp spike? Understanding frame time graphs helps you spot these patterns

Option 3: Open in Excel/Google Sheets

  1. Open the CSV in Excel or Google Sheets
  2. Create charts for key columns
  3. Look for the timestamps where you experienced stutter

🚨 Red Flags to Look For in Your Log

What You SeeWhat It MeansNext Step
GPU Usage drops 99% → 30-50%CPU bottleneckCPU Bottleneck Guide →
CPU Temp hits 90°C+Thermal throttlingThermal Throttling Guide →
"Thermal Throttling: Yes"Confirmed overheatingThermal Throttling Guide →
"Power Limit: Yes"GPU power limit hitRaise power limit in GPU control panel
RAM >95% + Page File spikesOut of memoryAdd RAM or close background apps
GPU Memory at 100%VRAM exhaustedLower texture quality
All values normal but stutterShader or driver issueShader Stutter →

Alternative: Real-Time OSD Instead of Logging

Don't need a log file? HWiNFO supports on-screen overlays:

Method 1: HWiNFO Built-in OSD (2024+)

Settings → OSD (RTSS) tab → Check "Enable OSD" → Select sensors to display

Method 2: HWiNFO + MSI Afterburner

Install MSI Afterburner + RTSS → Settings → Monitoring → Enable HWiNFO plugin → Select sensors

When to use OSD vs Logging:
  • OSD: Quick checking, competitive gaming, spotting obvious issues
  • Logging: Detailed analysis, tech support, comparing before/after

Frequently Asked Questions

What is the best polling interval for HWiNFO gaming logs?

Use 500ms (0.5 seconds) for most gaming sessions — it captures enough detail to spot thermal throttling and clock drops without creating excessively large files. Use 1000ms for sessions longer than 30 minutes. Avoid 100ms or lower as HWiNFO itself can cause micro-stutters at very fast polling rates, especially with ASUS EC sensors enabled.

How do I analyze HWiNFO log files?

Open your HWiNFO CSV in Excel or Google Sheets and look for: 1) Temperature spikes above 90°C (thermal throttling), 2) Clock speed drops during gameplay (power or thermal limits), 3) CPU usage hitting 100% on any single core (CPU bottleneck), 4) GPU usage dropping below 90% (bottleneck elsewhere). Or upload the CSV to SmoothFPS for instant AI-powered analysis.

Which HWiNFO sensors should I enable for gaming?

Enable these sensors: CPU Package Temperature, CPU Core Clocks, CPU Total Usage, GPU Temperature, GPU Clock, GPU Usage, GPU Power, GPU Memory Usage, RAM Usage, and Physical Memory Used. Disable disk SMART sensors and ASUS EC sensors to prevent monitoring overhead. This gives you everything needed to diagnose thermal throttling, bottlenecks, and power issues.

What polling interval should I use?

500ms for most sessions. 1000ms for 30+ minute sessions. Only use 250ms to catch sub-second spikes.

My log only shows CPU sensors, not GPU. Why?

GPU sensors may be hidden. Settings → Layout tab → find GPU sensors → click "Show".

How big will my log file be?

~5MB per 10 min at 500ms polling. ~2MB at 1000ms with ~50 sensors.

Can I auto-log when starting a game?

HWiNFO Pro supports command-line auto-logging. Combine with a batch file that launches both.

How long should I log?

Stuttering: 5-15 min in the problematic scenario. Thermal issues: 20-30 min to see temps climb.

📊 Got Your Log? Here's What to Do Next

Now that you have your HWiNFO CSV file, you have three options:

  1. Instant AI Analysis: Upload your CSV to our AI analyzer — it reads your log and tells you exactly what's wrong in plain English.
  2. Learn to Read It Yourself: Our HWiNFO metrics guide teaches you what each sensor means and what values are problematic.
  3. Compare Before/After: Upload two logs to see if your fix actually worked.

Related Guides

Visual Walkthrough (Screenshots)HWiNFO Analysis HubRead IndicatorsThermal Throttling
Back to HWiNFO Guide