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

[heavyarms1912]

I keep getting this now on 1.5.9 every now and then.  Nothing changed in settings.
shut_down_miner exception: Resource deadlock avoided

[DevelopmentBank]

Thanks for the latest update dok. It really works well.

Just have one question though, i'm a victim of the hashrate drop because my temp is always too high. 60+ degrees all the time even after i set voltage to 900 and set min. RPM fan speed to 4000! I don't understand why my VEGAs are getting this hot. Any tips?

[MaxHa$h]

So as of today, can we expect ~500 H/s from a typical Rx 550?

http://i64.tinypic.com/2cyqsu0.png

It's a silicone lottery too... 4x Sapphire, 2x Gigabyte, 1x Asus

2 of the 4 Sapphire and the Asus are hit over 510+ H\s I have to get a box fan for it now though no ac or windows in this part of the house, it's about 88-90* in there

[Kgonla]

I think I can confirm...

After the difficulty monitor is executed for 4th time the program closes itself

[2018-06-09 15:01:33] Connection to pool lost. Reconnecting in 10 seconds.

And the program is closed.

i will check it out.
 Also it's not triggerring momentally when the set difficulty is reached. Check is made every 45 seconds.
No point setting it for ex 1 sec because it just eats up cpu resources, and i think its not THAT important to disconnect momentally.
But correct me if i am wrong.

I did not know how this works, I thought it was detected automatically.
About the time, I think it depends on how often the pool sets difficulty too high.
This option could be very useful for pools with badly configured vardiff to avoid loosing shares.
So, for me the shortest the best but every one is different
Maybe a command to choose between 1 & 60 secs.

[lebuawu2]

I keep getting this now on 1.5.9 every now and then.  Nothing changed in settings.
shut_down_miner exception: Resource deadlock avoided

I also getting this, suddenly all GPU hashing speed 0 h/s.

[2018-06-10 00:41:42] pool_ping: Sent keepalive message to pool
[2018-06-10 00:41:42] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-06-10 00:41:42] json_receive: Pool responded with KEEPALIVED
[2018-06-10 00:42:07] watchdog: GPU0 [BUS: 1] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU1 [BUS: 2] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU2 [BUS: 3] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU3 [BUS: 4] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU4 [BUS: 5] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU5 [BUS: 6] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU6 [BUS: 9] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU7 [BUS: 10] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU8 [BUS: 11] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU9 [BUS: 12] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU10 [BUS: 13] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU11 [BUS: 15] hashing speed is 0 H/S
[2018-06-10 00:42:33] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0707d1a3f0d805256279b460556b7c15ee3cd01fcdba90cfdadfbdcc0654c667f5a4ae0a9a78530 00000001ab26cc8554f6b2671add6a9c76cbaaa20eb9f31179f7e0d5c9d969a8fd7194303","job_id":"276673124018431","target":"cf8b0000"}}
[2018-06-10 00:42:38] pool_ping: Sent keepalive message to pool
[2018-06-10 00:42:38] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-06-10 00:42:38] json_receive: Pool responded with KEEPALIVED
[2018-06-10 00:42:56] shut_down_miner exception: Resource deadlock avoided
[2018-06-10 00:42:56] Stopping miner process

[zeii]

So as of today, can we expect ~500 H/s from a typical Rx 550?

http://i64.tinypic.com/2cyqsu0.png

It's a silicone lottery too... 4x Sapphire, 2x Gigabyte, 1x Asus

2 of the 4 Sapphire and the Asus are hit over 510+ H\s I have to get a box fan for it now though no ac or windows in this part of the house, it's about 88-90* in there

How much your intensity and what algo?

thx.

[doktor83]

V1.6.0
+ As some have issues with miner 'just waiting some time' on startup, i added more logging option so we can catch where it hangs, and i can possibly fix that

Reproduced
[2018-06-10 02:38:44] Heating up system, please wait...

[2018-06-10 02:38:28] Miner version: 1.6.0
[2018-06-10 02:38:43] AMD Platform ID: 1
[2018-06-10 02:38:43] AMD platform FOUND
[2018-06-10 02:38:43] Found 13 AMD devices
[2018-06-10 02:38:43] GPU0: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.0][W: 12][T: 2][K: 1][BUS: 1]
[2018-06-10 02:38:43] GPU1: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 4]
[2018-06-10 02:38:43] GPU2: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 6]
[2018-06-10 02:38:43] GPU3: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 8]
[2018-06-10 02:38:43] GPU4: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 9]
[2018-06-10 02:38:43] GPU5: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 10]
[2018-06-10 02:38:43] GPU6: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 11]
[2018-06-10 02:38:43] GPU7: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 12]
[2018-06-10 02:38:43] GPU8: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 13]
[2018-06-10 02:38:43] GPU9: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 14]
[2018-06-10 02:38:43] GPU10: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.0][W: 12][T: 2][K: 1][BUS: 15]
[2018-06-10 02:38:43] GPU11: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 16]
[2018-06-10 02:38:43] GPU12: Radeon 550 Series [gfx804] [2048 MB][Intensity 26.7][W: 12][T: 2][K: 1][BUS: 17]
[2018-06-10 02:38:43] ADL is enabled
[2018-06-10 02:38:43] CryptonightV7 mode enabled
[2018-06-10 02:38:44] DevFee pools loaded
[2018-06-10 02:38:44] DevFee pool SET
[2018-06-10 02:38:44] DevFee address SET
[2018-06-10 02:38:44] Starting init of mining threads

ok, now i know its not the new devfee method that is problematic.
But i would suggest to try now a previous version that you know was working good.
Nothing was changed in the new version in the GPU's initialisation process (this is where it hangs), so my guess is something at your side is causing this.

[doktor83]

I keep getting this now on 1.5.9 every now and then.  Nothing changed in settings.
shut_down_miner exception: Resource deadlock avoided

you can ignore this, its not a problem

[doktor83]

I keep getting this now on 1.5.9 every now and then.  Nothing changed in settings.
shut_down_miner exception: Resource deadlock avoided

I also getting this, suddenly all GPU hashing speed 0 h/s.

[2018-06-10 00:41:42] pool_ping: Sent keepalive message to pool
[2018-06-10 00:41:42] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-06-10 00:41:42] json_receive: Pool responded with KEEPALIVED
[2018-06-10 00:42:07] watchdog: GPU0 [BUS: 1] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU1 [BUS: 2] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU2 [BUS: 3] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU3 [BUS: 4] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU4 [BUS: 5] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU5 [BUS: 6] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU6 [BUS: 9] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU7 [BUS: 10] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU8 [BUS: 11] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU9 [BUS: 12] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU10 [BUS: 13] hashing speed is 0 H/S
[2018-06-10 00:42:07] watchdog: GPU11 [BUS: 15] hashing speed is 0 H/S
[2018-06-10 00:42:33] json_receive: {"jsonrpc":"2.0","method":"job","params":{"blob":"0707d1a3f0d805256279b460556b7c15ee3cd01fcdba90cfdadfbdcc0654c667f5a4ae0a9a78530 00000001ab26cc8554f6b2671add6a9c76cbaaa20eb9f31179f7e0d5c9d969a8fd7194303","job_id":"276673124018431","target":"cf8b0000"}}
[2018-06-10 00:42:38] pool_ping: Sent keepalive message to pool
[2018-06-10 00:42:38] json_receive: {"id":1,"jsonrpc":"2.0","error":null,"result":{"status":"KEEPALIVED"}}
[2018-06-10 00:42:38] json_receive: Pool responded with KEEPALIVED
[2018-06-10 00:42:56] shut_down_miner exception: Resource deadlock avoided
[2018-06-10 00:42:56] Stopping miner process

0 hash and shutdown exception are not related. this is just an information that on shutdown process resource clean up avoided a deadlock

[MaxMidnite]

V1.6.0
- Added support for Haven new algo after fork (block 89200)
- Added support for Masari new algo (fast) after fork (block 204000)
- Job timeout default is now 20 minutes
- More logging on miner startup
- Added option 'persistent_memory' in gpu_conf

Hey Dok, thanks for the update. I just started playing with persistent_memory. I know that your notes in CAPS after each option shown in the ReadMe are meant to be purely informational, but you may want to change the TRUE OR FALSE to lower case or use it in an example config to limit potential confusion, since the parser will throw an error if true/false is in CAPS when loading.

Keep up the great work!

yeah i wrote all in caps to draw attention
When i get some time i will change it here and in the docs too.

Do you have any success with per.mem on ?
Using it should allow to go for a bigger intensity setting, on my test card (580 8g) algo normalv7, the best setting was i:54 / w:8 / t:2 i got ~926hs , now i can go to i:60 without problems, and have ~933-936hs

edit: i:63 ~940hs 

What are your card clock settings? CC, MC ?

[doktor83]

I did not know how this works, I thought it was detected automatically.
About the time, I think it depends on how often the pool sets difficulty too high.
This option could be very useful for pools with badly configured vardiff to avoid loosing shares.
So, for me the shortest the best but every one is different
Maybe a command to choose between 1 & 60 secs.

No worries, i managed to make it to be instant, so it will be a next version update.
Also i changed the reconnecting procedure, don't know if it will help you in the miner closing after 4th diff reconnect. (i can't reproduce this)

[doktor83]

What are your card clock settings? CC, MC ?

1150/2100

[popow_sergei]

[2018-06-08 23:07:33] Error CL_OUT_OF_HOST_MEMORY when creating clCreateCommandQueue for DeviceID 0 (Thread 0)
[2018-06-08 23:07:33] Error initing GPU's. Stopping miner process

what caused the error ?

You can read? Miner all wrote to you. Not enogh memory on card. Lower intensity.

1.4.9 works, and 1.5.9 gives the following error
with the same settings

[UnclWish]

[2018-06-08 23:07:33] Error CL_OUT_OF_HOST_MEMORY when creating clCreateCommandQueue for DeviceID 0 (Thread 0)
[2018-06-08 23:07:33] Error initing GPU's. Stopping miner process

what caused the error ?

You can read? Miner all wrote to you. Not enogh memory on card. Lower intensity.

1.4.9 works, and 1.5.9 gives the following error
with the same settings

From 1.4.9 to 1.5.9 was 10 versions. I don't want to find in wich version what was changed. But you must understand that through 10 versions same settings can used by miner different ways. Just try to lower intensity and increase pagefile size to 8Gb * number of videocards.

[Mashy81]

So as of today, can we expect ~500 H/s from a typical Rx 550?

It's a silicone lottery too... 4x Sapphire, 2x Gigabyte, 1x Asus

2 of the 4 Sapphire and the Asus are hit over 510+ H\s I have to get a box fan for it now though no ac or windows in this part of the house, it's about 88-90* in there

How much your intensity and what algo?

thx.

I have gigabyte 550's and I get 530hs from them. I'm still on 1.5.8 so I will update with the new intensity feature and see if I get more

[popow_sergei]

[2018-06-08 23:07:33] Error CL_OUT_OF_HOST_MEMORY when creating clCreateCommandQueue for DeviceID 0 (Thread 0)
[2018-06-08 23:07:33] Error initing GPU's. Stopping miner process

what caused the error ?

You can read? Miner all wrote to you. Not enogh memory on card. Lower intensity.

1.4.9 works, and 1.5.9 gives the following error
with the same settings

From 1.4.9 to 1.5.9 was 10 versions. I don't want to find in wich version what was changed. But you must understand that through 10 versions same settings can used by miner different ways. Just try to lower intensity and increase pagefile size to 8Gb * number of videocards.

that's obviously not the point. installed 8 GB of RAM and 80 GB of virtual 6 cards .

[livada]

how i use this for all card without gpu conf?

"gpu_conf" :
[
{ "id" : 0, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 1, "intensity" : 120, "worksize" : 16, "threads" : 2},
{ "id" : 2, "intensity" : 120, "worksize" : 16, "threads" : 2},

]
}

this is not work

"intensity" : 120,
"worksize" : 16,
"double_threads" : true,

W alwys 8 not 16

@DOCTOR ?

[UnclWish]

[2018-06-08 23:07:33] Error CL_OUT_OF_HOST_MEMORY when creating clCreateCommandQueue for DeviceID 0 (Thread 0)
[2018-06-08 23:07:33] Error initing GPU's. Stopping miner process

what caused the error ?

You can read? Miner all wrote to you. Not enogh memory on card. Lower intensity.

1.4.9 works, and 1.5.9 gives the following error
with the same settings

From 1.4.9 to 1.5.9 was 10 versions. I don't want to find in wich version what was changed. But you must understand that through 10 versions same settings can used by miner different ways. Just try to lower intensity and increase pagefile size to 8Gb * number of videocards.

that's obviously not the point. installed 8 GB of RAM and 80 GB of virtual 6 cards .

What algo? What intensity, worksize and threads?

[duyquang06]

In ver 1.6.0 my 580 4gb final break 1020h/s  v7

[StarLordRammi]

V1.6.0
- Added support for Haven new algo after fork (block 89200)
- Added support for Masari new algo (fast) after fork (block 204000)
- Job timeout default is now 20 minutes
- More logging on miner startup
- Added option 'persistent_memory' in gpu_conf

+ 2 new algos added : 'haven' and 'fast'
So after the fork you can use them like :

"cryptonight_type" : "fast"
"cryptonight_type" : "haven"


+ As some have issues with miner 'just waiting some time' on startup, i added more logging option so we can catch where it hangs, and i can possibly fix that
+ 'persistent_memory' parameter added to gpu_conf, basically what it does is tries to allocate some memory that is normally not available to the GPU. It can increase hashrate in some ocassions, by finding the right intensity and threads setup, but also it can make the gpu crash, so it's up to you to experiment

I am still looking for the cause of random miner crashes (mostly on new 'great' win 1803 update), also for the abnormality that causes higher hashrate on after X runs.

Hi Doc!

as I told you before, you have to take a good look at memory usage in task manager for the first run after reboot and all the next ones.
There is something strange there!
Behaviour is different.

PS. This doesn't happening in other miners.

same here.. sometimes on heavy algo my 3 cards are:
750h/s - 1100h/s - 950 h/s
or
780h/s - 950h/s - 950h/s
or
750h/s - 1050h/s - 920h/s

sometimes restarting the program i get more hasrate, doesnt always work but i dont know why it does that BUT all other miners dont even give me 2.5Kh/s in total where im getting up to 2.8Kh/s with this sometimes

cannot seem to get over 760h/s on my RX 570 4GB Samsung Memory card also

In ver 1.6.0 my 580 4gb final break 1020h/s  v7

what memory and what clocks?