Author

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

newbie
Activity: 8
Merit: 0
sr. member
Activity: 1484
Merit: 253
why -cvddc does not effect on AMD cards in windows? Huh Huh Huh Huh

any reason Huh

yes there is reason

if you know the reason say it
DO NOT SPAM


why -cvddc does not effect on AMD cards in windows? Huh Huh Huh Huh

any reason Huh

Please be more specific. What Windows? What cards? What drivers?
On my Windows 10 x64 Pro AMD 18.3.4 on RX 580 cvddc works. On 270X didn't work.


windows 10 X64
AMD 22.19.695   (blockchain driver)
rx 470

Use 18.3.4. driver with ati dirvers patcher.
newbie
Activity: 14
Merit: 0
6x Sapphire Nitro+ RX 580 8GB with Micron memory clocked at 1170/2200MHz with 850/850mv and -20% power limit doing 192.9 mhs eth at little under 810w. Using the nanopool i get average hashrates over the reported ones. (usually, 4 out of 7 days, in the rest, really close to reported, max 10 mhs less)
PS: Check the GPUz reported consumption. 80w... Also check my highest temps which are 51 and 52* degrees celcius with the fan at only 37% in a warm room, around 25* today, for example. One last thing, no incorrect shares, not even 1 memory error reported in hwinfo, not one.

https://image.ibb.co/bygsTy/32324939_1663807277070731_5687913318526746624_o.jpg
https://image.ibb.co/euOjad/32416549_1663806050404187_7786284067036594176_n.jpg
https://image.ibb.co/hQ2cvd/32423238_1663806450404147_7487452397338361856_n.jpg


what device do you have to meassure de electrical power Huh
newbie
Activity: 197
Merit: 0
why -cvddc does not effect on AMD cards in windows? Huh Huh Huh Huh

any reason Huh

yes there is reason

if you know the reason say it
DO NOT SPAM


why -cvddc does not effect on AMD cards in windows? Huh Huh Huh Huh

any reason Huh

Please be more specific. What Windows? What cards? What drivers?
On my Windows 10 x64 Pro AMD 18.3.4 on RX 580 cvddc works. On 270X didn't work.


windows 10 X64
AMD 22.19.695   (blockchain driver)
rx 470
newbie
Activity: 8
Merit: 0
6x Sapphire Nitro+ RX 580 8GB with Micron memory clocked at 1170/2200MHz with 850/850mv and -20% power limit doing 192.9 mhs eth at little under 810w. Using the nanopool i get average hashrates over the reported ones. (usually, 4 out of 7 days, in the rest, really close to reported, max 10 mhs less)
PS: Check the GPUz reported consumption. 80w... Also check my highest temps which are 51 and 52* degrees celcius with the fan at only 37% in a warm room, around 25* today, for example. One last thing, no incorrect shares, not even 1 memory error reported in hwinfo, not one.

https://image.ibb.co/bygsTy/32324939_1663807277070731_5687913318526746624_o.jpg
https://image.ibb.co/euOjad/32416549_1663806050404187_7786284067036594176_n.jpg
https://image.ibb.co/hQ2cvd/32423238_1663806450404147_7487452397338361856_n.jpg
legendary
Activity: 2254
Merit: 2253
From Zero to 2 times Self-Made Legendary
I have noticed one of my mining rig stop or restart every so often and I was wondering if anyone could help me find a solution to this problem.

This is my bat file
Code:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool us-east.ethash-hub.miningpoolhub.com:20535 -ewal arkalab.eth01 -eworker arkalab.eth01 -epsw x -esm 2 -mode 1 -platform 2 -cclock -200,-200,-200,-200,-200,-200 -mclock +650,+650,+650,+600,+600,+600 -powlim -30,-30,-30,-30,-30,-30 -tt -70,-70,-70,-70,-80,-85
pause

and this is my Log File for the issue
Code:
05:32:29:039	3d8	ETH: 05/13/18-05:32:29 - New job from us-east.ethash-hub.miningpoolhub.com:20535
05:32:29:041 3d8 target: 0x00000000ffb34c02 (diff: 4300MH), epoch 186(2.45GB)
05:32:29:043 3d8 ETH - Total Speed: 214.160 Mh/s, Total Shares: 6, Rejected: 0, Time: 00:02
05:32:29:045 3d8 ETH: GPU0 32.990 Mh/s, GPU1 33.097 Mh/s, GPU2 33.111 Mh/s, GPU3 31.570 Mh/s, GPU4 51.967 Mh/s, GPU5 31.426 Mh/s
05:32:29:473 212c checked ETH share on CPU, spent 5ms
05:32:29:475 212c sent: {"id": 12, "method": "mining.submit", "params": ["arkalab.eth01","e00e","0x855cbfac0099e783","0x8aa4b6811007cfcbcc6f3dce84fc9d2b67defc1c42c7a265a2be7f69ccc39de8","0x8ed1fe8e7a45e7cc250afd976c2b9ecb246f627904589cd8b1fd46920f7099ac"]}

05:32:29:477 212c ETH: put share nonce 855cbfac0099e783
05:32:29:481 3d8 ETH: 05/13/18-05:32:29 - SHARE FOUND - (GPU 2)
05:32:29:721 3d8 buf: {"id":12,"result":true,"error":null}

05:32:29:722 3d8 ETH: Share accepted (250 ms)!

05:32:42:908 e7c GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:913 e7c GPU 5, GpuMiner kx failed 1
05:32:42:915 e7c Set global fail flag, failed GPU5
05:32:42:917 e7c GPU 5 failed
05:32:42:919 252c GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:925 252c GPU 5, GpuMiner kx failed 1
05:32:42:928 19c0 GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:930 212c GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:927 252c Set global fail flag, failed GPU5
05:32:42:937 252c GPU 5 failed
05:32:42:941 212c GPU 2, GpuMiner kx failed 1
05:32:42:948 19c0 GPU 0, GpuMiner kx failed 1
05:32:42:947 212c Set global fail flag, failed GPU2
05:32:42:954 e8c GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:952 19c0 Set global fail flag, failed GPU0
05:32:42:958 212c GPU 2 failed
05:32:42:964 1b9c GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:967 e8c GPU 1, GpuMiner kx failed 1
05:32:42:970 19c0 GPU 0 failed
05:32:42:972 1f44 GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:974 1b9c GPU 2, GpuMiner kx failed 1
05:32:42:976 2790 GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:42:980 2790 GPU 4, GpuMiner kx failed 1
05:32:42:985 2790 Set global fail flag, failed GPU4
05:32:42:988 2790 GPU 4 failed
05:32:42:976 1b9c Set global fail flag, failed GPU2
05:32:42:979 3d8 sent: {"id":6,"worker":"arkalab.eth01","jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6f5f8bc", "0x0000000000000000000000000000000000000000000000000000000016477d18"]}

05:32:42:970 e8c Set global fail flag, failed GPU1
05:32:42:995 e8c GPU 1 failed
05:32:42:999 2494 GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:002 2328 GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:008 1b9c GPU 2 failed
05:32:43:014 1f44 GPU 0, GpuMiner kx failed 1
05:32:43:020 1f44 Set global fail flag, failed GPU0
05:32:43:029 1f44 GPU 0 failed
05:32:43:032 2328 GPU 4, GpuMiner kx failed 1
05:32:43:039 2b4 GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:041 2494 GPU 3, GpuMiner kx failed 1
05:32:43:038 2328 Set global fail flag, failed GPU4
05:32:43:047 2328 GPU 4 failed
05:32:43:044 2494 Set global fail flag, failed GPU3
05:32:43:054 2b4 GPU 1, GpuMiner kx failed 1
05:32:43:063 2494 GPU 3 failed
05:32:43:070 2588 GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
05:32:43:062 2b4 Set global fail flag, failed GPU1
05:32:43:079 2588 GPU 3, GpuMiner kx failed 1
05:32:43:085 2b4 GPU 1 failed
05:32:43:085 2588 Set global fail flag, failed GPU3
05:32:43:089 2588 GPU 3 failed
05:32:43:221 3d8 buf: {"id":6,"result":true,"error":null}

05:32:43:934 bb0 em hbt: 0, fm hbt: 78,
05:32:43:935 bb0 watchdog - thread 0 (gpu0), hb time 1188
05:32:43:936 bb0 watchdog - thread 1 (gpu0), hb time 1063
05:32:43:938 bb0 watchdog - thread 2 (gpu1), hb time 1110
05:32:43:939 bb0 watchdog - thread 3 (gpu1), hb time 1235
05:32:43:940 bb0 watchdog - thread 4 (gpu2), hb time 1172
05:32:43:942 bb0 watchdog - thread 5 (gpu2), hb time 1047
05:32:43:943 bb0 watchdog - thread 6 (gpu3), hb time 1063
05:32:43:945 bb0 watchdog - thread 7 (gpu3), hb time 1188
05:32:43:946 bb0 watchdog - thread 8 (gpu4), hb time 1188
05:32:43:947 bb0 watchdog - thread 9 (gpu4), hb time 1047
05:32:43:949 bb0 watchdog - thread 10 (gpu5), hb time 1406
05:32:43:950 bb0 watchdog - thread 11 (gpu5), hb time 1953
05:32:43:951 bb0 WATCHDOG: GPU error, you need to restart miner :(
05:32:45:414 bb0 Restarting OK, exit...



And how to put the right value for -eres function.The default value is 2, but i dont know what the effect if i increase or decrease the value through this -eres command line
newbie
Activity: 13
Merit: 0
the reason is not important. do not use miner restart. AMD drivers is the major factor anyways. Instead do system reboot using "-r 1" flag and reboot.bat (in the same folder) with the following content: "shutdown /r /t 5 /f".

I have created reboot.sh with "reboot -f" command in Claymore's program folder.
But problem ist if I test it:
sudo reboot -f
or
sudo shutdown -r
the rig does not reboot but it freezes with black screen instead. I have to physically switch off the power to start it again.
jr. member
Activity: 100
Merit: 6
Question here, do I loose speed or shares by using the ssl port, 5555?

Is there realy any advantage by using SSL? Got the -mport set at 0 any ways



 do I loose speed or shares by using the ssl port, 5555? - nope

Is there realy any advantage by using SSL? -  communication is secured by strong encryption algorithms and the server's identity is digitally signed by a certificate authority. man in the middle attack is not possible
newbie
Activity: 72
Merit: 0
Question here, do I loose speed or shares by using the ssl port, 5555?

Is there realy any advantage by using SSL? Got the -mport set at 0 any ways

jr. member
Activity: 113
Merit: 1
wow the diff have really gone up..  Ethermine.org reporting 3,523.58T...

people are really jumping on board the recent increase in price...  sigh...  Oh well.. 
newbie
Activity: 14
Merit: 0
Last windows update is problem. Nvidia driver is struggling with it. Go back 2- 3 driver and try. I have 1070s working @ 391.35 and windows updated ( well, still some weird behavior )....AMD also have problems, older cards newer drivers and update. I have 480 reference that no driver works normally with last W10 update. Anybody share experiences?

i have tryed with nvidia drivers 391.35 and not works...
i have tryed with nvidia drivers 376.33 and not works...

I am goint to revert the update...


Set up metered connection in windows settings for windows updates and it wont auto update.

I had revert the update and now i can mining fine with the latest nvidia drivers (397.64).

I recommend that nobody update to the latest windows 10 version "April 2018 Update"

I recommend desactivate the update options in windows 10, so it not update for his own.

regards,thanks
sr. member
Activity: 574
Merit: 261
Hi all, i have read many pages and lost many hours but i don't find the answer....
Sapphire rx 550 2gb, not works with any version of claymore, Ethereum and ethereum classic do not work ok, but Muscoin is the same problem, errod DAG...

What is the right command to working with 2gb memory?? Any possibility to mine directly ethereum with this card ?_?

what's you config settings?

EthDcrMiner64.exe -epool europe.ethash-hub.miningpoolhub.com:20585 -ewal name -eworker name -esm 2 -allcoins 1 -epsw x -lidag 1 -eres 0

I have tried without lidag and eres or change the other..same message error...you cannot mine this coin with this gpu..

You cannot mine Ethereum or Ethereum Classic with a 2GB card the DAG sizes for these coins in now in excess of 2GB, but you should still be able to mine Musicon as it's DAG is only 1.66GB. You can still mine the Cryptonight variant coins with a 2GB card.
https://investoon.com/tools/dag_size
newbie
Activity: 20
Merit: 0
Last windows update is problem. Nvidia driver is struggling with it. Go back 2- 3 driver and try. I have 1070s working @ 391.35 and windows updated ( well, still some weird behavior )....AMD also have problems, older cards newer drivers and update. I have 480 reference that no driver works normally with last W10 update. Anybody share experiences?

i have tryed with nvidia drivers 391.35 and not works...
i have tryed with nvidia drivers 376.33 and not works...

I am goint to revert the update...


Set up metered connection in windows settings for windows updates and it wont auto update.
newbie
Activity: 14
Merit: 0
Last windows update is problem. Nvidia driver is struggling with it. Go back 2- 3 driver and try. I have 1070s working @ 391.35 and windows updated ( well, still some weird behavior )....AMD also have problems, older cards newer drivers and update. I have 480 reference that no driver works normally with last W10 update. Anybody share experiences?

i have tryed with nvidia drivers 391.35 and not works...
i have tryed with nvidia drivers 376.33 and not works...

I am goint to revert the update...

newbie
Activity: 13
Merit: 0
Gpu4 oc'd too much?
There are 2 more same GPUs with the same modded BIOS.

the reason is not important. do not use miner restart. AMD drivers is the major factor anyways. Instead do system reboot using "-r 1" flag and reboot.bat (in the same folder) with the following content: "shutdown /r /t 5 /f".
Could you please give me command for Linux?
legendary
Activity: 1030
Merit: 1006
newbie
Activity: 14
Merit: 0
i have try with nvidia drivers 391.35 that i have in the past. The fail is the same. Maybe this fail is in the new windows version??
newbie
Activity: 14
Merit: 0
I have update my windows 10 to the lastes update "April 2018 Update" and update to the lastes nvidia drivers 397.64, now i can´t use the claymore´s it give a fail, and it was working fine before update.

The program say that CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
My cards are GTX 1050Ti 4GB and GTX 1070 8GB

Code:
21:12:14:755 249c NVIDIA Cards available: 6
21:12:14:755 249c CUDA Driver Version/Runtime Version: 9.2/8.0
21:12:15:161 249c GPU #0: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 1:0:0)
21:12:15:176 249c GPU #1: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1  (pci bus 8:0:0)
21:12:15:176 249c GPU #2: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 12:0:0)
21:12:15:192 249c GPU #3: GeForce GTX 1050 Ti, 4096 MB available, 6 compute units, capability: 6.1  (pci bus 13:0:0)
21:12:15:208 249c GPU #4: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 14:0:0)
21:12:15:223 249c GPU #5: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1  (pci bus 15:0:0)
21:12:15:223 249c Total cards: 6
21:12:17:676 249c NVML version: 9.397.64
21:12:19:800 249c SSL: Imported 43 certificates from local storage
21:12:19:832 221c ETH: Stratum - connecting to 'europe.ethash-hub.miningpoolhub.com' <18.197.166.72> port 20535 (unsecure)
21:12:19:894 221c sent: {"id": 1, "method": "mining.subscribe", "params": []}
.
.
.
.
.
21:12:20:410 221c ETH: Authorized
21:12:22:081 3dc Setting DAG epoch #186 for GPU5
21:12:22:081 231c Setting DAG epoch #186 for GPU4
21:12:22:081 26bc Setting DAG epoch #186 for GPU2
21:12:22:081 358 Setting DAG epoch #186 for GPU0
21:12:22:081 2578 Setting DAG epoch #186 for GPU1
21:12:22:081 1f40 Setting DAG epoch #186 for GPU3
21:12:22:081 1f40 Create GPU buffer for GPU3
21:12:22:081 2578 Create GPU buffer for GPU1
21:12:22:081 3dc Create GPU buffer for GPU5
21:12:22:081 358 Create GPU buffer for GPU0
21:12:22:081 26bc Create GPU buffer for GPU2
21:12:22:081 231c Create GPU buffer for GPU4
21:12:22:425 358 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

21:12:22:440 2578 CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

21:12:25:455 2578 Set global fail flag, failed GPU1
21:12:25:455 358 Set global fail flag, failed GPU0
21:12:25:455 368 Setting DAG epoch #186 for GPU1
21:12:25:455 358 GPU 0 failed
21:12:25:455 2578 GPU 1 failed
21:12:25:455 368 GPU 1, CUDA error 11 - cannot write buffer for DAG

21:12:25:455 314 Setting DAG epoch #186 for GPU0
21:12:25:455 314 GPU 0, CUDA error 11 - cannot write buffer for DAG

21:12:28:470 368 Set global fail flag, failed GPU1
21:12:28:470 368 GPU 1 failed
21:12:28:486 314 Set global fail flag, failed GPU0
21:12:28:486 314 GPU 0 failed
21:12:29:986 231c GPU4 DAG creation time - 7560 ms
21:12:29:986 231c Setting DAG epoch #186 for GPU4 done
21:12:30:110 26bc GPU2 DAG creation time - 7565 ms
21:12:30:110 26bc Setting DAG epoch #186 for GPU2 done
21:12:30:173 3dc GPU5 DAG creation time - 7550 ms
21:12:30:173 3dc Setting DAG epoch #186 for GPU5 done
sr. member
Activity: 1484
Merit: 253
why -cvddc does not effect on AMD cards in windows? Huh Huh Huh Huh

any reason Huh

Please be more specific. What Windows? What cards? What drivers?
On my Windows 10 x64 Pro AMD 18.3.4 on RX 580 cvddc works. On 270X didn't work.

A tip on voltage changing for R9 270x.
You can change the voltage on an R9 270x with Afterburner, althought the manila version of AB will not let you do it there is a tweak (which I am using) to let you change the core voltage. https://rog.asus.com/forum/archive/index.php/t-81916.html

The image below shows the core voltage adjustment is not greyed out anymore.




I don't want to use AB. For RX 580 card I use miner's settings. For 270X I flashed voltage in bios.
sr. member
Activity: 574
Merit: 261
why -cvddc does not effect on AMD cards in windows? Huh Huh Huh Huh

any reason Huh

Please be more specific. What Windows? What cards? What drivers?
On my Windows 10 x64 Pro AMD 18.3.4 on RX 580 cvddc works. On 270X didn't work.

A tip on voltage changing for R9 270x.
You can change the voltage on an R9 270x with Afterburner, althought the manila version of AB will not let you do it there is a tweak (which I am using) to let you change the core voltage. https://rog.asus.com/forum/archive/index.php/t-81916.html

The image below shows the core voltage adjustment is not greyed out anymore.



Jump to: