Whatsminer Error 205 – PSU Output Current Error
Warning — Should be addressed soon
Symptoms
- BTMiner dashboard / WhatsMinerTool shows Error Code: 205 with message like 'power current error', 'current anomaly', or 'current out of range'
- Kernel log near the failure event contains 'current err', 'psu current out of range', or 'current sense fail' lines
- BTMiner API on TCP 4028 returns one or more current_X values that are 15-30% off the others on the same load profile
- One hashboard's per-chain current reads visibly different from the other two (visible in stock BTMiner status page if you scroll past the rollup)
- Miner may still be hashing — 205 is often raised as a warning while the rig keeps running degraded, unlike 200 or 233 which halt the miner
- Realised hashrate is 5-20% below nameplate with no obvious thermal or fan complaint
- PSU case feels noticeably warmer than baseline at the bus-bar end during steady-state operation
- Visible discoloration, oxidation, or heat-darkening on or around the PSU output copper bars / bolts
- Audible buzzing or high-pitched ticking from the PSU when the rig is hashing at full load
- Thermal scan shows one or more chips on a hashboard running 10-25 °C above peers
- Outlet runs warmer than usual after sustained operation, even though breaker doesn't trip
- Pattern: 205 appears intermittently after the rig has been running 10-30 minutes (thermal expansion opens the loose-bolt gap)
Step-by-Step Fix
Hard power-cycle the rig at the wall. Unplug the AC cord for 60 seconds, reconnect, and boot. Some 205 events are transient sensor faults that the BTMiner state machine latches; full mains removal lets the PSU clear its internal flags. About 10% of cases self-clear here. Monitor for 24 hours after; if 205 returns, escalate to Tier 2.
Visually inspect the PSU end of the chassis with the miner running. Look and listen for audible buzzing or visible heat shimmer near the PSU output bus-bars. Any darkening or discolouration on the bolts or copper bars is a direct hint that you've found the high-resistance contact causing the 205. No tools required, just your eyes and 60 seconds of attention.
Check intake air temperature with a plug-in or IR thermometer at the front grille. A 205 paired with elevated intake (>32 °C) is often a thermal-stress signal on a PSU on the edge — heat expands the loose-bolt gap and tips the current sensor out of envelope. Move the rig to better airflow before escalating.
Verify wall voltage with a plug-in voltage meter or multimeter at the outlet. Whatsminer PSUs want 220-240 V stable. If you see 215 V or below at the outlet during operation, sag from a shared circuit or marginal panel is part of the cause. Shared kitchen breaker with a fridge that cycles is the classic 'intermittent 205' residential pattern.
Restart the miner via WhatsMinerTool, not the chassis power button. Soft restart preserves PSU power but cycles BTMiner. If 205 clears on a soft restart and the rig runs a few hours then re-throws, BTMiner config or current-envelope state is part of the fault — note for the Tier 3 SD-card recovery step.
Power off at the breaker, wait 2 minutes for capacitor discharge, pull the chassis cover. Locate every PSU output bus-bar bolt (typically 4-8 depending on model — 2 per phase per output). Note the size — usually 6 mm hex on M30 family, 8 mm on M50/M60. Inspect each bolt for looseness, darkening, or oxidation around the head and washer.
Torque every PSU output bus-bar bolt to spec. Apply 2.5-3.5 N·m of firm even torque using a calibrated torque wrench, or a hex socket on a short driver with firm hand pressure (no impact tools). Over-torquing shears the bolt or deforms the copper; under-torquing leaves the high-resistance gap. Re-torque every 6 months as preventive maintenance — bolts walk loose under thermal cycling.
Clean the bus-bar surface if you see oxidation. Use a fibreglass pen, fine grey ScotchBrite, or 2000-grit wet sandpaper on the contact face. Wipe with isopropyl alcohol 99%, blow dry, retighten the bolt onto the freshly cleaned surface. This restores contact conductivity and removes the high-impedance oxide layer that distorts the current waveform BTMiner is sensing.
Measure per-board DC current under load with a clamp DC ammeter (Fluke 376 FC or similar) around each board's positive supply lead while the rig is hashing at full load. Expected M30S: 75-85 A per board; M50S: 85-95 A; M60S: 95-110 A. One board ±15-30% off peers = that board is the load-side problem. All boards similar but absolute wrong = PSU or sensor drift.
Re-seat the 10-pin PSU-to-control-board signal harness. This carries the current-sense telemetry BTMiner reads. Loose pins or oxidised contacts produce noise on the telemetry line that BTMiner interprets as out-of-envelope readings. Unplug, inspect both ends for bent or corroded contacts, re-seat firmly, listen for the click. Free fix; clears a small but real percentage of 205 cases.
Audit the AC circuit with a plug-in voltage logger or scope on the outlet for 6 hours during normal operation. Voltage drift more than ±5 V from 240 V nominal, or visible spikes / brownouts during HVAC cycling, points at the panel as a contributor. Address before continuing — feeding a sensitive miner from a marginal circuit is whack-a-mole on multiple error codes including 205.
Force a BTMiner firmware recovery via microSD card. Burn the latest stable BTMiner image for your exact model variant (M30S vs M50S vs M60S — images are not interchangeable) using Raspberry Pi Imager or Etcher. Insert the SD card, hold the reset button per your model's recovery pattern (M30S: 10 seconds through boot; M50/M60 vary by hardware revision), let recovery complete, pull SD, reboot. Factory image is the baseline for distinguishing config corruption from hardware fault on 205.
Pull per-chain current via the BTMiner API. With the suspect board reconnected and the rig hashing, query get_miner_status on TCP 4028 and look at the per-chain current values. Healthy chains report current within ~5% of each other on the same workload. A chain pulling 8-15% above peers contains a partially shorted MOSFET, a leaking decoupling cap, or a failing chip. Note the exact chain index — that's where Tier 3 chip-level work begins.
Thermal-scan the suspect chain under load with a FLIR ONE Pro or equivalent thermal camera. Run the rig for 5 minutes at full load, scan the suspect chain. The hot chip is the failing chip — expect 10-25 °C above peer chips on the same chain. Mark the chip position. Reflow if the hot-spot is on the BGA package (preheat 150 °C, top-side hot air 310-330 °C for 30 s, cool naturally). Replace the chip if reflow doesn't clear it within 30 days.
Inspect capacitors and MOSFETs on the suspect board. Look for bulging electrolytics, cracked MLCCs near the voltage-domain MOSFETs, or burn marks. Bulged caps on a power-domain rail directly cause the irregular current that produces 205. Replacement MLCCs are pennies, electrolytics $1-3 each. Soldering-iron + hot-air rework job — out of scope for a beginner; well within reach for a bench-capable home miner.
Audit PSU current-sensor calibration as the last DIY step before declaring the PSU faulty. With a clamp DC ammeter on each PSU output rail, compare measured current against the value BTMiner reports via API. Drift greater than 10% between actual and reported = sensor has drifted, PSU is on the hospice list. There's no in-situ recalibration on Whatsminer PSUs — drift is a one-way trip to bench-level repair or replacement.
Stop DIY and ship to D-Central when any of the following is true: PSU sensor drift confirmed via clamp ammeter audit, primary-side cap bulging or burn marks visible on PSU teardown, single chip identified and reflow doesn't hold, or bus-bar bolts have been re-torqued twice in 60 days and 205 keeps returning. These need a bench with a programmable load PSU tester, a calibrated current-sense reference, and ESD-safe chip rework capability.
Ship safely. Remove all hashboards and bag each individually in ESD-safe anti-static. Box the PSU separately with at least 5 cm of foam on every side. Include a written note with: BTMiner firmware version, observed 205 pattern (constant vs intermittent vs thermal), every diagnostic step you've already tried, and your recorded per-board current values. Pre-diagnosed miners save bench time and repair dollars — quotes are materially lower when we don't redo the work you've already done.
When to Seek Professional Repair
If the steps above do not resolve the issue, or if you are not comfortable performing these repairs yourself, professional service is recommended. Attempting advanced repairs without proper equipment can cause further damage.
Related Error Codes
Still Having Issues?
Our team of Bitcoin Mining Hackers has been repairing ASIC miners since 2016. We have seen it all and fixed it all. Get a professional diagnosis.
