Formula Used
Total submitted work = accepted + rejected + stale + invalid + hardware errors.
Hardware error rate = hardware errors / total submitted work × 100.
Accepted-base hardware rate = hardware errors / (accepted shares + hardware errors) × 100.
Reject impact rate = (rejected + stale + invalid) / pool share traffic × 100.
Expected errors = accepted shares × target decimal / (1 − target decimal).
Z score = (actual hardware errors − expected errors) / square root of expected errors.
Energy used = power watts × miner count × uptime hours / 1000.
Hashrate efficiency = average hashrate / rated hashrate × 100.
How to Use This Calculator
Enter the miner model, location, uptime, accepted shares, rejected shares, stale shares, invalid shares, and hardware errors.
Add average hashrate, rated hashrate, power draw, electricity rate, and target hardware error rate.
Press Calculate to show the result above the form. Use CSV for spreadsheet work. Use PDF for maintenance records.
Compare the z score, excess errors, reject impact, and quality score. Review miners with high rates first.
Antminer Hardware Error Analysis Guide
Why Hardware Error Tracking Matters
Antminer devices work by testing many hash attempts. Some attempts are accepted by the pool. Some are rejected. Hardware errors are different. They show failed work inside the machine. A small number can be normal. A rising number needs attention. It may point to heat, weak power, dust, bad chips, or aggressive tuning.
Reading the Main Rates
The hardware error rate compares failed hardware work with submitted work. The reject rate compares pool-side lost shares with valid share traffic. Both values should be reviewed together. A miner can show a low reject rate while hardware errors still climb. That means the pool may look fine, but the device is wasting internal effort.
Using Thresholds
This calculator lets you enter a target hardware error rate. It then estimates expected errors for your accepted shares. The excess error count shows the gap above that target. The z score gives a simple statistical warning. A high positive z score means the error count is far above the expected level. Treat it as a prompt for inspection, not as a final diagnosis.
Practical Mining Checks
Always compare several time windows. Ten minutes can be noisy. Twenty four hours is more useful. Check ambient temperature, fan speed, firmware settings, and power draw. Clean the miner and inspect cables. Review each hashboard when your firmware provides board-level details. If errors increase after overclocking, reduce frequency or voltage step by step.
Result Interpretation
The score in this tool is a quick diagnostic index. It combines hardware errors, rejected shares, and hashrate efficiency. It does not replace pool reports or repair logs. Use it to rank machines, spot weak units, and document changes after tuning. Export the CSV for spreadsheets. Export the PDF for service notes. Keep results with dates and miner names for clearer trend tracking.
Maintenance Workflow
Start with the miner that has the worst excess error count. Record room temperature and outlet voltage. Reboot once, then watch a fresh sample. Change one setting at a time. Keep the same pool during testing. This avoids mixed data. When a repair lowers the rate, save the result. It proves the change helped and supports future maintenance planning. This supports every mining site.
FAQs
What is an Antminer hardware error?
It is failed work produced inside the miner. It usually means the hashboard attempted work that could not become a valid share. Small counts may be normal, but rising counts need review.
What is a good hardware error rate?
There is no single value for every model. Many operators track their own target. Use this calculator to compare your actual rate with a chosen operating threshold.
Why do hardware errors increase?
Common causes include heat, dust, unstable power, loose cables, aging chips, firmware changes, or overclock settings. Compare results before and after each change.
Are rejected shares the same as hardware errors?
No. Rejected shares are pool-side share problems. Hardware errors are miner-side failed work. Both can reduce useful output, but they point to different issues.
Why does uptime matter?
Uptime turns raw errors into an hourly rate. This makes short tests and long tests easier to compare. Longer stable samples usually give better insight.
What does the z score show?
It compares actual hardware errors against expected errors from your target rate. A high positive value suggests the miner is performing worse than the chosen target.
Can this tool diagnose a bad hashboard?
It can highlight unusual error behavior. It does not identify the exact failed component. Use firmware logs, board-level data, temperature readings, and repair tests.
Why export CSV and PDF files?
CSV is useful for spreadsheets and trend dashboards. PDF is useful for service notes, audit records, and sharing a fixed summary with technicians.