HWiNFO64 Complete Sensor Monitoring and Logging Guide

HWiNFO64 is the gold standard for hardware sensor monitoring on Windows. Unlike basic tools, it exposes hundreds of sensors across your CPU, GPU, motherboard, storage drives, and power delivery system — all in real time. This guide walks you through setup, customization, logging, and integrating HWiNFO64 with overlay tools like RTSS.

Why HWiNFO64 Over Alternatives

Tools like CPU-Z and GPU-Z show static specs, while HWiNFO64 monitors live sensor data: temperatures, voltages, clock speeds, power draw, fan RPMs, and utilization percentages. It supports virtually every modern sensor chip from Nuvoton, ITE, Fintek, and others found on mainstream motherboards.

Key advantages:

• Free for personal use
• Updated frequently with new hardware support
• Exports data to CSV for analysis
• Integrates with RivaTuner Statistics Server (RTSS) for in-game overlays
• Supports remote monitoring via plugins

Installation and First Launch

1. Download HWiNFO64 from hwinfo.com — choose the installer or portable version.
2. Run as Administrator for full sensor access.
3. On first launch, choose Sensors-only mode to skip the summary window, or leave it unchecked to see both.

At startup, HWiNFO64 scans your hardware. This takes 10–30 seconds. Do not skip this — it initializes all sensor polling.

Understanding the Sensor Window

The sensor window is organized by hardware component:

Section	What It Shows
CPU [#0]	Per-core temps, clocks, voltages, power (TDP)
GPU [NVIDIA/AMD]	GPU temp, VRAM temp, clock, power, utilization
Motherboard	VRM temps, system fan headers
Drive (NVMe/SSD)	Drive temp, health status
Memory	DRAM frequency, voltage if supported

Color coding:

• White: Normal range
• Yellow: Elevated but not critical
• Red: Exceeded safe threshold

Right-click any sensor row to Add to Tray for a miniature readout in the system tray — useful for a quick at-a-glance temperature without keeping the full window open.

Customizing What You See

HWiNFO64 shows hundreds of sensors by default. To reduce clutter:

1. Click the small wrench icon in the sensor toolbar.
2. Navigate to Layout tab.
3. Uncheck sensors you don’t need.

Alternatively, right-click a sensor and select Hide to remove it from view without disabling polling.

Renaming sensors: Right-click → Rename to give sensors friendly names like “CPU Package Temp” instead of the chip-internal label.

Setting Up Logging to CSV

Long-term logging is invaluable for diagnosing thermal throttling, instability under load, or power anomalies.

1. Click Start Logging (the floppy disk icon in the sensor toolbar).
2. Choose a save location and filename — HWiNFO64 will append .csv automatically.
3. Set your log interval in Settings → General → Sensor polling period (default: 2000ms, i.e., 2 seconds).

Log files can be opened in Excel or imported into Python/pandas for graphing. To parse timestamps correctly, use HWiNFO’s own date format: DD.MM.YYYY HH:MM:SS.

import pandas as pd

df = pd.read_csv("hwinfo_log.csv", skiprows=1)
df["Date"] = pd.to_datetime(df["Date"], format="%d.%m.%Y %H:%M:%S")
df.set_index("Date", inplace=True)
df["CPU Package Power [W]"].plot(title="CPU Power Over Time")

Integrating With RTSS for In-Game Overlays

RivaTuner Statistics Server (RTSS) + MSI Afterburner can display HWiNFO sensor data as an in-game overlay.

Step-by-Step Integration

1. Install MSI Afterburner and RTSS (both free).
2. Open Afterburner → Settings → Monitoring tab.
3. Scroll through the list and enable the sensors you want displayed.
4. For each sensor, check Show in On-Screen Display.
5. Under the OSD column, choose which sensors appear in the overlay layout.
6. Launch a game — the overlay appears in the corner you configured in RTSS.

Tip: If Afterburner doesn’t show certain sensors (like CPU core voltages), enable “Use HWiNFO shared memory support” inside HWiNFO64 Settings → General. This pipes HWiNFO data directly into Afterburner.

Configuring Alarms

HWiNFO64 can alert you when sensors exceed thresholds:

1. Right-click any sensor → Configure Sensor.
2. Under Alarm, set a threshold value.
3. Choose the action: Beep, Log, Run program, or Show balloon tip.

Useful alarm thresholds:

• CPU Package Temp: Alert at 90°C
• GPU Temperature: Alert at 83°C
• NVMe Drive Temp: Alert at 70°C
• CPU Core Voltage: Alert if it drops below 0.8V (may indicate instability)

Reading GPU VRAM Temperature

Modern NVIDIA RTX 30/40/50 series and AMD RX 6000/7000/9000 cards report a separate GPU Memory Temperature sensor. This is critical — VRAM runs hotter than the GPU die and directly impacts memory clock speeds.

In the sensor window, look for:

• GPU Memory Temperature (NVIDIA)
• GPU (Hot Spot) Temperature and GPU Memory Temperature (AMD)

GDDR6X VRAM (found on RTX 3080/3090 and some 4000-series cards) routinely hits 100–110°C under load — this is within spec but worth monitoring. GDDR7 on newer cards runs cooler.

Monitoring VRM and Motherboard Sensors

Voltage Regulator Module (VRM) temperatures tell you how hard your power delivery is working:

• Under 80°C: Normal
• 80–100°C: Heavy load, consider airflow improvements
• 100°C+: Thermal throttling risk; improve case airflow or add heatsinks

Many budget B650/B760 motherboards have limited VRM cooling. Adding a 120mm fan blowing toward the VRM area can drop temperatures by 15–25°C under Prime95 sustained loads.

Diagnosing Thermal Throttling

One of HWiNFO64’s most useful features is exposing throttling flags:

• Look for a sensor called CPU Thermal Throttling or Package Power Limit Throttling — a value of Yes or 1 confirms throttling is active.
• Cross-reference with CPU Clock drops during high load.

If you see throttling during gaming or rendering:

1. Check CPU cooler mounting pressure (reapply thermal paste if needed).
2. Verify your power limits in BIOS (increase PL1/PL2 on Intel, or enable PBO on AMD).
3. Check ambient temperatures and case airflow.

Conclusion

HWiNFO64 is an indispensable tool for any PC builder or enthusiast. Whether you’re stress-testing an overclock, diagnosing mystery crashes, or just verifying your cooling is adequate, its sensor depth and logging capabilities are unmatched. Combine it with RTSS for in-game visibility and CSV logging for historical analysis, and you have a complete hardware health monitoring pipeline at no cost.