Miner Shows No Hashrate — Troubleshooting Guide

Complete troubleshooting guide for when your ASIC miner reports 0 TH/s. Covers Antminer, Whatsminer, and Avalon miners with step-by-step diagnostic procedures.

Symptoms

You are experiencing one or more of the following:

Dashboard shows 0 TH/s or 0 GH/s across all hash boards
Web UI reports "Chain find 0 ASIC" on one or more chains
Hash boards are not detected by the control board
Pool dashboard shows the worker as offline or producing no shares
Miner appears to power on (fans spin, LEDs light up) but produces no work
Status page shows chains with 0 chips detected

Safety First: Before opening your miner or handling any internal components, disconnect power and wait at least 60 seconds. Always wear an ESD wrist strap when touching hash boards or control boards.

Quick Checks

Before diving into detailed diagnostics, verify these basics first. Most "no hashrate" situations are resolved at this stage:

Is the PSU fully on? Check that the power supply switch is in the ON position and that all power connectors are firmly seated.
Is the network cable connected? Verify the Ethernet cable is plugged in and link lights are active on both the miner and your switch/router.
Can you access the web UI? Open a browser and navigate to your miner's IP address. If you cannot reach it, see Network Problems.
Are pool settings correct? Wrong pool URL, port, or worker name is the single most common cause of zero hashrate.
Is the firmware up to date? Some older firmware versions have known bugs that cause chain detection failures.
Have you tried a reboot? Power cycle the miner completely (off for 30 seconds, then back on) and wait 5-10 minutes for initialization.

Diagnostic Flowchart

Follow this decision tree to narrow down the root cause:

Miner shows 0 TH/s
│
├─ Can you access the web UI?
│  ├─ NO → See "Network Problems" guide
│  │
│  └─ YES → Check pool configuration
│     ├─ Pool URL/port/worker WRONG → Fix settings, reboot, wait 5 min
│     │
│     └─ Pool settings CORRECT → Check chain status page
│        ├─ All chains show "0 ASIC" or missing
│        │  ├─ PSU voltages OK? (12V or 48V present)
│        │  │  ├─ NO → PSU failure or bad power cord → See "Power Issues"
│        │  │  └─ YES → Control board failure or all connectors loose
│        │  │     ├─ Reseat all ribbon/signal cables
│        │  │     └─ Still 0 ASIC → Control board likely failed
│        │  │
│        │  └─ Only SOME chains show 0 ASIC
│        │     ├─ Reseat that chain's connectors
│        │     ├─ Swap chain to different control board port
│        │     └─ If follows the PORT → control board issue
│        │        If follows the BOARD → hashboard issue
│        │
│        └─ Chains detected but 0 TH/s
│           ├─ Check for high ASIC temp or errors in log
│           ├─ Firmware corruption → See "Firmware Corruption"
│           └─ Pool-side issue → Test with a different pool

Causes

Causes are listed from most common to least common. Work through them in order.

1. Pool Configuration Error

Probability: Very High

The most frequent cause of "no hashrate" is simply wrong pool settings. The miner may be running perfectly, but if it cannot connect to a pool or is sending shares to the wrong address, your dashboard will show zero.

Symptoms specific to this cause:

Miner fans spin normally, web UI is accessible
Chain status shows chips detected and ASIC temperatures are normal
Pool dashboard shows worker offline
Miner log shows "Stratum connection failed" or "Pool not responding"

Diagnosis:

Verify Pool URL and Port

Log into the miner's web UI and navigate to the pool configuration page.

Go to Miner Configuration > General Settings. Verify the URL format: stratum+tcp://pool.example.com:3333. Common mistake: missing stratum+tcp:// prefix or wrong port number.

Access the Settings page. Whatsminer uses the format stratum+tcp://pool.example.com:3333. Check all three pool entries (Pool 1, Pool 2, Pool 3).

Navigate to Configuration > Pool. Avalon miners managed via AUC (Avalon USB Converter) use CGMiner configuration. Verify the pool URL in the CGMiner settings.

Check Worker Name

Ensure the worker name matches your pool account. For Slush Pool / Braiins, it must be username.workername. For F2Pool, it is your account name. An incorrect worker name will cause shares to be rejected or lost.

Test Pool Connectivity

From a computer on the same network, test that you can reach the pool:

# Test pool connectivity
nc -zv stratum.braiins.com 3333
# or
telnet stratum.braiins.com 3333

If this fails, you may have a firewall or ISP blocking mining traffic on that port. Try an alternate port (many pools offer ports 443 or 25).

Try a Different Pool

Temporarily configure a well-known public pool to rule out pool-side issues. If hashrate appears on the test pool, the original pool configuration was the problem.

Prevention: Double-check pool settings after every firmware update, as some updates reset configuration. Keep a text file with your correct pool settings for quick reference.

2. Network Issue

Probability: High

The miner needs a stable network connection to receive work from the pool and submit shares. Even brief network interruptions can cause the hashrate to drop to zero temporarily.

Symptoms specific to this cause:

Web UI may be slow or unreachable intermittently
Miner log shows "Stratum connection timeout" or "Network unreachable"
Pool shows worker going online/offline repeatedly
Other devices on the same network may also have issues

Diagnosis:

Check Physical Connection

Inspect the Ethernet cable for damage. Verify link lights are active on both the miner's Ethernet port and the switch/router port. Try a different cable and a different switch port.

Verify IP Address

Access your router's DHCP lease table and confirm the miner has a valid IP address. If using static IP, ensure there are no IP conflicts.

Test DNS Resolution

Some miners fail silently when DNS resolution fails. Try using the pool's IP address directly instead of the hostname to rule out DNS issues.

Fix: Replace faulty cables, ensure the miner has a reliable DHCP lease or static IP, and verify your router is not dropping connections. For detailed network troubleshooting, see Network Problems.

Prevention: Use quality Cat5e or Cat6 cables. Assign static IP addresses or DHCP reservations to miners. Monitor network health with tools like ping monitoring.

3. Hashboard Connector Loose or Damaged

Probability: Medium-High

Hash boards connect to the control board via ribbon cables (Antminer), signal cables, and power cables. Vibration from fans, shipping, or maintenance can loosen these connections.

Symptoms specific to this cause:

One or more chains show "0 ASIC" while others work fine
Problem appeared after moving or shipping the miner
Intermittent detection: chain appears and disappears across reboots

Diagnosis:

Identify the Affected Chain

In the web UI, note which chain number(s) show 0 chips. Each chain corresponds to a specific hash board and control board port.

Antminer S19/S21 series have 3 chains (Chain 0, 1, 2). Each connects via a ribbon cable to the control board. The ribbon cable carries both data signals (SPI/UART) and chip addressing.

Whatsminer M30/M50/M60 series have 3 hash boards. Each connects with both a signal cable and a power cable to the PSU. Check the 10-pin signal connector on the control board side.

Avalon miners use a modular design with hash boards connecting to the controller (AUC). Check the 5-pin or 7-pin connectors on each board.

Reseat All Connectors

Power off the miner completely. Open the miner and firmly reseat:

Signal/data cables (ribbon cables or pin headers)
Power cables from PSU to each hash board
Fan connectors (a missing fan can cause the miner to shut down chains)

Ensure ribbon cables are not bent at sharp angles and connector latches are fully engaged.

Swap Test

To determine if the problem is the hash board or the control board port:

Swap the ribbon cable of the failing chain with a working chain
If the problem follows the port on the control board, the control board port is damaged
If the problem follows the hash board, the hash board has a fault

Fix: Reseat or replace damaged connectors. If the ribbon cable is torn or the connector pins are bent, replace the cable. For Antminer ribbon cables, ensure the blue stripe faces the correct direction (marked on the PCB).

Prevention: Handle miners carefully during transport. Use anti-vibration mounting where possible. During maintenance, be gentle with ribbon cables -- they are fragile.

4. Control Board Failure

Probability: Medium

The control board is the "brain" of the miner. It runs the mining firmware, communicates with hash boards, and connects to the pool. A failed control board can prevent all hash boards from being detected.

Symptoms specific to this cause:

ALL chains show "0 ASIC" simultaneously
Web UI loads but shows no chain data
Miner keeps rebooting (boot loop)
LEDs on the control board show abnormal patterns
SSH access shows kernel errors or filesystem corruption

Diagnosis:

Check the red/green LEDs on the control board. A solid red LED typically indicates a fault. Try accessing the miner via SSH (ssh root@<ip>, default password root) and check the system log:

# Check kernel log for errors
dmesg | tail -50

# Check miner log
cat /tmp/log/miner.log | tail -100

# Check if chain detection is running
ps | grep bmminer

If the filesystem is read-only or corrupted, this indicates NAND flash failure on the control board.

Use the WhatsMiner Tool software to scan for the miner. If the tool detects the miner but shows "abnormal" status, try a firmware reflash. Whatsminer control boards have a status LED near the Ethernet port -- it should blink during normal operation.

Connect the AUC (Avalon USB Converter) to a computer and check the CGMiner output. If CGMiner cannot detect any modules, the controller or AUC may be faulty. Try a different AUC first.

Fix: Flash fresh firmware via SD card (Antminer), WhatsMiner Tool (Whatsminer), or UART (Avalon). If firmware reflash does not help, the control board hardware is faulty and needs replacement. See Firmware Corruption Recovery.

Prevention: Use a UPS or surge protector to prevent power-related control board damage. Avoid interrupted firmware updates.

5. Hashboard Failure

Probability: Medium

A hash board can fail completely due to a shorted component, failed voltage regulator, or communication chain break at the first chip. When this happens, the entire board reports 0 chips.

Symptoms specific to this cause:

Single chain consistently shows "0 ASIC" across reboots
Problem persists after swapping to a different control board port
The board may feel abnormally hot or cold compared to working boards
Visible damage (burnt components, swollen capacitors, cracked solder joints)

Diagnosis:

Visual Inspection

Remove the hash board and inspect both sides under good lighting (a magnifying glass or phone camera zoom helps):

Look for burnt or discolored components
Check for cracked solder joints especially on the first and last ASIC chips
Inspect the connector pins for bent or corroded contacts
Look for swollen or leaking capacitors

Voltage Domain Check

Using a multimeter, measure the voltage across each voltage domain while the board is powered (with proper safety precautions). Each domain should show the expected chip voltage (typically 0.25V-0.40V depending on the model). A domain reading 0V or abnormally high indicates a regulator or short-circuit failure.

Communication Chain Test

The ASIC chips are connected in a daisy chain. If chip #0 (the first chip) has failed, no other chips on the board can be detected. Check signal continuity on the CLK, CI (Command Input), and RI (Response Input) traces from the connector to the first chip.

Fix: Hash board repair requires component-level soldering skills. Common repairs include replacing failed ASIC chips, voltage regulators, or repairing broken traces. See the Antminer S21 Hashboard Repair Guide for detailed procedures.

Prevention: Maintain proper airflow and temperature. Clean miners regularly to prevent dust-induced shorts. Avoid running miners above recommended voltage or frequency settings.

6. PSU Insufficient or Failed

Probability: Medium-Low

If the power supply cannot deliver enough power, the miner may start but fail to initialize hash boards. This can happen when a PSU is degraded, undersized, or has a failed rail.

Symptoms specific to this cause:

Miner powers on, fans spin briefly, then some or all boards fail to start
PSU makes clicking or buzzing sounds
Hashrate appears briefly then drops to zero as all boards power up
PSU overheating or shutting down under load
Multiple hash boards fail simultaneously

Diagnosis:

Measure PSU Output

Using a multimeter, measure the PSU's output voltage at the hash board connectors:

12V systems (most miners): Should read 11.8V-12.3V under load
48V systems (S21, newer models): Should read 47V-52V under load

If voltage sags significantly below spec under load, the PSU is failing.

Test PSU Independently

Bitmain APW series (APW7, APW9, APW12) can be tested by shorting the signal pins on the control connector to force the PSU on without the miner. Measure the output voltage and check for stability. Refer to the specific APW model's pinout documentation.

Whatsminer P21/P22 PSUs are integrated or semi-integrated. Use WhatsMiner Tool to read PSU telemetry data. If the PSU reports over-current protection (OCP) triggers, it may be undersized for the configured power limit.

For ATX-style PSUs (used with some mining setups), perform the paperclip test: short the green wire (PS_ON) to any black wire (ground) on the 24-pin connector to turn on the PSU without a motherboard.

Check Power Cord and Outlet

Measure voltage at the wall outlet. For 240V installations, verify you have 220-240V. Low input voltage causes PSU efficiency to drop and may trigger under-voltage protection. Ensure the power cord is rated for the miner's current draw (typically 15A-20A).

Fix: Replace the PSU if it cannot maintain stable output voltage under load. Ensure the replacement PSU is rated for the miner's power draw with at least 10% headroom. For more details, see Power Supply Issues.

Prevention: Use dedicated circuits for miners. Avoid daisy-chaining power strips. Keep PSUs clean and well-ventilated. Monitor input voltage at the wall outlet.

7. Firmware Corruption

Probability: Low

Corrupted firmware can cause the mining software to fail silently. The miner may appear to boot normally but never start hashing, or it may enter a boot loop.

Symptoms specific to this cause:

Problem started after a firmware update (especially if it was interrupted)
Miner boots but the mining process never starts
Web UI shows unusual behavior or is partially broken
SSH shows errors in the mining software startup

Diagnosis:

Check the miner log for firmware-related errors:

# SSH into the miner
ssh root@<miner_ip>

# Check if the mining process started
ps | grep bmminer

# Look for startup errors
cat /tmp/log/miner.log

If bmminer (or cgminer on older models) is not running or keeps crashing, firmware corruption is likely.

Use WhatsMiner Tool to check the firmware version and status. If the tool shows "abnormal" status, a firmware reflash is recommended.

Check CGMiner output via the AUC connection. Kernel panics or repeated "module not found" messages indicate firmware issues.

Fix: Reflash the firmware using the appropriate method for your miner brand. See Firmware Corruption Recovery for complete instructions.

Prevention: Always download firmware from the manufacturer's official website. Verify checksums before flashing. Never interrupt a firmware update -- ensure stable power during the process.

When to Seek Professional Help

Contact a qualified repair technician if:

You have worked through all the causes above and the problem persists
You see visible damage on the control board or hash boards (burnt components, corrosion)
The miner produces electrical burning smells or smoke
You are not comfortable measuring voltages on live equipment
Multiple miners developed the same issue simultaneously (possible electrical infrastructure problem)

When contacting a repair service, provide: the miner model, firmware version, the exact error messages from the web UI, and which troubleshooting steps you have already completed. This helps the technician diagnose the issue faster.

Frequently Asked Questions

Q: My miner was working fine yesterday and now shows 0 hashrate. What happened?

The most likely causes for sudden zero hashrate are: pool-side issues (pool maintenance or configuration change), network interruption, or a PSU trip. Start with the Quick Checks section above. If the miner's web UI shows all chains with normal chip counts and temperatures, the issue is almost certainly pool- or network-related.

Q: Only one chain shows 0 ASIC. Should I worry?

A single chain reading 0 ASIC while others work normally is most likely a loose connector or a hash board failure. This does not indicate a systemic problem. Follow the connector reseat procedure, then the swap test to isolate the cause.

Q: My miner shows chips detected but hashrate is 0 TH/s. What is different?

If chips are detected but hashrate is zero, the mining software may be failing to send work to the chips. This is typically a firmware or pool configuration issue, not a hardware problem. Check pool settings first, then consider a firmware reflash.

Q: How long should I wait after powering on before being concerned about zero hashrate?

Allow 5-10 minutes after power-on for the miner to fully initialize. Some models, particularly after a firmware update or configuration change, take longer to detect all chips and begin hashing. If there is no hashrate after 15 minutes, begin troubleshooting.

Q: Can a bad fan cause zero hashrate?

Yes. Most miners have thermal protection that prevents hash boards from starting if fans are not detected or not spinning fast enough. Check that all fans are connected and spinning. See Fan Errors.

Power Supply Issues -- PSU testing and replacement
Network Problems -- Finding your miner on the network
Firmware Corruption Recovery -- How to reflash firmware
Missing ASIC Chips -- When some but not all chips are detected
Fan Errors -- Fan detection and speed issues
How Hash Boards Work -- Understanding hash board architecture
Antminer S21 Hashboard Repair Guide -- Board-level repair procedures

Miner Shows No Hashrate — Troubleshooting Guide

On this page