The Troubleshooting and FAQ section provides miners with quick solutions to common technical issues encountered during setup or operation of the HashCloud system.
By addressing driver conflicts, verification errors, and performance issues, this section helps maintain consistent uptime and optimal compute performance across all hardware tiers.
❓ GPU Not Detected
Symptoms:
The HashCloud client (HCLD-cli) does not recognize any available GPUs.
Possible Causes:
Outdated or missing GPU drivers
Incorrect CUDA / ROCm installation
Hardware detection issues after system updates
Solution:
Update to the latest GPU drivers.
Reboot your system.
Verify that CUDA (NVIDIA) or ROCm (AMD) is correctly installed.
Confirm that your OS has proper GPU permissions for the mining process.
❓ “VRAM Exceeds VIP Tier”
Symptoms:
The backend rejects mining authorization with a VRAM mismatch warning.
Possible Causes:
The GPU has more VRAM than allowed by the current VIP level.
Configuration file references more GPUs than permitted under your tier.
Solution:
Upgrade your VIP tier to unlock additional GPU or VRAM capacity.
Alternatively, reduce the GPU count or select compliant hardware per tier (see Section 9: Hardware Tiering).
❓ Backend Rejecting Proofs
Symptoms:
The backend server consistently rejects proof submissions.
Possible Causes:
Local clock desynchronization
Network latency or expired challenge windows
Invalid computation or altered proof packets
Solution:
Sync your system clock with a reliable NTP server.
Ensure your internet connection is stable.
Confirm that challenges are executed and submitted before expiration.
Restart the miner if the issue persists, as it may refresh expired sessions.
❓ Performance is Low
Symptoms:
Mining output or performance scores appear below expected levels.
Possible Causes:
GPU underclocking or thermal throttling
Oversized matrix computation relative to GPU capability
Background applications consuming GPU resources
Solution:
Lower matrix size manually using local configuration mode.
Monitor GPU temperatures and fan speed to avoid thermal throttling.
Close unnecessary background applications.
Run a benchmark test (HCLD-cli benchmark) to recalibrate difficulty.
❓ Miner Crashes
Symptoms:
The mining client stops responding or closes unexpectedly.
Possible Causes:
Memory leaks or unstable GPU overclocks
Driver conflicts or failed updates
Incomplete installation of required dependencies
Solution:
Run the built-in diagnostic mode:
HCLD-cli diagnose
Review the generated report for driver or dependency errors.
Reinstall the HashCloud CLI or update GPU drivers.
Use default GPU clock settings for stable operation.
Additional Support Resources
If issues persist, miners can access official support channels:
Community Discord: Real-time help and configuration advice from moderators and veteran miners.