AZIC Education

How Hash Boards Work: Complete Guide to Mining Hardware Architecture

Learn how cryptocurrency mining hash boards work — from ASIC chip architecture to voltage domains, signal chains, and common failure modes explained for repair technicians.

Introduction

A hash board is the beating heart of every ASIC miner. It is the single component responsible for performing the cryptographic computations that secure proof-of-work blockchains like Bitcoin. While control boards manage communication and power supplies deliver energy, it is the hash board that converts electricity into hashes — trillions of SHA-256 double-hash operations every second.

For repair technicians, the hash board is where most failures occur and where most repair work is focused. A single Antminer S21, for example, contains three hash boards, each carrying 156 BM1368 ASIC chips. When one of those chips fails, or when a voltage regulator drifts out of specification, or when a signal trace cracks from thermal cycling, the entire board can go offline. Understanding the architecture of these boards — how power is delivered, how chips communicate, how clock signals propagate — is the foundation of every successful diagnosis and repair.

This guide provides a comprehensive technical walkthrough of hash board architecture, organized from the physical layer up through the computational layer. Whether you are diagnosing your first "0 ASIC" error or building expertise in multi-domain voltage testing, this document will give you the mental model you need.

What Is a Hash Board and Its Role in a Miner

The Miner as a System

An ASIC miner is composed of three primary subsystems that work together:

  1. Control board — the "brain" that communicates with the mining pool, distributes work, and monitors health
  2. Power supply unit (PSU) — converts AC mains power to the DC voltages the system needs
  3. Hash boards — the "muscles" that perform the actual SHA-256 computation

The control board receives block header templates from the mining pool over Ethernet, breaks the work into smaller job packets, and distributes those jobs across the hash boards. Each hash board independently processes its assigned work and reports back any valid nonces (solutions) it discovers. The control board then submits those solutions to the pool for credit.

Why Hash Boards Matter Most

In a typical Antminer, hash boards account for roughly 85-90% of the total power consumption, nearly 100% of the heat generation, and the vast majority of component failures. A miner with three hash boards where one has failed loses a third of its revenue while still consuming significant power for cooling and control overhead. This is why hash board repair is the most economically valuable skill in mining hardware maintenance.

Hash Board Generations at a Glance

Bitmain's hash board designs have evolved significantly across generations:

Miner ModelASIC ChipProcess NodeChips/BoardHashrate/BoardBoard PowerYear
Antminer S9BM138716nm63~4.5 TH/s~460W2016
Antminer S17BM13977nm54~18 TH/s~820W2019
Antminer S19BM13987nm76~34 TH/s~1100W2020
Antminer S19 XPBM13665nm110~47 TH/s~1050W2022
Antminer S21BM13685nm156~67 TH/s~1150W2023

Each generation packs more chips onto the board and runs them at lower core voltages. The trend is clear: more parallelism at lower per-chip power. This means newer boards have more voltage domains, tighter tolerances, and more potential failure points — making repair knowledge increasingly valuable.

Physical Anatomy: PCB Layers, Component Placement, and Signal Flow

PCB Construction

Hash board PCBs are multilayer boards, typically 4 to 6 layers, designed to handle the extreme current demands of dozens or hundreds of ASIC chips. The layer stackup serves distinct purposes:

  • Top layer — ASIC chip pads, signal routing (CI/CO/RI/RO), decoupling capacitors
  • Inner layer 1 — power plane (VDD core voltage distribution)
  • Inner layer 2 — ground plane (VSS return path)
  • Inner layer 3 — additional signal routing or secondary power plane
  • Bottom layer — voltage regulator components, connector pads, additional routing

The ground plane is critical. It provides a low-impedance return path for the massive currents flowing through the board. A hash board running 156 chips at 0.30V core voltage may draw over 300 amps of total current across all voltage domains. The ground plane must handle this without excessive voltage drop.

Component Layout

Looking at a hash board from above, you will see a highly regular pattern. The board is organized into repeating blocks, each containing:

  • A group of ASIC chips (typically 7-15 chips depending on generation)
  • A voltage regulator circuit powering that group (buck converter, inductor, capacitors)
  • Decoupling capacitors on every chip's VDD and VDDIO pins
  • Signal chain traces connecting each chip to its neighbors

This repeating pattern is the voltage domain — a concept so fundamental to hash board repair that it deserves its own section.

Board Connectors

At the edges of the hash board, you will find connectors for:

  • Power input — heavy-gauge pins or edge connectors carrying 12V (or 48V) from the PSU
  • Signal connector — typically a ribbon cable or pin header connecting to the control board, carrying UART/SPI communication, clock reference, and status signals
  • Temperature sensor — on-board NTC thermistor or digital sensor (LM75A, TMP451) for thermal monitoring

The power input connectors carry enormous current. Burnt or corroded power connectors are a common failure mode, especially in humid environments. Always inspect these connectors visually before applying power to a board under test.

The Signal Path at a High Level

The overall signal flow on a hash board follows this path:

Control Board

    ├── CLK (clock reference)
    ├── TX (commands/jobs to hash board)
    ├── RX (nonces/responses from hash board)


[Chip 0] → [Chip 1] → [Chip 2] → ... → [Chip N]
   CI/CO      CI/CO      CI/CO              CI/CO
   RI/RO      RI/RO      RI/RO              RI/RO

Commands flow from the control board into chip 0 and propagate down the chain. Responses (nonces) flow back through the chain in the reverse direction. The clock signal may be distributed from a single source or regenerated at each chip, depending on the architecture.

Voltage Domains: How Power Is Distributed Across Chip Groups

The Problem of Low Voltage at High Current

ASIC chips operate at remarkably low core voltages — as low as 0.25V for some modern chips. Delivering power at these voltages is an engineering challenge because of Ohm's law: at low voltage, even tiny resistances in the PCB traces cause significant voltage drops. If you tried to power all 156 chips on an S21 board from a single 0.30V supply, the far end of the board would see substantially less voltage than the near end. Chips would malfunction or fail to operate.

The Domain Solution

The solution is to divide the board into voltage domains — independent groups of chips, each with its own local voltage regulator. This way, no chip is more than a few centimeters from its power source, and voltage drops are kept within acceptable tolerances.

Each voltage domain consists of:

  1. A buck converter — steps down the 12V (or 48V) input to the chip core voltage (e.g., 0.30V)
  2. An LC filter — inductor and output capacitors to smooth the switching regulator output
  3. A group of ASIC chips — connected in parallel to this power rail
  4. Decoupling capacitors — small ceramics on each chip's power pins to handle transient demands

Voltage Domain Comparison by Generation

ParameterS19 / BM1398S19 XP / BM1366S21 / BM1368
Total chips per board76110156
Number of voltage domains~12~12~12
Chips per domain~7~11~13
Core voltage (VDD)0.31V0.28V0.30V
I/O voltage (VDDIO)1.8V1.8V1.8V
Domain current (typical)~15A~20A~25A

When measuring voltage domains, always measure at the chip pads, not at the regulator output. The PCB trace resistance between the regulator and the farthest chip in the domain can cause a measurable voltage difference. For detailed measurement procedures, see Voltage Domains & Regulators.

What Happens When a Domain Fails

A failed voltage domain typically presents as a group of consecutive "missing chips" in the miner's diagnostic output. If domain 5 fails on an S21 board, you might see chips 52 through 64 reported as unresponsive while all other chips function normally. This is a strong diagnostic clue — a cluster of missing chips almost always points to a voltage domain problem rather than individual chip failures.

Common domain failure causes include:

  • Failed buck converter IC — the regulator itself has died
  • Shorted output capacitor — pulls the voltage rail to ground
  • Shorted ASIC chip — an internally failed chip that shorts VDD to ground, dragging down the entire domain
  • Open inductor — the power path is interrupted
  • Cold solder joint on the regulator — intermittent or complete loss of the voltage rail

VDDIO and VDD33 Rails

In addition to the core VDD voltage, hash boards have secondary voltage rails:

  • VDDIO (1.8V) — powers the I/O buffers on each chip. This rail handles the communication signals (CI/CO/RI/RO). If VDDIO fails, chip communication breaks even if the core voltage is healthy.
  • VDD33 (3.3V) — powers miscellaneous logic, temperature sensors, and sometimes the PLL circuits. This rail is typically generated by a separate regulator near the signal connector end of the board.

A common misdiagnosis is blaming ASIC chips when the real problem is the 1.8V VDDIO rail. If the entire board shows "0 ASIC" but the VDD domains all measure correctly, check VDDIO immediately. Without I/O power, no chip can communicate regardless of whether its cores are functional.

Hash Chain: How Chips Are Connected in Series

The Daisy Chain Architecture

ASIC chips on a hash board are not independently addressed like devices on an I2C bus. Instead, they are connected in a daisy chain (also called a signal chain or hash chain), where each chip's output feeds directly into the next chip's input.

The chain uses two primary signal pairs:

  • CI/CO (Clock In / Clock Out) — carries the clock signal from chip to chip
  • RI/RO (Receive In / Receive Out) — carries data (commands and responses) from chip to chip
Control Board

    ├── CLK ──→ [Chip 0 CI] → [CO→CI Chip 1] → [CO→CI Chip 2] → ... → [Chip N CO]

    ├── TX  ──→ [Chip 0 RI] → [RO→RI Chip 1] → [RO→RI Chip 2] → ... → [Chip N RO]

    └── RX  ←── [responses propagate back through the chain]

Chip Addressing and Enumeration

When the control board initializes a hash board, it performs an enumeration process. Starting from chip 0, it sends an address assignment command down the chain. Each chip receives its address and passes the next address to the following chip. After enumeration, every chip has a unique address, and the control board knows exactly how many chips are present.

Bitmain chips (BM1366, BM1368, BM1398) use a UART-based protocol at the physical layer. During enumeration:

  1. The control board sends a broadcast "set address" command
  2. Chip 0 claims address 0x00 and forwards the command with an incremented address
  3. Each subsequent chip repeats this process
  4. The final chip's response tells the control board the total chip count

The enumeration process also reads each chip's version register to verify the chip type and detect any chips that are unresponsive or returning incorrect data.

The physical signals between chips are single-ended UART-like signals running at 1.8V logic levels (set by VDDIO). Typical baud rates range from 1.5 Mbps to 6 Mbps depending on the chip generation and firmware configuration.

Each chip acts as a repeater: it receives data on RI, processes it, and forwards it (or its own response) on RO. Similarly for the clock path through CI/CO. This means every chip in the chain must be functional for communication to reach chips further down the chain.

The "Broken Chain" Problem

The daisy chain architecture has an inherent vulnerability: a single failed chip can break communication to all chips downstream of it. This is the most common cause of "missing chips" errors in miner diagnostics.

Consider a board with 156 chips. If chip 43 fails with an open circuit on its RO pin:

  • Chips 0-42: functional (they are upstream of the failure)
  • Chip 43: unresponsive (the failed chip)
  • Chips 44-155: unreachable (they never receive any data from upstream)

The miner's kernel log might report "found 42 chips" or show a large block of missing chips starting at position 43. This pattern — functional chips followed by a cliff where all remaining chips disappear — is the hallmark of a signal chain break.

Some newer chip designs include a BO (Break Out) signal that can bypass a failed chip in the chain. When a chip detects that it cannot communicate, it activates BO, which routes the signal around the dead chip to the next one. This feature does not exist on all generations. See ASIC Chip Architecture for details on which chips support this.

Finding the Break Point

Repair technicians use several methods to locate the exact point of a chain break:

  1. Chip count analysis — if the miner reports N chips found, the break is likely at chip N or N+1
  2. Signal injection — using a test fixture or UART adapter to inject signals at various points along the chain and observing which chips respond
  3. Voltage probing — measuring the CI/CO and RI/RO signals with an oscilloscope at various chip positions to find where the signal stops propagating

For a hands-on walkthrough, see Your First Hash Board Repair and Systematic Diagnostics Methodology.

Clock Distribution: PLL and Crystal Oscillators

Why Clock Matters

Every ASIC chip needs a precise clock signal to operate. The clock determines the hashing frequency — how many SHA-256 operations the chip performs per second. A chip running at 500 MHz performs approximately 500 million hash attempts per second per core. With hundreds of cores per chip, this translates to hundreds of gigahashes per second per chip.

Clock Source

Hash boards receive a reference clock from the control board, typically a crystal oscillator running at 25 MHz or a similar frequency. This reference clock enters the first chip in the chain (chip 0) through its CI (Clock In) pin.

PLL (Phase-Locked Loop)

Each ASIC chip contains an internal PLL (Phase-Locked Loop) that multiplies the incoming reference clock to the chip's operating frequency. For example:

  • Input: 25 MHz reference clock
  • PLL multiplication: 25 MHz x 20 = 500 MHz internal clock
  • Result: chip cores run at 500 MHz

The PLL configuration is programmable. The control board firmware sets each chip's PLL registers during initialization, allowing the operating frequency to be tuned for optimal performance versus power consumption. Overclocking (running the PLL at a higher multiplier) increases hashrate but also increases power consumption and heat.

PLL Register Configuration

PLL settings are encoded in registers specific to each chip family:

// Example PLL frequency settings (simplified)
// BM1398 (S19): postdiv encoding differs from newer chips
// BM1366 (S19 XP) and BM1368 (S21): use postdiv-minus-1 encoding

// Target 500 MHz on BM1366:
//   PLL register value: 0x00F0286401
// Target 600 MHz on BM1366:
//   PLL register value: 0x00F0306401
// Target 700 MHz on BM1366:
//   PLL register value: 0x00F0386401

PLL registers are chip-specific and must use the correct encoding for the chip model. The BM1398 uses a different post-divider encoding than the BM1366 and BM1368. Using the wrong encoding can result in chips running at incorrect frequencies, causing hardware errors or instability.

Clock Propagation Through the Chain

The reference clock propagates through the chip chain via the CI/CO (Clock In / Clock Out) path. Each chip receives the clock on CI, uses it as the PLL reference, and outputs it on CO to the next chip. The PLL in each chip is independently locked to this reference, so all chips on the board operate at the same reference frequency even though each has its own PLL.

If a chip's PLL fails to lock, that chip may:

  • Produce no hashes (completely non-functional)
  • Produce hashes at the wrong rate (frequency drift)
  • Generate excessive hardware errors (HW errors in the miner log)
  • Fail to forward the clock to downstream chips, breaking the chain

Diagnosing Clock Problems

Clock-related failures are more subtle than voltage domain failures. Symptoms include:

  • High HW error rate on specific chips — PLL is unstable or not locked properly
  • Low hashrate with all chips detected — one or more PLLs running at wrong frequency
  • Intermittent chain breaks — clock signal degrading as it propagates through many chips

An oscilloscope is essential for diagnosing clock problems. You should see a clean, stable clock signal on the CI pin of each chip. A degraded, noisy, or absent clock signal points to a problem upstream — either a failed chip's CO output or a damaged trace between chips.

For more on clock circuits, see Clock Distribution & PLL.

Data Flow: Job Distribution, Nonce Finding, and Result Reporting

The Mining Process on a Hash Board

Understanding the full data flow from pool to nonce is essential for diagnosing performance problems. Here is how mining work moves through a hash board:

Pool Sends Work to Controller

The mining pool sends a block header template to the miner's control board over the network. This template includes:

  • Previous block hash
  • Merkle root of transactions
  • Timestamp
  • Difficulty target (encoded as nBits)
  • A nonce range for this miner to search

Controller Distributes Jobs to Chips

The control board firmware divides the total nonce search space among the available hash boards, and each hash board further divides its share among its chips. Each chip receives a job containing:

  • The block header data (midstate — a pre-computed partial SHA-256 state)
  • A nonce range to search (each chip gets a unique range to avoid duplicate work)
  • The difficulty target

Jobs are sent as UART packets down the chip chain. Each chip reads the job addressed to it and passes the rest downstream.

Chips Search for Valid Nonces

Each chip's hashing cores work in parallel, iterating through their assigned nonce range. For every nonce value, the chip computes:

result = SHA-256(SHA-256(block_header + nonce))

If the result is below the difficulty target, the chip has found a valid nonce — a potential solution to the block. The chip immediately reports this result.

Results Flow Back to Controller

When a chip finds a valid nonce, it constructs a response packet containing the nonce value and the job ID it was working on. This response travels back through the chain to the control board.

The control board validates the result and submits it to the mining pool. If the nonce meets the pool's current difficulty, the miner earns a share of the block reward.

Midstate Optimization

Modern ASIC miners use a technique called midstate optimization to reduce the work each chip must perform. The SHA-256 algorithm processes data in 64-byte blocks. The block header is 80 bytes, which means two SHA-256 compression rounds. The first 64 bytes of the header rarely change (they contain the previous block hash and most of the Merkle root), so the control board pre-computes the SHA-256 state after processing those first 64 bytes. This pre-computed state is called the midstate.

Each chip only needs to complete the second compression round with the remaining 16 bytes (which include the nonce). This cuts the per-hash computation roughly in half, significantly improving throughput.

Nonce Space Division

The nonce field in a Bitcoin block header is 32 bits wide, providing a search space of approximately 4.29 billion values. Modern miners exhaust this space in a fraction of a second, so additional variation is introduced through:

  • Version rolling — varying bits in the block version field (BIP 320)
  • Merkle root variation — the pool can provide multiple Merkle roots with different transaction orderings

The control board firmware manages this division, ensuring no two chips waste time searching the same nonce space.

Hardware Errors

A hardware error (HW error) occurs when a chip reports a nonce that does not actually meet the difficulty target. This can happen due to:

  • Electrical noise causing bit flips in the computation
  • Marginal core voltage causing logic errors
  • Clock instability from a poorly locked PLL
  • Overheating causing the chip to malfunction

A small number of HW errors is normal (less than 0.1% of total shares). A high HW error rate on specific chips indicates a problem that needs attention — either the chip itself is failing, or its power or clock supply is marginal.

To check HW errors on a running Antminer, SSH into the control board and examine the kernel log. The bitmain-soc process reports per-chip HW error counts. A chip with a significantly higher error rate than its neighbors is a candidate for replacement.

Thermal Management

Heat Generation

ASIC chips convert nearly 100% of their input electrical power into heat. A single voltage domain on an S21 board consuming 25 amps at 0.30V dissipates approximately 7.5 watts across its 13 chips — about 0.6W per chip for core power alone. Across 156 chips and all voltage rails, total board power dissipation can exceed 1,100W.

Cooling Architecture

Hash boards use a layered approach to thermal management:

LayerComponentFunction
1Thermal interface material (TIM)Transfers heat from chip die to heatsink
2Aluminum heatsinksSpreads and absorbs heat from chips
3Forced airflowCarries heat away from heatsinks
4Miner enclosureChannels airflow across all boards

Heatsinks are bonded to both sides of the hash board PCB using thermal paste or thermal pads. The top-side heatsink contacts the chip packages directly, while the bottom-side heatsink contacts the exposed thermal pad on the chip's BGA substrate (which conducts heat through the PCB via thermal vias).

Temperature Monitoring

Modern hash boards include one or more temperature sensors positioned along the board. These sensors report to the control board, which uses the readings for:

  • Fan speed control — adjusting fan RPM to maintain target temperatures
  • Thermal throttling — reducing chip frequency if temperatures exceed safe limits
  • Emergency shutdown — powering off the board if a critical temperature is reached (typically 90-95 degrees C)
Sensor TypeInterfaceResolutionTypical Placement
NTC ThermistorAnalog (ADC)~1 degree CLegacy boards (S9, S17)
LM75AI2C0.5 degree CS19 series boards
TMP451I2C0.0625 degree CS19 XP, S21 boards
NCT218I2C0.125 degree CSome S21 variants

When reassembling hash boards after repair, thermal paste application is critical. Too little paste creates air gaps that cause hotspots. Too much paste can overflow onto signal traces. Apply a thin, even layer that covers the entire chip surface without excess. See Cooling & Thermal Management for application techniques.

Common Failure Modes and What Causes Them

Understanding the most frequent failure modes helps you diagnose problems faster and more accurately. Here are the failure patterns you will encounter most often, organized from most to least common.

1. Missing Chips (Partial or Complete Chain Break)

Symptom: Miner reports fewer chips than expected, or "0 ASIC" for the entire board.

Causes:

  • Dead ASIC chip with open CI/CO or RI/RO — breaks the signal chain at that point
  • Cracked signal trace between chips — thermal cycling causes PCB flex and trace fractures
  • Cold solder joint on a chip's communication pins — intermittent or complete signal loss
  • Failed VDDIO (1.8V) rail — no chip can drive or receive communication signals

Diagnosis approach: Check chip count to identify where the break occurs. If 0 chips are found, check VDDIO first. If some chips are found, the break is near the last functional chip.

2. Voltage Domain Failure

Symptom: A group of consecutive chips are missing or report errors. Other domains function normally.

Causes:

  • Failed buck converter IC
  • Shorted ASIC chip pulling the domain voltage to ground
  • Failed output capacitor (shorted or open)
  • Open inductor in the buck converter circuit
  • Burnt PCB trace in the power path

Diagnosis approach: Measure the voltage at each domain's output. A dead domain will read 0V or a voltage far outside specification. A shorted domain may read near 0V and the regulator IC may be hot. See Voltage Domains & Regulators for measurement procedures.

3. High Hardware Error Rate

Symptom: Board is detected with correct chip count, but hashrate is below expected and HW error rate is elevated.

Causes:

  • Marginal core voltage (VDD drifting out of spec on one or more domains)
  • PLL instability causing incorrect hashing frequency
  • Overheating chips (thermal paste dried out or heatsink poorly mounted)
  • Degraded chip with partial core failures

Diagnosis approach: Use SSH to identify which chips have high HW error rates. Check voltage on those chips' domain. Check thermal interface. Reflow or replace chips with persistently high errors.

4. Thermal Shutdown

Symptom: Board operates normally for a period then shuts down. May restart and repeat the cycle.

Causes:

  • Dried or missing thermal paste
  • Damaged or improperly seated heatsink
  • Blocked airflow (dust accumulation)
  • Failed temperature sensor reporting incorrect values
  • Ambient temperature too high for the cooling capacity

Diagnosis approach: Check miner logs for temperature readings at shutdown. Clean dust from heatsinks and fans. Reapply thermal paste if needed. Verify fan operation.

5. Board Not Detected

Symptom: Control board does not recognize the hash board at all — no chips counted, no voltage readings.

Causes:

  • Damaged signal connector or ribbon cable
  • Failed level shifter or buffer IC at the board's input
  • 3.3V rail failure (control logic unpowered)
  • Corroded or bent connector pins
  • Incompatible firmware (board type mismatch)

Diagnosis approach: Inspect the connector visually. Check 3.3V rail. Try a known-good cable. Verify firmware matches the board type.

6. Power Connector Burn

Symptom: Visible damage or discoloration at the power input connector. Board may work intermittently or not at all.

Causes:

  • Loose connector creating high-resistance contact
  • Corrosion from humidity
  • Overloaded connector (running board above rated power)
  • Poor connector quality (aftermarket PSU cables)

Diagnosis approach: Visual inspection is usually sufficient. Burnt connectors must be replaced — cleaning alone will not restore reliable contact.

Never operate a miner with a visibly burnt power connector. The high-resistance connection generates localized heat that can ignite PCB material. Replace the connector on both the hash board and the PSU cable before returning the unit to service.

Failure Mode Summary Table

Failure ModeSeverityFrequencyTypical RepairDifficulty
Missing chips (chain break)HighVery commonChip replacement or reflowModerate
Voltage domain failureHighCommonRegulator or capacitor replacementModerate
High HW errorsMediumCommonChip replacement, thermal workModerate
Thermal shutdownMediumCommonThermal paste, heatsink serviceEasy
Board not detectedHighOccasionalConnector or buffer IC repairEasy-Moderate
Power connector burnCriticalOccasionalConnector replacementEasy

Key Takeaways

After reading this guide, you should understand these fundamental concepts:

  1. Hash boards are organized into voltage domains — groups of chips with independent power regulators. Most repairs involve identifying which domain has failed and replacing the faulty component within it.

  2. Chips are connected in a daisy chain — a single failed chip can break communication to all downstream chips. The chip count reported by the miner tells you where the break is.

  3. Three voltage rails must all be healthy — VDD (core, ~0.3V), VDDIO (I/O, 1.8V), and VDD33 (logic, 3.3V). A failure on any rail can take down the entire board or a section of it.

  4. Clock distribution through PLL — each chip generates its operating frequency from a reference clock using an internal PLL. Clock problems cause HW errors and performance degradation rather than complete failures.

  5. Data flows in a pipeline — pool sends work to controller, controller sends jobs to chips, chips search for nonces, and valid results flow back. Understanding this pipeline helps you interpret miner logs and diagnostic output.

  6. Thermal management is ongoing maintenance — thermal paste degrades over time, dust accumulates, and fans wear out. Many "hardware failures" are actually thermal problems in disguise.

  7. Newer generations are more complex — more chips, more domains, tighter voltage tolerances. The diagnostic principles remain the same, but the precision required increases with each generation.

Apply This Knowledge

Ready to put this understanding into practice? Here are the recommended next steps:

Start With Diagnostics Fundamentals

Deepen Your Component Knowledge

Try Model-Specific Repair Guides

Reference Specific Chips

On this page

IntroductionWhat Is a Hash Board and Its Role in a MinerThe Miner as a SystemWhy Hash Boards Matter MostHash Board Generations at a GlancePhysical Anatomy: PCB Layers, Component Placement, and Signal FlowPCB ConstructionComponent LayoutBoard ConnectorsThe Signal Path at a High LevelVoltage Domains: How Power Is Distributed Across Chip GroupsThe Problem of Low Voltage at High CurrentThe Domain SolutionVoltage Domain Comparison by GenerationWhat Happens When a Domain FailsVDDIO and VDD33 RailsHash Chain: How Chips Are Connected in SeriesThe Daisy Chain ArchitectureChip Addressing and EnumerationThe "Broken Chain" ProblemFinding the Break PointClock Distribution: PLL and Crystal OscillatorsWhy Clock MattersClock SourcePLL (Phase-Locked Loop)PLL Register ConfigurationClock Propagation Through the ChainDiagnosing Clock ProblemsData Flow: Job Distribution, Nonce Finding, and Result ReportingThe Mining Process on a Hash BoardPool Sends Work to ControllerController Distributes Jobs to ChipsChips Search for Valid NoncesResults Flow Back to ControllerMidstate OptimizationNonce Space DivisionHardware ErrorsThermal ManagementHeat GenerationCooling ArchitectureTemperature MonitoringCommon Failure Modes and What Causes Them1. Missing Chips (Partial or Complete Chain Break)2. Voltage Domain Failure3. High Hardware Error Rate4. Thermal Shutdown5. Board Not Detected6. Power Connector BurnFailure Mode Summary TableKey TakeawaysApply This KnowledgeStart With Diagnostics FundamentalsDeepen Your Component KnowledgeTry Model-Specific Repair GuidesReference Specific Chips