Bitcoin Forum
May 05, 2024, 06:14:20 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 ... 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 [841] 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 ... 1412 »
  Print  
Author Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)  (Read 6589777 times)
iRrromka
Newbie
*
Offline Offline

Activity: 37
Merit: 0


View Profile
October 11, 2017, 12:43:10 PM
 #16801


Earlier this week, I played with them again to squeeze in few more Mh. These are my settings:
-cclock 1140
-mclock 2075
-cvddc 875
-mvddc 875

They average a total of 177.5 now and cards hashes from 29.5 up to 30.0. But the best thing is they now only pull 1035w dual-mining with DCR.

Hi again! And how did you achieved such a great result??? My cards, but on UberMix3.2 are giving me just 172 on dual mining with dcri 25

I'm using custom straps  Wink

Please share this one Smiley. 0.1 ETH from me in case if I'll get 176 on this settings!
1714889660
Hero Member
*
Offline Offline

Posts: 1714889660

View Profile Personal Message (Offline)

Ignore
1714889660
Reply with quote  #2

1714889660
Report to moderator
1714889660
Hero Member
*
Offline Offline

Posts: 1714889660

View Profile Personal Message (Offline)

Ignore
1714889660
Reply with quote  #2

1714889660
Report to moderator
The block chain is the main innovation of Bitcoin. It is the first distributed timestamping system.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714889660
Hero Member
*
Offline Offline

Posts: 1714889660

View Profile Personal Message (Offline)

Ignore
1714889660
Reply with quote  #2

1714889660
Report to moderator
Zorr0
Newbie
*
Offline Offline

Activity: 10
Merit: 0


View Profile
October 11, 2017, 04:57:09 PM
 #16802

Hello everyone. I've been reading this topic for the past few months. Very informative.
I have a problem with blockchain drivers that I couldn't find real solution for.
I've build few rigs and they been working fine with old drivers, but with blockchain driver they are not stable.
Particularly I am trying to fix 2 completely different setups RX 580 (Asus Dual and Sapphire nitro+).
If I lower the voltage even slightly they work but give an error within a day (opencl error).
As I said everything works fine with old drivers (except low hashrate).
kkourmousis
Member
**
Offline Offline

Activity: 119
Merit: 10


View Profile
October 11, 2017, 05:07:17 PM
 #16803

Hey mate,

Since you are reading for such a long time you must have read my post - chain, where (in my final post) I concluded that the blockchain drivers can cause power spikes that cause great instability.

Mr. Claymore said on this:

As I said, I am not happy to see that those problems are getting noticed by more users everyday. For myself, lowering the voltages seems to did the trick but I still experience some freezes now and then (I guess that I didn't lower them enough).
I am hoping that with so many cases around, Mr. Claymore can verify the existence of the problem.
What I would like to hear from Mr. Claymore is if there are any thoughts for a solution and what I would love to hear is an ETA if one exists.

1. I still cannot reproduce this issue, I described what tests I did: https://bitcointalk.org/index.php?topic=1433925.msg21966972#msg21966972
If you have ste-by-step guide how to reproduce this issue - let me know.
2. I'm not sure if it is possible to fix this issue at all, since all these issues are from buggy ADL.

So there you have it.

Reducing voltage indeed does the trick on system freezes.
I myself had to lower my clocks as well with the voltage, sacrificing some hashrate in order to have stability

Buy me a souvlaki:
ETH: 0x22D1C05F89dbe036aABFFEc197949E635903C6FA
BTC: 1FHwEyiCqUTpauGfvPg5czMYoWMKqYGBWx
Call_Me_Bambi
Sr. Member
****
Offline Offline

Activity: 574
Merit: 261


View Profile
October 11, 2017, 06:21:40 PM
 #16804

I love learning all this stuff it’s giving me more knowledge 👍🏻👍🏻👍🏻👐🏼

It's giving me a headache ! Twiddle this up, tweak that down fiddle with this setting mangle that dangle and if you're lucky the risers won't oveheat and catch fire.
Yohow
Member
**
Offline Offline

Activity: 66
Merit: 10


View Profile
October 11, 2017, 07:05:19 PM
 #16805

480 or 580? 4GB or 8GB? I have a 6x RX 480 (8GB) rig and they hashes ~29.1 up to 29.6, ~176MH/s.

we are talking about Asus rx 580 dual 8gb OC with samsung memory.

Oh, okay many thanks for answer. Nice global hashrate Smiley
blackhwk77
Newbie
*
Offline Offline

Activity: 27
Merit: 0


View Profile
October 11, 2017, 07:28:26 PM
 #16806

I keep getting driver crashes that don't trigger the the -r flag in claymore using 10.0 and the AMD blockchain drivers.  I am working on figuring out the crashes but in the meantime is there something else I can do in Win 10 to reboot it maybe based on the log file?  I cheap losing 45 minutes for ethermine to notify me a rig is down.  Thanks
milicic
Full Member
***
Offline Offline

Activity: 180
Merit: 100



View Profile
October 11, 2017, 11:21:23 PM
 #16807

Does anyone know is today the day of Byzantium release on ethereum network? I read it should be released on October 9th. It should reduce blocktime from 30s to 14s (but also reduce reward from 5eth to 3eth per block). It would be increase 24% from current state...

23% to be exact.

It will be deployed when block reaches 4,370,000.
I see news about reducing the block time from 30s to 20s, will see. 14s it is better. But if 14s be true, 3gb 1060 may lose relevance before PoS.

For how long you think rx 470 4gb will be able to mine eth?

Not sure how the block time change will affect it but I believe the issue with size is actually down to the DAG size. From that the approximation is below

The 3GB limit will be hit around mid-April 2018
The 4GB limit will be hit around mid-September 2019


Correction - 3gb cards will be useless by November 2018, not April as per this reddit post.

4GB cards, probably Nov 2019 or later.

Do we need miner update for Byzantium?

Not that I know of - if you're mining with a pool.
Solo miners must update their software.

Werent there stories that 4gb cards will not be able to mine eth after march 2018?
jimmykl
Full Member
***
Offline Offline

Activity: 349
Merit: 102


View Profile
October 12, 2017, 12:15:42 AM
 #16808

Does anyone know is today the day of Byzantium release on ethereum network? I read it should be released on October 9th. It should reduce blocktime from 30s to 14s (but also reduce reward from 5eth to 3eth per block). It would be increase 24% from current state...

23% to be exact.

It will be deployed when block reaches 4,370,000.
I see news about reducing the block time from 30s to 20s, will see. 14s it is better. But if 14s be true, 3gb 1060 may lose relevance before PoS.

For how long you think rx 470 4gb will be able to mine eth?

Not sure how the block time change will affect it but I believe the issue with size is actually down to the DAG size. From that the approximation is below

The 3GB limit will be hit around mid-April 2018
The 4GB limit will be hit around mid-September 2019


Correction - 3gb cards will be useless by November 2018, not April as per this reddit post.

4GB cards, probably Nov 2019 or later.

Do we need miner update for Byzantium?

Not that I know of - if you're mining with a pool.
Solo miners must update their software.

Werent there stories that 4gb cards will not be able to mine eth after march 2018?

There were stories no-one would be able to mine eth after march 2018! ;-)
heavyarms1912
Full Member
***
Offline Offline

Activity: 729
Merit: 114



View Profile
October 12, 2017, 01:04:49 AM
 #16809

How to make claymore work with multigpu and 4gb ram.  Linux works fine but not windows.
EDIT: worked with 16gb of virtual memory.
drak24
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
October 12, 2017, 04:59:52 AM
 #16810

Having an issue with one of my 480 cards giving a low hashrate and I notice the memory/core being stuck at 300mHz. Also, when running claymore the computer gets sluggish, something that never used to happen. I've tried uninstalling/re-installing drivers, changing the page file to 16 or 32, plugging in/out monitors, disabling/enabling in device manager, none of which has worked. Some info on my setup:

2 ATI  Radeon RX 480 8GB with modded bios (samsung memory)
ASRock X370 Taichi (AM4) Motherboard
AMD Ryzen 7
Windows 10 64bit
32GB Ram

This used to work fine but I haven't ran claymore on it since version 9.7's release. Updated to 10, same results on both though. Any suggestions or ideas?


Bael
Jr. Member
*
Offline Offline

Activity: 87
Merit: 2


View Profile
October 12, 2017, 05:03:50 AM
 #16811

Hi

I have a problem with the Claymore boot, for some reason it only detects 3 gigabytes of the 4 that my gpu has

I made a clean installation of win10, using the latest version of Claymore with a rx 580 4GB and everything worked fine, but after some reboot the miner started to fail the boot and close the software.

Checking the logs only recognizes 3 GB of the 4 that should recognize.

Do you know what the problem could be?

Please excuse my bad english, I use a translator and I'm sure it will not be very suitable.

regards
P00P135
Full Member
***
Offline Offline

Activity: 1123
Merit: 136


View Profile
October 12, 2017, 05:45:30 AM
 #16812

Hi

I have a problem with the Claymore boot, for some reason it only detects 3 gigabytes of the 4 that my gpu has

I made a clean installation of win10, using the latest version of Claymore with a rx 580 4GB and everything worked fine, but after some reboot the miner started to fail the boot and close the software.

Checking the logs only recognizes 3 GB of the 4 that should recognize.

Do you know what the problem could be?

Please excuse my bad english, I use a translator and I'm sure it will not be very suitable.

regards

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

Make sure your bat file has this.
informatuss
Newbie
*
Offline Offline

Activity: 36
Merit: 0


View Profile
October 12, 2017, 07:58:30 AM
 #16813

I've got problem with windows freezing when I'm closing claymore after GPU hangs in OpenCL.
I need to do hard reset most of the time.
Same problem with 3 rigs, all windows 10, all RX580.

I had -r 1 for reboot and now I'm using -r -1 -wd 0
still same problem.



Ursul0
Sr. Member
****
Offline Offline

Activity: 857
Merit: 262


View Profile
October 12, 2017, 08:49:56 AM
Last edit: October 12, 2017, 09:04:49 AM by Ursul0
 #16814

I have a problem with the Claymore boot, for some reason it only detects 3 gigabytes of the 4 that my gpu has

I made a clean installation of win10, using the latest version of Claymore with a rx 580 4GB and everything worked fine, but after some reboot the miner started to fail the boot and close the software.


is your win10 a 64 bit install? how much RAM you've got?

in general:
Do proper DDU with reboots (until you see all adapters as MS in device manager), remove all hidden monitors, install drivers & patch, set mem to stock and core to 1080MHz with volts at ~ 0.900ish = all should work. if it doesn't check your physical connections (raisers, raisers power, etc)
Ursul0
Sr. Member
****
Offline Offline

Activity: 857
Merit: 262


View Profile
October 12, 2017, 08:55:49 AM
 #16815

Hi

I have a problem with the Claymore boot, for some reason it only detects 3 gigabytes of the 4 that my gpu has

I made a clean installation of win10, using the latest version of Claymore with a rx 580 4GB and everything worked fine, but after some reboot the miner started to fail the boot and close the software.

Checking the logs only recognizes 3 GB of the 4 that should recognize.

Do you know what the problem could be?

Please excuse my bad english, I use a translator and I'm sure it will not be very suitable.

regards

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

Make sure your bat file has this.

LOL. your gut feeling that these variables have something to do with memory is correct, but detection is not allocation, hence nothing to do with this case here

... also allowing some pointer to be in 32bits may cause the opposite effect.. in theory
coinsaburou
Member
**
Offline Offline

Activity: 84
Merit: 10

INS Ecosystem


View Profile
October 12, 2017, 09:40:49 AM
 #16816

I tried the new version , speed not change.

micax1
Hero Member
*****
Offline Offline

Activity: 708
Merit: 502


View Profile
October 12, 2017, 10:23:01 AM
 #16817

Whoever is still using r9 280x... I need your advice badly!
I have weird 13-26 mh/s ETH 29-58 mh/s LBC fluctuation.
Does not depend on overcloack, power limit, page file > 32gb different PSUs voltage, temperature or whatever, tried all the shit possible!

It`s like >2 times difference! And usually it is  ~13...

Please give me some advice on that behavior(GPU2 & GPU3):

Code:
ETH: 10/12/17-07:25:41 - New job from daggerhashimoto.eu.nicehash.com:3353
ETH - Total Speed: 176.130 Mh/s, Total Shares: 7, Rejected: 1, Time: 00:02
ETH: GPU0 29.026 Mh/s, GPU1 29.718 Mh/s, GPU2 13.242 Mh/s, GPU3 13.198 Mh/s, GPU4 30.733 Mh/s, GPU5 30.656 Mh/s, GPU6 29.557 Mh/s
 LBC - Total Speed: 489.846 Mh/s, Total Shares: 44, Rejected: 0
 LBC: GPU0 83.449 Mh/s, GPU1 85.440 Mh/s, GPU2 29.793 Mh/s, GPU3 29.694 Mh/s, GPU4 88.358 Mh/s, GPU5 88.136 Mh/s, GPU6 84.976 Mh/s
ETH: 10/12/17-07:25:42 - SHARE FOUND - (GPU 5)
ETH: Share accepted (93 ms)!
 LBC: 10/12/17-07:25:44 - SHARE FOUND - (GPU 4)
 LBC: Share accepted (94 ms)!
 LBC: 10/12/17-07:25:46 - SHARE FOUND - (GPU 0)
 LBC: Share accepted (203 ms)!
 LBC: 10/12/17-07:25:47 - New job from lbry.eu.nicehash.com:3356
 LBC: 10/12/17-07:25:51 - SHARE FOUND - (GPU 0)
 LBC: Share accepted (109 ms)!
ETH: 10/12/17-07:25:54 - SHARE FOUND - (GPU 6)
ETH: Share accepted (94 ms)!
 LBC: 10/12/17-07:25:59 - SHARE FOUND - (GPU 1)
 LBC: Share accepted (93 ms)!
 LBC: 10/12/17-07:26:07 - SHARE FOUND - (GPU 5)
 LBC: Share accepted (124 ms)!
GPU0 t=91C fan=82%, GPU1 t=84C fan=82%, GPU2 t=68C fan=35%, GPU3 t=78C fan=45%, GPU4 t=84C fan=82%, GPU5 t=79C fan=83%, GPU6 t=87C fan=81%
 LBC: 10/12/17-07:26:12 - SHARE FOUND - (GPU 4)
 LBC: Share accepted (140 ms)!
ETH: 10/12/17-07:26:14 - New job from daggerhashimoto.eu.nicehash.com:3353
ETH - Total Speed: 177.001 Mh/s, Total Shares: 9, Rejected: 1, Time: 00:03
ETH: GPU0 29.016 Mh/s, GPU1 30.652 Mh/s, GPU2 13.239 Mh/s, GPU3 13.203 Mh/s, GPU4 30.729 Mh/s, GPU5 30.609 Mh/s, GPU6 29.553 Mh/s
 LBC - Total Speed: 492.348 Mh/s, Total Shares: 50, Rejected: 0
 LBC: GPU0 83.420 Mh/s, GPU1 88.124 Mh/s, GPU2 29.786 Mh/s, GPU3 29.707 Mh/s, GPU4 88.346 Mh/s, GPU5 88.001 Mh/s, GPU6 84.964 Mh/s
ETH: 10/12/17-07:26:25 - New job from daggerhashimoto.eu.nicehash.com:3353
ETH - Total Speed: 176.912 Mh/s, Total Shares: 9, Rejected: 1, Time: 00:03
ETH: GPU0 29.006 Mh/s, GPU1 30.617 Mh/s, GPU2 13.243 Mh/s, GPU3 13.202 Mh/s, GPU4 30.690 Mh/s, GPU5 30.641 Mh/s, GPU6 29.515 Mh/s
 LBC - Total Speed: 492.093 Mh/s, Total Shares: 50, Rejected: 0
 LBC: GPU0 83.392 Mh/s, GPU1 88.023 Mh/s, GPU2 29.795 Mh/s, GPU3 29.704 Mh/s, GPU4 88.233 Mh/s, GPU5 88.092 Mh/s, GPU6 84.854 Mh/s
Setting DAG epoch #20...
Setting DAG epoch #20 for GPU1
Setting DAG epoch #20 for GPU6
Setting DAG epoch #20 for GPU0
Setting DAG epoch #20 for GPU5
Setting DAG epoch #20 for GPU4
Setting DAG epoch #20 for GPU2
Setting DAG epoch #20 for GPU3
GPU4 DAG creation time - 3780 ms
Setting DAG epoch #20 for GPU4 done
GPU1 DAG creation time - 3815 ms
Setting DAG epoch #20 for GPU1 done
GPU5 DAG creation time - 3814 ms
Setting DAG epoch #20 for GPU5 done
GPU6 DAG creation time - 3832 ms
Setting DAG epoch #20 for GPU6 done
GPU0 DAG creation time - 3870 ms
Setting DAG epoch #20 for GPU0 done
ETH: 10/12/17-07:26:30 - New job from daggerhashimoto.eu.nicehash.com:3353
ETH - Total Speed: 172.065 Mh/s, Total Shares: 9, Rejected: 1, Time: 00:03
ETH: GPU0 27.462 Mh/s, GPU1 29.873 Mh/s, GPU2 13.242 Mh/s, GPU3 13.192 Mh/s, GPU4 29.840 Mh/s, GPU5 29.724 Mh/s, GPU6 28.732 Mh/s
 LBC - Total Speed: 478.161 Mh/s, Total Shares: 50, Rejected: 0
 LBC: GPU0 78.954 Mh/s, GPU1 85.884 Mh/s, GPU2 29.794 Mh/s, GPU3 29.681 Mh/s, GPU4 85.790 Mh/s, GPU5 85.455 Mh/s, GPU6 82.603 Mh/s
GPU2 DAG creation time - 4985 ms
Setting DAG epoch #20 for GPU2 done
GPU3 DAG creation time - 5050 ms
Setting DAG epoch #20 for GPU3 done
 LBC: 10/12/17-07:26:34 - SHARE FOUND - (GPU 4)
 LBC: Share accepted (94 ms)!
ETH: 10/12/17-07:26:37 - SHARE FOUND - (GPU 2)
ETH: Share accepted (94 ms)!
GPU0 t=92C fan=82%, GPU1 t=84C fan=82%, GPU2 t=72C fan=39%, GPU3 t=84C fan=52%, GPU4 t=85C fan=82%, GPU5 t=79C fan=83%, GPU6 t=87C fan=81%
 LBC: 10/12/17-07:26:42 - New job from lbry.eu.nicehash.com:3356
 LBC: 10/12/17-07:26:45 - New job from lbry.eu.nicehash.com:3356
ETH: 10/12/17-07:26:46 - SHARE FOUND - (GPU 6)
ETH: Share accepted (94 ms)!
ETH: 10/12/17-07:26:49 - SHARE FOUND - (GPU 6)
ETH: Share accepted (94 ms)!

GPU #0: Hawaii, 4096 MB available, 40 compute units
GPU #1: Hawaii, 4096 MB available, 40 compute units
GPU #2: Tahiti, 3072 MB available, 32 compute units
GPU #3: Tahiti, 3072 MB available, 32 compute units
GPU #4: Hawaii, 4096 MB available, 44 compute units
GPU #5: Hawaii, 4096 MB available, 40 compute units
GPU #6: Hawaii, 4096 MB available, 40 compute units
ETH - Total Speed: 203.846 Mh/s, Total Shares: 12(0+0+3+0+0+3+6), Rejected: 1, Time: 00:03
ETH: GPU0 29.130 Mh/s, GPU1 30.926 Mh/s, GPU2 25.995 Mh/s, GPU3 25.968 Mh/s, GPU4 31.099 Mh/s, GPU5 30.890 Mh/s, GPU6 29.838 Mh/s
 LBC - Total Speed: 553.577 Mh/s, Total Shares: 51(8+10+2+0+15+8+8), Rejected: 0
 LBC: GPU0 83.748 Mh/s, GPU1 88.912 Mh/s, GPU2 58.488 Mh/s, GPU3 58.427 Mh/s, GPU4 89.410 Mh/s, GPU5 88.808 Mh/s, GPU6 85.784 Mh/s
Incorrect ETH shares: none
1 minute average ETH total speed: 189.878 Mh/s
Pool switches: ETH - 0, LBC - 0
Current ETH share target: 0x00000001fffe0000 (diff: 2147MH), epoch 20(1.16GB)
Current LBC share target: 0x00000000ffff0000 (diff: 4295MH)
GPU0 t=93C fan=82%, GPU1 t=84C fan=82%, GPU2 t=73C fan=40%, GPU3 t=86C fan=61%, GPU4 t=85C fan=82%, GPU5 t=80C fan=83%, GPU6 t=87C fan=82%












 LBC: 10/12/17-07:29:28 - New job from lbry.eu.nicehash.com:3356
 LBC: 10/12/17-07:29:40 - SHARE FOUND - (GPU 6)
 LBC: Share accepted (93 ms)!
ETH: 10/12/17-07:29:46 - New job from daggerhashimoto.eu.nicehash.com:3353
ETH - Total Speed: 199.601 Mh/s, Total Shares: 27, Rejected: 3, Time: 00:06
ETH: GPU0 26.587 Mh/s, GPU1 30.982 Mh/s, GPU2 25.978 Mh/s, GPU3 24.416 Mh/s, GPU4 30.970 Mh/s, GPU5 30.912 Mh/s, GPU6 29.756 Mh/s
 LBC - Total Speed: 542.354 Mh/s, Total Shares: 71, Rejected: 0
 LBC: GPU0 76.436 Mh/s, GPU1 89.074 Mh/s, GPU2 58.451 Mh/s, GPU3 54.936 Mh/s, GPU4 89.038 Mh/s, GPU5 88.871 Mh/s, GPU6 85.548 Mh/s
Setting DAG epoch #145...
Setting DAG epoch #145 for GPU2
Setting DAG epoch #145 for GPU6
Setting DAG epoch #145 for GPU3
Setting DAG epoch #145 for GPU1
Setting DAG epoch #145 for GPU5
Setting DAG epoch #145 for GPU4
Setting DAG epoch #145 for GPU0
GPU0 t=90C fan=83%, GPU1 t=86C fan=83%, GPU2 t=84C fan=57%, GPU3 t=87C fan=67%, GPU4 t=87C fan=83%, GPU5 t=80C fan=84%, GPU6 t=87C fan=82%
GPU4 DAG creation time - 7043 ms
Setting DAG epoch #145 for GPU4 done
GPU1 DAG creation time - 7104 ms
Setting DAG epoch #145 for GPU1 done
GPU5 DAG creation time - 7104 ms
Setting DAG epoch #145 for GPU5 done
GPU0 DAG creation time - 7146 ms
Setting DAG epoch #145 for GPU0 done
GPU6 DAG creation time - 7139 ms
Setting DAG epoch #145 for GPU6 done
ETH: 10/12/17-07:29:56 - New job from daggerhashimoto.eu.nicehash.com:3353
ETH - Total Speed: 150.259 Mh/s, Total Shares: 27, Rejected: 3, Time: 00:07
ETH: GPU0 28.973 Mh/s, GPU1 30.583 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 30.693 Mh/s, GPU5 30.542 Mh/s, GPU6 29.468 Mh/s
 LBC - Total Speed: 431.992 Mh/s, Total Shares: 71, Rejected: 0
 LBC: GPU0 83.296 Mh/s, GPU1 87.927 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 88.241 Mh/s, GPU5 87.808 Mh/s, GPU6 84.720 Mh/s
GPU2 DAG creation time - 9173 ms
Setting DAG epoch #145 for GPU2 done
GPU3 DAG creation time - 9274 ms
Setting DAG epoch #145 for GPU3 done
ETH: 10/12/17-07:30:05 - New job from daggerhashimoto.eu.nicehash.com:3353
ETH - Total Speed: 175.382 Mh/s, Total Shares: 27, Rejected: 3, Time: 00:07
ETH: GPU0 28.990 Mh/s, GPU1 30.457 Mh/s, GPU2 13.243 Mh/s, GPU3 11.957 Mh/s, GPU4 30.671 Mh/s, GPU5 30.545 Mh/s, GPU6 29.518 Mh/s
 LBC - Total Speed: 488.468 Mh/s, Total Shares: 71, Rejected: 0
 LBC: GPU0 83.346 Mh/s, GPU1 87.563 Mh/s, GPU2 29.797 Mh/s, GPU3 26.904 Mh/s, GPU4 88.179 Mh/s, GPU5 87.815 Mh/s, GPU6 84.864 Mh/s
ETH: 10/12/17-07:30:08 - SHARE FOUND - (GPU 0)
ETH: Share accepted (78 ms)!
 LBC: 10/12/17-07:30:09 - SHARE FOUND - (GPU 4)
 LBC: Share accepted (109 ms)!
 LBC: 10/12/17-07:30:12 - SHARE FOUND - (GPU 1)
 LBC: Share accepted (94 ms)!
ETH: 10/12/17-07:30:15 - New job from daggerhashimoto.eu.nicehash.com:3353
ETH - Total Speed: 172.323 Mh/s, Total Shares: 28, Rejected: 3, Time: 00:07
ETH: GPU0 26.254 Mh/s, GPU1 30.336 Mh/s, GPU2 13.199 Mh/s, GPU3 11.953 Mh/s, GPU4 30.621 Mh/s, GPU5 30.456 Mh/s, GPU6 29.505 Mh/s
 LBC - Total Speed: 479.706 Mh/s, Total Shares: 73, Rejected: 0
 LBC: GPU0 75.480 Mh/s, GPU1 87.214 Mh/s, GPU2 29.696 Mh/s, GPU3 26.895 Mh/s, GPU4 88.035 Mh/s, GPU5 87.560 Mh/s, GPU6 84.826 Mh/s
 LBC: 10/12/17-07:30:21 - SHARE FOUND - (GPU 5)
 LBC: Share accepted (94 ms)!


Thanks!
asdpof
Newbie
*
Offline Offline

Activity: 33
Merit: 0


View Profile
October 12, 2017, 01:01:56 PM
 #16818

I tried the new version , speed not change.

By the release description i would guess the speed increase in the new versin is only for vega
ciprianpt
Jr. Member
*
Offline Offline

Activity: 127
Merit: 8


View Profile WWW
October 12, 2017, 01:13:02 PM
 #16819

I've got problem with windows freezing when I'm closing claymore after GPU hangs in OpenCL.
I need to do hard reset most of the time.
Same problem with 3 rigs, all windows 10, all RX580.

I had -r 1 for reboot and now I'm using -r -1 -wd 0
still same problem.


Have you also created the reboot.bat file ?

https://1stMiningRig.com - Just Another Mining Blog Smiley
ingyenfrag
Newbie
*
Offline Offline

Activity: 84
Merit: 0


View Profile
October 12, 2017, 02:30:50 PM
 #16820

I tried the new version , speed not change.

By the release description i would guess the speed increase in the new versin is only for vega

What new version? I see the september 02 version as the latest.
Pages: « 1 ... 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 [841] 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 ... 1412 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!