← Back to Glossary

Hashboard Failure

A Hashboard Failure is a condition in which one of an ASIC miner’s hashboards stops operating correctly, operates only partially, or cannot be detected by the miner’s control system. The hashboard is the part of an ASIC miner that contains the specialized chips responsible for performing Bitcoin’s SHA-256 hashing calculations. A failure can affect an entire board or only part of it.

Hashboard Failure Explained in Simple Terms

An ASIC miner usually contains several major components:

  • control board

  • power supply

  • cooling system

  • one or more hashboards

The hashboards perform the actual hashing work.

Imagine an ASIC miner with three hashboards producing a combined 120 TH/s.

If each board contributes roughly one-third of the total performance, losing one board could significantly reduce the miner’s hash rate.

The miner may still be online.

Its fans may still operate.

Its management interface may still be accessible.

But part of its hashing hardware is no longer contributing normally.

This is why a miner that appears to be running can still have a hashboard failure.

How Hashboard Failure Works

A hashboard contains multiple ASIC chips and supporting electronic components.

Its basic role is:

Receive Mining Work → ASIC Chips Calculate Hashes → Results Return to Control System

The control board coordinates mining activity and communicates with the hashboards.

Power circuitry supplies the electrical energy required by the ASIC chips, while heat sinks or another cooling system remove the heat generated during operation.

All of these systems must work correctly for a hashboard to operate reliably.

Example of Hashboard Failure in Practice

A simplified failure sequence might look like this:

  1. The Hashboard Operates Normally
    ASIC chips perform hashing work.

  2. A Problem Develops
    A chip, power component, connection, thermal interface, or communication path becomes unstable.

  3. The Board Produces Abnormal Behavior
    Errors, temperature problems, or missing chips may appear.

  4. Firmware Detects the Problem
    Diagnostic logs or monitoring data show abnormal board status.

  5. Performance Declines
    The board may operate partially or stop hashing completely.

The sequence can be summarized as:

Component Problem → Board Instability → Errors/Detection Failure → Hash Rate Loss

Example of a Hashboard Failure

Suppose an ASIC miner contains three hashboards.

During normal operation, the monitoring interface shows:

  • Hashboard 1: detected

  • Hashboard 2: detected

  • Hashboard 3: detected

Later, total hash rate drops significantly.

The operator checks the miner and finds:

  • Hashboard 1: normal

  • Hashboard 2: normal

  • Hashboard 3: not detected

Firmware logs also show repeated initialization problems associated with the third board.

This indicates that the investigation should focus on Hashboard 3 and its associated power, communication, and hardware components.

However, the missing board does not automatically prove that the physical hashboard itself is permanently damaged. Problems elsewhere can produce similar symptoms.

Common Symptoms of Hashboard Failure

A failing hashboard can produce several symptoms:

  • significant reduction in total hash rate

  • one board missing from the miner interface

  • reduced detected ASIC chip count

  • unusually high hardware errors

  • board initialization failures

  • abnormal temperature readings

  • unstable hash rate

  • repeated miner restarts

  • one board operating differently from the others

  • complete failure to start hashing

Some failures are intermittent.

A board may operate normally when the miner starts and disappear after reaching operating temperature.

This can make diagnosis more difficult.

What Causes Hashboard Failure?

Hashboard problems can have many causes.

ASIC Chip Failure

A hashboard contains multiple ASIC chips.

Individual chips can become unstable or fail because of:

  • electrical stress

  • excessive temperature

  • physical damage

  • component degradation

  • manufacturing defects

Depending on the board architecture, one problematic chip may also interfere with communication to other chips.

Power Problems

Hashboards require stable electrical power.

Problems can originate from:

  • PSU failure

  • board-level power circuitry

  • damaged connectors

  • poor electrical contact

  • unstable voltage

  • excessive power settings

If a board does not receive appropriate power, it may fail to initialize or become unstable under load.

Overheating

ASIC chips generate substantial heat.

Poor thermal conditions can result from:

  • blocked airflow

  • dust accumulation

  • failed fans

  • high ambient temperature

  • poor heat sink contact

  • degraded thermal interface material

  • cooling-system problems

Persistent excessive temperatures can reduce stability and may eventually contribute to component damage.

Communication Problems

The control board must communicate with each hashboard.

A communication failure can cause a healthy board to appear missing.

Possible causes include:

  • loose connections

  • damaged signal cables

  • connector problems

  • control-board problems

  • board-level communication faults

This is one reason why a “missing hashboard” and a “failed hashboard” are not always the same thing.

Aggressive ASIC Tuning

Custom firmware can change:

  • frequency

  • voltage

  • power limits

Aggressive settings can place additional stress on hashboards.

For example:

Higher Frequency + Higher Voltage → More Power + More Heat

If the hardware or cooling system cannot support the configuration, instability can increase.

Physical Damage

Hashboards can also be damaged by:

  • improper handling

  • liquid exposure

  • corrosion

  • electrical shorts

  • damaged connectors

  • unsuitable operating environments

Physical inspection may be necessary when software diagnostics cannot identify the cause.

Hashboard Failure vs Missing Hashboard

These terms should be distinguished.

Missing Hashboard

Means the miner’s control system cannot successfully detect or initialize a board.

Hashboard Failure

Is a broader condition where a board cannot perform its intended function correctly.

A missing board can be caused by the hashboard itself, but it can also result from:

  • power problems

  • communication problems

  • cable or connector issues

  • control-board problems

Therefore:

Missing Hashboard ≠ Automatically a Dead Hashboard

Further diagnostics are required.

Hashboard Failure vs ASIC Chip Failure

A hashboard contains many ASIC chips.

An ASIC chip failure affects an individual chip.

A hashboard failure affects the operation of the board as a functional unit.

Depending on the hardware design, a single chip problem may:

  • affect only that chip

  • reduce board performance

  • interrupt communication with multiple chips

  • prevent the board from initializing correctly

Chip-level diagnostics can therefore be important when investigating a board-level problem.

Hashboard Failure and Hash Rate

A failed or partially functioning hashboard usually reduces total miner performance.

Consider a simplified example:

Hashboard

Normal Hash Rate

Current Status

Board 1

40 TH/s

Normal

Board 2

40 TH/s

Normal

Board 3

40 TH/s

Failed

Total

120 TH/s

~80 TH/s

This example assumes approximately equal board performance.

Real miners can distribute hash rate differently depending on the model and tuning configuration.

Hashboard Failure and Hardware Errors

A failing board does not always disappear completely.

Sometimes it remains online but produces unusually high HW errors.

For example:

Unstable ASIC Chip → Incorrect Computations → Increasing HW Errors

An operator may notice:

  • normal board detection

  • reduced effective performance

  • high error counts

  • unstable chip behavior

This can indicate a developing problem rather than a complete board failure.

Hashboard Failure and Temperature

Temperature data can provide important diagnostic clues.

Suppose one board consistently operates much hotter than the others.

Possible causes include:

  • poor heat sink contact

  • restricted local airflow

  • thermal interface problems

  • abnormal chip behavior

Alternatively, an unusually low or missing temperature reading could indicate a sensor or communication problem rather than excellent cooling.

Diagnostic data must therefore be interpreted in context.

Hashboard Failure and Power Consumption

Power data can also help identify failures.

If a miner loses one hashboard, its total electrical consumption may decrease because fewer ASIC chips are operating.

However, abnormal power behavior can also be the cause of the failure.

Operators may therefore compare:

Hash Rate + Board Status + Power Consumption

A major reduction in both hash rate and power can support the conclusion that part of the hashing hardware is no longer active.

Hashboard Failure and ASIC Diagnostics

ASIC diagnostics can help narrow the cause of a hashboard problem.

A typical diagnostic process may include:

  1. Compare current and expected hash rate.

  2. Check whether all hashboards are detected.

  3. Check the number of detected ASIC chips.

  4. Review board and die temperatures.

  5. Check HW errors.

  6. Review frequency and voltage settings.

  7. Examine firmware logs.

  8. Verify power delivery.

  9. Inspect communication connections.

  10. Retest after corrective action.

The objective is to distinguish between:

Board Hardware Problem

and problems involving:

Power / Cooling / Communication / Firmware / Configuration

Hashboard Failure and Firmware Logs

Firmware logs can provide useful information about what happens during miner startup and operation.

Logs may show:

  • board detection failures

  • ASIC initialization problems

  • abnormal chip counts

  • temperature sensor errors

  • communication failures

  • tuning instability

  • shutdown events

The terminology and level of detail vary between ASIC manufacturers and firmware implementations.

A log message should therefore be interpreted according to the specific miner and firmware.

Intermittent Hashboard Failure

Some hashboard problems are intermittent rather than permanent.

A board might:

  • appear after a restart

  • hash normally for several minutes

  • become unstable as temperature rises

  • disappear from the miner

  • return after cooling or rebooting

Possible causes can include thermal, electrical, connection, or component-level problems.

Intermittent failures can be particularly useful to analyze using historical monitoring data because the conditions immediately before the failure may reveal a pattern.

Hashboard Failure and Preventive Maintenance

Not every hashboard problem can be prevented, but good operating conditions can reduce unnecessary stress.

Useful practices include:

  • maintaining adequate cooling

  • controlling dust

  • monitoring temperatures

  • avoiding unsuitable tuning settings

  • maintaining stable power delivery

  • monitoring HW error trends

  • inspecting abnormal miners promptly

Preventive monitoring can identify deterioration before a board stops hashing completely.

For example:

Normal Errors → Rising Errors → Unstable Hash Rate → Board Failure

Recognizing the earlier stages can reduce downtime.

Can a Failed Hashboard Be Repaired?

Some hashboard failures can be repaired.

The solution depends on the cause.

Possible repair areas include:

  • failed electronic components

  • damaged connectors

  • communication circuits

  • power circuitry

  • individual ASIC chips

  • thermal components

Other boards may be more economical to replace than repair.

Board-level ASIC repair can require specialized diagnostic equipment and electronics expertise, so it is different from routine miner configuration or maintenance.

Hashboard Repair vs Replacement

The decision depends on several factors:

Factor

Why It Matters

Repair cost

May approach replacement cost

ASIC model

Older boards may have lower economic value

Component availability

Replacement chips or parts may be difficult to source

Failure type

Some faults are easier to repair than others

Downtime

Extended repair time reduces mining availability

Miner profitability

Low-efficiency hardware may not justify major repairs

The technically repairable option is not always the economically optimal option.

Hashboard Failure at Mining-Farm Scale

At a large mining facility, hashboard failures can affect hundreds of machines over time.

Monitoring systems can automatically identify miners with:

  • missing boards

  • reduced chip counts

  • abnormal hash rates

  • excessive HW errors

  • unusual temperatures

This allows technicians to prioritize machines that require physical inspection.

Instead of manually checking every miner, operators can use:

Monitoring → Automatic Alert → Diagnostics → Maintenance

Frequently Asked Questions

Still have questions about Hashboard Failure?

Have traffic?

Earn with the best product in cloud mining

Become a partner
15%

First purchase

On every new user’s first purchase. No limit on the purchase amount.

5%

Repeat purchases

Earn for life from every repeat purchase. When the user buys again, you earn again.