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

The only solution I found for the taking over 5 minutes to intialize Claymore.  Is reinstall os and not 'upgrade' to 1803.   Or  Reduce the number of card in rig to under 5 sometimes 6.   There is something that happened with 1803 that causes  claymore initializing process to take much longer.   To the point where if you have anything past 5 or 6 cards it times out at a hard coded 5 min.  Hope Claymore fixes this problem soon, if he can.   It might be a problem in the OS.  I've been wondering if I was the only one having this problem. 

I just had Bill on the phone. He confirmed we should wait at least 1803 minutes before some hashes appear. MS fee, just one time though.

is there 18.3.4 for Linux?

You can use "-oldkernels 1" if you don't like new kernels. A lot of modded BIOSes and OC settings were made for old kernels so new kernels can cause problems if you don't readjust these settings, "-oldkernels 1" option is the solution for this case.

Hi all,

I have two rigs mining on Ethermine with Claymore 11.7 and I copied the bat-file to the new rig. Is it ok like this and will it register right at the pool? Or do I have to name it differently? Seems like in principal no worker name is needed on Ethermine?

Thanks for any info

Maybe...
since the new kernels for polaris (around v 11) I've started to experience application crashes (maybe once in a week across some dozen workers), which never happened to me before. my guess is that this new behavior has to do with the driver.(I'm mostly using 18.2.2)  likely occurs with higher mem overclock
I have hw watchdogs so the machine would restart if the system hangs, so the new versions actually exhibit degraded performance, comparing to the previous ones in this regard.
I can configure the watchdogs to monitor for a certain process(will have issues switching algoes), or finally setup Chocolatey:)
But figuring out what exactly is wrong would be of course much nicer.

I'm using 372.54 drivers and still I can mine ethereum with all my 3gb cards..
I don't know for long again I could

I have the same problem any solutions?

376.33

for cards with 3GB and less

One of my rig updated windows a minutes ago and now does this. It closes Claymore without any error whatsoever. Checked the log, also no errors.
I can mine neoscrypt, equihash or x16r without problem, but when i try Claymore i get this:

C:\Users\xxx\Desktop\Claymore v11.7>EthDcrMiner64.exe -epool eu1.ethermine.org:4444 -ewal myaddress -epsw x -estale 0 -dpool stratum+tcp://xvg.eu1.unimining.net:5770 -dwal myotheraddress -dcoin blake2s -dcri 100

╔════════════════════════════════════════════════════════════════╗
║                Claymore's Dual GPU Miner - v11.7               ║
║              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             ║
╚════════════════════════════════════════════════════════════════╝

ETH: 1 pool is specified
Main Ethereum pool is eu1.ethermine.org:4444
B2S: 1 pool is specified
Main Blake2s pool is xvg.eu1.unimining.net:5770

C:\Users\miner5\Desktop\Claymore v11.7>pause
Press any key to continue . . .


Also tried mining with older version of Claymore miner, ethereum only mining and different drivers - its the same thing.
Anybody else?

Who sad?

System: WIN-10-64 bits, RAM: 4GB 2133 MHz, CPU: G3900, R9 295X2
Driver: 17.30.1029-170808a2-317304E-CrimsonReLive
Tested claymore starting from start.bat and after some seconds closes or crashes. Does anybody know the root cause? Thank you.
Here it is the log.

20:17:15:403   1a8   Check and remove old log files...
20:17:15:404   1a8   args: -epool eth-eu.dwarfpool.com:8008 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x -dpool stratum+tcp://dcr.suprnova.cc:3252 -dwal Redhex.my -dpsw x
20:17:15:405   1a8   
20:17:15:405   1a8   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:17:15:406   1a8   º                Claymore's Dual GPU Miner - v11.0               º
20:17:15:406   1a8   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
20:17:15:407   1a8   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:17:15:408   1a8   
20:17:15:408   1a8   b501
20:17:15:626   1a8   You specified default wallet address, it is good for tests only, for normal mining you must change it to your wallet address!
20:17:15:626   1a8   ETH: 1 pool is specified
20:17:15:626   1a8   Main Ethereum pool is eth-eu.dwarfpool.com:8008
20:17:15:626   1a8   DCR: 1 pool is specified
20:17:15:626   1a8   Main Decred pool is dcr.suprnova.cc:3252

The 11.7 version is with no fees? True? 

What about 18.10 for Ubuntu 16.04?
Currently I use:
amdgpu-pro 17.40-483984

Uncle, I just tested and can confirm that the 18.3.4 drivers don't drop to 0 and restart.

You can free use 18.3.4 - they working fine.

Thanks. That's what I use now. We'll see what will be with next drivers...

Win10 64Bit Version 10.0.16299.309
Claymore 11.7
GTX 1060 3GB x 8pcs , Driver 388.13 ( windows working on Intel iGPU ).
DAG 183 working fine ( in use 2621MB from 3072MB ) , DAG 184+ have error , like DAG size problem , but this is strange if we have like 400MB free ?

Any tip to fix this in windows 10 ? I know about windows 10 allocating more vram now ( for all cards ? or just desktop card ? ) like I see only ~70mb allocated from total 3072MB

Claymore, there is a libcurl3 package that can be installed (if libcurl4 is uninstalled).  However, 18.04 systems have other packages that depend on libcurl4.  Most notably for me virtualbox-5.2 and obs-studio.  I realize this would not be a problem for a dedicated mining rig, but some of us also do off-hours mining on our desktop rigs.

Fan management do not working. Only first videocard changing fan speed. Using option tt -70 or -70,70 with or without fanmin fanmax options. Only first card changes fan speed, rest cards uses firmware fan settings. Tried with different RX580 cards, also changed cards, windows drivers etc.