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

Are they all AMD cards?

Hi.

I am using Nicehash (claymore is added as 3rd party, version 10.6. EthDcrMiner64.exe).

The problem is that the claymore miner seems to be restarting. The window closes and a new one starts.
My rig is 13x amd radeon 570 gpu (only timestrap). (24.9 Mh/s, no modding on oc and undervolt etc).

What is MAX cool time exceeded. RESTARTING ?

I think it's Claymore v11.0 bug!  many peaple have the same problem. Add "-wd 0" option in .bat file

Awesome Miner, do I need to configure each mining rig with a pool? like rig 1 configure with eth and rig 2 again configure for eth?
aslo my claymore keeps crashing

Still having issues with the inbuilt overclocking,
Doesn't seem to register with multiple cards

The 3 configs I have tried

EthDcrMiner64.exe -epool etc-au1.nanopool.org:19999 -ewal Walletaddressisnormallyhere/RIG/[email protected] -epsw x -mode 1 -ftime 10  -cvddc 930,930,930,930,930,930,930 -cclock 1150,1150,1150,1150,1150,1150,1150, -mvddc 930,930,930,930,930,930,930 -mclock 1960,1960,1960,1960,1960,1960,1960
EthDcrMiner64.exe -epool etc-au1.nanopool.org:19999 -ewal Walletaddressisnormallyhere/RIG/[email protected] -epsw x -mode 1 -ftime 10 -di 0123456 -cvddc 930,930,930,930,930,930,930 -cclock 1150,1150,1150,1150,1150,1150,1150, -mvddc 930,930,930,930,930,930,930 -mclock 1960,1960,1960,1960,1960,1960,1960
EthDcrMiner64.exe -epool etc-au1.nanopool.org:19999 -ewal Walletaddressisnormallyhere/RIG/[email protected] -epsw x -mode 1 -ftime 10  -di 0,1,2,3,4,5,6,7 -cvddc 930,930,930,930,930,930,930 -cclock 1150,1150,1150,1150,1150,1150,1150, -mvddc 930,930,930,930,930,930,930 -mclock 1960,1960,1960,1960,1960,1960,1960

Anyone got any ideas on why the clocks only work for the first card and not the rest

Okay understood. Thanks again for your interest 

I never raise devfees, only reduce them from time to time.
I can add solo support when I have some time for it, but I'm really busy with other features and miners. For example, I spent a few weeks for this: https://bitcointalksearch.org/topic/claymores-neoscrypt-amd-gpu-miner-v12-windows-3012600

@Claymore, Thank you very much for your answer. At least now we know were we stand

I personally feel that I wouldn't mind seeing the 1.5% fee return to 2% (to pay for Claymore's hard work) if we were to get a SOLO option for the second algos of dual mining.
Those stealing pools are so annoying...

I am not saying it to apply pressure on Claymore, he made a valid point. But if there are enough people in here feeling the same way, then maybe there is something for Claymore to earn as well (by raising the fee again)

Solo mining support requires more efforts from me: installing wallets, using testnets, etc. And then I see that only few percents of miners use this feature. So not in near future.

Right now no. I asked a question here and I am hoping for an answer

Hello, I am using awesome miner and the claymore 11 continues to crash on all coins. Any suggestions?
when I run the program directly from awesome miners file, it crashes at dag file to blue screen.
available virtual memory 74.8 GB.

1060 w/3GB RAM should do about that, maybe 21Mh/s if you get things just right.  My Gigabyte card likes 70% power limit, about +220 GPU speed offset and +1000 memory offset.  Not all cards will do that, I have Hynix VRAM, also.  Some might get a little more, but I don't know of any way to set the memory more than +1000 offset.  My card will hold a stable +240 GPU, but I get crappy shares relative to what I get at +220.  Every single card is just a little different unless they came out of the same batch, same model from the same maker.  I have my temp max at 80C which is about what it does when I'm dual mining (and yes, about 350Mh/s for Verge / XVG is what I get, although you can tweak -dcri up to the best your card will do without impacting your ETH hashing much (I limit it to 1% impact) then you might be able to get 400+Mh/s but in my experience it messes things up and I get recycles way too often instead of it running the clock out (-r 239) at four hours, which is my self-imposed limit before I restart the miner.  I was using -dcri 70 which seemed to be the sweet spot for intensity on my specific card.  The other rig is a GTX1080 with RX 580's, all 8GB mostly Asus OC/ROG/Strix models with one Sapphire Nitro+ 580 OC.

Some people insist on just letting it run forever, but my machines seem to grow a minds of their own after a few hours, so 4 hours is what I picked.  For the GTX1060 memory ramped up to 10K speed, I build the DAG in between 8 and 9 seconds.  No big woop...  I am back to single mining ETH for now, I just get too darned squirrelly dual mining.

You can not change the nVidia GPU BIOS for GTX10x0 cards, it's encrypted and won't boot if you mess with it (which is assuming you are truly a crypto genius and can figure out the encryption, which nobody else has - so far, anyway), so you are stuck with mods using AfterBurner or nVidiaInspector, etc because Claymore doesn't do memory tweaks for nVidia (or fans, temps or power limits) like it does for AMD cards.

Yes, that's because the difficulty for mining Verge is very high last 48 hours. We didn't change anything, so eventually the block(s) should be found.... last night i was more worried because we had to wait for the first blocks to arrive, but i am sure all should be ok.

We are looking into coin alternatives already .... Join us on Telegram ( https://t.me/nlpool ) if you want specific coins added to mine or the latest update ;-)

And i was hoping you would advise they guy to set us up as primary pool 

I am still experiencing issues with XVG pools... Problem is, when XVG pool is unaccessable (antminepool currently), both ETH+XVG hashing crashes and miner has all zeros on all cards - even ETH. Do you know and hack how to fix this? Have anyone tried some parameters that if XVG is not mining, it will restart mining ETH only? Really dont know how to solve this, half of my farm is down due to antminepool issues since 5 hours ago currently... Thanks.

The same parameters work for both the .bat or config files, so as long as the parameters are set correctly, it should make no difference which one you used. If you look at the log file, the first line is the parameters passed to the miner. You can also use different config files in the same way you use different .bat files. You just need to put the name of the config file to use when you start the miner.

Okay, thanks. I usually do have three or four different start.bats for those very reasons. Dual setups, Eth only different pools etc... One thing I had happen recently that got me thinking along these lines was one of my rigs had a gpu hang and I noticed when the miner restarted I lost fan control on that particular gpu. It got me wondering if that had been setup in config instead of start.bat if it would have made any difference? 

I doubt it makes any difference, it's just a matter of convinience. The config file is parsed and passes the parameters to the miner at runtime anyway. If you change pools or use different settings often, a .bat file for each pool is more convininet than having to adjust the config file.

Hello miners, I've seen it mentioned several times, some recently, that you should set the majority of parameters in config file, not in a startup.bat. Would one of you kind gentlemen please take a moment to explain why that is the case. I started out early on setting everything in my start.bat. It works and I've just stuck with doing it that way on all my rigs. I guess it's more of a "If it's not broke don't fix it" kind of thing for me. I'm just curious what, if anything, I would gain by changing the way I currently have it set up.
Thanks.

Ikr... Well I knew it from the beginning that power cost would take half of my profits... So I guess I have learned to live with it. I got my ROI early so I got that going for me, which is nice  
"Greeks pay your taxes" they say... well we do...   (80% of that 0.3$ is taxes)