SRBMiner-MULTI AMD & NVIDIA & INTEL & CPU miner

[Phil1234]

Network hash is about 15 GH today and always miners on https://noj.viporlab.net - others maybe running their own nodes - I don't think its dead.

[doktor83]

V3.2.7
+ Added algorithm 'sha256mem' (Fairchain coin) for CPU and NVIDIA GPU mining, fee 2.50%*
+ Removed algorithm 'dutahashv4'


V3.2.6
+ Fixed a critical bug that affected maximum number of useable threads on GPU Yescrypts - delete your Autotune folder and re-run miner
+ New feature : when defining pool/s (with parameter --pool) it now accepts 'ssl://' or 'tls://' to enable encryption
+ Removed algorithm 'sha3x' and duals 'fishash+sha3x', 'autolykos2+sha3x'
+ Removed algorithms 'xelishashv2_pepew', 'randomhscx', 'randomxeq'

[energy_xxx]

Will GPU support be added to other versions of the yespower algorithm, . eqpay, sugar, r16.....?

[doktor83]

Will GPU support be added to other versions of the yespower algorithm, . eqpay, sugar, r16.....?

oh no, that makes no sense. even the currently added 2 yespower variants for gpu make no sense, but it was just a test.

[doktor83]

V3.3.0
+ Minor hashrate improvement on algorithm 'argon2id_exfer' on NVIDIA GPUs (delete your Autotune folder and re-run miner)
+ Nvidia P100 (SM_60) should now work on algorithm 'argon2id_exfer'
+ Bug fixes

V3.2.9
+ Added algorithm 'argon2id_exfer' (Exfer coin) for CPU, NVIDIA and AMD GPUs, fee 3.00%*

V3.2.8
+ Added AMD GPU support for algorithm 'sha256mem'
+ Hashrate improvement on algorithm 'sha256mem' on NVIDIA GPUs
+ Hashrate improvement on algorithm 'sha256mem' on CPUs with AVX2 and SHA-NI

[1971ECPT]

Hi!

3.30 version, starts ok on EXFER after autotune, runs couple minutes around 11xxH/s and after couple minutes, hashrate fall to around 680H/s.
Deleting autotune and cache folders, restarting miner situation repeats, after couple minutes hashrate falls down from 11xxH/s to 680H/s.
On "greedy" Nekominer (10% fee), it works stable at 12xxH/s all day long.
Graphic card is RTX2080Ti.

Thank you!

[fenomenyaa]

Will SRBMiner support PearlHash soon? I’m looking for a stable miner and pool. Hope you’ll be in the game soon.

[doktor83]

V3.3.1
+ Added algorithm 'pearlhash' (Pearl coin) for NVIDIA GPUs, fee 3.00%*
+ Nvidia P100 (SM_60) is now actually working on 'argon2id_exfer'
+ Bug fixes

Linux only binary - windows will come later

***
'pearlhash' can be mined on pearl.luckypool.io [ pearl-eu2.luckypool.io:3360 ]

[P00P135]

V3.3.1
+ Added algorithm 'pearlhash' (Pearl coin) for NVIDIA GPUs, fee 3.00%*
+ Nvidia P100 (SM_60) is now actually working on 'argon2id_exfer'
+ Bug fixes

Linux only binary - windows will come later

***
'pearlhash' can be mined on pearl.luckypool.io [ pearl-eu2.luckypool.io:3360 ]

Nice man!  Need some hashrate speed estimates before I can make a switch.

[doktor83]

V3.3.2
+ Fixed rejected shares on algorithm 'pearlhash' for 4000 series GPUs running older drivers (older than 580)*
+ Fixed high cpu usage on Hiveos when running algorithm 'pearlhash'
+ Fixed hashrate display on Hiveos UI
+ Fixed reported hashrate display on Luckypool UI

***
You should update your drivers to v580 for the smoothest experience

[fenomenyaa]

V3.3.2
+ Fixed rejected shares on algorithm 'pearlhash' for 4000 series GPUs running older drivers (older than 580)*
+ Fixed high cpu usage on Hiveos when running algorithm 'pearlhash'
+ Fixed hashrate display on Hiveos UI
+ Fixed reported hashrate display on Luckypool UI

***
You should update your drivers to v580 for the smoothest experience

Soon Support for Windows?

[doktor83]

V3.3.4
+ Huge hashrate improvement on algorithm 'pearlhash' for 2000 series GPU's
+ Improved hashrate on algorithm 'pearlhash' for weaker 5000 series GPU's
+ Swapped the power hungry - high hashrate 4000 series code on 'pearlhash' to a power efficient one. For the max hashrate one use previous miner version [v3.3.3]

V3.3.3
+ Fixed rejected shares on algorithm 'pearlhash' for 3000 series NVIDIA GPUs
+ Lowered power consumption on algorithm 'pearlhash' for 5000 series NVIDIA GPUs
+ Bug fixes

[fenomenyaa]

V3.3.4
+ Huge hashrate improvement on algorithm 'pearlhash' for 2000 series GPU's
+ Improved hashrate on algorithm 'pearlhash' for weaker 5000 series GPU's
+ Swapped the power hungry - high hashrate 4000 series code on 'pearlhash' to a power efficient one. For the max hashrate one use previous miner version [v3.3.3]

V3.3.3
+ Fixed rejected shares on algorithm 'pearlhash' for 3000 series NVIDIA GPUs
+ Lowered power consumption on algorithm 'pearlhash' for 5000 series NVIDIA GPUs
+ Bug fixes

Thank you for adding Windows support for the RTX 40-series.

However, I'm experiencing an issue where the miner fails to detect any supported GPU devices on a system with 8× RTX 4060 Ti GPUs. The log shows:

Error CL_INVALID_VALUE when getting PCIe topology

followed by:

No supported GPU devices found on OpenCL platform/s

The same platform, drivers, and hardware configuration work perfectly with LPMiner, so the GPUs themselves appear to be functioning correctly.

Additionally, I've noticed another issue with NVIDIA A2000 6GB cards. After running for some time, the miner occasionally reports "Out of Memory" errors, even though VRAM usage appears normal. This may indicate a memory leak or memory management bug.

Could you please advise whether these issues are known, and if there is a workaround or a fix planned for a future release?

Thank you for your work and support.

[PCMAGNAT]

V3.3.4
+ Huge hashrate improvement on algorithm 'pearlhash' for 2000 series GPU's
+ Improved hashrate on algorithm 'pearlhash' for weaker 5000 series GPU's
+ Swapped the power hungry - high hashrate 4000 series code on 'pearlhash' to a power efficient one. For the max hashrate one use previous miner version [v3.3.3]

One of my Windows 11 rigs gives me a naughty5 error when I launch it, but the others work fine, even on Windows 10. How do I fix this?

[1971ECPT]

Maybe virtual memory too low?
I always used virtual memory same size as graphic card memory
Ex if graphic card have 16384MB, virtual memory is set to 16384MB too.
If 2 cards of 16GB are on the rig, 16384+16384=32768MB as virtual memory.

[fenomenyaa]

Maybe virtual memory too low?
I always used virtual memory same size as graphic card memory
Ex if graphic card have 16384MB, virtual memory is set to 16384MB too.
If 2 cards of 16GB are on the rig, 16384+16384=32768MB as virtual memory.

Vm seted more than 100+GB , its not about vm.Thank you for your help.

[doktor83]

V3.3.6
+ Added algorithm 'oggpow' (Ogg coin) for AMD/NVIDIA/INTEL GPUs, fee 0.85%*
+ Improved hashrate on algorithm 'pearlhash' for NVIDIA H100/H200 (SM90) GPUs
+ Bug fixes

V3.3.5
+ Added AMD RDNA2 series support for algorithm 'pearlhash'
+ Minor hashrate improvement on algorithm 'pearlhash' for NVIDIA 3000 series GPUs
+ Reworked backend for GPU topology so the GPU order might be different than in previous miner versions
+ Added 'topology_id' to the API GPU report & web stats
+ Fixed mining of broken 'randomepic' + second algorithm
+ Bug fixes

[1971ECPT]

V3.3.6
+ Added algorithm 'oggpow' (Ogg coin) for AMD/NVIDIA/INTEL GPUs, fee 0.85%*

Hi, on Rplant pool it gives alot of "low difficulty share", regarding OGGminer wich works flawless.
No matter wich Nvidia graphic card used, tried with RTX2080Ti, RTX3090, RTX5080, the same error.

https://postimg.cc/s1RRz0vT

https://i.postimg.cc/MZnZyCxJ/1.jpg

[BoozyTalking]

Confirm, not work with Rplant.
Rplant pool is broken.

[omg345]

mining Pearlhash using SRBMiner-MULTI v3.3.6 on an 8x NVIDIA B300 rig
it seems that the miner might not be fully utilizing the potential of the Blackwell B300 architecture yet.
Each GPU is currently pushing around 68.6 TH/s with a power draw of only ~318W
[2026-06-10 00:44:37] ============================ v3.3.6 ============================
[2026-06-10 00:44:37]

•     [pearlhash]
[2026-06-10 00:44:37] GPU0 : 68.66 TH/s        [       0|     0|    0|   215.91 GH/W]
[2026-06-10 00:44:37] GPU1 : 68.64 TH/s        [       2|     0|    0|   212.51 GH/W]
[2026-06-10 00:44:37] GPU2 : 68.60 TH/s        [       0|     0|    0|   217.10 GH/W]
[2026-06-10 00:44:37] GPU3 : 68.62 TH/s        [       1|     0|    0|   215.10 GH/W]
[2026-06-10 00:44:37] GPU4 : 68.67 TH/s        [       1|     0|    0|   215.94 GH/W]
[2026-06-10 00:44:37] GPU5 : 68.64 TH/s        [       0|     0|    0|   215.83 GH/W]
[2026-06-10 00:44:37] GPU6 : 68.60 TH/s        [       0|     0|    0|   219.88 GH/W]
[2026-06-10 00:44:37] GPU7 : 68.61 TH/s        [       3|     0|    0|   214.39 GH/W]
[2026-06-10 00:44:37] Total: 549.03 TH/s       |       7|     0|    0|
[2026-06-10 00:44:37] ================================================================
[2026-06-10 00:44:37] GPU0 :

[T:  41c CC:  1905MHz MC:   3996MHz FAN:     - P:  318W]
[2026-06-10 00:44:37] GPU1 : [T:  44c CC:  1905MHz MC:   3996MHz FAN:     - P:  323W]
[2026-06-10 00:44:37] GPU2 : [T:  41c CC:  1905MHz MC:   3996MHz FAN:     - P:  316W]
[2026-06-10 00:44:37] GPU3 : [T:  43c CC:  1905MHz MC:   3996MHz FAN:     - P:  319W]
[2026-06-10 00:44:37] GPU4 : [T:  44c CC:  1905MHz MC:   3996MHz FAN:     - P:  318W]
[2026-06-10 00:44:37] GPU5 : [T:  44c CC:  1905MHz MC:   3996MHz FAN:     - P:  318W]
[2026-06-10 00:44:37] GPU6 : [T:  42c CC:  1905MHz MC:   3996MHz FAN:     - P:  312W]
[2026-06-10 00:44:37] GPU7 : [T:  42c CC:  1905MHz MC:   3996MHz FAN:     - P:  320W]
[2026-06-10 00:44:37] Total:                                                   2544W
[2026-06-10 00:44:37] ================================================================