Skip to content

Bitcoin accepted at checkout  |  Ships from Laval, QC, Canada  |  Expert support since 2016

Quick answer

If the hardware is healthy but you're losing shares, the problem is between the miner and the pool: credentials, latency, or an unstable tune.

Sort credentials and a stable backup pool first; a small reject % is normal.

Full diagnostic flow

Does the pool show the worker connecting at all?
  • Worker never authorises → Authorisation failure — wrong worker name, password, or wallet. Fix the worker credentials in the miner config. [Fix it yourself] Error-code guide →
  • Connects then drops → Add a reliable backup pool and watch. Does it still drop on both?
Add a reliable backup pool and watch. Does it still drop on both?
  • Drops on every pool → Network-side: DNS, NAT/firewall, or an unstable connection. Try the pool IP directly and a solid DNS (1.1.1.1). [Fix it yourself] Error-code guide →
  • Stable now, but high rejects → Are rejected/stale shares more than a few percent?
Are rejected/stale shares more than a few percent?
  • High reject rate → Latency or an aggressive overclock producing stale/HW-error shares. Use a closer pool and back the tune off to stock to confirm. [DIY with care] Error-code guide →
  • Only a small reject % → A low single-digit reject rate is normal and not worth chasing. You're fine. [Fix it yourself]

This points at board-level damage. You can attempt it, but the realistic call for most owners is to send it to a repair bench.

Fix it yourself

Work the matching symptom decision tree and error-code guide step by step. Most cable, cooling, network and firmware faults are solvable on the bench you already own.

Send it to D-Central

Cracked solder, dead domains, shorted chips and EEPROM faults need a real repair bench. See transparent repair pricing or get a free repair quote — we diagnose and repair 38+ ASIC models in Laval, board-level, since 2016.

More tools: Kernel-Log Decoder · ASIC Fault Finder (650 codes) · All symptom trees