Whatsminer Error 200 – Power Probing Error No Power Found

Hard power-cycle at the wall, not the UI. Unplug the AC cord for 60 full seconds to drain PSU hold-up capacitors, reconnect, and boot. Roughly 15% of Error 200 cases resolve here because the PSU had latched an internal fault state that clears only with full mains removal. If 200 clears, note the event and watch for recurrence.

Listen to the PSU fan on boot. A healthy Whatsminer PSU spins the fan for at least 2 seconds immediately on AC apply. If the fan hesitates, stutters, or doesn't spin, the standby converter inside the PSU is suspect — this is the earliest warning sign of PSU decline and often precedes recurring Error 200 by weeks.

Inspect every AC connection. Outlet face plate, C19 cable seating at both ends, AC plug prongs for discolouration or heat marks, breaker for warmth after failed boot. A loose or oxidised neutral is a classic cause of intermittent Error 200 that appears random but tracks with wall vibration or temperature cycling.

Verify wall voltage with a plug-in voltage meter or a multimeter at the outlet. Whatsminers require 200-240 VAC stable. If you're on 208 V commercial at the low end, or on 240 V residential where another heavy load shares the same leg, voltage sag under PSU inrush can throw Error 200 at boot and nothing else.

Leave the miner fully powered off for 30 minutes, then retry. A small percentage of Error 200 cases are thermal-latched fault flags inside the PSU. Fully cooling the PSU occasionally clears a false positive from a marginal internal temperature sensor. This is a free diagnostic data point before you escalate to tools.

Power off at the breaker. Pull the chassis cover and locate the 10-pin signal harness between the PSU and the control board. Unplug both ends, inspect all pins under good light for bent, discoloured, or corroded contacts, and re-seat firmly until the connector latches. This single step clears 30-40% of Error 200 in D-Central's repair queue — do it before buying anything.

Re-seat the PSU DC output connectors (large threaded studs on M30 family, blade connectors on some M50/M60 models). Torque to manufacturer spec if marked; otherwise firm hand-tight. Loose output hardware creates high contact resistance, which drops rail voltage at the hashboard end below the probe threshold and throws Error 200 even though the PSU is healthy.

Multimeter in DC mode, probes on the PSU output terminals or hashboard-side connector with leads clear of the fan. Power the miner on. Expected behaviour: rails climb from 0 V to 14-15 V (M30 family) or 15-16 V (M50/M60 family) within 2-3 seconds. No rise at all = PSU not responding to enable. Rise-then-collapse = load-side short.

Swap the PSU with a known-good unit of the same model family. Do not cross-mix between generations (P221 vs P12 vs P13) — enable signalling and aux rails differ and you will chase ghost symptoms. If Error 200 clears with the substitute PSU, the original is the fault. If 200 persists, the root cause is downstream of the PSU.

Measure AC input under boot load. Multimeter in AC mode, probes across the PSU input terminals. Press reboot. Voltage should stay above 200 V with less than 3 V of sag during the boot inrush transient. If it collapses to 180 V or below, the circuit is undersized, the wiring is aged, or the breaker is on its way out — electrician territory before another Whatsminer.

After a failed boot, check the breaker and outlet case temperature. A warm breaker or hot outlet means resistance is building in the electrical path — often from an aging breaker mechanism or a corroded outlet contact. Left unaddressed this eventually causes a real fire; address before you keep cycling the miner trying to clear the error.

Force a firmware recovery via microSD card. Burn the latest stable BTMiner image for your exact model variant using Raspberry Pi Imager or Etcher, insert the SD card into the control-board slot, hold the reset button through the recovery sequence per your model's pattern (M30S family: 10 seconds through boot; M50/M60 differs — check the firmware changelog). Factory firmware isolates config corruption from hardware fault.

Open the PSU with the unit out of circuit and fully discharged (10-minute minimum after unplug). Inspect primary-side electrolytics for bulged tops, crusty residue, cracked cases, or electrical smell. Replacement 400 V 220-470 uF caps are $5 each; installation is through-hole but demands good soldering technique. If not comfortable with primary-side AC work, ship to D-Central — this is not beginner territory.

Audit the PSU auxiliary / standby rail. On the output side there's a small converter that powers the control board's early boot. If the standby rail is dead, the control board may still limp on 12 V aux but BTMiner's power-sequencing logic never gets the all-clear from the PSU, producing Error 200. Measure standby pins per your model's pinout (forums document these better than MicroBT).

Disable hashboards one at a time via the BTMiner API (if the control board reaches network). Craft API requests on TCP port 4028 to enable subsets of boards. If the miner boots with two hashboards but Error 200 returns with the third connected, that third board is shorted or drawing initial current outside PSU tolerance — isolated to a specific board.

Reflow or replace the PSU main PWM controller if Error 200 persists with a known-good load and you've confirmed PSU output fails to come up. Controller is typically a SOIC-16 or QFN package with unforgiving pad geometry. Good practice job on an out-of-warranty PSU before you commit to chip-level work on a more expensive hashboard. Not a beginner task.

Stop DIY and book a D-Central Whatsminer repair slot when any of the following is true: PSU primary-side damage (bulged caps, burnt components, smell), hashboard-side short isolates to a specific board, control board unresponsive to SD-card recovery, or the miner trips a breaker on boot. These require a repair bench with a variable-load PSU tester and chip-level rework capability.

Ship safely. Remove all hashboards and bag each individually in ESD-safe anti-static. Box the PSU in its own padded container separate from the chassis — a dropped PSU is often how Error 200 gets born in the first place. Include a written note with firmware version, 200 timestamp, and every diagnostic step you've already tried. Saves bench hours and repair dollars.