Author

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

newbie
Activity: 36
Merit: 0
I got some improve on my hash rate speed. Before it usually used to work at 177Mh/s and now 188Mh/s.
I did the same config for the 3 rigs I have and the total gain was 30Mh/s it is like I have gotten another GPU  Shocked

However I'm gonna monitor my graph on the pool and see if I really had some gain... Let's see!!

https://i.ibb.co/9WY90LR/cm147.png


- 17 Cards are Asus Radeon RX 580 OC 4GB - samsung memory
- 1 Card is Asus Radeon RX 580 OC 4GB - elpida memory


For me -strap and -rxboost were waste of time. They really increased the hash rate, but I was getting too much:
"GPU #0 got incorrect share. If you see this warning often, make sure you did not overclock it too much!"
So the hash rate reported by the pool decreased a little.

I was using:
-strap 2
-rxboost 21

And undervolting and overclocking with OverDriveNTool
-cvddc 870
-mvddc 850
-cclock 1170
-mclock 2010

Too much undervolt for memory... dont touch memory voltage at all
jr. member
Activity: 50
Merit: 11
Hi,

What is the latest Dev fee for v14.7?
newbie
Activity: 28
Merit: 1
I got some improve on my hash rate speed. Before it usually used to work at 177Mh/s and now 188Mh/s.
I did the same config for the 3 rigs I have and the total gain was 30Mh/s it is like I have gotten another GPU  Shocked

However I'm gonna monitor my graph on the pool and see if I really had some gain... Let's see!!

https://i.ibb.co/9WY90LR/cm147.png


- 17 Cards are Asus Radeon RX 580 OC 4GB - samsung memory
- 1 Card is Asus Radeon RX 580 OC 4GB - elpida memory


For me -strap and -rxboost were waste of time. They really increased the hash rate, but I was getting too much:
"GPU #0 got incorrect share. If you see this warning often, make sure you did not overclock it too much!"
So the hash rate reported by the pool decreased a little.

I was using:
-strap 2
-rxboost 21

And undervolting and overclocking with OverDriveNTool
-cvddc 870
-mvddc 850
-cclock 1170
-mclock 2010
newbie
Activity: 1
Merit: 0
My antivirus removed the file as soon as it was available.

So ill keep off until some more comments are available Smiley

i also got the Win32/Uwamson.A!ml Trojan horse virus.
full member
Activity: 1148
Merit: 132
Still crashes on Vega 56
member
Activity: 168
Merit: 15
Please add DAG epoch number in API responce.
Yes. Please!!!

And add best intensities found in auto tuning mode.
@Claymore, if you really want to add all that, please add a choice of what to show in web interface - there's too much data already (
newbie
Activity: 1
Merit: 0
Windows 10 and new XFX 580 8GB card.  I have updated the OS and AMD drivers.  Trying to run the install I get this info from the log:
Check and remove old log files...
16:21:52:637   494   args: -epool us1.ethpool.org:3333 -ewal  -mode 1 -tt 70 -rxboost 1 -lidag 0 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
16:21:52:639   494   
16:21:52:640   494   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
16:21:52:642   494   º                Claymore's Dual GPU Miner - v14.7               º
16:21:52:643   494   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
16:21:52:646   494   º                       Supercharged Edition                     º
16:21:52:647   494   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
16:21:52:649   494   
16:21:52:651   494   b745
16:21:52:853   494   ETH: 1 pool is specified
16:21:52:858   494   Main Ethereum pool is us1.ethpool.org:3333
16:21:53:093   494   OpenCL platform: AMD Accelerated Parallel Processing
16:21:53:098   494   OpenCL initializing...

16:21:53:101   494   AMD Cards available: 1
16:21:53:103   494   GPU #0: Ellesmere (Radeon RX 580 Series), 8192 MB available, 36 compute units (pci bus 1:0:0)
16:21:53:105   494   GPU #0 recognized as Radeon RX 480/580
16:21:53:107   494   POOL/SOLO version
16:21:53:109   494   Platform: Windows
16:21:53:284   494   start building OpenCL program for GPU 0...
16:21:53:939   494   done
16:21:54:189   494   GPU #0: algorithm ASM 1
16:21:54:193   494   cudaGetDeviceCount failed (35, CUDA driver version is insufficient for CUDA runtime version), probably no CUDA devices
16:21:54:196   494   No NVIDIA CUDA GPUs detected.
16:21:54:199   494   Total cards: 1
16:21:54:202   494   
Please consider using "-strap" option to increase mining speed, check Readme for details.

16:21:58:205   494   
You can use "+" and "-" keys to achieve best ETH speed, see "FINE TUNING" section in Readme for details.

16:21:59:207   494   No NVIDIA cards in the list, NVML library will not be used.
16:21:59:209   494   Driver is not installed! Trying to install it...
16:21:59:222   494   Driver is in use, try to start miner with "-driver uninstall" parameter.
16:22:00:443   494   SSL: Imported 47 certificates from local storage
16:22:00:491   259c   ETH: Stratum - connecting to 'us1.ethpool.org' <172.65.229.54> port 3333 (unsecure)
16:22:00:525   259c   sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x6aacd0c259bD5496205a4018f91deDf028281fFb", ""], "id": 2, "method": "eth_submitLogin"}

16:22:00:528   259c   ETH: Stratum - Connected (us1.ethpool.org:3333) (unsecure)
16:22:00:546   494   ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

16:22:00:552   494   ETH: eth-proxy stratum mode
16:22:00:555   494   Watchdog enabled
16:22:00:558   494   Remote management (READ-ONLY MODE) is enabled on port 3333
16:22:00:562   494   

16:22:00:567   494   You did not specify -dcri values directly, so they will be detected automatically
16:22:00:571   494   Automatic detection of best -dcri values started, please wait...

16:22:00:640   259c   buf: {"id":2,"jsonrpc":"2.0","result":true}

16:22:00:642   259c   ETH: Authorized
16:22:00:644   259c   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

16:22:00:726   259c   buf: {"id":0,"jsonrpc":"2.0","result":["0xfdf2fae80b46091d061159bfb20b05b722be62f1203f9bfe8eec4dec4fa15187","0x419e0d426d7007dadfc87e69afc4a36bcc31930b529e3df47d4e769a272c8975","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7a8567"]}

16:22:00:760   d9c   Setting DAG epoch #267...
16:22:01:889   26b0   GPU 0 temp = 39, old fan speed = 0, new fan speed = 70

16:22:03:343   259c   buf: {"id":0,"jsonrpc":"2.0","result":["0x5325836e155801a639c99e2c3b8e0d063818d9878012201240a6834dcfecaed3","0x419e0d426d7007dadfc87e69afc4a36bcc31930b529e3df47d4e769a272c8975","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7a8567"]}

16:22:03:349   259c   ETH: 06/25/19-16:22:03 - New job from us1.ethpool.org:3333
16:22:03:352   259c   target: 0x0000000112e0be82 (diff: 4000MH), epoch 267(3.09GB)
16:22:03:356   259c   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
16:22:03:359   259c   ETH: GPU0 0.000 Mh/s
16:22:04:899   26b0   GPU 0 temp = 39, old fan speed = 0, new fan speed = 55

16:22:05:322   d9c   Setting DAG epoch #267 for GPU0
16:22:05:325   d9c   Create GPU buffer for GPU0
16:22:05:336   d9c   GPU0 - not enough GPU memory to place DAG, you cannot mine this coin with this GPU
16:22:05:339   d9c   GPU0 - OpenCL error -4 - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

16:22:07:326   259c   buf: {"id":0,"jsonrpc":"2.0","result":["0xaa433c45529b0edfa43d7d6065da808cfdd2b6a1b9962a977e10f24b51a30c67","0x419e0d426d7007dadfc87e69afc4a36bcc31930b529e3df47d4e769a272c8975","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7a8567"]}

16:22:07:328   259c   ETH: 06/25/19-16:22:07 - New job from us1.ethpool.org:3333
16:22:07:333   259c   target: 0x0000000112e0be82 (diff: 4000MH), epoch 267(3.09GB)
16:22:07:336   259c   ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
16:22:07:339   259c   ETH: GPU0 0.000 Mh/s
16:22:07:909   26b0   GPU 0 temp = 39, old fan speed = 0, new fan speed = 40

16:22:08:341   d9c   Set global fail flag, failed GPU0
16:22:08:344   d9c   GPU 0 failed
16:22:08:346   1eb0   Setting DAG epoch #267 for GPU0
16:22:08:349   1eb0   GPU0, OpenCL error -38 - cannot write buffer for DAG

16:22:10:739   259c   ETH: checking pool connection...
16:22:10:741   259c   sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

16:22:10:826   259c   buf: {"id":0,"jsonrpc":"2.0","result":["0xaa433c45529b0edfa43d7d6065da808cfdd2b6a1b9962a977e10f24b51a30c67","0x419e0d426d7007dadfc87e69afc4a36bcc31930b529e3df47d4e769a272c8975","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7a8567"]}

16:22:10:893   1b8c   GPU 0 temp = 37, old fan speed = 0, new fan speed = 25

16:22:10:999   1b8c   Quit, please wait...
16:22:11:352   1eb0   Set global fail flag, failed GPU0
16:22:11:356   1eb0   GPU 0 failed

I took out my ewal number.  What am I missing?  Thank you.
full member
Activity: 144
Merit: 100
What could be the reason for this message?

"opencl error -4 cannot write buffer DAG" after that miner freezes and I have to restart the rig.


I have virtual memory set to 20+ gigs on 8 GPU rig

use virtual file 8gpu x gpu ram size, for example 8x 4 = 32gb if u have 4gb cards. if you have 8gb, then 64gb cards and u are safe for future dag size+ some miners are option to use double size.


I had around 32 gigs actually, and now increased it to 38gigs. I no longer get the error message, however the miner crashes after a minute of mining, and nothing is written in the log file. I am mining with the default clock values and 14.7 miner
It just crashed with one GPU mining and 42 gigs. Any troubleshooting tips?
jr. member
Activity: 200
Merit: 3
v14.7:

- now the miner driver does not require switching Windows to Test Mode. If you want to turn Test Mode off, use "-driver uninstall" option (with admin rights) and reboot,
   then start miner with admin rights to install new driver automatically when necessary (or use "-driver install" option directly).
   If you have any problems with signed driver you can use "-driver install_test" option, it uses old approach: enables Test Mode (reboot is required) and installs unsigned driver.
- added "-showpower" option for stats about GPU power consumption, press "s" to see it. Both AMD and Nvidia cards are supported, except Linux gpu-pro drivers and Radeon7 cards.
- updated Remote Manager to show total power consumption.
- fixed issue with "-logsmaxsize" option when "-logfile" option is used to specify directory for log files.
- a few minor bug fixes and improvements.
Please add DAG epoch number in API responce.


Yes. Please!!!

And add best intensities found in auto tuning mode.
full member
Activity: 144
Merit: 100
What could be the reason for this message?

"opencl error -4 cannot write buffer DAG" after that miner freezes and I have to restart the rig.


I have virtual memory set to 20+ gigs on 8 GPU rig

use virtual file 8gpu x gpu ram size, for example 8x 4 = 32gb if u have 4gb cards. if you have 8gb, then 64gb cards and u are safe for future dag size+ some miners are option to use double size.


I had around 32 gigs actually, and now increased it to 38gigs. I no longer get the error message, however the miner crashes after a minute of mining, and nothing is written in the log file. I am mining with the default clock values and 14.7 miner
full member
Activity: 1209
Merit: 209
v14.7:

- now the miner driver does not require switching Windows to Test Mode. If you want to turn Test Mode off, use "-driver uninstall" option (with admin rights) and reboot,
   then start miner with admin rights to install new driver automatically when necessary (or use "-driver install" option directly).
   If you have any problems with signed driver you can use "-driver install_test" option, it uses old approach: enables Test Mode (reboot is required) and installs unsigned driver.
- added "-showpower" option for stats about GPU power consumption, press "s" to see it. Both AMD and Nvidia cards are supported, except Linux gpu-pro drivers and Radeon7 cards.
- updated Remote Manager to show total power consumption.
- fixed issue with "-logsmaxsize" option when "-logfile" option is used to specify directory for log files.
- a few minor bug fixes and improvements.
Please add DAG epoch number in API responce.
jr. member
Activity: 169
Merit: 1
What could be the reason for this message?

"opencl error -4 cannot write buffer DAG" after that miner freezes and I have to restart the rig.


I have virtual memory set to 20+ gigs on 8 GPU rig

use virtual file 8gpu x gpu ram size, for example 8x 4 = 32gb if u have 4gb cards. if you have 8gb, then 64gb cards and u are safe for future dag size+ some miners are option to use double size.
member
Activity: 168
Merit: 15
What could be the reason for this message?

"opencl error -4 cannot write buffer DAG" after that miner freezes and I have to restart the rig.


I have virtual memory set to 20+ gigs on 8 GPU rig
each card requires DAG size of memory (3+ Gb for ETH now) + some memory for Windows. you need up to 30 Gb swap
newbie
Activity: 55
Merit: 0
What could be the reason for this message?

"opencl error -4 cannot write buffer DAG" after that miner freezes and I have to restart the rig.


I have virtual memory set to 20+ gigs on 8 GPU rig

Check your risers. I had that recently, I unplugged, gave them a blast out and away I went.
full member
Activity: 144
Merit: 100
What could be the reason for this message?

"opencl error -4 cannot write buffer DAG" after that miner freezes and I have to restart the rig.


I have virtual memory set to 20+ gigs on 8 GPU rig
jr. member
Activity: 169
Merit: 1
hello,

i have latest wn 10, amd 19.5.2 and claymore 14.7 and despsite i use rxboost or strapo value, still getting same ahsrate with or without it.
i had 14.6, downloaded 14.7, used driver uninstall, rebooted, then driver install, again reboot but still getting same hash.

it wrote rxoption is applied succesfuly, same for strap, but i do not see any changes in hashrate...any advice what could be wrong?

The latest Win10 has a new feature called Tamper Protection.  It seems to prevent writing directly to the card's I2C interfaces even with the proper driver.  That may be the problem.  I found that it would prevent AMDMemTweak from adjusting the values as well.  You can turn it off but I can't recall how.  It gave me the option at one point and I took it.

Might not be your problem, but worth a look.  I've been bouncing around with various versions of the AMD driver as well trying to get around this.  I found that 19.6.2 would crash on my machine when going to the settings page.  I backed off to 19.5.2 and it works ok.  I'm only running Claymore 11.9 though.  Waiting for the 14.x to stabilize.

well i have disable windows defender in group policies... tamper protection is disabled, however i can see realtime protection is still on...so will try tomorrow disable realtime protection and will see how it will go.

EDIT: no chance after disabling realtime protection...
member
Activity: 168
Merit: 15
Hello! Is there a way to connect to pools via external proxy/socks?
jr. member
Activity: 73
Merit: 3
hello,

i have latest wn 10, amd 19.5.2 and claymore 14.7 and despsite i use rxboost or strapo value, still getting same ahsrate with or without it.
i had 14.6, downloaded 14.7, used driver uninstall, rebooted, then driver install, again reboot but still getting same hash.

it wrote rxoption is applied succesfuly, same for strap, but i do not see any changes in hashrate...any advice what could be wrong?

The latest Win10 has a new feature called Tamper Protection.  It seems to prevent writing directly to the card's I2C interfaces even with the proper driver.  That may be the problem.  I found that it would prevent AMDMemTweak from adjusting the values as well.  You can turn it off but I can't recall how.  It gave me the option at one point and I took it.

Might not be your problem, but worth a look.  I've been bouncing around with various versions of the AMD driver as well trying to get around this.  I found that 19.6.2 would crash on my machine when going to the settings page.  I backed off to 19.5.2 and it works ok.  I'm only running Claymore 11.9 though.  Waiting for the 14.x to stabilize.
newbie
Activity: 1
Merit: 0
I have some test rig on windows machine with some different cards and with latest 14.7 I saw a nice new feature - showing power consumption of every card and total of the rig. But for some reason there is no info on power consumption on my R9 380 (GPU2 on log). Is there any way to fix it by me or it's just a bug?

Code:
GPU0 t=63C fan=87% P=52W, GPU1 t=62C fan=56% P=81W, GPU2 t=59C fan=33%, GPU3 t=62C fan=62% P=75W, GPU4 t=55C fan=60% P=74W
Total GPUs power consumption: 282 Watts
Adrenalin 19.4.3
Windows 10 LTSC 1809
newbie
Activity: 28
Merit: 1
I got some improve on my hash rate speed. Before it usually used to work at 177Mh/s and now 188Mh/s.
I did the same config for the 3 rigs I have and the total gain was 30Mh/s it is like I have gotten another GPU  Shocked

However I'm gonna monitor my graph on the pool and see if I really had some gain... Let's see!!

https://i.ibb.co/9WY90LR/cm147.png


- 17 Cards are Asus Radeon RX 580 OC 4GB - samsung memory
- 1 Card is Asus Radeon RX 580 OC 4GB - elpida memory
Jump to: