How to Troubleshoot Common Mining Rig Problems?

Power Supply Instability

1. Check all PCIe power connectors for secure insertion into both the GPU and PSU; loose connections cause random shutdowns.

2. Verify PSU wattage meets or exceeds total system draw—underpowered units trigger brownouts during hash bursts.

3. Test with a multimeter on the 12V rail; voltage below 11.4V indicates failing capacitors or overload.

4. Swap in a known-working PSU to isolate whether instability originates from power delivery or elsewhere.

5. Monitor PSU fan behavior—if silent under load, thermal throttling may be occurring inside the unit.

GPU Detection Failures

1. Re-seat each GPU individually while powering off the rig completely—residual charge can lock PCIe enumeration.

2. Confirm BIOS settings: disable Fast Boot, enable Above 4G Decoding, and set PCIe Speed to Gen3 if supported.

3. Use lspci -v on Linux or GPU-Z on Windows to verify device ID recognition—not just presence.

4. Replace riser cables one at a time; damaged USB 3.0 or PCIe extension wires commonly break GPU enumeration chains.

5. Flash GPU BIOS to mining-optimized versions where vendor support exists—stock gaming BIOS often blocks multi-GPU detection.

Hash Rate Fluctuations

1. Inspect ambient temperature—rigs operating above 35°C ambient show measurable hash variance even with stable VRM cooling.

2. Cross-check memory clock offsets across all GPUs using MSI Afterburner; inconsistent tuning causes pool-side rejection spikes.

3. Review pool difficulty adjustment logs—sudden jumps in network difficulty mimic local hash instability.

4. Disable GPU power limiting temporarily; undervolting too aggressively introduces core timing errors under sustained load.

5. Capture kernel messages via dmesg | grep -i 'nv' or dmesg | grep -i 'amdgpu' to detect driver-level compute faults.

Cooling System Breakdowns

1. Clean dust filters weekly—accumulated debris reduces airflow by up to 60% without triggering thermal alerts.

2. Validate fan PWM curves in BIOS or software; some motherboards default to static low-RPM profiles incompatible with mining loads.

3. Measure GPU hotspot temperature separately from junction temp—hotspots exceeding 105°C indicate localized thermal paste failure.

4. Audit case fan orientation: intake must exceed exhaust volume by at least 20% to prevent internal recirculation of heated air.

5. Replace thermal pads on VRAM and VRMs after 18 months—even without visible cracking, dielectric breakdown degrades conductivity.

Network and Pool Connectivity Drops

1. Bypass router QoS settings—many consumer firmware versions throttle sustained UDP traffic resembling mining stratum packets.

2. Assign static IP and disable DHCP lease renewal during active mining sessions to avoid mid-hash IP reassignment.

3. Ping stratum endpoint continuously with timestamped logging—intermittent 100ms+ latency spikes correlate strongly with rejected shares.

4. Replace CAT6 cable with shielded CAT6a if running near high-voltage AC lines—EMI induces packet corruption undetected by TCP checksums.

5. Run tcpdump -i eth0 port 3333 to capture raw stratum handshake failures; malformed JSON responses point to pool-side misconfiguration.

Frequently Asked Questions

Q: Why does my rig crash only when mining Ethereum Classic but not Ergo?A: ETC uses Keccak-256 with heavier memory bandwidth demands—older GPUs with degraded GDDR5X modules fail silently under that specific workload.

Q: Can BIOS updates permanently damage mining hardware?A: Yes—flashing non-mining BIOS versions onto LHR-enabled cards may hard-brick the vBIOS region, requiring external programmer recovery.

Q: Is it safe to run GPUs at 95°C junction temperature during mining?A: Not long-term—silicon degradation accelerates exponentially beyond 85°C; sustained operation above that threshold cuts expected lifespan by 70% or more.

Q: Why do rejected shares increase after switching from Claymore to T-Rex miner?A: T-Rex enforces stricter stratum protocol compliance—older pool servers with malformed job IDs or incorrect nonce encoding generate higher rejection rates under strict clients.