YukiSG
Newbie
Offline
Activity: 4
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 09, 2018, 10:01:38 PM |
|
Kill windows 1803 update with fire: Here's what we have so far about win 1803 update effect on me, after applying all known fixes:
I can't get all 13 gpus to work above 900 h/s each, a very low intensity seems to work. I used to do stable 1040 h/s. Hash rate fluctuates badly. GPU-Z trick does NOT work.
tldr, Windows 1803 update is utter bullshit. I failed to prevent it from installing, so it's my fault. I'm thinking of leaving to a miner Os, I hope SRBMiner adds linux compatibility.
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) 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 You literally copy and pasted from laptomags article lmao. Gtfo... 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.
|
|
|
|
wudafuxup
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 09, 2018, 10:06:10 PM |
|
Kill windows 1803 update with fire: Here's what we have so far about win 1803 update effect on me, after applying all known fixes:
I can't get all 13 gpus to work above 900 h/s each, a very low intensity seems to work. I used to do stable 1040 h/s. Hash rate fluctuates badly. GPU-Z trick does NOT work.
tldr, Windows 1803 update is utter bullshit. I failed to prevent it from installing, so it's my fault. I'm thinking of leaving to a miner Os, I hope SRBMiner adds linux compatibility.
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) 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 You literally copy and pasted from laptomags article lmao. Gtfo... 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. ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2F0Oxrzn1.png&t=665&c=ZACFR1gjPq07mg) 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 like crypto
|
|
|
ipe4enko
Newbie
Offline
Activity: 34
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 09, 2018, 11:43:36 PM |
|
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
|
|
|
|
YukiSG
Newbie
Offline
Activity: 4
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 01:07:51 AM |
|
Kill windows 1803 update with fire: Here's what we have so far about win 1803 update effect on me, after applying all known fixes:
I can't get all 13 gpus to work above 900 h/s each, a very low intensity seems to work. I used to do stable 1040 h/s. Hash rate fluctuates badly. GPU-Z trick does NOT work.
tldr, Windows 1803 update is utter bullshit. I failed to prevent it from installing, so it's my fault. I'm thinking of leaving to a miner Os, I hope SRBMiner adds linux compatibility.
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) 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 You literally copy and pasted from laptomags article lmao. Gtfo... 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. https://i.imgur.com/0Oxrzn1.pngYou 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. 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.
|
|
|
|
heavyarms1912
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 03:03:40 AM |
|
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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 03:14:20 AM |
|
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
Newbie
Offline
Activity: 37
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 03:19:36 AM |
|
So as of today, can we expect ~500 H/s from a typical Rx 550?
http://i64.tinypic.com/2cyqsu0.pngIt'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
Newbie
Offline
Activity: 129
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 03:45:28 AM |
|
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 ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Maybe a command to choose between 1 & 60 secs. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif)
|
|
|
|
lebuawu2
Jr. Member
Offline
Activity: 176
Merit: 2
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 04:42:01 AM |
|
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
Newbie
Offline
Activity: 41
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 04:52:59 AM |
|
So as of today, can we expect ~500 H/s from a typical Rx 550?
http://i64.tinypic.com/2cyqsu0.pngIt'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 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 06:06:48 AM Last edit: June 10, 2018, 08:37:05 AM by 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 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 06:09:48 AM |
|
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 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 06:12:56 AM |
|
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 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|
MaxMidnite
Newbie
Offline
Activity: 143
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 08:06:10 AM |
|
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 ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) 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 ![Cool](https://bitcointalk.org/Smileys/default/cool.gif) What are your card clock settings? CC, MC ?
|
|
|
|
doktor83 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 08:40:29 AM |
|
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 ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Maybe a command to choose between 1 & 60 secs. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) 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 (OP)
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 08:41:10 AM |
|
What are your card clock settings? CC, MC ?
1150/2100
|
|
|
|
popow_sergei
Newbie
Offline
Activity: 26
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 08:47:14 AM |
|
[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
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 09:22:13 AM |
|
[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
Jr. Member
Offline
Activity: 225
Merit: 1
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 09:31:44 AM |
|
So as of today, can we expect ~500 H/s from a typical Rx 550?
![](https://ip.bitcointalk.org/?u=http%3A%2F%2Fi64.tinypic.com%2F2cyqsu0.png&t=665&c=XSU83c6haajZcw) 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
Newbie
Offline
Activity: 26
Merit: 0
|
![](https://bitcointalk.org/Themes/custom1/images/post/xx.gif) |
June 10, 2018, 09:49:19 AM |
|
[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 .
|
|
|
|
|