|
platinum4
|
 |
July 05, 2014, 11:56:50 PM |
|
I've been trying to get this to run stable for days now, without success. It's hashing and switching fine, but after a couple of hours my GPU goes DEAD. It has never run more than about 5-6 hours straight. I never had a DEAD card before and if I use another miner it runs stable for days, so there's nothing wrong with my card (I rechecked). I don't know what else to try, so hopefully someone else can help me! Here's the config (Asus 280x DC2T):
Yep, not til hamsi came on the scene. Shit will trash some cards at non-stock specs. |
|
|
|
|
|
|
|
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
|
Meticulous7
Newbie
 Offline
Activity: 47
Merit: 0
|
|
July 06, 2014, 12:05:16 AM |
|
That was the ticket, Badman! Thank you so much. Seeing some pretty large gains now that I have the new build up and running. Went from 1.4MH/s per card to just over 2MH/s per card! 1.2 MH/s improvement overall! I am very stoked  . Now I'm wondering if there may still be room for improvement  Anyone else running R9 270s out there? And if so what kind of rates are you getting? |
|
|
|
|
cgladue
Member
Offline
Activity: 97
Merit: 10
|
|
July 06, 2014, 02:10:39 AM |
|
That was the ticket, Badman! Thank you so much. Seeing some pretty large gains now that I have the new build up and running. Went from 1.4MH/s per card to just over 2MH/s per card! 1.2 MH/s improvement overall! I am very stoked . Now I'm wondering if there may still be room for improvement Anyone else running R9 270s out there? And if so what kind of rates are you getting? 4 x R9 270X's here getting: Scrypt - 1.7 MH/s nScrypt - 800 kH/s x11 - 10.2 mH/s x13 - 7.5 mH/s x15 - 6.4 mH/s nist5 - 30.8 mH/s Keccak - 900 mH/s Divide numbers above by 4 to get individual card speeds what are you getting ? |
|
|
|
|
BrewCrewFan
|
|
July 06, 2014, 02:19:15 AM
Last edit: July 06, 2014, 03:21:26 AM by BrewCrewFan |
|
That was the ticket, Badman! Thank you so much. Seeing some pretty large gains now that I have the new build up and running. Went from 1.4MH/s per card to just over 2MH/s per card! 1.2 MH/s improvement overall! I am very stoked . Now I'm wondering if there may still be room for improvement Anyone else running R9 270s out there? And if so what kind of rates are you getting? 4 x R9 270X's here getting: Scrypt - 1.7 MH/s nScrypt - 800 kH/s x11 - 10.2 mH/s x13 - 7.5 mH/s x15 - 6.4 mH/s nist5 - 30.8 mH/s Keccak - 900 mH/s Divide numbers above by 4 to get individual card speeds what are you getting ? At least playing around with what I think are overclocks I can get high 2.8 MH per card on x11.... With this it seems like moving the mem speed does little and the GPU clocks seem to bump it up a bit but not much though. O and cgwatcher is garbage with this program. For whatever reason I get below share errors if it goes from like x11 to nist5 or vice versa.... Okay I had the 39.... guess they just came out with the 1.4.0.... see how that goes |
|
|
|
Meticulous7
Newbie
Offline
Activity: 47
Merit: 0
|
|
July 06, 2014, 02:33:24 AM |
|
That was the ticket, Badman! Thank you so much. Seeing some pretty large gains now that I have the new build up and running. Went from 1.4MH/s per card to just over 2MH/s per card! 1.2 MH/s improvement overall! I am very stoked . Now I'm wondering if there may still be room for improvement Anyone else running R9 270s out there? And if so what kind of rates are you getting? 4 x R9 270X's here getting: Scrypt - 1.7 MH/s nScrypt - 800 kH/s x11 - 10.2 mH/s x13 - 7.5 mH/s x15 - 6.4 mH/s nist5 - 30.8 mH/s Keccak - 900 mH/s Divide numbers above by 4 to get individual card speeds what are you getting ? Getting 2mH/s per card so 4mH/s in total. By your numbers it sounds like I may be able to improve a few hundred kH/s. What TC / Intensity settings are you using? Looks like it's time to tweak some more |
|
|
|
|
|
badman74
|
|
July 06, 2014, 06:42:53 AM |
|
That was the ticket, Badman! Thank you so much. Seeing some pretty large gains now that I have the new build up and running. Went from 1.4MH/s per card to just over 2MH/s per card! 1.2 MH/s improvement overall! I am very stoked . Now I'm wondering if there may still be room for improvement Anyone else running R9 270s out there? And if so what kind of rates are you getting? 4 x R9 270X's here getting: Scrypt - 1.7 MH/s nScrypt - 800 kH/s x11 - 10.2 mH/s x13 - 7.5 mH/s x15 - 6.4 mH/s nist5 - 30.8 mH/s Keccak - 900 mH/s Divide numbers above by 4 to get individual card speeds what are you getting ? At least playing around with what I think are overclocks I can get high 2.8 MH per card on x11.... With this it seems like moving the mem speed does little and the GPU clocks seem to bump it up a bit but not much though. O and cgwatcher is garbage with this program. For whatever reason I get below share errors if it goes from like x11 to nist5 or vice versa.... Okay I had the 39.... guess they just came out with the 1.4.0.... see how that goes i had to remove the profile options to get cgwatcher to work properly with mine |
|
|
|
|
|
mrbrdo
|
|
July 06, 2014, 09:29:53 AM |
|
If any of you have been experiencing a problem with these new sgminers running under 14.6beta let me give you an example of what happened to me: I have 4 rigs of 7970s and 280xs. 3 rigs were fine running x11-x15 under the new AMD beta drivers. The other one would run for anywhere from 20 minutes to 2 hours and die with a BSOD no matter what engine speed, voltage, or memory speed I used. After days of troubleshooting it finally came down to doing a complete uninstall of all AMD software, reinstall 14.6 and remove GPU devices and drivers and reinstalling the device drivers for the GPUs. That finally fixed it. Even though I treated all 4 rigs the same, sometimes something glitches out. I hope this saves someone somewhere some time.
I am getting freezes with bin-files compiled with the 14.6 beta drivers. I guess now we know why they are beta...  |
|
|
|
|
mrbrdo
|
|
July 06, 2014, 09:31:43 AM |
|
Again in the Night the Rig close down SGMiner 23:21:05] NH x15 multi extranonce change requested
[23:21:05] NH x15 multi difficulty changed to 0.100
[23:21:08] Accepted Coin 182 Diff 0.113/0.100 GPU 1 at NH x15 multi
[23:21:12] Accepted Coin 182 Diff 0.892/0.100 GPU 2 at NH x15 multi
[23:21:30] Accepted Coin 182 Diff 0.330/0.100 GPU 0 at NH x15 multi
[23:22:14] Accepted Coin 189 Diff 0.112/0.100 GPU 5 at NH x15 multi
[23:22:26] Accepted Coin 189 Diff 0.171/0.100 GPU 5 at NH x15 multi
[23:22:55] Accepted Coin 189 Diff 0.306/0.100 GPU 0 at NH x15 multi
[23:23:16] Accepted Coin 189 Diff 1.319/0.100 GPU 1 at NH x15 multi
[23:23:26] Accepted Coin 189 Diff 9.627/0.100 GPU 0 at NH x15 multi
[23:23:41] NH x11 multi alive, testing stability
[23:23:41] Accepted Coin 176 Diff 0.394/0.100 GPU 5 at NH x15 multi
[23:23:49] NH x11 multi stable for 30 seconds
[23:23:49] Switching to NH x11 multi
[23:23:54] Stratum connection to NH x11 multi interrupted
[23:23:54] NH x11 multi not responding!
[23:23:54] Switching to NH x15 multi
[23:24:50] thread was not cancelled in 60 seconds after restart_mining_threads
[23:24:50]
Summary of runtime statistics: Dont know why it closed. SGminer didnt try to get on the Backup Pool  This has been fixed about a day or two ago. |
|
|
|
|
platinum4
|
|
July 06, 2014, 09:36:09 AM |
|
@badman74, do you find your Windows binaries build from 7-4-2014 to cross hash on the wrong pool?
It's hit or miss whether it picks the right pool, and then if it hashes with a different algo, it produces HW errors I haven't seen since an incorrectly configured scrypt-jane miner.
I tested the jansson builds for troky prior to final push to repo too, never saw this shit going on.
|
|
|
|
|
datosti
Newbie
Offline
Activity: 3
Merit: 0
|
|
July 06, 2014, 10:11:58 AM |
|
I've been trying to get this to run stable for days now, without success. It's hashing and switching fine, but after a couple of hours my GPU goes DEAD. It has never run more than about 5-6 hours straight. I never had a DEAD card before and if I use another miner it runs stable for days, so there's nothing wrong with my card (I rechecked). I don't know what else to try, so hopefully someone else can help me! Here's the config (Asus 280x DC2T): {
"pools" : [
{
"name" : "NH x13 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "BTC adres",
"pass" : "d=.01;f0=0;f2=0;f3=4.14;f4=3.18;f5=0;f6=2.66;f7=0",
"profile" : "x13"
},
{
"name" : "NH x11 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "BTC adres",
"pass" : "d=.04;f0=0;f2=0;f3=4.14;f4=3.18;f5=0;f6=2.66;f7=0",
"profile" : "x11"
},
{
"name" : "NH x15 multi",
"url" : "stratum+tcp://stratum.nicehash.com:4339",
"user" : "BTC adres",
"pass" : "d=.01;f0=0;f2=0;f3=4.14;f4=3.18;f5=0;f6=2.66;f7=0",
"profile" : "x15"
},
{
"name" : "TMB",
"url" : "stratum+tcp://am01.eu.trademybit.com:3458",
"user" : "user",
"pass" : "x",
"profile": "x11"
}
],
"profiles" : [
{
"name" : "x11",
"algorithm" : "darkcoin-mod",
"intensity" : "17",
"gpu-threads" : "2",
"worksize": "256"
},
{
"name" : "x13",
"algorithm" : "marucoin-mod",
"intensity" : "18",
"gpu-threads" : "2",
"worksize": "128"
},
{
"name" : "x15",
"algorithm" : "bitblock",
"intensity" : "16",
"gpu-threads" : "2",
"worksize": "64"
}
],
"hamsi-expand-big" : "1",
"hamsi-short" : true,
"gpu-engine" : "1070",
"gpu-memclock" : "1500",
"gpu-fan" : "20-60",
"failover-only" : true,
"temp-cutoff" : "75",
"temp-overheat" : "72",
"temp-target" : "68",
"auto-fan" : true,
"auto-gpu" : true,
"expiry" : "1",
"gpu-dyninterval" : "7",
"log" : "5",
"queue" : "0",
"scan-time" : "1",
"no-submit-stale" : false,
"no-restart" : false,
"failover-switch-delay" : "30"
}
try setting intensity on x15 to 16, if that doesn't work it is probably your clocks on one of the algo's is too high Intensity on 16 for X15 fixed it I think. Its running stable for over 10 hours now, thanks alot! Here are the speeds with the config in the quote for an Asus 280x DC2T: X11 - 4.15 MH/s X13 - 3.17 MH/s X15 - 2.62 MH/s |
|
|
|
|
|
badman74
|
|
July 06, 2014, 01:42:32 PM |
|
@badman74, do you find your Windows binaries build from 7-4-2014 to cross hash on the wrong pool?
It's hit or miss whether it picks the right pool, and then if it hashes with a different algo, it produces HW errors I haven't seen since an incorrectly configured scrypt-jane miner.
I tested the jansson builds for troky prior to final push to repo too, never saw this shit going on.
the ones i built on 7/14 do not work for me at all, so i had to roll the binaries back to 7/3. but 7/3 version has been working perfectly for me. |
|
|
|
|
cgladue
Member
Offline
Activity: 97
Merit: 10
|
|
July 06, 2014, 01:49:45 PM |
|
That was the ticket, Badman! Thank you so much. Seeing some pretty large gains now that I have the new build up and running. Went from 1.4MH/s per card to just over 2MH/s per card! 1.2 MH/s improvement overall! I am very stoked . Now I'm wondering if there may still be room for improvement Anyone else running R9 270s out there? And if so what kind of rates are you getting? 4 x R9 270X's here getting: Scrypt - 1.7 MH/s nScrypt - 800 kH/s x11 - 10.2 mH/s x13 - 7.5 mH/s x15 - 6.4 mH/s nist5 - 30.8 mH/s Keccak - 900 mH/s Divide numbers above by 4 to get individual card speeds what are you getting ? Getting 2mH/s per card so 4mH/s in total. By your numbers it sounds like I may be able to improve a few hundred kH/s. What TC / Intensity settings are you using? Looks like it's time to tweak some more { "name" : "x11", "algorithm" : "darkcoin-mod", "xintensity" : "300", "gpu-threads" : "1", "gpu-powertune" : "20", "worksize": "256", "gpu-engine": "1160,1160,1160,1160", "gpu-memclock": "1250,1250,1250,1250", "thread-concurrency" : "8193" } |
|
|
|
|
badman74
|
|
July 06, 2014, 02:18:52 PM |
|
@badman74, do you find your Windows binaries build from 7-4-2014 to cross hash on the wrong pool?
It's hit or miss whether it picks the right pool, and then if it hashes with a different algo, it produces HW errors I haven't seen since an incorrectly configured scrypt-jane miner.
I tested the jansson builds for troky prior to final push to repo too, never saw this shit going on.
the ones i built on 7/14 do not work for me at all, so i had to roll the binaries back to 7/3. but 7/3 version has been working perfectly for me. here is the latest build. it closes at "Probing for an alive pool" every time for me no matter what i have tried. i don't know if it is my computer or my build i would appreciate it if someone would test and see if this works for them https://mega.co.nz/#!SBo1RJbR!rA0EvI1bHpxdToHxCN8YDZRwH_-dovp0oal29dAcuEw |
|
|
|
|
|
bitdude
|
|
July 06, 2014, 03:17:04 PM |
|
guys, how does these Xnn switching algs compare to scrypt switching in a sense of BTC/day/MH, I mean with GPU having 1 MH scrypt, it is about 0.0007 BTC / day, what would be with Xnn algs?
|
|
|
|
|
|
BrewCrewFan
|
|
July 06, 2014, 03:18:02 PM |
|
@badman74, do you find your Windows binaries build from 7-4-2014 to cross hash on the wrong pool?
It's hit or miss whether it picks the right pool, and then if it hashes with a different algo, it produces HW errors I haven't seen since an incorrectly configured scrypt-jane miner.
I tested the jansson builds for troky prior to final push to repo too, never saw this shit going on.
the ones i built on 7/14 do not work for me at all, so i had to roll the binaries back to 7/3. but 7/3 version has been working perfectly for me. here is the latest build. it closes at "Probing for an alive pool" every time for me no matter what i have tried. i don't know if it is my computer or my build i would appreciate it if someone would test and see if this works for them https://mega.co.nz/#!SBo1RJbR!rA0EvI1bHpxdToHxCN8YDZRwH_-dovp0oal29dAcuEwIts working at least on my end...the only thing I moved from my original to yours is my .bat and .conf.... and then I always do the AMD files that I do by default. Edit.... running x11.... so the dark algo on 2x 270x's |
|
|
|
|
platinum4
|
|
July 06, 2014, 03:47:59 PM |
|
@badman74, mine's hashing just fine on this 4.2.2-265-g363f you just dropped off for us the morning of the 6th. Tested only x11 right now, not necessarily a day full of algo flips, but it gets right through building bins and goes to pools in order now. I'm on 14.6rc2 drivers as well, and I'm using old-style .conf's (no include "profiles.conf," I specify algo-settings per pool for CGWatcher, as posted a page or two ago in the thread).
|
|
|
|
|
|
badman74
|
|
July 06, 2014, 03:56:50 PM |
|
@badman74, mine's hashing just fine on this 4.2.2-265-g363f you just dropped off for us the morning of the 6th. Tested only x11 right now, not necessarily a day full of algo flips, but it gets right through building bins and goes to pools in order now. I'm on 14.6rc2 drivers as well, and I'm using old-style .conf's (no include "profiles.conf," I specify algo-settings per pool for CGWatcher, as posted a page or two ago in the thread).
hmm i finally got it to work with a single pool in the conf and no profiles but if i add pools with a different algo or ad profiles it just closes on me must be something about my computer i guess... check the issues to see what it is doing to me https://github.com/sgminer-dev/sgminer/issues/327 |
|
|
|
|
kocur
Full Member
Offline
Activity: 140
Merit: 100
We're not in Wonderland anymore Alice
|
|
July 06, 2014, 04:19:21 PM |
|
I tried nicehash for 12hrs or so but it stops accepting shares and my miners switched over backup pool. Is there some reason for that ? Or next fucking shitty scam what works few hrs without paying? {
"pools" : [
{
"name" : "NiceHash_X11_Auto",
"url" : "stratum+tcp://stratum.nicehash.com:4336",
"user" : "--------------------------",
"pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=2.6;f7=0",
"profile" : "x11"
},
{
"name" : "NiceHash_X13_Auto",
"url" : "stratum+tcp://stratum.nicehash.com:4337",
"user" : "--------------------------",
"pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=2.6;f7=0",
"profile" : "x13"
},
{
"name" : "NiceHash_X15_Auto",
"url" : "stratum+tcp://stratum.nicehash.com:4339",
"user" : "----------------------------",
"pass" : "f0=0;f2=0;f3=4;f4=3;f5=0;f6=2.6;f7=0",
"profile" : "x15"
},
{
"name" : "NiceHash_X11_Stat",
"url" : "stratum+tcp://stratum.nicehash.com:3336",
"user" : "----------------------------",
"pass" : "x",
"profile" : "x11"
},
{
"name" : "NiceHash_X13_Stat",
"url" : "stratum+tcp://stratum.nicehash.com:3337",
"user" : "-----------------------------",
"pass" : "x",
"profile" : "x13"
},
{
"name" : "NiceHash_X15_Stat",
"url" : "stratum+tcp://stratum.nicehash.com:3339",
"user" : "-------------------------------",
"pass" : "x",
"profile" : "x15"
},
{
"name" : "WafflePool_X11_EU",
"url" : "stratum+tcp://eu.wafflepool.com:3331",
"user" : "-------------------------------",
"pass" : "x",
"profile" : "x11"
},
.
.
.
there is normal btc address, just edited to -----
any ideas ? now its working more than 18hrs without any issue, good job,, Im using sgminer-5.0-pre-release-2014-06-30-win32 from nicehash web I reccomend use mem and engine frequencies from your old miner drivers: 14.6 and 14.4 |
Community Coin: Fair & Free Distribution
|
|
|
|
platinum4
|
|
July 06, 2014, 06:19:40 PM |
|
@badman74, mine's hashing just fine on this 4.2.2-265-g363f you just dropped off for us the morning of the 6th. Tested only x11 right now, not necessarily a day full of algo flips, but it gets right through building bins and goes to pools in order now. I'm on 14.6rc2 drivers as well, and I'm using old-style .conf's (no include "profiles.conf," I specify algo-settings per pool for CGWatcher, as posted a page or two ago in the thread).
hmm i finally got it to work with a single pool in the conf and no profiles but if i add pools with a different algo or ad profiles it just closes on me must be something about my computer i guess... check the issues to see what it is doing to me https://github.com/sgminer-dev/sgminer/issues/327Looks like this one is less stable. Not sure if pools have dropped but the miner has restarted a few times according to uptime counter. |
|
|
|
|
|
BrewCrewFan
|
|
July 06, 2014, 07:54:42 PM |
|
@badman74, mine's hashing just fine on this 4.2.2-265-g363f you just dropped off for us the morning of the 6th. Tested only x11 right now, not necessarily a day full of algo flips, but it gets right through building bins and goes to pools in order now. I'm on 14.6rc2 drivers as well, and I'm using old-style .conf's (no include "profiles.conf," I specify algo-settings per pool for CGWatcher, as posted a page or two ago in the thread).
hmm i finally got it to work with a single pool in the conf and no profiles but if i add pools with a different algo or ad profiles it just closes on me must be something about my computer i guess... check the issues to see what it is doing to me https://github.com/sgminer-dev/sgminer/issues/327Looks like this one is less stable. Not sure if pools have dropped but the miner has restarted a few times according to uptime counter. I been mining on it for 4 hours now and not one issue. |
|
|
|
|
