Author

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 263. (Read 6590565 times)

member
Activity: 134
Merit: 11
@Claymore

Works like a charm - as always.
Still having issues with my AMD cards lowering hashrate for a few seconds (up to two mins) and then back to normal. Have learned to live with it, but I wonder why...

Ollis
check the clock speeds and temperature while it does this and after the speeds return to normal.  My guess is they get too hot, and gpu and memory clocks throttle down to lower speeds until it cools down to normal temperatures.  Then it will go back up.

Thanks, dave4925

I will chech the clock speeds later, but I'm sure they are not too hot.
The rigs are placed in a cold area with good venting. -tt is 60 and they are always between 58 and 63.

Ollis
I would set -tt to 70
member
Activity: 134
Merit: 11
Hi,

I've an 8 x Rx580 rig. I'm on the lastest drivers (18.3.4 drivers only, no CCC /AMD settings).

On 11.6, I was getting a lot of crashshes, freezes, reboots. Until I've realized that it was because I had -cclock 1150 configured. I've reverted to normal clocks, and reduced them indirectly, through power limit. So this stopped the crashes.
I've also tried OverdriveNTool, seems to behave similarly (unstable miner) if i downclock

On 11.7, I've tried to set the -cclock 1150 again. Now it seems that the miner no longer freezes. But the setting just doesn't work now, clock are easily in 1250 Mhz range.


How are you applying your downlcloaks? I wouldn't like flashing  them in BIOSes, because it's inflexible. Best results were for me achieved with Radeon Settings app (+5% better hashrate than what I'm at now, while also shaving almost 10% power consumed ) . But AMD settings reset themselves from time to time, which is hugely frustrating
Try reducing voltage on your gpu core by -100mV
newbie
Activity: 13
Merit: 0
Hi,

I've an 8 x Rx580 rig. I'm on the lastest drivers (18.3.4 drivers only, no CCC /AMD settings).

On 11.6, I was getting a lot of crashshes, freezes, reboots. Until I've realized that it was because I had -cclock 1150 configured. I've reverted to normal clocks, and reduced them indirectly, through power limit. So this stopped the crashes.
I've also tried OverdriveNTool, seems to behave similarly (unstable miner) if i downclock

On 11.7, I've tried to set the -cclock 1150 again. Now it seems that the miner no longer freezes. But the setting just doesn't work now, clock are easily in 1250 Mhz range.


How are you applying your downlcloaks? I wouldn't like flashing  them in BIOSes, because it's inflexible. Best results were for me achieved with Radeon Settings app (+5% better hashrate than what I'm at now, while also shaving almost 10% power consumed ) . But AMD settings reset themselves from time to time, which is hugely frustrating
newbie
Activity: 2
Merit: 0
Windows 7, GTX1063 - 3gb - 7 GPU
Claymore's v10.0 mining OK.
Claymore's v11.6, v11.7 error

EthDcrMiner64.exe
   0.0.0.0
   ntdll.dll
   c0000005
   C:\Claymore's Miner v11.7\EthDcrMiner64.exe
   C:\Windows\SYSTEM32\ntdll.dll

Help me, please.  English not my native.
donator
Activity: 1610
Merit: 1325
Miners developer
One of my rigs has 2 AMD RX 470 and 1 GTX 1070.
So I always put -powlim, -cclock, -mclock, -tt, -fanmin and -fanmax only for the first 2 cards because it was not supported for NVIDIA and MSI Afterburner opened to control NVIDIA clocks and fan.

Now I am trying to stop using MSI Afterburner and use only Claymore commandline.
But on MSI Afterburner,

while on AMD I set Power Limit +15, Core Clock 1250, Memory Clock 2080,

on NVIDIA I set Power Limit 102, Core Clock +85 and Memory Clock +700 (for example).

How could I 'translate' that into Claymore commandline? Since MSI Afterburner shows 1898 MHz for coreclock and 4498 MHz for memory clock on NVIDIA so I assume that I have to use -cclock 1898 -mclock 4498 ?

Is it correct?

Thank you!


So the miner uses three GPUs: AMD, AMD, NVIDIA. Use this:

-powlim 15,15,2
-cclock 1250,1250,+85
-mclock 2080,2080,+700
donator
Activity: 1610
Merit: 1325
Miners developer
Dear Claymore,
thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.
If it worked before try lower clocks to see if that is the reason.
@Claymore : do you mean under clocking my GPU's?

From your log:
Code:
22:25:30:396   294c   gpu 9 nvidia memclock set ok (6355MHz, previous value was 5505MHz)

So may be set a bit lower overclock than +850? That's what I mean.
newbie
Activity: 11
Merit: 0
Today I stopped Claymore and restarted, it said not enough memory but will try - and succeeded Smiley 3Gb 1060s mining ETH on ethermine.org  Tongue

I hope it will work for others, too.

WIN10 64 bit
Claymore 11.6
Driver 388.13


same here .. it was inevitable .. 3gb zotacs were near end of dag file size


Great Mining Program.  One of my favorites.   Grin
But today it stop mine on GTX 1060 3gb((

Ceгoдня c yтpa yжe нe дoбывaeт эфиp видeoкapтa gtx 1060 c 3gb нa win10

http://priscree.ru/img/266398352ae8ab.jpg




Switch to windows 7 or linux, you'll be good for another while.
newbie
Activity: 15
Merit: 0
One of my rigs has 2 AMD RX 470 and 1 GTX 1070.
So I always put -powlim, -cclock, -mclock, -tt, -fanmin and -fanmax only for the first 2 cards because it was not supported for NVIDIA and MSI Afterburner opened to control NVIDIA clocks and fan.

Now I am trying to stop using MSI Afterburner and use only Claymore commandline.
But on MSI Afterburner,

while on AMD I set Power Limit +15, Core Clock 1250, Memory Clock 2080,

on NVIDIA I set Power Limit 102, Core Clock +85 and Memory Clock +700 (for example).

How could I 'translate' that into Claymore commandline? Since MSI Afterburner shows 1898 MHz for coreclock and 4498 MHz for memory clock on NVIDIA so I assume that I have to use -cclock 1898 -mclock 4498 ?

Is it correct?

Thank you!
newbie
Activity: 8
Merit: 0

The program crashes every time i run it. See below log file.

My system is my home pc, windows 7 64bit, 16gb RAM, GTX1070 6Gb


13:20:39:342   23d8   Check and remove old log files...
13:20:39:342   23d8   args: -epool eth-eu1.nanopool.org:9999 -ewal 0x9276eebafe0ec188e06137364d68da756700e8af.HomePC/[email protected] -epsw x
13:20:39:342   23d8   
13:20:39:343   23d8   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
13:20:39:343   23d8   º                Claymore's Dual GPU Miner - v11.7               º
13:20:39:343   23d8   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
13:20:39:343   23d8   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
13:20:39:343   23d8   
13:20:39:344   23d8   b583
13:20:39:544   23d8   ETH: 1 pool is specified
13:20:39:544   23d8   Main Ethereum pool is eth-eu1.nanopool.org:9999
13:20:39:544   23d8   DCR: 0 pool is specified
13:20:39:560   23d8   OpenCL platform: NVIDIA CUDA
13:20:39:560   23d8   AMD OpenCL platform not found
13:20:39:579   23d8   CUDA initializing...

13:20:39:579   23d8   NVIDIA Cards available: 1
13:20:39:579   23d8   CUDA Driver Version/Runtime Version: 8.0/8.0
13:20:39:580   23d8   GPU #0: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 1:0:0)
13:20:39:580   23d8   Total cards: 1
13:20:43:582   23d8   NVML version: 8.373.06
13:20:44:097   23d8   SSL: Imported 65 certificates from local storage
13:20:44:126   20cc   ETH: Stratum - connecting to 'eth-eu1.nanopool.org' <213.32.29.168> port 9999 (unsecure)
13:20:44:159   20cc   sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x9276eebafe0ec188e06137364d68da756700e8af.HomePC/[email protected]", "x"], "id": 2, "method": "eth_submitLogin"}

13:20:44:159   20cc   ETH: Stratum - Connected (eth-eu1.nanopool.org:9999) (unsecure)
13:20:44:197   23d8   No pool specified for Decred! Ethereum-only mining mode is enabled

13:20:44:197   23d8   ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

13:20:44:197   23d8   ETH: eth-proxy stratum mode
13:20:44:197   23d8   Watchdog enabled
13:20:44:197   23d8   Remote management (READ-ONLY MODE) is enabled on port 3333
13:20:44:197   23d8   

13:20:44:220   20cc   buf: {"jsonrpc":"2.0","id":2,"result":true}
{"jsonrpc":"2.0","id":0,"result":["0x2ccc78f177aaca43292c7a9acc6c6be8f51dd1149fd56cf59f727ee1de708669","0x3ffd591ffcc97fb5e4150c521510e446bb11563ff632ea15845332648cabc086","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

13:20:44:220   20cc   ETH: Authorized
13:20:44:220   20cc   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

13:20:44:220   20cc   remove first packet 243
13:20:44:260   20cc   buf: {"jsonrpc":"2.0","id":0,"result":["0x2ccc78f177aaca43292c7a9acc6c6be8f51dd1149fd56cf59f727ee1de708669","0x3ffd591ffcc97fb5e4150c521510e446bb11563ff632ea15845332648cabc086","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

13:20:44:273   1728   Setting DAG epoch #183...
newbie
Activity: 15
Merit: 0
Dear Claymore,
thanks for the updated version, but i have error for NVML cannot detect temperature as well as CUDA error.

If it worked before try lower clocks to see if that is the reason.

@Claymore : do you mean under clocking my GPU's?
newbie
Activity: 23
Merit: 0
Hello Claymore.


I've installed Windows 7 for use 1060 3GB to mine ETH.

I've test and found a problem with Proxy mining.

For more effective mining and less stale share i'm using Ethproxy (https://github.com/Atrides/eth-proxy/releases)

Problem is : Normally i can mine Musicoin by pool, bu Claymore still not working with local proxy.


Proxy : Eth-proxy
Pool : music.2miners.com or others
Claymore : Version 11.7
Coin : Music
Error : DAG error (like ETH mining)
GPU : Zotac 1060  3GB
Rig OS : Windows 7 SP1 X64


Thank you
Best Regards.
jr. member
Activity: 76
Merit: 2
any example bat file for Nvidia 1070-1080?
newbie
Activity: 30
Merit: 0
@Claymore

Works like a charm - as always.
Still having issues with my AMD cards lowering hashrate for a few seconds (up to two mins) and then back to normal. Have learned to live with it, but I wonder why...

Ollis
check the clock speeds and temperature while it does this and after the speeds return to normal.  My guess is they get too hot, and gpu and memory clocks throttle down to lower speeds until it cools down to normal temperatures.  Then it will go back up.

Thanks, dave4925

I will chech the clock speeds later, but I'm sure they are not too hot.
The rigs are placed in a cold area with good venting. -tt is 60 and they are always between 58 and 63.

Ollis
newbie
Activity: 81
Merit: 0
Hi, Im getting this error since day 19, I tried a lot of possibles solutions but I cant fix it. Also Im trying to fix it with devs of simplemining and they cant fix it neither. Could be a claymore bug?

OFC I tried to reinstall simplemining, low OC/UV etc without luck

Thanks!

https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Foai9ALG.jpg&t=588&c=6D4Xqcvf_lRV4A
member
Activity: 134
Merit: 11
@Claymore

Works like a charm - as always.
Still having issues with my AMD cards lowering hashrate for a few seconds (up to two mins) and then back to normal. Have learned to live with it, but I wonder why...

Ollis
check the clock speeds and temperature while it does this and after the speeds return to normal.  My guess is they get too hot, and gpu and memory clocks throttle down to lower speeds until it cools down to normal temperatures.  Then it will go back up.
jr. member
Activity: 73
Merit: 3

Thanks for the update and letting everybody know. Did they steal a lot of ethereum coin? When the hack start?
I'm going to read the article on Reddit now.


Yup it seems like quite a lot of coins were transferred to rogue account.  
However this was not MEW being hacked but a DNS attack.  Also, there should've been a SSL/TLS certificate mismatch shown by the browser.  If the user still went and logged in that user's wallet might be compromised.

I think from reports, it was the MEW DNS servers that were hacked and they, of course, report their addresses out to the public DNS servers since they are authoritative for the MEW domain.  So many people use Google DNS that they just placed the blame there as that's the system they see giving them the bad address.  But it was the MEW DNS servers pushing the bad address up to the public DNS system.
newbie
Activity: 37
Merit: 0
@Claymore, do you know about stability problems at mining configs with more than 12 AMD GPUs? I have one based on Astock pro btc+ and 13 sapphire rx 580 nitro+. It can mine for hours without any problems, and after it can restart/freeze/report OpenCL errors (can’t create dag file at startup, hangs up and so on).

I saw, that AMD writes about problems in their AMD Adrenalin 18.3.4, but wtf??? What do you think?
full member
Activity: 729
Merit: 114

Thanks for the update and letting everybody know. Did they steal a lot of ethereum coin? When the hack start?
I'm going to read the article on Reddit now.


Yup it seems like quite a lot of coins were transferred to rogue account.  
However this was not MEW being hacked but a DNS attack.  Also, there should've been a SSL/TLS certificate mismatch shown by the browser.  If the user still went and logged in that user's wallet might be compromised.
newbie
Activity: 55
Merit: 0
I re-uploaded v11.7 with these changes:

- fixed issue with "-esm 3" (again).
- fixed issue with Nvidia fan control (Windows only)

Please re-download v11.7 if you have any of these issues, it must write "b583" to the log at the beginning.

Windows defender is decting a Trojan in this release:

Threat ID 2147723652
  Threat Name Trojan:Win32/Fuerboos.A!cl
  Severity ID 5
  Severity Name Severe
  Category ID 8
  Category Name Trojan
  FWLink https://go.microsoft.com/fwlink/?linkid=37020&name=Trojan:Win32/Fuerboos.A!cl&threatid=2147723652&enterprise=0


Did you read the first post? It is often flagged falsely as a trojan/virus.
newbie
Activity: 1
Merit: 0
I re-uploaded v11.7 with these changes:

- fixed issue with "-esm 3" (again).
- fixed issue with Nvidia fan control (Windows only)

Please re-download v11.7 if you have any of these issues, it must write "b583" to the log at the beginning.

Windows defender is decting a Trojan in this release:

Threat ID 2147723652
  Threat Name Trojan:Win32/Fuerboos.A!cl
  Severity ID 5
  Severity Name Severe
  Category ID 8
  Category Name Trojan
  FWLink https://go.microsoft.com/fwlink/?linkid=37020&name=Trojan:Win32/Fuerboos.A!cl&threatid=2147723652&enterprise=0
Jump to: