Schwacke
Member
Offline
Activity: 64
Merit: 10
|
|
February 17, 2017, 11:01:33 AM |
|
modded rx 470 -285 h/s (80W in Afterburner), modded rx480 - 305 h/s (86W in Afterburner), modded HD7950 - 245 h/s (around 110w I think). Very nice results Claymore, you made equihash most profitable algo at nicehash again.
would you pls post your settings? BR rx470 4gb: one has 1256 mhz and other has 1260 mhz stock clocks, mem clock is 1750 mhz. Voltage is 985 mV. rx480 8gb: core clock is 1266 mhz stock and mem clock is 2000 mhz. Voltage is 961 mV. hd7950 3gb: core clock is 900 mhz, mem clock is 1250 mhz all stock. Voltage is 956 mV. Thanks alot. but one thing i dont get i was searching and searching and then i gaved up. In Afterburner the Core Voltage (mV) is set to 0. what do i change there? i can change from -100 to +100. BR You change mVolts. If your card is running on 1120 mV and you change it to -100 then you get 1020 mV. But I couldn't lower it more so I changed it in gpu's bios to 985 mV is it save to change it to -100? sry for the noob question but i have no clue of undervolting and what will happen if i undervolt to much. BR depends of the card, some will hang.Some may work @ -100 even. ok if it only will hang its ok. i thought it will burn something maybe. Ty
|
|
|
|
pwpwpw
|
|
February 17, 2017, 12:12:45 PM |
|
Hi ALL! So, having 4*R9 280X with 8 Gb RAM and 32 Gb Virtual mem. CM 12.0 runs only with -i 2 stable. With -i 3 or -i 4 after ~1 hr. one card hows 0 hash and miner restarts . With default -i ( -i 6) miner writes low virtual mem. and lower intensity to 5 and i get same situation as with -i 3 , -i 4. Only way to run it stable is -i 2 option ? My hash rate lower by ~10-15 hashes per card with this intensity. Anyone in this situation ? pwpwpw,thesaltonsea and me ownmind. We all in one boat. Claymore or someone, can you explain this situation? Please, take a look at problem. https://bitcointalk.org/index.php?topic=1670733.msg17878165#msg178781654x 280x, tried to run -i 0 all cards still fail, looked at v11.1 had settings at i 6,6,4,5, now I'm trying 5,5,0,1 with asm 1,1,0,1 so the 3rd card is completely turned down, doing 210H/s (way worse than V11), the rest do, 290 290 270, this is barely faster but somehow one card simply dies with this new miner and another can only go with low setting, using 40GB virtual memory, 4GB system ram, tried the cpu with and without OC, no difference, wiped and reinstalled drivers no difference, meanwhile v11.1 flawless so it's not a physical loose plug or something.
|
|
|
|
d57heinz
Legendary
Offline
Activity: 1453
Merit: 1011
Bitcoin Talks Bullshit Walks
|
|
February 17, 2017, 12:24:56 PM |
|
Constantly getting "GPU #1 returned incorrect data!" on v12.0 v11.1 works fine. Virtual memory size = 16Gb
SET GPU_FORCE_64BIT_PTR 1 SET GPU_MAX_HEAP_SIZE 100 SET GPU_USE_SYNC_OBJECTS 1 SET GPU_MAX_ALLOC_PERCENT 100 SET GPU_SINGLE_ALLOC_PERCENT 100
are set
UPD. In my case they are set via SETX but I think it doesn't matter.
Same here as well. Gpu 1 incorrect data. 7970. Finally pulled the card and put in a 390x. All is well. Funny was that after running v12. That 7970 does same now on v11.1. Think it wiped out my card. Def some bugs in the new release. Save yourself some headaches and move to v11.1 if you can't get stability. At least it will run more than a few hours. Also same rig when it would drop to 0 hash on a different random card before replacing 7970 it would start getting socket errors. Then pc was no longer accessible via team viewer. Had to manually reboot Computer. Great effort claymore. I am getting over 400 sols on 390x. Those seem to have no issues running v12. BR
|
As in nature, all is ebb and tide, all is wave motion, so it seems that in all branches of industry, alternating currents - electric wave motion - will have the sway. ~Nikola Tesla~
|
|
|
Redhotdog
Newbie
Offline
Activity: 4
Merit: 0
|
|
February 17, 2017, 12:53:40 PM |
|
Same here as well. Gpu 1 incorrect data. 7970. Finally pulled the card and put in a 390x. All is well. Funny was that after running v12. That 7970 does same now on v11.1. Think it wiped out my card. Def some bugs in the new release. Save yourself some headaches and move to v11.1 if you can't get stability. At least it will run more than a few hours. Also same rig when it would drop to 0 hash on a different random card before replacing 7970 it would start getting socket errors. Then pc was no longer accessible via team viewer. Had to manually reboot Computer. Great effort claymore. I am getting over 400 sols on 390x. Those seem to have no issues running v12.
BR
Also rolled back to 11.1 My rig consists of 3 RX470 and one R9 390 (the above mentioned GPU 1). Tried to increase voltage. Nothing helped.
|
|
|
|
fr4nkthetank
Legendary
Offline
Activity: 2294
Merit: 1182
Now the money is free, and so the people will be
|
|
February 17, 2017, 01:42:16 PM |
|
for the incorrect data thingy, I had the same problem with 280x but at i -2 it seems to be good. One card is good at -3. So lower i it should work.
|
|
|
|
IOTUSA
|
|
February 17, 2017, 02:11:56 PM |
|
Same here as well. Gpu 1 incorrect data. 7970. Finally pulled the card and put in a 390x. All is well. Funny was that after running v12. That 7970 does same now on v11.1. Think it wiped out my card. Def some bugs in the new release. Save yourself some headaches and move to v11.1 if you can't get stability. At least it will run more than a few hours. Also same rig when it would drop to 0 hash on a different random card before replacing 7970 it would start getting socket errors. Then pc was no longer accessible via team viewer. Had to manually reboot Computer. Great effort claymore. I am getting over 400 sols on 390x. Those seem to have no issues running v12.
BR
Also rolled back to 11.1 My rig consists of 3 RX470 and one R9 390 (the above mentioned GPU 1). Tried to increase voltage. Nothing helped. I have a 6 x Fury rig that also started behaving real odd. I keep getting 'GPU 3' crashing for no reason. Driver reinstall, and stock settings have not helped.
|
|
|
|
PandaPanda!
Newbie
Offline
Activity: 35
Merit: 0
|
|
February 17, 2017, 03:47:12 PM |
|
My farm is a mess with v12.0 - i'm moving back to v11.1 until claymore sorts out all the issues with crashing GPUs etc.
|
|
|
|
IOTUSA
|
|
February 17, 2017, 04:00:24 PM |
|
Question: I have a few Bios modded Rx 470/480 that I'm trying to get running under Windows 10 ver. 1607. On install they show as 'problem detected, code 43' in device manager. Do I have to use modded driver files and disable signature check etc. to solve the issue? I tried 15.12 and 16.3 and I get the issue with both.
Anyone of you scholars that know?
|
|
|
|
IOTUSA
|
|
February 17, 2017, 04:01:31 PM |
|
My farm is a mess with v12.0 - i'm moving back to v11.1 until claymore sorts out all the issues with crashing GPUs etc.
The strange part is that it seems v12.0 actually messed up my Fury cards somehow so now when I revert to 11.x they still crash. Could be some kind of odd coincidence but it seems unlikely.
|
|
|
|
Redhotdog
Newbie
Offline
Activity: 4
Merit: 0
|
|
February 17, 2017, 04:12:25 PM |
|
for the incorrect data thingy, I had the same problem with 280x but at i -2 it seems to be good. One card is good at -3. So lower i it should work.
Tried to reduce intensity and remove undervoltage = recieve definetly less "incorrect data" messages. Will see.
|
|
|
|
spyshagg
|
|
February 17, 2017, 04:39:07 PM |
|
suprnova shows my hashrate but not my " SOL " hashrate nor my " SOL " sharerate. Anyone else?
|
|
|
|
PandaPanda!
Newbie
Offline
Activity: 35
Merit: 0
|
|
February 17, 2017, 04:44:16 PM |
|
Question: I have a few Bios modded Rx 470/480 that I'm trying to get running under Windows 10 ver. 1607. On install they show as 'problem detected, code 43' in device manager. Do I have to use modded driver files and disable signature check etc. to solve the issue? I tried 15.12 and 16.3 and I get the issue with both.
Anyone of you scholars that know?
Use 16.11.5 - will work perfectly. 16.12 and up won't work with modded BIOSes as far as i know.
|
|
|
|
PandaPanda!
Newbie
Offline
Activity: 35
Merit: 0
|
|
February 17, 2017, 04:46:15 PM |
|
My farm is a mess with v12.0 - i'm moving back to v11.1 until claymore sorts out all the issues with crashing GPUs etc.
The strange part is that it seems v12.0 actually messed up my Fury cards somehow so now when I revert to 11.x they still crash. Could be some kind of odd coincidence but it seems unlikely. You know, its funny you say that - i've just noticed the stability I had when I was originally using 11.1 has now gone after downgrading from 12.0 back to 11.1. This is strange.. However, the instability seems to be coming from only my 2xx/3xx cards.. RX4xx series cards seem to be running okay.
|
|
|
|
IOTUSA
|
|
February 17, 2017, 04:56:22 PM |
|
Question: I have a few Bios modded Rx 470/480 that I'm trying to get running under Windows 10 ver. 1607. On install they show as 'problem detected, code 43' in device manager. Do I have to use modded driver files and disable signature check etc. to solve the issue? I tried 15.12 and 16.3 and I get the issue with both.
Anyone of you scholars that know?
Use 16.11.5 - will work perfectly. 16.12 and up won't work with modded BIOSes as far as i know. Ah, OK. Damn I hate AMD drivers.
|
|
|
|
zzzzzzzzzz
|
|
February 17, 2017, 05:15:02 PM |
|
My farm is a mess with v12.0 - i'm moving back to v11.1 until claymore sorts out all the issues with crashing GPUs etc.
The strange part is that it seems v12.0 actually messed up my Fury cards somehow so now when I revert to 11.x they still crash. Could be some kind of odd coincidence but it seems unlikely. You've probably already tried this, but have you powered off the rig, disconnected the power cord for 15 seconds or so (to ensure the PSU drains residual current), and power on? It sounds as the the GPUs have not been fully reset after you switched back. Just a thought.
|
|
|
|
BogdanCo
|
|
February 17, 2017, 05:18:14 PM Last edit: February 17, 2017, 05:49:07 PM by BogdanCo |
|
Constantly getting "GPU #1 returned incorrect data!" on v12.0 v11.1 works fine. Virtual memory size = 16Gb
SET GPU_FORCE_64BIT_PTR 1 SET GPU_MAX_HEAP_SIZE 100 SET GPU_USE_SYNC_OBJECTS 1 SET GPU_MAX_ALLOC_PERCENT 100 SET GPU_SINGLE_ALLOC_PERCENT 100
are set
UPD. In my case they are set via SETX but I think it doesn't matter.
Same here as well. Gpu 1 incorrect data. 7970. Finally pulled the card and put in a 390x. All is well. Funny was that after running v12. That 7970 does same now on v11.1. Think it wiped out my card. Def some bugs in the new release. Save yourself some headaches and move to v11.1 if you can't get stability. At least it will run more than a few hours. Also same rig when it would drop to 0 hash on a different random card before replacing 7970 it would start getting socket errors. Then pc was no longer accessible via team viewer. Had to manually reboot Computer. Great effort claymore. I am getting over 400 sols on 390x. Those seem to have no issues running v12. BR Same here with my 7990. I reduced mining intensity from 5 (default) to 4 and seems the issue is solved.
|
|
|
|
rpg
|
|
February 17, 2017, 06:46:55 PM |
|
Constantly getting "GPU #1 returned incorrect data!" on v12.0 v11.1 works fine. Virtual memory size = 16Gb
SET GPU_FORCE_64BIT_PTR 1 SET GPU_MAX_HEAP_SIZE 100 SET GPU_USE_SYNC_OBJECTS 1 SET GPU_MAX_ALLOC_PERCENT 100 SET GPU_SINGLE_ALLOC_PERCENT 100
are set
UPD. In my case they are set via SETX but I think it doesn't matter.
Same here as well. Gpu 1 incorrect data. 7970. Finally pulled the card and put in a 390x. All is well. Funny was that after running v12. That 7970 does same now on v11.1. Think it wiped out my card. Def some bugs in the new release. Save yourself some headaches and move to v11.1 if you can't get stability. At least it will run more than a few hours. Also same rig when it would drop to 0 hash on a different random card before replacing 7970 it would start getting socket errors. Then pc was no longer accessible via team viewer. Had to manually reboot Computer. Great effort claymore. I am getting over 400 sols on 390x. Those seem to have no issues running v12. BR Same here with my 7990. I reduced mining intensity from 5 (default) to 4 and seems the issue is solved. The 11.1 settings on my 290x didn't work. No more oc and not as aggressive under volt
|
|
|
|
devlin
|
|
February 17, 2017, 07:52:52 PM |
|
For 280X cards I need to reduce intensity to 4, with -i 5 freeze after a few hours even with no OC. No problem so far for other cards with default intensity. (v12.0)
|
|
|
|
pwpwpw
|
|
February 17, 2017, 09:29:39 PM |
|
4x 280x, 1 of my cards restarts the rig even without asm and with i 0, I can't reduce it any lower, had to revert to 11.1, no OC at all.
|
|
|
|
ivomm
Legendary
Offline
Activity: 1886
Merit: 3079
All good things to those who wait
|
|
February 17, 2017, 10:39:05 PM |
|
4x 280x, 1 of my cards restarts the rig even without asm and with i 0, I can't reduce it any lower, had to revert to 11.1, no OC at all.
The same problem here. One of my 280x hangs causing multiple restarts of the watchdog! Never happened before!
|
|
|
|
|