sensors tab says..you cannot downlclock below 1500 or VRAM..
In that case you would have to flash gpu with modified bios and set memclocks in it (vbe7 and atiflash would be the easiest way).
Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 1332. (Read 6590565 times)
May 08, 2016, 03:00:34 PM
sensors tab says..you cannot downlclock below 1500 or VRAM..
In that case you would have to flash gpu with modified bios and set memclocks in it (vbe7 and atiflash would be the easiest way).
May 08, 2016, 10:38:10 AM
Check with Hwinfo, temperatures of VRMs and voltages (12V line)
With 80 on core, VRMs can easily go above 90-95.
Dual mining needs more power..., ether alone barely heats VRMs to 60
With 80 on core, VRMs can easily go above 90-95.
Dual mining needs more power..., ether alone barely heats VRMs to 60
May 08, 2016, 09:36:27 AM
i have this rig with 2x r9 390 and 1x r9 390x
using gpu-z monitoring (sensors tab), i OC all the cards 1120 clock and 1600 ram ...
looking at sensors tab only one card is at 1120 clock the rest are ~ 930 clock (i'm not sure which card is 390x coz gpuz labels them all 390)
therefore only one GPU is OC'ed...
all ram are at 1600mhz
graphics card tab at gpu-z shows uniform 1120 clock for all cards...sensors do not
any tips?
my 280x rig is uniform, all clocks matched.
edit: these issue occurs only in dual mining mode, mining in ETH only (-mode 1) shows uniform clocks in sensors tab of GPU-Z.
using gpu-z monitoring (sensors tab), i OC all the cards 1120 clock and 1600 ram ...
looking at sensors tab only one card is at 1120 clock the rest are ~ 930 clock (i'm not sure which card is 390x coz gpuz labels them all 390)
therefore only one GPU is OC'ed...
all ram are at 1600mhz
graphics card tab at gpu-z shows uniform 1120 clock for all cards...sensors do not
any tips?
my 280x rig is uniform, all clocks matched.
edit: these issue occurs only in dual mining mode, mining in ETH only (-mode 1) shows uniform clocks in sensors tab of GPU-Z.
claymore..any suggestions?
Sounds like down throttling, of course. If cards are getting too hot or drawing too much power, the firmware downclocks them.
Why do you overclock RAM? It doesn't seem to offer any hashrate increase from my testing. In fact, on my R9 290 cards, I downclock VRAM to 1125mhz for increased power savings (with no hashrate decrease).
I also find downvolting usually results in more stable hashrates, as the GPU is less stressed and is more likely not to throttle.
tried cclock 1100 vram 1125
dual mining core clocks (gpu-z sensors tab) are 970, 995, 1100 ...all vram are 1500
gpu-z (gpu-z graphics card tab) core clock are all 1100 and vram are 1125..
in ETH only mode (gpu-z sensors tab and graphics card tab) all core clock 1100 and vram 1125 (sensors tab 1500)
i could say in dual mining mode, two out of three of my cards are under-performing.
my cards are ~77 temp, only msi r9 390 can reach up to 81 temp ..... i could say it is not down throttling due to heat, besides i run gpu-z right after i started the miner...i don't know if it is a power draw issue.
i haven't done downvolting yet..
sensors tab says..you cannot downlclock below 1500 or VRAM..
@restless
i OC thru cclock and mclock
May 08, 2016, 09:35:33 AM
Took first crack at using this (linux).
Works fine for a bit, then crashes one of the GPUs. Interestingly enough, the watchdog doesn't. :-) YOU HAD ONE JOB, WATCHDOG!
...excerpt from debug log...
WATCHDOG: GPU 2 hangs in OpenCL call, exit
can't fall back & try older version (no linux build for pre-4.1). If you can fix this, I'd prefer to deploy this, even with a fee. The problem here is that it's constantly crashing at variable rates.
Works fine for a bit, then crashes one of the GPUs. Interestingly enough, the watchdog doesn't. :-) YOU HAD ONE JOB, WATCHDOG!
...excerpt from debug log...
WATCHDOG: GPU 2 hangs in OpenCL call, exit
can't fall back & try older version (no linux build for pre-4.1). If you can fix this, I'd prefer to deploy this, even with a fee. The problem here is that it's constantly crashing at variable rates.
May 08, 2016, 06:57:21 AM
hmm..
I have problem with 4.1 version
I have 4 cards on one of my rigs
r9 280x
r9 280x
7970
r9 390x
i adjust core clock for each card in msi afterburner, but when i start miner 390x downclocks to around 950 MHz, this is not throttling because temp is blow 70C for all cards!
I have problem with 4.1 version
I have 4 cards on one of my rigs
r9 280x
r9 280x
7970
r9 390x
i adjust core clock for each card in msi afterburner, but when i start miner 390x downclocks to around 950 MHz, this is not throttling because temp is blow 70C for all cards!
In my rigs, using 270x and 7950, every time I use Afterburner to change some settings I always restart the system before starting the miner.
This way, I make sure the settings are permanent because I double check they are in effect before firing up the miner.
It works for me
May 08, 2016, 06:53:23 AM
hmm..
I have problem with 4.1 version
I have 4 cards on one of my rigs
r9 280x
r9 280x
7970
r9 390x
i adjust core clock for each card in msi afterburner, but when i start miner 390x downclocks to around 950 MHz, this is not throttling because temp is blow 70C for all cards!
I have problem with 4.1 version
I have 4 cards on one of my rigs
r9 280x
r9 280x
7970
r9 390x
i adjust core clock for each card in msi afterburner, but when i start miner 390x downclocks to around 950 MHz, this is not throttling because temp is blow 70C for all cards!
May 08, 2016, 05:33:42 AM
For some reason, version 4 crashes my gfx card drivers on one of my rigs. I've moved back to 3.3, and everything is working fine again. Not sure what is going on...
Exactly the same i had, 4 x 390x righ,left stock everything ,even moved down power limits,crash random ,drier 15.12,windows 10,i switched back to 1.0 which always worked best and with it i can run 1100/1500 with -100 mv perfect stable !!
May 08, 2016, 03:53:05 AM
i have this rig with 2x r9 390 and 1x r9 390x
using gpu-z monitoring (sensors tab), i OC all the cards 1120 clock and 1600 ram ...
looking at sensors tab only one card is at 1120 clock the rest are ~ 930 clock (i'm not sure which card is 390x coz gpuz labels them all 390)
therefore only one GPU is OC'ed...
all ram are at 1600mhz
graphics card tab at gpu-z shows uniform 1120 clock for all cards...sensors do not
any tips?
my 280x rig is uniform, all clocks matched.
edit: these issue occurs only in dual mining mode, mining in ETH only (-mode 1) shows uniform clocks in sensors tab of GPU-Z.
How are you overclocking?using gpu-z monitoring (sensors tab), i OC all the cards 1120 clock and 1600 ram ...
looking at sensors tab only one card is at 1120 clock the rest are ~ 930 clock (i'm not sure which card is 390x coz gpuz labels them all 390)
therefore only one GPU is OC'ed...
all ram are at 1600mhz
graphics card tab at gpu-z shows uniform 1120 clock for all cards...sensors do not
any tips?
my 280x rig is uniform, all clocks matched.
edit: these issue occurs only in dual mining mode, mining in ETH only (-mode 1) shows uniform clocks in sensors tab of GPU-Z.
AB or with -mclock -cclock ?
May 08, 2016, 03:37:03 AM
i have this rig with 2x r9 390 and 1x r9 390x
using gpu-z monitoring (sensors tab), i OC all the cards 1120 clock and 1600 ram ...
looking at sensors tab only one card is at 1120 clock the rest are ~ 930 clock (i'm not sure which card is 390x coz gpuz labels them all 390)
therefore only one GPU is OC'ed...
all ram are at 1600mhz
graphics card tab at gpu-z shows uniform 1120 clock for all cards...sensors do not
any tips?
my 280x rig is uniform, all clocks matched.
edit: these issue occurs only in dual mining mode, mining in ETH only (-mode 1) shows uniform clocks in sensors tab of GPU-Z.
using gpu-z monitoring (sensors tab), i OC all the cards 1120 clock and 1600 ram ...
looking at sensors tab only one card is at 1120 clock the rest are ~ 930 clock (i'm not sure which card is 390x coz gpuz labels them all 390)
therefore only one GPU is OC'ed...
all ram are at 1600mhz
graphics card tab at gpu-z shows uniform 1120 clock for all cards...sensors do not
any tips?
my 280x rig is uniform, all clocks matched.
edit: these issue occurs only in dual mining mode, mining in ETH only (-mode 1) shows uniform clocks in sensors tab of GPU-Z.
claymore..any suggestions?
Sounds like down throttling, of course. If cards are getting too hot or drawing too much power, the firmware downclocks them.
Why do you overclock RAM? It doesn't seem to offer any hashrate increase from my testing. In fact, on my R9 290 cards, I downclock VRAM to 1125mhz for increased power savings (with no hashrate decrease).
I also find downvolting usually results in more stable hashrates, as the GPU is less stressed and is more likely not to throttle.
May 07, 2016, 10:24:32 PM
i have this rig with 2x r9 390 and 1x r9 390x
using gpu-z monitoring (sensors tab), i OC all the cards 1120 clock and 1600 ram ...
looking at sensors tab only one card is at 1120 clock the rest are ~ 930 clock (i'm not sure which card is 390x coz gpuz labels them all 390)
therefore only one GPU is OC'ed...
all ram are at 1600mhz
graphics card tab at gpu-z shows uniform 1120 clock for all cards...sensors do not
any tips?
my 280x rig is uniform, all clocks matched.
edit: these issue occurs only in dual mining mode, mining in ETH only (-mode 1) shows uniform clocks in sensors tab of GPU-Z.
using gpu-z monitoring (sensors tab), i OC all the cards 1120 clock and 1600 ram ...
looking at sensors tab only one card is at 1120 clock the rest are ~ 930 clock (i'm not sure which card is 390x coz gpuz labels them all 390)
therefore only one GPU is OC'ed...
all ram are at 1600mhz
graphics card tab at gpu-z shows uniform 1120 clock for all cards...sensors do not
any tips?
my 280x rig is uniform, all clocks matched.
edit: these issue occurs only in dual mining mode, mining in ETH only (-mode 1) shows uniform clocks in sensors tab of GPU-Z.
claymore..any suggestions?
May 07, 2016, 09:26:31 PM
For some reason, version 4 crashes my gfx card drivers on one of my rigs. I've moved back to 3.3, and everything is working fine again. Not sure what is going on...
for a moment there, I thought gtx cards are now supported ....
May 07, 2016, 06:22:39 PM
For some reason, version 4 crashes my gfx card drivers on one of my rigs. I've moved back to 3.3, and everything is working fine again. Not sure what is going on...
May 07, 2016, 06:02:07 PM
Miner shows GPU temps and fan speed every 30 seconds if you specified "-tt" parameter to manage fans.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
So what happens when target temp exceeds, does it shutdown the GPUs and restart when temp drops down? It will be a nice feature for summer time garage mining.
May 07, 2016, 05:55:08 PM
For me this miner more steble than genoil. My Gpu upload about 99-100%.
May 07, 2016, 04:43:59 PM
Miner shows GPU temps and fan speed every 30 seconds if you specified "-tt" parameter to manage fans.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
As it is now the -tt parameter works perfectly!
May 07, 2016, 04:08:13 PM
Miner shows GPU temps and fan speed every 30 seconds if you specified "-tt" parameter to manage fans.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
u r the best!
May 07, 2016, 04:07:18 PM
Miner shows GPU temps and fan speed every 30 seconds if you specified "-tt" parameter to manage fans.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
You the man Claymore!
May 07, 2016, 03:56:27 PM
Miner shows GPU temps and fan speed every 30 seconds if you specified "-tt" parameter to manage fans.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
I will add "-tt 1" that will not manage fans but will show temps and fan speeds.
May 07, 2016, 03:50:57 PM
Is there a flag to enable showing current GPU temps during run time? How about fan speed as %? I don't see anything in the Readme.txt...
i need this too
@claymore
it will be great if u can put these flags
ttks for all u good work
May 07, 2016, 02:39:25 PM
Is there a flag to enable showing current GPU temps during run time? How about fan speed as %? I don't see anything in the Readme.txt...
Jump to: