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

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.

How much your intensity and what algo?

thx.

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

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.

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

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?

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

Rolling back wont work after  10 DAYS not fyi.

As for the steps, Its simply being typed out and i can swear i aint doing the copy and pasting shit. If you are unhappy that included the donation part you can tell me off nicely. i ain't here to hi-jack crap or whatever else. just simply trying to help out while asking people if they found it helpful they could give me some cookies/brownies.

Why get to mad over my post? or are you simply just out here to troll whoever just joined and stuff? While posting this im still in midst of trying out different configs for the miner to make the best out of it.

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

You copy and pasted the rolling back section from a 2017 article lmao. Rolling back won't work after 7 days of updating. You didn't find shit lmao. The ATIFlash on 1803 thing was already discussed on reddit and techpowerup lmao. Get out of here with your money begging.

I copy and pasted? bro are you alright? i spent some time replying to that post and u said i copy pasted. and best of all i dont think they did mentioned anything about ATIFlasher issues with 1803. i find out about that myself. besides, i work as a System Administrator. this kind of shit i have to know else i would be out of job duh.

Aside from that, you reminded my to add something into the post.

You literally copy and pasted from laptomags article on how to roll back lmao. Gtfo...

You also forgot to mention rolling back won't work after 7 days of the update.

For those who are affected by Windows 10 1803 updates.

Fix is here no worries.

Roll back to previous version.
1.To get started, click Start and then Settings.
2.Click on Update & security.
3.In the sidebar, choose Recovery.
4.Click the Get Started link under Go back to the previous version of Windows 10.
5.Select why you'd like to go back to a previous build and click Next. ...
6.Click Next once more after reading the prompt
7. Wait for it to finish rolling back and reboot.

Part 2 of the fix. (To disable windows update)

Optional: Its actually better to update to latest AMD Adrenaline Driver as it actually performs better than Blockchain Beta Driver FYI.

1. Windows Button + R and run services.msc
2. type in "Services.msc" Without the quote.
3. Scroll down to Windows Update and right click it and select Properties.
4. Change Startup Type to Disabled and click Stop and go to Recovery tab and on First Failure change it to "Take no Action"
5. Click apply and followed by OK.
6. Reboot PC and ur windows update is disable ( you can re-enable it in the future by reversing step 4 in the future when they finally Microsoft fix their own shit)
7. Reinstall any programs you have installed AFTER the 1803 update as they will be missing.

The benefit of rolling back also fixes AtiFlash as in Version 1803 u are unable to use ATIFlasher due to compatibility issues.

Like my work/Discovery?

Donate me to help me clear my debt.

ETH: 0x052898045e73a56691eca5210EE6a2Aa15397295

Edit. Added step 7 into part 2.

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

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

did you test this on one card, a rig, or multiple rigs? All behave same?
We are talking about memory usage for the miner, not the gpu (as you say task manager).
On start miner 'eats' more memory, after that it slowly decreases over time.

how persistent_memory works?

Hi all
I am using this miner for few months already and wanted to share my results. I have rig with 3x XFX RX 570 Black Edition and 2x Sapphire RX 580 Nitro+ all 4GB version.
For 570 clock are 1220/890 and 2030/905
For 580 clock are 1230/885 and 2130/890 and full rig consumption from the wall is around 530W.
With all versions of the miner I was getting around same speed (cryptonight v7 algo) with I58-W8-T2
570 - 953 H/s
580 - 1008 H/s
Total around 4873 H/s

Today I try new version 1.6.0 with persistent_memory and manage to increase intensity to 59 (with 60 miner crashed) and get this results
570 - 956 H/s
580 - 1010 H/s
Total around 4888 H/s
Not a big increase but it is better

Hvala doktore za odlican miner 

hi brother i'm getting interminent crash with 1.60 on some of my machines? miner doesn't start up past

GPU MAX ALLOC

I have 1.5.2 files on them still and those are running fine, any ideas?


UPDATE: nevermind, i figured it out. disable windows defender on all your miners and make sure you make an exception for srbminer. if it's already flagged, allow the app.

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.