Purpose: this is symptom-led triage, not a live repair guide. Preserve evidence before changing hardware, firmware, or settings. The exact model manual and warranty process control every operator action.
Capture Evidence Before Changing Anything
Collect the model, revision, serial, timestamp, firmware version and source, exact alarms/log text, permitted UI readings, pool connection status, ambient observations, recent changes, and safe external photographs after shutdown. A symptom is not a component-level diagnosis.
The Safe Triage Decision Tree
No Power, Shutdowns, or Breaker Events
Do not infer a power-supply fault from a symptom alone. Check only the externally visible, model-authorized items after safe shutdown. A breaker event, damaged insulation, heat damage, or repeated shutdown is an escalation condition; do not open a PSU, probe live equipment, or repair mains wiring.
Fan, Airflow, Temperature, and Environmental Alerts
Preserve the exact alert and compare permitted readings with the model-specific baseline. Check the documented external airflow path and environment only as authorized. Do not substitute generic temperature/humidity thresholds, bypass a thermal protection, or restart equipment with liquid, condensation, corrosion, smoke, or heat damage.
Reduced Hashrate, Board Detection, and Error Logs
A reduced rate, missing board indication, or error message can have multiple causes. Export or record the exact evidence and follow the model’s approved operator procedure. Do not use a generic board swap, connector reseat, or component test to decide that a board has failed.
Network, Control-board, and Firmware Symptoms
Preserve configuration and the complete error text. Confirm the model/controller revision before taking any documented recovery action. Firmware recovery is not a generic cure: use only the authorized source and the exact documented method, with warranty implications understood.
Moisture, Corrosion, and Contamination
Liquid, condensation, corrosion, chemical exposure, or conductive contamination can create electrical and reliability risk. Stop use, document safely, and escalate. Do not dry, wash, heat, or power-cycle the unit as a substitute for the manufacturer or qualified-service process.
Operator Checks Versus Qualified Service
| Operator evidence capture | Qualified or authorized service |
|---|---|
| Logs, permitted UI values, external observations, documented configuration backup. | PSU work, mains wiring, energized testing, exposed boards, component diagnosis, damaged conductors, and warranty-restricted work. |
Warranty, Firmware Provenance, and Repair Authorization
Verify warranty/RMA status before opening enclosures, removing labels, changing firmware, or sending components away. Use only the exact model’s authorized image and process. Document the model/revision, symptom, evidence, and authorization scope so a later assessment can distinguish an observed fault from a change made during triage.
Deciding on Diagnosis, Repair, or Retirement
Make a documented decision from a verified diagnosis, warranty/RMA status, authorized repair scope, shipping and downtime, approved-parts availability, observed condition, environmental or electrical root cause, and local reuse/disposal requirements. Do not rely on a universal age, percentage, efficiency, or price rule.
Return to Preventive Maintenance
After a verified repair or resolved condition, rebuild a baseline and use the model-specific preventive maintenance checklist.
Sources
Use the exact manufacturer manual and warranty process for the unit. Safety references: CCOHS lockout/tagout, hazardous-energy control, and ESD control fundamentals.
Frequently Asked Questions
Answers for safe triage
Which ASIC miner symptoms mean I should stop using it immediately?
Stop use and follow the applicable isolation procedure for smoke, burning or ozone smell, melting or discoloration, a breaker event, liquid or condensation, damaged insulation, or repeated protective shutdown. Do not restart pending qualified or authorized assessment.
What information should I collect before troubleshooting?
Record the exact model, revision and serial; timestamp; firmware version and source; exact alarm or log text; permitted UI readings; pool status; ambient observations; recent changes; and safe external photographs after shutdown.
Can I test or open an ASIC power supply myself?
Not as ordinary operator triage. Do not open a PSU, probe energized equipment, repair mains wiring, or attempt live voltage tests. Use the exact manufacturer procedure and qualified or authorized service.
Can a log message prove that a hashboard has failed?
No. A log message is evidence to preserve, not a component-level diagnosis. Several causes can produce similar symptoms, and the exact model manual or qualified diagnostic process determines the next step.
When is a firmware recovery safe to attempt?
Only when the exact model documentation authorizes an operator recovery path, the correct image and controller revision are confirmed, and warranty implications are understood. Do not use unverified images or interrupt a documented recovery process.
When should I use authorized or qualified service?
Use it for power supplies, mains wiring, energized tests, exposed electronics, board-level diagnosis or repair, damaged conductors, liquid/corrosion damage, warranty-restricted work, and any step outside the exact model manual.
