Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[bigdaddymccarron]

Could you possibly show the power the cards are using?

[induktor]

Hello, I just like to report that, newer versions (11,2 forward, crashes with the OhGodACompany's Enlargement pill mempatch with GTX 1080s) Nvidia driver crash, doesn't happen with 9.8 Version, which works just fine.
without the mempatch works fine but the hash rate on the 1080 is a joke due to the GDDR5X memory.
Lubuntu 14.04 , driver 378.09

actually i noticed that 11.6 does that (low hash rate with ethelargement pill), but 11.4 runs fine at 50+ mhs. driver doesnt crash on 11.6, just low hash rate. havent tried 11.7 yet.

thought it just operator error on my part.have 2 1080tis on ethlargment.

Thanks!, interesting!, I will download 11.4, i don't have it, i tested 11.2, 11.6 and 11.7 also 9.8 , 9.7 and 9.4.
there is a new 11.8 will test it now.

Could you possibly show the power the cards are using?

me?, TPL power used?

1080 top efficiency is at 100W TPL
1080 Ti top efficiency is at 140W TPL

[kgminer]

Could you possibly show the power the cards are using?

Vote for this feature

[mijnerke]

Could you possibly show the power the cards are using?

Vote for this feature

+1

[74hawksfan]

Hello,
Just set up Asus B250 board with 13 AMD RX 580's, this is my 4th miner and 2nd AMD rig exactly like this one.
Weird thing happening...when I start the CM miner, it gives me nothing past the start up screen:
Eth: 1 pool is specified
Main Ethereum pool is eth.suprnova.cc:5005
DCR: 0 pool is specified

Then after 5 minutes (apperently) it says:
Miner cannot initialize for 5 minutes, need to restart miner!

Here is command line:
ethdcrminer64.exe -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1


I have a funny feeling it's to do with Windows Defender, because since I've been trying to get this thing working for the last few days, it never popped up and asked for me to Allow it through the firewall...but idk for sure. I shut it off and still no action.

I would post a pic to make it easier but I cannot figure out how to do that :-)

Hey there,
So you have debug on, what do your logs tell you?

Try adding

-di 0

Start with GPU0 only, would be a good thing to try, as you could be overloading your PSUs.
If it's a new rig, never been running/stable, break it down, get through the init on one GPU, prove your config and basic hw/sw enviro, and take it from there.

jooi, what PSU are you using, and how many GPU on each, how many risers per cable?

Kudos on the 13gpu rig man, not so easy to get those stable.

Good luck.


footnote:
Try this.

setx GPU_FORCE_64BIT_PTR 1
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 ssl://eu1.ethermine.org:5555 -ewal wallet.rig -epsw x -di 0 -gser 1 -esm 0 -etha 0 -ethi 16 -eres 2 -erate 1 -estale 1 -asm 1 -platform 1 -y 1 -dcri 9 -wd 1 -ftime 5 -r 1440 -cclock 1200 -cvddc 900 -mclock 2100 -mvddc 850 -tstop 83 -tstart 50 -tt 60 -fanmin 40 -fanmax 100 -ttdcr 80 -ttli 80 -mode 1 -dbg 1 -altnum 3 -mport -3333 -mpsw whatever -logfile logs\

So that was a great idea taking the cards out and just doing 1, I should have tried that before posting.  Unfortunately it didn't work, same result. Here is the last log file, the others say the exact same thing :-(

20:25:58:457   1460   Check and remove old log files...
20:25:58:457   1460   args: -epool eth.suprnova.cc:5005 -ewal ***.*** -epsw * -esm 3 -allpools 1 -dbg 1
20:25:58:457   1460   
20:25:58:457   1460   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
20:25:58:457   1460   º                Claymore's Dual GPU Miner - v11.7               º
20:25:58:457   1460   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
20:25:58:457   1460   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
20:25:58:457   1460   
20:25:58:457   1460   b583
20:25:58:685   1460   ETH: 1 pool is specified
20:25:58:685   1460   Main Ethereum pool is eth.suprnova.cc:5005
20:25:58:685   1460   DCR: 0 pool is specified
20:26:31:509   d48   
20:27:04:325   d48   
20:27:37:141   d48   
20:28:09:957   d48   
20:28:42:541   d48   



2x 1,200 watt gold psu's, even distrubuted as with my other one.
and only 2 risers per sata leg

Thank you for you help!

OK, will it sounds like your PSU and topology is thought through, so maybe leave that for now.
Could you post the debug log, from the batch file I added above?

(Just to rule out the pool angles, as I have no experience with suprnova, and Ethermine, being pretty much the biggest there is, makes for a good choice when testing, even if you don't plan on mining with those guys).

Now that said, what SHOULD be happening at this stage is the init of OpenCL, (or CUDA if you're using Nvidia).
OpenCL is managed via the AMD driver, so assuming you don't have a problem with the pool, I think you need to investigate if OpenCL is available.

One way to do that, (with a only single GPU in the rig), is you use GPU-z, and see if the OpenCL check box is populated.

Now, I have also seen perfectly good working rigs, where that checkbox is NOT populated, and clearly that is wrong, so to be absolutely sure, you (again with only 1 GPU in the rig), could boot to safe mode, DDU, reboot, install the AMD driver, set to compute, reboot, and check GPU-z, I have never seen that fail to confirm OpenCL.

From there, try my batch file again, and post the log if you're still stuck.
Good luck

Also, VM? Set to 48000GB if need be.

Foot note, in case anyone needs convincing of the single GPU method. If you do a clean AMD driver install with 13GPU, this alone can take hours, more so, if it fails, and AMD themselves STILL have an open bug on init fail with more than 12GPU.

Often when testing theories, working through troubleshooting etc, this is time consuming, and for sure you probably work at testing, (proving) some angles that were perfectly fine to start with. Time is not wasted of course, as you can cross those off the list, elimination of them, takes you closer to the answer.
But all the same, if you have multiple GPU, that's an exponential multiplier on the possibilities of fault, and means more time to troubleshoot is a given.
Breaking it down to basics, (you only need to pull the USB cables from the MB, for the most part), is pretty quick, you don't need to physically remove the GPUs etc, means you can run DDU, and reinstall the AMD driver with the minimum time consumed, and get back to starting Claymore as quickly as possible.

AMD driver install time, is pretty acceptable with a single GPU, but 12 and 13 is really nasty, and I have seen that fail many times, so working on proof of concept with a single GPU is by far the fastest, and most likely to provide solutions imho.

BTW 18.3.4 is a stable driver for mining.
Note: there is NOTHING mentioned in any release notes from AMD, on any mining related improvements in the drivers release since 18.3.4.
That is not to say the newer drivers are bad, (some are though), but simply, 18.3.4 has been out for a while, rolls up all the mining related things you probably need for RX570/580 hardware, and has proved itself far more than any of the drivers released since then. So, if you're going to DDU etc, I'd suggest 18.3.4 is a good choice, known good, known stable, well proven choice, and when you're troubleshooting, you need to focus on elimination of doubt. Go with what you know, (is good).

I was wondering why niether of the cuda opencl boxes were checked, and there has been an error that GPU-Z gives me when I open it or switch cards. I installed W10 1709 I believe then it updated to 1803, so I reverted back and have had strange things since. So I'mma do a fresh install and see what happens, I was able to flash the mod bios already so I don't really need atiflash to work anyway so I'll try 1803 fresh.
Thank you so much!

No worries, wow, that is a nasty situation with win updates. But before you roll back, it would be very helpful to know, if the DDU, clean install, or alternatively a manual driver install in devman as Ursul0 pointed out, gets you anywhere.

Because one would hope that DDU/clean install-driver option is an available solution.

But indeed, you could be right, I have seen some systems in a real mess after a OS roll back, and while that isn't to say that applies in your case, it's always one of those nasty things that sow the seeds of doubt later.

Also, you might like to set all your NICs to metered connection, that at least for the most part, prevents MS from updating your rig, or if nothing else, gives you some warning when they try to.

Regedit
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\DefaultMediaCost]

Grant your user "folder" permissions, and change all NICs to dword 2.
e.g.
"3G"=dword:00000002
"4G"=dword:00000002
"Default"=dword:00000002
"Ethernet"=dword:00000002
"WiFi"=dword:00000002

It won't help you with your current problem, but might be useful on your rigs
Good luck.

Same result after multiple DDU removes and fresh GPU driver installs.  Spent today doing fresh install of 1803, which as soon as I installed 7 or more GPU's the thing would just crawl to a snails pace...lagging so heavy I couldn't handle it.
Then did a fresh install of 1709, super quick, no BSOD during install, no freezes, smooth.  Got driver installed and all the W10 tweaks done, tried to install Hwinfo64 after all the oc/uv was complete...Hwinfo64 stops working almost immediately after starting it up, gets stuck and freezes on "checking system configuration - analyzing pcie bus"
Searched and couldn't find a solution, uncheck this, check that...etc.  Nothing worked.
Then noticed your guys comments, and I'm still getting the same error on GPU-Z, and still no Opencl populated.  So there I am :-)

I think this was actually a rufus setting problem on my part...didn't set the gpt/uefi correctly so I had all sort of issues.  Still don't have it fixed, I get it up but then a new problem starts, can't tell if it's the Win10 download I'm using or what, so I'mma try the link that someone put out for 1609.  This last round of tests I did 1709 and did everything one by one, testing mining ever step.  This time I got all the way to installing the drivers then it crapped out and wouldn't opencl, CM would just hang there and do nothing.  Uninstalled driver and tried to go back to windows driver but that won't work now either...so to the next version of Win10 I go :-/

[bigdaddymccarron]

Been using the -mclock and -cclock options and I have noticed that they seem to not be applied once the miner stops unless I change the value by at least 1 then it seems the overclock settings will work.  Anyone else had this issue?

[chaoprokia]

How do set email notification ?

i tried the below it dont work


EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal address/worker -epsw email@gmail.com

[kgminer]

How do set email notification ?

i tried the below it dont work


EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal address/worker -epsw email@gmail.com

two ways to set email notification

1) set it up on the pool, if the pool supports
2) Use "Claymore eth dual miner manager", go to options -> notifications -> define SMTP settings, go to events and define what notifications do you want to receive

[chaoprokia]

How do set email notification ?

i tried the below it dont work


EthDcrMiner64.exe -epool eth-eu.dwarfpool.com:8008 -ewal address/worker -epsw email@gmail.com

two ways to set email notification

1) set it up on the pool, if the pool supports
2) Use "Claymore eth dual miner manager", go to options -> notifications -> define SMTP settings, go to events and define what notifications do you want to receive

thanks for your advise i love to have more specific information on claymore + dwarf pool.


dwarf pool anyone has knowledge of how to set it in claymore.

[Yutard]

Could you possibly show the power the cards are using?

Vote for this feature

This is only accurate for nVidia cards.

[nenvar]

claymore 11.7 crushing windows sometime, but when i use 11.2 then its going good and stable, i think blockchain driver causes crush with claymore, i did upgrade last amd adrenaline driver and v11.8 working good

[groovytechno]

claymore 11.7 crushing windows sometime, but when i use 11.2 then its going good and stable, i think blockchain driver causes crush with claymore, i did upgrade last amd adrenaline driver and v11.8 working good

Thanks for your input, nenvar.  I too have been having some random miner issues with the blockchain driver and Claymore's recent releases. 

I have been using claymore 11.3 with no problems using the AMD blockchain driver.   I mainly used the blockchain driver because I really liked using MSI Afterburner for the fan curve and other settings, but recently the latest version of MSI Afterburner and the Adrenaline drivers seem to be compatible - which is fantastic. 

For the past couple of hours I have been testing Claymore 11.8, Adrenaline driver 18.5.1 and Afterburner 4.5 - I'm happy to report things seem quite well.

[papampi]

Getting random crashes on linux with latest 11.8
Had no problem on 11.7

Code:

GPU 8, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 8, GpuMiner kx failed 1
GPU 8 failed
GPU 8, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 8, GpuMiner kx failed 1
GPU 8 failed
GPU 11, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 11, GpuMiner kx failed 1
GPU 11 failed
GPU 11, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 11, GpuMiner kx failed 1
GPU 11 failed
GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 0, GpuMiner kx failed 1
GPU 0 failed
GPU 0, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 0, GpuMiner kx failed 1
GPU 0 failed
GPU 9, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 9, GpuMiner kx failed 1
GPU 9 failed
GPU 9, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 9, GpuMiner kx failed 1
GPU 9 failed
GPU 5, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 5, GpuMiner kx failed 1
GPU 5 failed
GPU 5, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 5, GpuMiner kx failed 1
GPU 5 failed
GPU 10, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 10, GpuMiner kx failed 1
GPU 10 failed
GPU 10, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 10, GpuMiner kx failed 1
GPU 10 failed
GPU 2, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 2, GpuMiner kx failed 1
GPU 2 failed
GPU 2, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 2, GpuMiner kx failed 1
GPU 2 failed
GPU 4, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 4, GpuMiner kx failed 1
GPU 4 failed
GPU 4, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 4, GpuMiner kx failed 1
GPU 4 failed
GPU 7, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 7, GpuMiner kx failed 1
GPU 7 failed
GPU 7, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 7, GpuMiner kx failed 1
GPU 7 failed
GPU 6, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 6, GpuMiner kx failed 1
GPU 6 failed
GPU 6, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 6, GpuMiner kx failed 1
GPU 6 failed
GPU 1, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 1, GpuMiner kx failed 1
GPU 1 failed
GPU 1, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 1, GpuMiner kx failed 1
GPU 1 failed
GPU 3, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 3, GpuMiner kx failed 1
GPU 3 failed
GPU 3, GpuMiner cu_k1 failed 77, an illegal memory access was encountered
GPU 3, GpuMiner kx failed 1
GPU 3 failed
WATCHDOG: GPU error, you need to restart miner :(

[stef_stef]

Guys what drivers should I use for 480 cards? I am currently running the blockchain ones. Any difference with the newer one?

[Vann]

The AMD blockchain driver was a patch released to fix the Ethash Dag file growth issue that caused Polaris cards to lose hash rate with every new epoch once the Dag file reached over 2GB. Starting with the Crimson Relive compute drivers that were released for Windows 10 v1703, AMD incorporated the fix from the blockchain driver in to the mainstream release drivers when the cards are set to compute mode.

The correct driver to use for Windows 10 v1703 Fall Creator update and newer versions is the latest AMD Adrenaline driver and set the cards to compute mode.

https://support.amd.com/en-us/kb-articles/Pages/DH-024.aspx

[stef_stef]

The AMD blockchain driver was a patch released to fix the Ethash Dag file growth issue that caused Polaris cards to lose hash rate with every new epoch once the Dag file reached over 2GB. Starting with the Crimson Relive compute drivers that were released for Windows 10 v1703, AMD incorporated the fix from the blockchain driver in to the mainstream release drivers when the cards are set to compute mode.

The correct driver to use for Windows 10 v1703 Fall Creator update and newer versions is the latest AMD Adrenaline driver and set the cards to compute mode.

https://support.amd.com/en-us/kb-articles/Pages/DH-024.aspx

Thanks so much! One of the most informative answers I've ever received on the web

One more questions, what build for win10 would you recommend?

[Vann]

I'm running Claymore v11.8 on Windows 10 v1709 until more miners and software are updated to be compatible with the latest Windows build. The Windows v1803 April update breaks some miners and programs like Atiflash.

On Windows 10 Pro you can set a Group Policy to defer feature updates until they have been targeted for business deployment, which is about 4 months after the public release, or you can also defer feature updates for up to 365 days.

gpedit ==> Administrative Templates ==> Windows Components ==> Windows Updates ==> Windows Update for Business ==> Select when Preview Builds and Feature Updates are Received ==> Set to 'enabled' and  in the drop down select 'Semi-Annual Channel'.

[Call_Me_Bambi]

I'm running Claymore v11.8 on the Windows 10 v1709 until more miners are software and updated to be compatible with the latest Windows build. The Windows v1803 April update breaks some miners and programs like the Atiflash.

On Windows 10 Pro you can set a Group Policy to defer feature updates until they have been targeted for business deployment, which is about 4 months after the public release, or you can also defer feature updates for up to 365 days.

gpedit ==> Administrative Templates ==> Windows Components ==> Windows Updates ==> Windows Update for Business ==> Select when Preview Builds and Feature Updates are Received ==> Set to 'enabled' and  in the drop down select 'Semi-Annual Channel'.

I found out too late that AtiWinFlash does not work with the Windows v1803 update, I could have used my Windows 7 PC to do the GPU flashing but found that Windows 10 has a 'roll back' option so I just rolled it back to v1703 - problem solved. Hope that ATI come out with a v1803 workable solution.

[dollos]

Thank you for that heads up on the atiflash issue and windows 10 1803.
was going to be updating the rigs this week...
saved me the hassle.......

[Digital_Seytan]

I have on a rig 3 x Inno3D iChill GeForce GTX 1060 X3 6GB of which only 1 GPU at 25 Mh works the other two run at up to 20.950 Mh, win10 64, afterburn 3.50, which I also try the other two Inno3D iChill GeForce GTX 1060 X3 6GB do not want to run faster, who o who has the same problem, on ethminer, claymore and phoenixminer the same result.love all opinions are welcome.



-------------------------------------------------------------

WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH