Topic: SRBMiner Cryptonight AMD GPU Miner V1.9.3 - native algo switching - page 150. (Read 237247 times)

@doktor83
I am dont change any settings in my firewall, if i am do it i am dont post here.
It was do not my fail, we dont know maybe your server was fault
I am see what mining runs at my mining pool and then it stop because cant connect to the devfee.

I would if i get some logs

You can generate a PS script to restart a process if its not active.
If you don't know PS you can always use a program to do it for you, you can check some here:
https://www.raymond.cc/blog/keep-application-running-by-automatically-rerun-when-closed/

Doctor, the miner sometimes closes anyway, even if its not blocked by FW or antivirus, you should look into this.

I used to have these issues, these are caused by aggresive coreclock/memclock/too low vddc voltage. Either/or combination of those 3 settings.

I solved the bsod by using more conservative core clock/mem clock and increase the vddc voltage

That's what I thought. There are some nice things that can be done about this that everybody would appreciate It involves connecting early to pool, starting watchdog early, starting gpu's as they load the opencl code. The benefits would be four-fold, the hashing would start slightly earlier, watchdog would be able to catch a failed init, no time would be wasted if the active algo is different at the initial run, and there would be less strain on the PSU's that supply power during the ramp up. The last one would be very nice on the PSU's and would add more stability for the initializing sequence.

I know you are extremely busy with the monero forking and all but I hope you could take a look at this option!

edit: Have you even tried my proxy yet? It works quite nice with your miner

Hi, I,m using your excelent miner doc but i have some inestability with my vegas, i have 5 vegas in a rig 2 vega 64 1 vega 56 @vega64 bios and 2 vega 56, my windows got me bsod with video scheduler internal error, and i answer if i could use the block chain driver instead the adrenaline 18.6.1? PD FYC Lately the vega 56 with bios 64 hang up with black screen and fan go to max rev. And i have to reset the rig. what do you suggest?

edit the pools.txt:
Example:

{"pool" : "stratum+tcp://cryptonightheavy.br.nicehash.com:3364", "wallet" : "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.worker_name", "password" : "x"},

Greetings!

Tell me, did you solve the issue with an intensity of 45 in the srb miner ... encountered the same thing ...

broke the Windows account, then created a new one, but the miner stopped running with an intensity higher than 45 ...

Removing drivers, reinstalling all the software, does not help yet!

Such a moment is observed only in Heavy, on other aglorhrams the intensity is set out to be necessary !!! !!!

Hi everyone, I`m new to SRBMiner.
Can someone please share a working Nicehash config please.
I tried but with no luck.

The watchdog is for initialised and running gpu's, so at the phase of opencl platform etc detection it is not running yet.

Similarly on my end, on algo change, just at the warmup, it may free on algo change, and this is not picked up by the watchdog, the rig does not freeze, just SRBminer, with a probably crashed gpu. The problem is that the watchdog does not pick this at the start. Manually re-applying OverdriveNTool and restarting solves the problem. I had earlier sent the log here.

You should check your firewall or antivirus apps policy. This can happen only if it can't connect to a devfee pool minimum 3 or more times in a row (and when it can't connect to a devfee pool for the first time, it then tries another devfee pool when devfee mining time comes again, so the chances that a few different pools aren't available are i would say impossible).

So in practice it couldnt connect to different pools in a timespan of minimum few hours. Well you must admit that looks like something is blocking the outgoing miner connections.

Very bad expirience i have today.
Miner stopped mining with messege can't connect to the dev pool, you are blocked
Hey its not my problem if your dev pools not working, maybe you review your policy

The Asus 580 get lower hashrate with these values, I tried already.
What means 'warmup' stuff? More heat on cards?

that change did work - just didnt configure it properly -- Thank You!!!

how you do that automatically?

probao i odistao nakon sat vremena probavanja
to radi jedino ak nisi kartice vec natjero na krajnje granice.
kad kartica daje na 56 int 1600+HR onda sa 61/9 pukne nakon 15 sekundi a da sad krecem mjenjat napone i sppustat frekve mi se i neda jer sto cu onda dobit?

Ak imas vise od 1600Hr na tube sa 900mv mem i gpui ak 4 kartice od toga jedna LE koja trosi 30W vise jer je LE i trosi 700W iz zida onda cu probat opet? ak to sve imas onda cu se poigrat al za 5 HR da rusim sve i jebem se opet danima bas mi i nije neki djir. ktome nitko ovdje nije stavio neki SS da to fercera. stavio si ti kao 1500+HR sto je daleko ispod mojeg HR pa mi to nis ne znaci. ja sam opet na 1834 driverima i jedino sa njima i v7 algoom mi radi ta fora. sa nijednim drugim algoom to ne radi kod mene i to samo na referentnim samsung karitcama dok na nitru s hynixom to nicem ne sluzi ni u v7 algu. lili daje manji HR ili bloka kartice.

jedino  na referentnima na sTL/v7 radi s ovim postavkama
{ "id" : 0, "intensity" : 120, "worksize" : 16, "threads" : 1},
{ "id" : 0, "intensity" : 122, "worksize" : 16, "threads" : 1},
{ "id" : 1, "intensity" : 120, "worksize" : 16, "threads" : 1},
{ "id" : 1, "intensity" : 122, "worksize" : 16, "threads" : 1},
{ "id" : 2, "intensity" : 120, "worksize" : 8, "threads" : 1},
{ "id" : 2, "intensity" : 122, "worksize" : 8, "threads" : 1},
{ "id" : 3, "intensity" : 120, "worksize" : 16, "threads" : 1},
{ "id" : 3, "intensity" : 122, "worksize" : 16, "threads" : 1},

vege 56 sam isprobo w od 4 do 20 i najbolje daje na 16
vega 64 na w=9 daje osjetno manji hr

I tried different configurations with the Kernel settings and received the same results each time.

Try to set manually 56/8/2 for the 580 8g card.
Adrenalin 18.5.1 or 18.6.1 is recommended, if you want to do the 'warmup' stuff use 18.3.4 and maybe you can get out more hash on bittube algo.

PowerShell requested I use "./SRBMiner-CN.exe --SetComputeMode" as the command. The first one didn't take as you noted. Thank you, this resolved it!