Docs

Monitor your CPU / GPU miners without losing visibility

PC Miner keeps desktop rigs observable: track hashrate, power, temps, pools and wallets in one place, while every binary stays verifiable.

Quickstart

Connect your miners to monitoring

Three actions to get a PC rig (CPU or GPU) visible in the dashboard and ready for alerts.

1) Install a verified build

Use the Downloads table to pull the exact miner binary mapped to your coin. Hashes and release notes stay upstream for easy verification.

  • Keep CPU and GPU miners in separate folders per rig.
  • Compare checksums before allowing AV exceptions.

2) Add coins, pools and wallets

Create a profile per rig with coin, pool endpoint, wallet and worker. PC Miner binds those to the hardware so telemetry is labeled correctly.

  • Use SSL pool URLs where supported.
  • Label rigs and wallets for later audits.

3) Confirm telemetry

Launch the miner once and confirm hashrate, share rate, power and temps show up. Set expected ranges — they drive alerts later.

  • Capture 10–15 minutes of stable shares before trusting numbers.
  • Save baseline power/temps per rig.

Monitoring scope

What PC Miner watches by default

Coverage is built for desktop miners: solid telemetry without invasive agents.

Hashrate & shares

Miner-reported hashrate per coin, accepted/rejected share rate, and pool round status.

  • Alert on sudden hashrate drops or rising stale share rate.
  • Track per-profile history to spot drifting rigs.

Power & thermals

Power draw, temperature and fan signals where exposed by the miner or driver.

  • Separate thresholds for GPUs vs CPUs.
  • Flag runaway temps before throttling kicks in.

Pool connectivity

Connection health, reconnect attempts and stratum errors for each configured pool.

  • Detect “running but not submitting” states quickly.
  • Swap to a backup pool when primary is unstable.

System health

Optional OS-level signals to explain miner behavior without over-collecting data.

  • CPU load and memory pressure on the rig.
  • Disk space checks to avoid log-induced stalls.

Policies & alerts

Catch bad runs before they burn time or power

Alerts are simple rules tied to each rig and profile so CPU and GPU miners stay predictable.

Policy templates

  • Hashrate drop vs baseline after warmup.
  • Stale or rejected share rate spikes.
  • Offline duration beyond X minutes.
  • Temp above limit or sudden power surge.

Use templates as-is or tighten for specific rigs with weak cooling or pricier power.

Where alerts go

  • In-app banners for active sessions.
  • Desktop notifications when minimized.
  • Webhook slot for your own scripts/Discord.

Each alert message includes coin, miner version, pool and the last good baseline.

Runbook

Troubleshooting common miner states

A quick checklist for CPU/GPU rigs when telemetry looks off.

Hashrate lower than baseline

  • Confirm miner version and clocks match the saved profile.
  • Check pool latency and switch to a closer endpoint.
  • Look for thermal throttling; clean filters and reduce ambient heat.

Shares rejected or stale

  • Verify wallet address/worker names; pools may silently drop bad IDs.
  • Reduce aggressive memory overclocks for stability.
  • Check ISP or VPN jitter if using SSL pools.

Rig runs hot

  • Lower power limit or switch to efficiency profile.
  • Update to a miner build with better kernel for your GPU/CPU.
  • Re-seat fans and ensure intake/exhaust is unobstructed.

Offline alerts

  • Verify the miner is allowed through AV/firewall after an update.
  • Swap to a backup pool and compare stability.
  • Restart with the last known-good profile to rule out bad configs.

Operational notes

Keep your monitoring trustworthy

Transparency-first defaults so you always know what runs on your machine.

Data handling

  • Profiles, wallets and pools live locally on disk.
  • No seeds or private keys are needed by the app.
  • Telemetry is scoped to miner metrics and optional OS health only.

Change control

  • Log miner version, driver version and coin per rig.
  • Test new binaries on one rig before rolling out.
  • Export configs before major OS or driver changes.