Offline miner
Start with power, switch port, VLAN, DHCP, and the IP range being scanned.
Updated June 16, 2026 - BTC Tools operations guide
ASIC miner troubleshooting guide for BTC Tools workflows
Troubleshoot ASIC miners with BTC Tools: offline devices, wrong pools, low hashrate, heat, rejects, and network issues.
BTC Tools
ASIC Miner Troubleshooting - BTC Tools
Troubleshooting works best when symptoms are separated by network, configuration, pool, firmware, hardware, and cooling causes.
Workflow
Troubleshooting order
Use this page as a practical planning reference for local ASIC miner operations. The exact behavior available in BTC Tools can depend on miner model, firmware, network access, and the action being performed.
Wrong pool
Review pool URL, worker name, backup pools, and the device group that received the change.
Low hashrate
Compare local status with pool-side activity and inspect heat or hardware symptoms.
Rejected shares
Check pool endpoint, latency, worker format, and firmware-specific settings.
Checklist
Troubleshooting order
Keep the scope narrow, document device groups, and separate local miner status from pool-side account data.
- Confirm the miner should be in the scanned IP range.
- Check whether the miner web UI is reachable.
- Compare BTC Tools data with pool dashboard data.
- Separate one-device issues from rack or switch-level issues.
- Document repeated failures and maintenance actions.
- Check whether the problem follows the miner, cable, port, or power outlet.
- Separate firmware behavior from hardware failure symptoms.
- Review recent pool, network, or maintenance changes before changing the miner again.
Operations
ASIC miner troubleshooting table
These tables are written for miners and technicians who need repeatable local workflows rather than broad crypto marketing copy.
| Area | What to check | BTC Tools workflow |
|---|---|---|
| Network unreachable | Wrong subnet, firewall, VLAN, DHCP, switch, or cable. | Confirm IP plan and physical network. |
| Wrong credentials | Password changed or inconsistent device group. | Confirm access for the selected miners. |
| Low hashrate | Overheating, pool issue, firmware, or hardware condition. | Check temperature, pool data, and miner logs. |
| Fan errors | Fan failure, cabling, dust, or sensor issue. | Inspect device cooling and maintenance records. |
| Firmware mismatch | Different model or firmware behavior. | Test actions on a small compatible group. |
| Wrong pool | Pool URL or worker value was applied to the wrong group. | Compare current values with the intended batch plan. |
| Duplicate IP | Static IP conflict or stale DHCP reservation. | Reconcile MAC address and IP records. |
| Rejected shares | Pool endpoint, worker format, latency, or firmware setting. | Compare pool dashboard data with miner-side settings. |
| Thermal throttling | Airflow, fan, room heat, or dust buildup. | Fix cooling conditions before expanding changes. |
| Intermittent reachability | Switch, cable, PSU, firmware, or overloaded network segment. | Check physical path and isolate the affected segment. |
Setup
Plan, scan, change, and review
For every BTC Tools workflow, start from the intended IP range and device group, then apply changes in small controlled batches and review results before expanding the scope.
