SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching

[Baikal miner]

Why i want this is error Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 1 (Thread 2)
Error while creating GPU threads.. Stopping miner process.
http://prntscr.com/nbutg3
http://prntscr.com/nbutn6

[doktor83]

Why i want this is error Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 1 (Thread 2)
Error while creating GPU threads.. Stopping miner process.

Because r9 380 is not ellesmere. Integrated gpu or driver is messing up there.

[ManDoneKTM]

Hello ! After i update it to 1 8 3 i have this issues . https://imgur.com/a/jwg9PeQ

[doktor83]

Hello ! After i update it to 1 8 3 i have this issues . https://imgur.com/a/jwg9PeQ

check the second tip on the first page here : https://bitcointalk.org/index.php?topic=3167363.msg32748623#msg32748623

[Sadopwnz]

I have 8 GPUs, but the 8th GPU crashes still mining after ~5-30 min with log:
https://c.radikal.ru/c42/1904/8b/c9e6fe0e2f72t.jpg
Switching GPUs, risers, stock settings did nothing. MB asus z370-p, 8xflashed vega56.
Any ideas?

[Baikal miner]

Why i want this is error Error CL_BUILD_PROGRAM_FAILURE when calling clBuildProgram [ctx->Program] for DeviceID 1 (Thread 2)
Error while creating GPU threads.. Stopping miner process.
http://prntscr.com/nbutg3
http://prntscr.com/nbutn6

Because r9 380 is not ellesmere. Integrated gpu or driver is messing up there.

i re-install driver not work

[Dubai-Industry]

nice relise

[Rabotaet]

Увaжaeмый дoктop83.

1)Чтoбы вaшa yтилитa SRB-Restarter paбoтaлa кoppeктнo нa windows 7  нeoбxoдимo oтключить в cиcтeмe oкoшкo oб aвapийнoм зaвepшeнии пpилoжeния. Бeз этoгo вaшa yтилитa дyмaeт, чтo пpoцecc SRB-miner eщe зaпyщeн и paбoтaeт, xoтя мaйнep yжe двaнo зaвиc и виcит cиcтeмнoe oкoшкo oб oшибкe в пpилoжeнии. Haвepнo этo дeлaeтcя тaк: Пycк-Bыпoлнить-> gpedit.msc-> Computer Settings -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> Turn off Windows Error Reporting.

2)Haчинaя c вepcии 1.8.2 мaйнep нa cтapтe пoкaзывaeт oчeнь низкиx xэшpeйт и пepeзaпycкaeтcя, т.к. ycтaнoвлeн пapaмeтp "минимaльный xэшpeйт". Кapты rx562. Oпытным пyтeм былo ycтaнoвлeнo, чтo либo нe иcпoльзoвaть этoт пapaмeтp вooбщe, либo ycтaнoвить cимвoличecкoe знaчeниe, cкaжeм 100.

[doktor83]

Увaжaeмый дoктop83.

1)Чтoбы вaшa yтилитa SRB-Restarter paбoтaлa кoppeктнo нa windows 7  нeoбxoдимo oтключить в cиcтeмe oкoшкo oб aвapийнoм зaвepшeнии пpилoжeния. Бeз этoгo вaшa yтилитa дyмaeт, чтo пpoцecc SRB-miner eщe зaпyщeн и paбoтaeт, xoтя мaйнep yжe двaнo зaвиc и виcит cиcтeмнoe oкoшкo oб oшибкe в пpилoжeнии. Haвepнo этo дeлaeтcя тaк: Пycк-Bыпoлнить-> gpedit.msc-> Computer Settings -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> Turn off Windows Error Reporting.

2)Haчинaя c вepcии 1.8.2 мaйнep нa cтapтe пoкaзывaeт oчeнь низкиx xэшpeйт и пepeзaпycкaeтcя, т.к. ycтaнoвлeн пapaмeтp "минимaльный xэшpeйт". Кapты rx562. Oпытным пyтeм былo ycтaнoвлeнo, чтo либo нe иcпoльзoвaть этoт пapaмeтp вooбщe, либo ycтaнoвить cимвoличecкoe знaчeниe, cкaжeм 100.

I tried to translate with google translate but i still don't understand what you want to say 

[Rabotaet]

1) When the miner freezes, the system error window appears.

But the SRB-Miner process is still in computer memory.

The SRB-Restarter utility thinks that the miner is working. But the miner is frozen.

Perhaps this problem can be solved on Windows 7.

It is necessary to disable the output of system notifications.

 gpedit.msc-> Computer Settings -> Administrative Templates -> System -> Internet Communication Management -> Internet Communication Settings -> Turn off Windows Error Reportin

2)
RX562, miner 1.8.1 - OK
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"retry_time" : 2,
"persistent_memory" : false,
"min_rig_speed" : 2100,
"min_rig_speed_duration" : 60,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 1, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 2, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 3, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 4, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8}
]
}

RX562, miner 1.8.2 - 1.8.3 - not OK
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"retry_time" : 2,
"persistent_memory" : false,
"min_rig_speed" : 2100,  <<<<<<<<<==============   only works if set to 100. otherwise restart miner!!!!!!!
"min_rig_speed_duration" : 60,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 1, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 2, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 3, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 4, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8}
]
}

[ledgerdary]

Which driver is meant by Adrenalin 2019 in the recommended drivers? Is that 18.12.2 only or also newer versions?

My 19.4.1 is disapproved by the miner...

[viljy]

For some reason it seems to me that automatic settings for RX550 are not optimal.
How much does the average kh/s can give RX550? ~1.2 kh/s for cn-upx is this normal?

[psthoy]

Has anyone tried srbminer 1.8.3 on a hashvaultpro pool?  Im trying to merge mine haven+bloc, anyone can share how its done?  TIA.

[Iamtutut]

Which driver is meant by Adrenalin 2019 in the recommended drivers? Is that 18.12.2 only or also newer versions?

My 19.4.1 is disapproved by the miner...

Never mine with a driver newer than your miner version.

[doktor83]

1) When the miner freezes, the system error window appears.

But the SRB-Miner process is still in computer memory.

The SRB-Restarter utility thinks that the miner is working. But the miner is frozen.

Not every crash can be catched, restarter works for restarting the miner when a crash occurs because of miner bug code (access violation etc.)

RX562, miner 1.8.2 - 1.8.3 - not OK
{
"cryptonight_type" : "normalv4",
"intensity" : 0,
"double_threads" : true,
"retry_time" : 2,
"persistent_memory" : false,
"min_rig_speed" : 2100,  <<<<<<<<<==============   only works if set to 100. otherwise restart miner!!!!!!!
"min_rig_speed_duration" : 60,
"gpu_conf" :
[
{ "id" : 0, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 1, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 2, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 3, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8},
{ "id" : 4, "intensity" : 26, "worksize" : 32, "threads" : 2, "fragments" : 8}
]
}

Someone else also reported the 'min_rig_speed' parameter is broken and triggers much earlier than it is set. I am testing it, but so far so good.
On a rig that does 38khs turtle i set it to 36khs and it's not triggering - restarting miner.

Im using with minimal config :

Code:

{
"cryptonight_type" : "turtle",
"intensity" : 0,
"double_threads" : true,
"min_rig_speed" : 36000
}

Going to check it out in code, maybe when gpu_conf is set this parameter gets omitted, or idk.

[doktor83]

Which driver is meant by Adrenalin 2019 in the recommended drivers? Is that 18.12.2 only or also newer versions?

My 19.4.1 is disapproved by the miner...

It is not disapproved, you just see a notice that you are not using one of the recommended drivers 
Basically you can use any driver, if it is working good for you. But the most tested driver is 18.6.1

[alexcrys1]

Which driver is meant by Adrenalin 2019 in the recommended drivers? Is that 18.12.2 only or also newer versions?

My 19.4.1 is disapproved by the miner...

It is not disapproved, you just see a notice that you are not using one of the recommended drivers 
Basically you can use any driver, if it is working good for you. But the most tested driver is 18.6.1

Hello, u will support uplexa new algo:UPXTWO ?

[Lio78]

Hello, u will support uplexa new algo:UPXTWO ?

Quote 

[symplink]

"+ --preparedata can now give a small boost with turtle, mox, heavy and gpu algo on Vega56. Did not test on other cards."
It is like going worse on vega64 - from 49700 to 48400 /12 vegas
Maybe I am doing something wrong?:
SRBMiner-CN.exe --config Config\config-mox.txt --pools poolsmox.txt --preparedata --resetvega --gpureorder --disablegpuwatchdog --logfile %LOGTIME%
or
SRBMiner-CN.exe --config Config\config-mox.txt --pools poolsmox.txt --resetvega --preparedata  --gpureorder --disablegpuwatchdog --logfile %LOGTIME%\
Same results
19.1.1

[doktor83]

Hello, u will support uplexa new algo:UPXTWO ?

Quote 

Sure i will, im waiting on the dev/devs

"+ --preparedata can now give a small boost with turtle, mox, heavy and gpu algo on Vega56. Did not test on other cards."
It is like going worse on vega64 - from 49700 to 48400 /12 vegas
Maybe I am doing something wrong?:
SRBMiner-CN.exe --config Config\config-mox.txt --pools poolsmox.txt --preparedata --resetvega --gpureorder --disablegpuwatchdog --logfile %LOGTIME%
or
SRBMiner-CN.exe --config Config\config-mox.txt --pools poolsmox.txt --resetvega --preparedata  --gpureorder --disablegpuwatchdog --logfile %LOGTIME%\
Same results
19.1.1

You are not doing anything wrong, looks like vega64 does not like it. I tested only on Vega56 with Hynix mem, cause thats what i got.