Author

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

newbie
Activity: 118
Merit: 0
I have a new setup on Windows 10 Pro and I'm getting terrible hashrates running 1070's. I have tried running 1 GPU and multiple GPUs with the same result. My other setup running the same Claymore settings runs fine, 28-29 Mh/s.
https://i.imgur.com/pHZTxR2.jpg

For some reason, the power consumption is only running about half of what it should be, and obviously temps indicate that the card isn't even trying.
https://i.imgur.com/M6vIlvI.jpg

Any suggestions? A few algorithms benchmark pretty slow in Nicehash, but some of them run at expected speeds (Lbry and Lyra primarily).

Windows 10 Pro, 8GB ram, 16GB pagefile
Asus Z270-AR
Intel Pentium G4560
Asus GTX 1070 Dual OC x 3 (directly plugged into MB)
378.78 drivers
Seasonic 750W

Try W7
newbie
Activity: 27
Merit: 0
Looking for help will may some eth!!!!

My current Rig
Sapphire r9 380x 20 m/h
Gtx 970 18-20 M/h
gtx 970 18-20 m/h
gtx 1060 11 m/h (Was at 20 but decided to halve for unknown reasons.)
1300 watt evga gold rated

Whats next? I know that I can tweak them to get more m/hs just dont know where to start. Anyone point me in the right driection?  Or if anyone has clues to why one of my cards satrting mining at half m/s that would be great.

newbie
Activity: 2
Merit: 0
Hi,

What drivers are recommended for RX 480s and Ubuntu 16 with this miner?

I'm running the amdgpu-pro 17.10 drivers with Claymore 9.4 (solo mining ETH) and only seeing ~22mh/s per card...

Thanks!
sr. member
Activity: 476
Merit: 250
I have strange problem that requires several reboots to resolve. My rig works fine good for days. But my location sometimes has issues with power outages. I start my rig after power recovers, however one of the gpus hashing less than usual rate (26.3 or 13 instead of 29.3 modded rate).To fix this, I need to reboot my rig several times. At first try I lose one or two gpus. I reseat their risers and problem resolved.

Then I start my rig and this time, everything is great. Problem repeats every time whenever a power outage occurs.

Any suggestions?

I would invest in a UPS maybe? If the outages are short you're probably good. If they're longer than the UPS battery will stand at least it will shut the system down correctly. Not sure why one of your gpus would show that behavior though.

I've thought about that. Actually I have  1kVA online UPS but out of battery. And I don't think it will provide enough power.
full member
Activity: 126
Merit: 100
I have strange problem that requires several reboots to resolve. My rig works fine good for days. But my location sometimes has issues with power outages. I start my rig after power recovers, however one of the gpus hashing less than usual rate (26.3 or 13 instead of 29.3 modded rate).To fix this, I need to reboot my rig several times. At first try I lose one or two gpus. I reseat their risers and problem resolved.

Then I start my rig and this time, everything is great. Problem repeats every time whenever a power outage occurs.

Any suggestions?

I would invest in a UPS maybe? If the outages are short you're probably good. If they're longer than the UPS battery will stand at least it will shut the system down correctly. Not sure why one of your gpus would show that behavior though.
newbie
Activity: 27
Merit: 0
Hey so I just set a up a 4 gpu mining Rig. 1 r9 380, 2 gtx 970s, and a gtx 1060.
Im currently getting a 67 M/hs and I believe it should be much higher. The gtx 1060 mining alone produces 18-20 m/h yet when mining with the group only 10m/h?

Suggestions Im quite new obviously but learn quick.
sr. member
Activity: 476
Merit: 250
I have strange problem that requires several reboots to resolve. My rig works fine good for days. But my location sometimes has issues with power outages. I start my rig after power recovers, however one of the gpus hashing less than usual rate (26.3 or 13 instead of 29.3 modded rate).To fix this, I need to reboot my rig several times. At first try I lose one or two gpus. I reseat their risers and problem resolved.

Then I start my rig and this time, everything is great. Problem repeats every time whenever a power outage occurs.

Any suggestions?
hero member
Activity: 1036
Merit: 606
Latest version is v9.5:

-tt   set target GPU temperature. For example, "-tt 80" means 80C temperature. You can also specify values for every card, for example "-tt 70,80,75".
   You can also set static fan speed if you specify negative values, for example "-tt -50" sets 50% fan speed. Specify zero to disable control and hide GPU statistics.
   "-tt 1" (default) does not manage fans but shows GPU temperature and fan status every 30 seconds. Specify values 2..5 if it is too often.
   Note: for NVIDIA cards only temperature monitoring is supported, temperature management is not supported.
   Note: for Linux gpu-pro drivers, miner must have root access to manage fans, otherwise only monitoring will be available.


@Claymore: are temps and fan speed available for RX 5xx with latest driver in Windows 10?  They display for NVIDIA cards but not for the 5xx series.

/c

You need a monitor or a dummy plug in the card plugged in the primary PCI-E x16 slot for the AMD drivers to be able to read and set the fan and temperature settings. You also need to change the primary video to the PCI-E slot and not the on board video in the motherboard Bios.
newbie
Activity: 8
Merit: 0
hello, Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v9.5 bug, not connet servers ethermine pool

09:47:11:437   7b0   args: -mode 0 -epool us1.ethermine.org:4444 -ewal 0xbd517d281151d2c0e57c81d4dddcfd6a0041748d.rig01 -esm 2 -epsw x -allpools 1 -ethi 8 -tstop 80 -dpool stratum+tcp://pasc-us-east1.nanopool.org:15555 -dwal 86646-64.bc25062087b03fd6.rig01/[email protected] -dpsw x -dcoin pasc -dcri 7
09:47:11:438   7b0   
09:47:11:440   7b0   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
09:47:11:442   7b0   º      Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.5      º
09:47:11:443   7b0   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
09:47:11:444   7b0   
09:47:11:647   7b0   ETH: 1 pool is specified
09:47:11:648   7b0   Main Ethereum pool is us1.ethermine.org:4444
09:47:11:649   7b0   PASC: 1 pool is specified
09:47:11:650   7b0   Main Pascal pool is pasc-us-east1.nanopool.org:15555
09:47:12:573   7b0   OpenCL platform: Intel(R) OpenCL
09:47:12:574   7b0   OpenCL platform: AMD Accelerated Parallel Processing
09:47:12:580   7b0   OpenCL initializing...

09:47:12:581   7b0   AMD Cards available: 6
09:47:12:581   7b0   GPU #0: Hawaii, 8192 MB available, 44 compute units
09:47:12:582   7b0   GPU #0 recognized as Radeon 390X
09:47:12:583   7b0   GPU #1: Hawaii, 8192 MB available, 44 compute units
09:47:12:583   7b0   GPU #1 recognized as Radeon 390X
09:47:12:584   7b0   GPU #2: Hawaii, 8192 MB available, 44 compute units
09:47:12:585   7b0   GPU #2 recognized as Radeon 390X
09:47:12:586   7b0   GPU #3: Hawaii, 8192 MB available, 44 compute units
09:47:12:586   7b0   GPU #3 recognized as Radeon 390X
09:47:12:587   7b0   GPU #4: Hawaii, 8192 MB available, 44 compute units
09:47:12:588   7b0   GPU #4 recognized as Radeon 390X
09:47:12:588   7b0   GPU #5: Hawaii, 8192 MB available, 44 compute units
09:47:12:589   7b0   GPU #5 recognized as Radeon 390X
09:47:12:589   7b0   POOL/SOLO version
09:47:12:590   7b0   b351
09:47:12:590   7b0   Platform: Windows
09:47:12:608   7b0   start building OpenCL program for GPU 0...
09:47:12:827   7b0   done
09:47:13:028   7b0   start building OpenCL program for GPU 1...
09:47:13:243   7b0   done
09:47:13:445   7b0   start building OpenCL program for GPU 2...
09:47:13:668   7b0   done
09:47:13:870   7b0   start building OpenCL program for GPU 3...
09:47:14:105   7b0   done
09:47:14:308   7b0   start building OpenCL program for GPU 4...
09:47:14:558   7b0   done
09:47:14:759   7b0   start building OpenCL program for GPU 5...
09:47:14:979   7b0   done
09:47:15:205   7b0   GPU #0: algorithm ASM
09:47:15:225   7b0   GPU #1: algorithm ASM
09:47:15:243   7b0   GPU #2: algorithm ASM
09:47:15:260   7b0   GPU #3: algorithm ASM
09:47:15:346   7b0   GPU #4: algorithm ASM
09:47:15:413   7b0   GPU #5: algorithm ASM
09:47:15:414   7b0   cudaGetDeviceCount failed (35, CUDA driver version is insufficient for CUDA runtime version), probably no CUDA devices
09:47:15:414   7b0   No NVIDIA CUDA GPUs detected.
09:47:15:416   7b0   Total cards: 6
09:47:21:772   7b0   No NVIDIA cards in the list, NVML library will not be used.
09:47:21:932   7b0   DUAL MINING MODE ENABLED: ETHEREUM+PASCAL

09:47:21:933   7b0   ETH: miner-proxy stratum mode
09:47:21:934   7b0   "-allpools" option is set, default pools can be used for devfee, check "Readme" file for details.
09:47:21:936   1700   ETH: Stratum - connecting to 'us1.ethermine.org' <149.56.26.221> port 4444
09:47:21:936   7b0   Watchdog enabled
09:47:21:937   7b0   Remote management (READ-ONLY MODE) is enabled on port 3333
09:47:21:939   7b0   

09:47:22:030   f84    PASC: Stratum - connecting to 'pasc-us-east1.nanopool.org' <158.69.86.187> port 15555
09:47:22:043   1700   send: {"id": 1, "method": "mining.subscribe", "params": []}

09:47:22:044   1700   send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

09:47:22:044   1700   send: {"id": 2, "method": "mining.authorize", "params": ["0xbd517d281151d2c0e57c81d4dddcfd6a0041748d.rig01","x"]}

09:47:22:045   1700   ETH: Stratum - Connected (us1.ethermine.org:4444)
09:47:22:134   f84   send: {"id": 1, "method": "mining.subscribe", "params": ["dual 1.0"]}

09:47:22:134   f84   send: {"id": 5, "method": "mining.extranonce.subscribe", "params": []}

09:47:22:135   f84   send: {"id": 2, "method": "mining.authorize", "params": ["86646-64.bc25062087b03fd6.rig01/[email protected]","x"]}

09:47:22:135   f84    PASC: Stratum - Connected (pasc-us-east1.nanopool.org:15555)
09:47:22:158   1700   got 39 bytes
09:47:22:158   1700   buf: {"id":1,"jsonrpc":"2.0","result":true}

09:47:22:158   1700   parse packet: 38
09:47:22:159   1700   new buf size: 0
09:47:22:253   1700   got 74 bytes
09:47:22:253   1700   buf: {"id":5,"jsonrpc": "2.0","result": false,"error": "Miner not registered"}

09:47:22:253   1700   parse packet: 68
09:47:22:254   1700   new buf size: 0
09:47:22:254   1700   Socket was closed remotely (by pool)
09:47:22:256   1700   ETH: Job timeout, disconnect, retry in 20 sec...
09:47:22:422   f84   got 688 bytes
09:47:22:423   f84   buf: {"id":1,"result":[[["mining.notify","00000000000000000000000000000000"]],"4e616e6f706f6f6c2f3433363234343331313030303030303030",8],"error":null}
{"id":null,"method":"mining.set_difficulty","params":[8]}
{"method":"mining.notify","params":["29a9","0000000000000000000000000000000000000000000000000000000000000000","EB8E0100CA02200042B6D71C8BDD83EB6DAB79713BCFCFF330C4AB5BA2BB7B7C02A30882B54E31E 62000CA1FF7B7804CE8BC3AFA0C5A7F7F72E372C30A3A3FFAC81563C67672781D2DFD40420F0000 00000001000100AFE45932","DF151D924651CE35813C5B238D9693293134419661196E67F330F8A02B8FF8E52C158408D965291 4E2111E7D40F244FE809B6033433C0FF432AC1D634C1561DD64000000",[],"00000000","23000000","59395241",true],"id":null}

09:47:22:423   f84   parse packet: 144
09:47:22:423   f84   remove first packet 543
09:47:22:423   f84   new buf size: 543
09:47:22:424   f84   parse packet: 57
09:47:22:424   f84   remove first packet 485
09:47:22:424   f84   new buf size: 485
09:47:22:425   f84   parse packet: 484
09:47:22:425   f84   new buf size: 0
09:47:22:435   f84   got 557 bytes
09:47:22:436   f84   buf: {"id":5,"result":true,"error":null}
{"id":2,"result":true,"error":null}
{"method":"mining.notify","params":["29a9","0000000000000000000000000000000000000000000000000000000000000000","EB8E0100CA02200042B6D71C8BDD83EB6DAB79713BCFCFF330C4AB5BA2BB7B7C02A30882B54E31E 62000CA1FF7B7804CE8BC3AFA0C5A7F7F72E372C30A3A3FFAC81563C67672781D2DFD40420F0000 00000001000100AFE45932","DF151D924651CE35813C5B238D9693293134419661196E67F330F8A02B8FF8E52C158408D965291 4E2111E7D40F244FE809B6033433C0FF432AC1D634C1561DD64000000",[],"00000000","23000000","59395241",true],"id":null}

09:47:22:436   f84   parse packet: 35
09:47:22:436   f84   remove first packet 521
09:47:22:436   f84   new buf size: 521
09:47:22:437   f84   parse packet: 35
09:47:22:437   f84    PASC: Authorized
09:47:22:438   f84   remove first packet 485
09:47:22:439   f84   new buf size: 485
09:47:22:439   f84   parse packet: 484
09:47:22:439   f84   new buf size: 0
09:47:22:440   f84    PASC: 06/08/17-09:47:22 - New job from pasc-us-east1.nanopool.org:15555
09:47:22:440   f84   target: 0x000000001fffe000 (diff: 34GH)
09:47:31:397   f84   got 485 bytes
09:47:31:397   f84   buf: {"method":"mining.notify","params":["29aa","0000000000000000000000000000000000000000000000000000000000000000","EC8E0100CA02200042B6D71C8BDD83EB6DAB79713BCFCFF330C4AB5BA2BB7B7C02A30882B54E31E 62000CA1FF7B7804CE8BC3AFA0C5A7F7F72E372C30A3A3FFAC81563C67672781D2DFD40420F0000 00000001000100471D5E32","43515A9FC77616E55C147014E0F2E72AE117EF2F74596B410CAB772FC78E6057E3B0C44298FC1C1 49AFBF4C8996FB92427AE41E4649B934CA495991B7852B85500000000",[],"00000000","23000000","59395258",true],"id":null}

09:47:31:398   f84   parse packet: 484
09:47:31:399   f84   new buf size: 0
09:47:31:399   f84    PASC: 06/08/17-09:47:31 - New job from pasc-us-east1.nanopool.org:15555
09:47:31:400   f84   target: 0x000000001fffe000 (diff: 34GH)
 
newbie
Activity: 6
Merit: 0
Latest version is v9.5:

-tt   set target GPU temperature. For example, "-tt 80" means 80C temperature. You can also specify values for every card, for example "-tt 70,80,75".
   You can also set static fan speed if you specify negative values, for example "-tt -50" sets 50% fan speed. Specify zero to disable control and hide GPU statistics.
   "-tt 1" (default) does not manage fans but shows GPU temperature and fan status every 30 seconds. Specify values 2..5 if it is too often.
   Note: for NVIDIA cards only temperature monitoring is supported, temperature management is not supported.
   Note: for Linux gpu-pro drivers, miner must have root access to manage fans, otherwise only monitoring will be available.


@Claymore: are temps and fan speed available for RX 5xx with latest driver in Windows 10?  They display for NVIDIA cards but not for the 5xx series.

/c
sr. member
Activity: 249
Merit: 250
Guys, did you experience that if you restart the miner from Ethman in the most cases (8 from 10 times) the miner freeze/crash on the rig? Is it a known bug or I'm the lame? Smiley

I don't know if any of you guys use Awesome Miner to manage your rigs, but it works great especially if you mine with NiceHash.

New release seems to be working fine for me.  Not getting much of a performance improvement but stability seems fine for my rigs.  Running R9 290 and 290x's.
full member
Activity: 160
Merit: 100
Guys, did you experience that if you restart the miner from Ethman in the most cases (8 from 10 times) the miner freeze/crash on the rig? Is it a known bug or I'm the lame? Smiley
newbie
Activity: 11
Merit: 0
Hello.

Im minning with 6x KFA2 Geforce 1060. Windows 10 x64, and maximum mh's i get is 2.5 at the moment.. Zec and other coins are 280 sols. I want to know whats the trick, or why im getting so bad results on eth? Anybody have same problem?

Any thoughts?
newbie
Activity: 3
Merit: 0
I have a new setup on Windows 10 Pro and I'm getting terrible hashrates running 1070's. I have tried running 1 GPU and multiple GPUs with the same result. My other setup running the same Claymore settings runs fine, 28-29 Mh/s.
https://i.imgur.com/pHZTxR2.jpg

For some reason, the power consumption is only running about half of what it should be, and obviously temps indicate that the card isn't even trying.
https://i.imgur.com/M6vIlvI.jpg

Any suggestions? A few algorithms benchmark pretty slow in Nicehash, but some of them run at expected speeds (Lbry and Lyra primarily).

Windows 10 Pro, 8GB ram, 16GB pagefile
Asus Z270-AR
Intel Pentium G4560
Asus GTX 1070 Dual OC x 3 (directly plugged into MB)
378.78 drivers
Seasonic 750W
member
Activity: 101
Merit: 10
Dear,

In this morning, all rigs stop hashing, the error in Claymore is:
Unhandled Signal in divisionErrorHandler()

I try to reset couple times, and some of rigs are still get this error after couple hours of mining.

Could you figure out this problem?

Regards,
full member
Activity: 224
Merit: 102
MY RX580 gets 2m/h more with 9.5 version. Thanks!

My 470&480s gets 1 Mhs less on v9.5
newbie
Activity: 21
Merit: 0
MY RX580 gets 2m/h more with 9.5 version. Thanks!
sr. member
Activity: 318
Merit: 250
Why when I try to download this from either Google Drive or Mega do i get "Out of HTML5 offline storage space:  Your available browser storage for MEGA cannot handle this download size, please free up some disk space."
sr. member
Activity: 464
Merit: 252
Im mining on a 1070 and 2 480s. Trying to do ETH+SC on nanopool.

I have dcri 30 on my 1070  ~30Mh/s ETH and ~290Mh/s SC
I have dcri 8 on my 480 8gb  ~30Mh/s and ~240Mh/s SC

Are these in line or can I be doing more. I really want to focus on ETH. SC as a bonus.

My 6 Rx 480 8Gb give me 985mh/s Sia and 29.9/30.0 mg/s Eth using -dcr 24
newbie
Activity: 3
Merit: 0
What are the best drivers for rx570? The claymore miner recommends 15.12. I have a combo between the 16.XX and 17.XX but my hashrate is 22mh/s Sad
Jump to: