WildRig Multi 0.40.9 multi-algo miner with low dev-fee (AMD/NVIDIA/INTEL)

[prominertools]

Latest version (and all previous) mirrored at:


https://prominertools.com/wildrig-multi/

Direct download links:
https://prominertools.com/miners/wildrig-multi/wildrig-multi-0.15.2.2.zip (Windows)
https://prominertools.com/miners/wildrig-multi/wildrig-multi-0.15.2.2.tgz (Linux)
https://prominertools.com/miners/wildrig-multi/wildrig-multi-0.15.2.kernels.zip (Hawaii Kernels)

pointless post when they are all on github anyways...

https://github.com/andru-kun/wildrig-multi/releases

But how can he hack your wallets if you download from GitHub

Ever heard of a little thing called "checksum" ?

Figured so.

[willy35]

Hi,

I have trouble using my R9 380 -

 * VERSIONS:     WildRig/0.15.3.7 beta libuv/1.21.0 OpenCL/2.0 MSVC/2015
 * CPU:          Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz x64 AES-NI
 * ALGO:         x21s
 * POOL #1:      rito-eu.skypool.co:8626
 * COMMANDS:     hashrate, pause, resume
[10:42:40] donation: 2%
[10:42:40] strategy: 0
[10:42:40] send-stale: no
[10:42:40] watchdog: disabled
[10:42:40] good-risers: default
[10:42:40] initializing GPUs...
[10:42:40] GPU #0 [BusID: #1] [Tonga] AMD Radeon (TM) R9 380 Series
[10:42:40] threads: 1, intensity: 18, worksize: 0/256, cu: 28, mem: 4096Mb
[10:42:40] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram

How can I solve this, I am on windows 10

thank you

[andrucrypt]

Hi,

I have trouble using my R9 380 -

 * VERSIONS:     WildRig/0.15.3.7 beta libuv/1.21.0 OpenCL/2.0 MSVC/2015
 * CPU:          Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz x64 AES-NI
 * ALGO:         x21s
 * POOL #1:      rito-eu.skypool.co:8626
 * COMMANDS:     hashrate, pause, resume
[10:42:40] donation: 2%
[10:42:40] strategy: 0
[10:42:40] send-stale: no
[10:42:40] watchdog: disabled
[10:42:40] good-risers: default
[10:42:40] initializing GPUs...
[10:42:40] GPU #0 [BusID: #1] [Tonga] AMD Radeon (TM) R9 380 Series
[10:42:40] threads: 1, intensity: 18, worksize: 0/256, cu: 28, mem: 4096Mb
[10:42:40] Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram

How can I solve this, I am on windows 10

thank you

Hi, what drivers are you running?

update: hmm, looks like my bad, tonga has some different instruction set from other GCN 3rd gen cards(e.g. Fiji). Will try to fix it in next release, before that you can use older version(0.15.2.2)

[andrucrypt]

0.15.3.8 beta:
- tuned auto-parameters for Vega
- fixed Tonga and Bonaire support

@willy35 try new version please

[katar14]

i have wildrig-multi-windows-0.15.3.8-beta
i have text:

@echo off

:loop

wildrig.exe --print-full --algo MTP --opencl-threads auto --opencl-launch auto --url zcoin.mintpond.com:3000 --user Dn7MMYjVQqenT11VFDYHfFdwXmSTRUTak --pass x

if ERRORLEVEL 1000 goto custom
timeout /t 5
goto loop

:custom
echo Some error happened, put custom command here
timeout /t 5
goto loop


no mining, white? i have 2x rx580

https://images91.fotosik.pl/125/46ac0ef841d5bc93med.jpg

http://www.picshare.ru/uploads/190215/3DD5v292G8.jpg

[andrucrypt]

i have wildrig-multi-windows-0.15.3.8-beta
i have text:

@echo off

:loop

wildrig.exe --print-full --algo MTP --opencl-threads auto --opencl-launch auto --url zcoin.mintpond.com:3000 --user Dn7MMYjVQqenT11VFDYHfFdwXmSTRUTak --pass x

if ERRORLEVEL 1000 goto custom
timeout /t 5
goto loop

:custom
echo Some error happened, put custom command here
timeout /t 5
goto loop


no mining, white? i have 2x rx580

MTP algo not supported since version 0.15.2. Will be returned sometime later with improvements, but I have no plans for it right now.

[Plushka1357]

Hello! I have problems with my r7 260x! Driver 15.12.
https://i.ibb.co/9wz6GS5/image.png

[andrucrypt]

Hello! I have problems with my r7 260x! Driver 15.12.

damn, still not working... looks like need to buy one of those cards %) Next week I won't be around my dev-pc, so will return to this question later

[andrucrypt]

Hello! I have problems with my r7 260x! Driver 15.12.

Oh, driver 15.12 is too old. Try newer one, 18.6.1

[Plushka1357]

Hello! I have problems with my r7 260x! Driver 15.12.

Oh, driver 15.12 is too old. Try newer one, 18.6.1

Oh thanks! It worked!

[balko14]

Why r9 280x Tahiti is not supported on X16RT 

[nordmann666]

how to handle problems with this miner at X21s and Vega 56/64?

got many trouble to run it on my CN optimized rig with windows 10 and 18.6.1 drivers - but i cant get it stable

with 1400mhz and 910mv some cards are crashing the whole computer and not only the software...with 1350mhz i have it stable for some minutes but temps growing fast and mining performance goes way down to 8MHs

i use --opencl-threads auto --opencl-launch auto

[andrucrypt]

how to handle problems with this miner at X21s and Vega 56/64?

got many trouble to run it on my CN optimized rig with windows 10 and 18.6.1 drivers - but i cant get it stable

with 1400mhz and 910mv some cards are crashing the whole computer and not only the software...with 1350mhz i have it stable for some minutes but temps growing fast and mining performance goes way down to 8MHs

i use --opencl-threads auto --opencl-launch auto

Try to lower memory clocks, they are not so important on this algo. This should make less heat. Also try lower intensity or 1 thread instead of 2(it used when auto set). Problem here is Lyra2 part(pretty hot), and core intensive calculations in general.

[nordmann666]

how to handle problems with this miner at X21s and Vega 56/64?

got many trouble to run it on my CN optimized rig with windows 10 and 18.6.1 drivers - but i cant get it stable

with 1400mhz and 910mv some cards are crashing the whole computer and not only the software...with 1350mhz i have it stable for some minutes but temps growing fast and mining performance goes way down to 8MHs

i use --opencl-threads auto --opencl-launch auto

Try to lower memory clocks, they are not so important on this algo. This should make less heat. Also try lower intensity or 1 thread instead of 2(it used when auto set). Problem here is Lyra2 part(pretty hot), and core intensive calculations in general.

i disabled mem_p3 and mem is running slowly and cold...but core side is a big problem on my rig - 1 thread gives horrible low hs

[andrucrypt]

i disabled mem_p3 and mem is running slowly and cold...but core side is a big problem on my rig - 1 thread gives horrible low hs

what if try 1 thread with higher intensity?

[nordmann666]

i disabled mem_p3 and mem is running slowly and cold...but core side is a big problem on my rig - 1 thread gives horrible low hs

what if try 1 thread with higher intensity?

for example?

[andrucrypt]

i disabled mem_p3 and mem is running slowly and cold...but core side is a big problem on my rig - 1 thread gives horrible low hs

what if try 1 thread with higher intensity?

for example?

auto-parameters are 2 threads and intensity 18, so try --opencl-threads 1 --opencl-launch 19x0 or even 20. Try that with --benchmark to find what is best(stable) for your cards. With this parameter hashrate will be stable because of static hashorder.

[nordmann666]

i disabled mem_p3 and mem is running slowly and cold...but core side is a big problem on my rig - 1 thread gives horrible low hs

what if try 1 thread with higher intensity?

for example?

auto-parameters are 2 threads and intensity 18, so try --opencl-threads 1 --opencl-launch 19x0 or even 20. Try that with --benchmark to find what is best(stable) for your cards. With this parameter hashrate will be stable because of static hashorder.

THX - thats way better...11MHs and much lower power consumption and heat

[andrucrypt]

i disabled mem_p3 and mem is running slowly and cold...but core side is a big problem on my rig - 1 thread gives horrible low hs

what if try 1 thread with higher intensity?

for example?

auto-parameters are 2 threads and intensity 18, so try --opencl-threads 1 --opencl-launch 19x0 or even 20. Try that with --benchmark to find what is best(stable) for your cards. With this parameter hashrate will be stable because of static hashorder.

THX - thats way better...11MHs and much lower power consumption and heat

But don't forget to remove --benchmark afterward! This is only for finding best parameters, hashrate with pool will differ, depends on current hashorder

[nordmann666]

i disabled mem_p3 and mem is running slowly and cold...but core side is a big problem on my rig - 1 thread gives horrible low hs

what if try 1 thread with higher intensity?

for example?

auto-parameters are 2 threads and intensity 18, so try --opencl-threads 1 --opencl-launch 19x0 or even 20. Try that with --benchmark to find what is best(stable) for your cards. With this parameter hashrate will be stable because of static hashorder.

THX - thats way better...11MHs and much lower power consumption and heat

But don't forget to remove --benchmark afterward! This is only for finding best parameters, hashrate with pool will differ, depends on current hashorder

i know that...other miners also had benchmark modes...but it´s hard to find examples for different cards on mining software i dont know...

best stable for me atm (have to wait one hour minimum) is 2 threads and 17 intensity (11.2MH)
with auto settings i got 12.2MH but one card cant handle this and after some time the others follow