corsaro
Legendary
 Offline
Activity: 1400
Merit: 1000
|
 |
June 16, 2014, 11:37:32 AM |
|
sorry, but the latest nis5 release with double hashrate is very, very unstable on my windows machines... everything crashes after 20-50 minutes of work...
Maybe you need to lower clocks of your graphic cards. nothing to do... exe is very unstable i have 3 rigs, and all 3 rigs returned back to old sgminer-talkcoin Weird I don't have such problems. How many hours is running continously your rig ? |
|
|
|
|
|
|
|
|
|
|
|
|
|
In order to get the maximum amount of activity points possible, you just need to post once per day on average. Skipping days is OK as long as you maintain the average.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
|
|
|
|
|
amacar
|
|
June 16, 2014, 11:47:16 AM |
|
sorry, but the latest nis5 release with double hashrate is very, very unstable on my windows machines... everything crashes after 20-50 minutes of work...
Maybe you need to lower clocks of your graphic cards. nothing to do... exe is very unstable i have 3 rigs, and all 3 rigs returned back to old sgminer-talkcoin Weird I don't have such problems. How many hours is running continously your rig ? Over night, so I suppose about 10 hours. |
|
|
|
|
corsaro
Legendary
Offline
Activity: 1400
Merit: 1000
|
|
June 16, 2014, 12:16:22 PM |
|
sorry, but the latest nis5 release with double hashrate is very, very unstable on my windows machines... everything crashes after 20-50 minutes of work...
Maybe you need to lower clocks of your graphic cards. nothing to do... exe is very unstable i have 3 rigs, and all 3 rigs returned back to old sgminer-talkcoin Weird I don't have such problems. How many hours is running continously your rig ? Over night, so I suppose about 10 hours. my six R9-290 do not want to run more then 30-50 min using this optimized nist5 sgminer.exe. I tried lowering gpu-memclock, gpu-engine, intensity but it was not useful. I'll try to recompile a new exe on my windows PC and test it again |
|
|
|
|
restless
Legendary
Offline
Activity: 1151
Merit: 1001
|
|
June 16, 2014, 12:18:43 PM |
|
try running without ANY arguements. Just the pools
ANother option - use CGWatcher. Works like charm, set it to restart miner if no shares for 1min or working devices are lower than X.
|
|
|
|
|
|
deathmul
|
|
June 16, 2014, 12:20:01 PM |
|
When Poloniex will add TAC? We are on first place from couple of days
|
|
|
|
|
atleticofa
|
|
June 16, 2014, 12:24:38 PM |
|
When Poloniex will add TAC? We are on first place from couple of days
This week for sure |
|
|
|
|
corsaro
Legendary
Offline
Activity: 1400
Merit: 1000
|
|
June 16, 2014, 12:40:54 PM |
|
try running without ANY arguements. Just the pools
ANother option - use CGWatcher. Works like charm, set it to restart miner if no shares for 1min or working devices are lower than X.
I strongly suspect it hangs when I put --thread-concurrency higher then 8192 Now I am testing again but setting manually --thread-concurrency 8192 to see if my R9-290 are more stable... I'll let you know |
|
|
|
|
Ignition75
Sr. Member
Offline
Activity: 462
Merit: 250
www.dashpay.io
|
|
June 16, 2014, 12:49:34 PM |
|
sorry, but the latest nis5 release with double hashrate is very, very unstable on my windows machines... everything crashes after 20-50 minutes of work...
Maybe you need to lower clocks of your graphic cards. nothing to do... exe is very unstable i have 3 rigs, and all 3 rigs returned back to old sgminer-talkcoin Weird I don't have such problems. How many hours is running continously your rig ? Over night, so I suppose about 10 hours. my six R9-290 do not want to run more then 30-50 min using this optimized nist5 sgminer.exe. I tried lowering gpu-memclock, gpu-engine, intensity but it was not useful. I'll try to recompile a new exe on my windows PC and test it again I had the same issue, my 270s and 280s are fine, the 290s were rebooting using the same core and memclock settings from the old miner... I was using the official miner so I was only playing with intensity. I got one of my 290 rigs stable by bringing clock back to factory spec and lowering intensity to 19. I haven't touched TC or threads or anything yet, I will have a play soon and let you know how I get on... |
The new generation have arrived and they brought their own currency...
|
|
|
corsaro
Legendary
Offline
Activity: 1400
Merit: 1000
|
|
June 16, 2014, 01:01:23 PM |
|
sorry, but the latest nis5 release with double hashrate is very, very unstable on my windows machines... everything crashes after 20-50 minutes of work...
Maybe you need to lower clocks of your graphic cards. nothing to do... exe is very unstable i have 3 rigs, and all 3 rigs returned back to old sgminer-talkcoin Weird I don't have such problems. How many hours is running continously your rig ? Over night, so I suppose about 10 hours. my six R9-290 do not want to run more then 30-50 min using this optimized nist5 sgminer.exe. I tried lowering gpu-memclock, gpu-engine, intensity but it was not useful. I'll try to recompile a new exe on my windows PC and test it again I had the same issue, my 270s and 280s are fine, the 290s were rebooting using the same core and memclock settings from the old miner... I was using the official miner so I was only playing with intensity. I got one of my 290 rigs stable by bringing clock back to factory spec and lowering intensity to 19. I haven't touched TC or threads or anything yet, I will have a play soon and let you know how I get on... yes, R9-290 and R9-290X are more difficult to be set. I am testing with --thread-concurrency 8192 and --gpu-memclock 1250 directly inside sgminer.conf and it seems more stable then before... more tests will come out in the following hours... I'll keep you informed |
|
|
|
|
corsaro
Legendary
Offline
Activity: 1400
Merit: 1000
|
|
June 16, 2014, 01:11:00 PM |
|
|
|
|
|
|
|
AizenSou
|
|
June 16, 2014, 01:14:36 PM |
|
yes, R9-290 and R9-290X are more difficult to be set.
I am testing with --thread-concurrency 8192 and --gpu-memclock 1250 directly inside sgminer.conf and it seems more stable then before... more tests will come out in the following hours...
I'll keep you informed
thread-concurrency doesn't affect much NIST5-performance (check the source code) I would not touch it. Play with thread-concurrency only bring you 1% more in my experience. Important is delete all the *.bin file in sgminer-nist5 and set proper clock, intensity. |
|
|
|
|
corsaro
Legendary
Offline
Activity: 1400
Merit: 1000
|
|
June 16, 2014, 01:21:48 PM |
|
yes, R9-290 and R9-290X are more difficult to be set.
I am testing with --thread-concurrency 8192 and --gpu-memclock 1250 directly inside sgminer.conf and it seems more stable then before... more tests will come out in the following hours...
I'll keep you informed
thread-concurrency doesn't affect much NIST5-performance (check the source code) I would not touch it. Play with thread-concurrency only bring you 1% more in my experience. Important is delete all the *.bin file in sgminer-nist5 and set proper clock, intensity. Ok... more tests to come out... |
|
|
|
|
corsaro
Legendary
Offline
Activity: 1400
Merit: 1000
|
|
June 16, 2014, 01:30:19 PM |
|
OK, compiled successfully on ubuntu 12.04 64 bit. and working fine with HD7970 at doubled hashrate with old drivers  git clone https://github.com/djm34/sph-sgminer_x11modcd sph-sgminer_x11mod autoreconf -i CFLAGS="-O2 -Wall -march=native" ./configure make |
|
|
|
|
corsaro
Legendary
Offline
Activity: 1400
Merit: 1000
|
|
June 16, 2014, 01:36:32 PM |
|
yes, R9-290 and R9-290X are more difficult to be set.
I am testing with --thread-concurrency 8192 and --gpu-memclock 1250 directly inside sgminer.conf and it seems more stable then before... more tests will come out in the following hours...
I'll keep you informed
thread-concurrency doesn't affect much NIST5-performance (check the source code) I would not touch it. Play with thread-concurrency only bring you 1% more in my experience. Important is delete all the *.bin file in sgminer-nist5 and set proper clock, intensity. anyway, now I am running fine sph-sgminer_nist5 on my windows machines with R9-290 and R9-290X at double hashrate... the secret is to set --thread-concurrency 8192 and gpu memclock at lowest possible value (--gpu-memclock 1250 or --gpu-memclock 1300) on some R9-290 lowest gpu-memclock is 1250 and on other R9-290X it is 1300 |
|
|
|
|
Ignition75
Sr. Member
Offline
Activity: 462
Merit: 250
www.dashpay.io
|
|
June 16, 2014, 01:52:50 PM |
|
yes, R9-290 and R9-290X are more difficult to be set.
I am testing with --thread-concurrency 8192 and --gpu-memclock 1250 directly inside sgminer.conf and it seems more stable then before... more tests will come out in the following hours...
I'll keep you informed
thread-concurrency doesn't affect much NIST5-performance (check the source code) I would not touch it. Play with thread-concurrency only bring you 1% more in my experience. Important is delete all the *.bin file in sgminer-nist5 and set proper clock, intensity. anyway, now I am running fine sph-sgminer_nist5 on my windows machines with R9-290 and R9-290X at double hashrate... the secret is to set --thread-concurrency 8192 and gpu memclock at lowest possible value (--gpu-memclock 1250 or --gpu-memclock 1300) on some R9-290 lowest gpu-memclock is 1250 and on other R9-290X it is 1300 I'm running memclock at 650 on all rigs, no difference in speed and saves a little power... |
The new generation have arrived and they brought their own currency...
|
|
|
|
atleticofa
|
|
June 16, 2014, 02:37:48 PM |
|
OK, compiled successfully on ubuntu 12.04 64 bit. and working fine with HD7970 at doubled hashrate with old drivers git clone https://github.com/djm34/sph-sgminer_x11modcd sph-sgminer_x11mod autoreconf -i CFLAGS="-O2 -Wall -march=native" ./configure make I'm getting just 6mhs for HD7970 with the last day miner and old drivers. It would be possible this new miner for windows? |
|
|
|
|
|
karimdr2
|
|
June 16, 2014, 02:38:08 PM |
|
yes, R9-290 and R9-290X are more difficult to be set.
I am testing with --thread-concurrency 8192 and --gpu-memclock 1250 directly inside sgminer.conf and it seems more stable then before... more tests will come out in the following hours...
I'll keep you informed
thread-concurrency doesn't affect much NIST5-performance (check the source code) I would not touch it. Play with thread-concurrency only bring you 1% more in my experience. Important is delete all the *.bin file in sgminer-nist5 and set proper clock, intensity. anyway, now I am running fine sph-sgminer_nist5 on my windows machines with R9-290 and R9-290X at double hashrate... the secret is to set --thread-concurrency 8192 and gpu memclock at lowest possible value (--gpu-memclock 1250 or --gpu-memclock 1300) on some R9-290 lowest gpu-memclock is 1250 and on other R9-290X it is 1300 I'm running memclock at 650 on all rigs, no difference in speed and saves a little power... At 650 your gpu run at the stock clock ! You can check it on Sgminer console ! |
|
|
|
Ignition75
Sr. Member
Offline
Activity: 462
Merit: 250
www.dashpay.io
|
|
June 16, 2014, 02:47:08 PM |
|
Wallet manager at Poloniex just confirmed TAC will go on Polo today...
|
The new generation have arrived and they brought their own currency...
|
|
|
corsaro
Legendary
Offline
Activity: 1400
Merit: 1000
|
|
June 16, 2014, 03:10:39 PM |
|
yes, R9-290 and R9-290X are more difficult to be set.
I am testing with --thread-concurrency 8192 and --gpu-memclock 1250 directly inside sgminer.conf and it seems more stable then before... more tests will come out in the following hours...
I'll keep you informed
thread-concurrency doesn't affect much NIST5-performance (check the source code) I would not touch it. Play with thread-concurrency only bring you 1% more in my experience. Important is delete all the *.bin file in sgminer-nist5 and set proper clock, intensity. anyway, now I am running fine sph-sgminer_nist5 on my windows machines with R9-290 and R9-290X at double hashrate... the secret is to set --thread-concurrency 8192 and gpu memclock at lowest possible value (--gpu-memclock 1250 or --gpu-memclock 1300) on some R9-290 lowest gpu-memclock is 1250 and on other R9-290X it is 1300 I'm running memclock at 650 on all rigs, no difference in speed and saves a little power... At 650 your gpu run at the stock clock ! You can check it on Sgminer console ! none of my R9-290 goes under 1300 Mhz as memclock. I can set 1300 as minimum. A couple of them can be set at 1250 |
|
|
|
|
djm34
Legendary
Offline
Activity: 1400
Merit: 1050
|
|
June 16, 2014, 03:17:32 PM |
|
yes, R9-290 and R9-290X are more difficult to be set.
I am testing with --thread-concurrency 8192 and --gpu-memclock 1250 directly inside sgminer.conf and it seems more stable then before... more tests will come out in the following hours...
I'll keep you informed
thread-concurrency doesn't affect much NIST5-performance (check the source code) I would not touch it. Play with thread-concurrency only bring you 1% more in my experience. Important is delete all the *.bin file in sgminer-nist5 and set proper clock, intensity. anyway, now I am running fine sph-sgminer_nist5 on my windows machines with R9-290 and R9-290X at double hashrate... the secret is to set --thread-concurrency 8192 and gpu memclock at lowest possible value (--gpu-memclock 1250 or --gpu-memclock 1300) on some R9-290 lowest gpu-memclock is 1250 and on other R9-290X it is 1300 I'm running memclock at 650 on all rigs, no difference in speed and saves a little power... At 650 your gpu run at the stock clock ! You can check it on Sgminer console ! none of my R9-290 goes under 1300 Mhz as memclock. I can set 1300 as minimum. A couple of them can be set at 1250 there is some sort of a bug with msi afterburner /amd drivers (kill msi) then restart it should give the possibility to change the clock (or you have to restart the computer) |
djm34 facebook pageBTC: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze Pledge for neoscrypt ccminer to that address: 16UoC4DmTz2pvhFvcfTQrzkPTrXkWijzXw
|
|
|
|
