SRBMiner-MULTI AMD & NVIDIA & INTEL & CPU miner

[File0]

Dear Doktor83,
I am writing to report a bug in SRBMiner-MULTI. The miner crashes immediately on startup on versions newer than 3.8.0 when running a CMP90 GPU on the quantus algorithm. The console window just instantly closes without any error logs. The OS is Windows 10 x64.
Everything works fine on version 3.8.0, but any release after that breaks the launch for this card.
Please check what broke compatibility with the CMP90 after version 3.8.0 and fix it in the next update.

[maXonja]

Switched to Onezero 1.8.4, higher and stable hashrate across all GPU's (CMP 50, 3070, 4070-4080, 5060-5080)

[egocentr]

quantus v3.8.3 AMD win 10. The issues with hashrate/power fluctuations haven't stopped.

[random8191]

Again BS:

"Devfee related operations were blocked! Check your firewall/antivirus.
Make sure you have 'wget' installed on your system!"

At another ISP now! Old one "bad" at the same time is working.

Suggestion: at your server make whitelist of wallet addresses so mining will start despite connection to secret devfee pools.

[coinminery]

I think at last, one graphic card fails and then entire system crash.

Are overcloocked cards? Can you put .bat file here (copy/paste text from .bat file)?
Try to use log file command on miner .bat file. Maybe too much overclock or too hot GPU caused from dryed thermal paste especially at Gigabyte cards, if never had maintenance to them.

Can you put .bat file here (copy/paste text from .bat file)?
Here's my .bat file, what is bolded, is to "get rid" of open cl error because not AMD or Intel Graphic Cards on the rig, wich are enabled by default.
What is underlined, is the command for enable and keep log file, where "MyMinerLog" is the name of the .txt file.

SRBMiner-MULTI.exe --log-file MyMinerLog.txt --log-file-mode 2 --disable-gpu-amd --disable-gpu-intel --algorithm-gpu pearlhash --pool pearl-pl.luckypool.io:3360 --wallet prl-wallet --worker prl-worker

EDIT: for SRBMiner-multi developer.

Tried today 3.8.1 version to one mixed rig with RTX5070Ti + RTX4070Ti; from time to time, hashrate showed are enormous, couple thousand of TH some like RTX5070Ti hashrate is 44638TH instead around 198-200TH like usually. On Pool, hashrate looks normal.
Coin is Pearl, Nvidia drivers are 616.64.
With 3.8.0 version, all are OK.

Later EDIT: tried 3.8.2 version too, it increased a little efficiency, but hashrate fluctuates from 200-202TH lower to 184TH, then goes up again on 5070Ti after 10 minutes from start. I will stick to 3.8.0, until now it looks the best, 201TH rock stable after couple minutes from start on 5070Ti.

Hi!
3.8.3  3070ti hash?

[coinminery]

Switched to Onezero 1.8.4, higher and stable hashrate across all GPU's (CMP 50, 3070, 4070-4080, 5060-5080)

Hi!
hashrate models?

[1971ECPT]

Hi!
3.8.3  3070ti hash?

Hi, I don't own RTX3xxx series, so I don't know, sorry.
RTX4070Ti does 168TH at 195 Watts, RTX5070Ti does 201TH at 203 Watts.

[tbearhere]

Switched to Onezero 1.8.4, higher and stable hashrate across all GPU's (CMP 50, 3070, 4070-4080, 5060-5080)

Hi!
hashrate models?

Try https://hashrate.no/GPUcalculator?selected=3070ti-1&systemWatts=40&psuEfficiency=92

[UDICrypto]

If one card drops out and takes the whole rig down with it, it is almost always one of three things: an unstable memory/core offset, a power-limit/PSU or riser problem, or the driver timing out. A few things I would check, in this order:

1. Back the overclock off to stock and add it back one step at a time. Pearlhash is heavy on the tensor/compute side, so settings that were rock stable on an older algorithm can fall over. Lock the power limit per card (nvidia-smi -pl) rather than letting boost float, and leave a little headroom on the PSU, since transient spikes are what usually kill rigs.
2. Keep the log file option you already use, and also watch Windows Event Viewer for Display/nvlddmkm errors right at the crash time. If a driver reset is logged, it is the card/OC; if the machine just reboots with nothing logged, suspect the PSU or a riser.
3. The huge hashrate figures (44638 TH on a 5070 Ti) on a mixed rig look like a reporting glitch in that miner build rather than a real hardware problem, since the pool-side number is normal. Staying on the build that was stable for you is a sensible call, and the dev will likely want those logs.
4. For unattended rigs, put a watchdog in place (a script that restarts the miner if the hashrate drops to 0 or the process dies, plus BIOS "restore on AC loss" and auto-login), so a single crash does not cost you hours of mining.

If you post the GPU model that actually crashes plus its power limit and clocks, people here can probably narrow it down further.

[batsonxl]

I think at last, one graphic card fails and then entire system crash.

Are overcloocked cards? Can you put .bat file here (copy/paste text from .bat file)?
Try to use log file command on miner .bat file. Maybe too much overclock or too hot GPU caused from dryed thermal paste especially at Gigabyte cards, if never had maintenance to them.

Can you put .bat file here (copy/paste text from .bat file)?
Here's my .bat file, what is bolded, is to "get rid" of open cl error because not AMD or Intel Graphic Cards on the rig, wich are enabled by default.
What is underlined, is the command for enable and keep log file, where "MyMinerLog" is the name of the .txt file.

SRBMiner-MULTI.exe --log-file MyMinerLog.txt --log-file-mode 2 --disable-gpu-amd --disable-gpu-intel --algorithm-gpu pearlhash --pool pearl-pl.luckypool.io:3360 --wallet prl-wallet --worker prl-worker

EDIT: for SRBMiner-multi developer.

Tried today 3.8.1 version to one mixed rig with RTX5070Ti + RTX4070Ti; from time to time, hashrate showed are enormous, couple thousand of TH some like RTX5070Ti hashrate is 44638TH instead around 198-200TH like usually. On Pool, hashrate looks normal.
Coin is Pearl, Nvidia drivers are 616.64.
With 3.8.0 version, all are OK.

Later EDIT: tried 3.8.2 version too, it increased a little efficiency, but hashrate fluctuates from 200-202TH lower to 184TH, then goes up again on 5070Ti after 10 minutes from start. I will stick to 3.8.0, until now it looks the best, 201TH rock stable after couple minutes from start on 5070Ti.

Thanks for help.
I found the problem.
1 open cl id error was srbminer could not identify onboard vga. This is not problem for crash.
2 crash was bad psu. On this rig i have 2 psu. 2nd psu was dying. It is working but after some time it cant deliver enough power.
I changed ram didnt worked then changed whole motherboard  didnt work. After that i understood it was psu.
Spend so many days problem was bad psu. Now im thinking where was my head???

[1971ECPT]

Glad to help, we are a community!
You didn't tell about 2x psu on the rig, and other details. All of them, matters!
As usually, I thing one miner, every of us, based his rig on good PSU, because power supply is essential.
I always load PSU's no more than 60-65% of his rated power, when PC system or rig, is at maximum possible load.
For 2xRTX5070Ti, and entire rig (mb/cpu/memory/ssd/2 risers/6fans, etc) I have one Seasonic 1300W psu, a platinum one.
For the others 2xRTX4070Ti and 2 risers, I use for each card+riser, one 750Watts platinum server HP PSU, powered when Master PSU Seasonic, turns on. All 3 PSU's, stays cold and silent.