Win Stat Server

Windows performance diagnostics, now with per-frame capture analysis

HWiNFO live telemetry, CapFrameX capture analysis, remote access and controlled gameplay measurement for identifying CPU, GPU, memory, thermal, power and frame-delivery constraints.

Host OS Windows 10 / 11
Local Port 8080
Telemetry HWiNFO + CapFrameX
Remote Parsec + Tunnelmole
Integrated workflowCapture + telemetry

Use the Capture Analyzer at /dash for true per-frame CapFrameX metrics, synchronized hardware graphs and range analysis. KUM-FPS can prepare the complete toolchain automatically.

Download Choose setup flow
01

Required software

Download the required components before starting the diagnostics session.

Remote access

Parsec

Low-latency remote access for initial configuration and live troubleshooting.

Download
Telemetry source

HWiNFO64

Provides CPU, GPU, memory, power and temperature telemetry through shared memory.

Download
Local dashboard

win-stat-server

Browser interface for live telemetry, completed captures, synchronized graphs and analysis exports.

Download Repository
Per-frame capture

CapFrameX

Records true per-frame frametimes, FPS distribution, low-percentile metrics, stutters and freezes.

Latest release Documentation
Public tunnel

Tunnelmole

Standalone Windows executable for temporary HTTPS access to the local dashboard.

tmole.exe Docs
02

Choose a setup flow

Use one path only. The automatic installer is recommended; the manual flow provides full control over every component.

A

Automatic installer

KUM-FPS installs and configures the complete local toolchain.

Recommended
A1

Download and extract the package

Download
A2

Run the installer

Start the included bootstrap and approve elevation when Windows requests it.

Installed and configured: HWiNFO, CapFrameX, win-stat-server, Tunnelmole and required Windows runtimes. Parsec is installed when missing.
A3

Launch and verify

Security: the remote URL is publicly reachable while Tunnelmole is active. Close it after the session.
B

Manual installation

Install and configure each component separately.

Advanced
B1

Configure Parsec

Download
Capture condition: disconnect Parsec before the final gameplay sample when possible.
B2

Configure HWiNFO64

Download
Required: HWiNFO must remain running throughout the diagnostics session.
B3

Install CapFrameX

Download
B4

Start win-stat-server

Download
powershell -ExecutionPolicy Bypass -File .\hwinfo-performance-lab.ps1
If the BAT launcher fails, open PowerShell in the extracted directory and run the command above.
B5

Enable remote dashboard access

Download tmole.exe

Skip this step if the dashboard will only be used on the Windows host.

.\tmole.exe 8080
Security: terminate Tunnelmole immediately after the session.
C

Capture workflow

Continue here after completing either setup path.

Both flows
C1

Record a controlled gameplay sample

Capture representative gameplay only. Keep loading screens, menus and idle desktop periods outside the measured lap.

Setup progress
0%
03

Analysis scope

Correlate FPS and frame time with utilization, thermals, clocks, power and resource-limit signals.

Primary telemetry

FPS / Frame timeHWiNFO trends plus true per-frame CapFrameX analysis
CPULoad, clocks, package power, PPT/TDC/EDC utilization
GPULoad, clocks, power, temperature, VRAM and limit signals
MemorySystem memory utilization and pressure
Capture quality1% low, 0.2% low, frametime spikes, stutters and freezes

Interpretation notes

PPT / TDC / EDC: percentages represent utilization of resource limits. They do not independently prove throttling.
Low-percentile FPS: use CapFrameX capture results for exact per-frame analysis. HWiNFO polling remains useful for hardware trends and bottleneck correlation.
Capture Analyzer: open /dash, choose a completed capture, then drag across the frametime graph to analyze a specific range. Hovering synchronizes frame and hardware values.
04

Capture and advanced diagnostics

CapFrameX is integrated into the main workflow; LatencyMon remains an optional supporting diagnostic.

CapFrameX

Integrated per-frame capture source for the main dashboard and Capture Analyzer.

Download

Procedure

  1. Start a current CapFrameX release before launching the test scene. KUM-FPS starts it automatically.
  2. Select the game process and verify that capture is armed.
  3. Use the same representative gameplay scenario used for the HWiNFO capture.
  4. Capture approximately 60–120 seconds.
  5. Keep menus, loading screens and desktop activity outside the capture.
  6. Open http://localhost:8080/dash and select the completed capture.

Check

  • Frametime graph: look for spikes, repeated oscillation or sections where frame delivery becomes unstable.
  • Average vs low-percentile FPS: a high average with poor lows usually indicates inconsistent frame delivery rather than insufficient average throughput.
  • Stutter events: note whether spikes occur periodically or only during specific in-game actions.
  • GPU-bound vs CPU-bound behavior: compare the time of frame spikes with the HWiNFO CPU/GPU telemetry.
  • Consistency: repeat the same scene at least once if the first run contains unrelated loading or shader-compilation activity.
Important: CapFrameX remains bound to localhost. Win Stat Server proxies only the capture data required by its dashboards. Treat a Tunnelmole URL as sensitive because it exposes those dashboards while active.

LatencyMon

Supporting diagnostic for DPC/ISR latency, driver execution and hard pagefault activity.

Download

Procedure

  1. Close unnecessary background applications before the test.
  2. Start LatencyMon and press Start.
  3. Reproduce the FPS drop or stutter during normal gameplay.
  4. Let it run for several minutes while the problem is occurring.
  5. Press Stop after the issue has been reproduced.
  6. Check the Main, Drivers, Processes and Stats tabs.

Check

  • Highest DPC routine execution time: identify the driver associated with unusually long DPC execution.
  • Highest ISR routine execution time: check whether a hardware driver repeatedly generates long interrupt service times.
  • Driver execution counts: repeated high-latency execution is more relevant than one isolated spike.
  • Hard pagefaults: excessive faults during gameplay may indicate memory pressure or storage-related stalls.
  • Driver filename: record the exact .sys file before changing or updating anything.
Interpretation: LatencyMon is supporting evidence, not an FPS benchmark. A single high value does not prove that a driver is causing the FPS problem. Correlate repeated driver latency with the time of visible stutter and the other telemetry.
05

Troubleshooting

Verify the local telemetry path first, then the tunnel and remote-access layer.

Symptom Resolution
No sensor data Confirm HWiNFO64 is running in Sensors-only mode and Shared Memory Support is enabled. Restart win-stat-server afterward.
CapFrameX shows offline Start a current CapFrameX release and confirm its local MCP endpoint is enabled. Win Stat Server checks the configured port, CapFrameX log and default port automatically.
Capture Analyzer has no captures Complete a CapFrameX capture first, wait for processing to finish, then reload http://localhost:8080/dash.
Hardware graph has no history Some metrics are stored inside the CapFrameX capture. Additional live HWiNFO history is available only from the time Win Stat Server started and is intentionally bounded.
KUM-FPS setup failed Review the timestamped log under %LOCALAPPDATA%\KUM-FPS\logs. Re-running the installer is safe because existing components are reused.
localhost:8080 unavailable Confirm the PowerShell/BAT process is still running. If the port is occupied, start the server with -Port 8081 and expose the same port through Tunnelmole.
tmole.exe not recognized Run it from its directory using .\tmole.exe 8080 unless that directory has been added to PATH.
Tunnel URL does not load Verify http://localhost:8080 works locally first.
FPS changes during Parsec connection Disconnect Parsec before the final performance sample when possible.
Mixed desktop and gameplay data Use a dedicated lap and start it only after entering the representative gameplay scene.