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

[WhackOBill]

Read the announcement and the answer is not in there...

for solo mining, if the share that is submitted that finds the block happens while the dev fee is mining, does the dev get the whole block or a percentage of the block?

Thanks!

Why would there be a "share" submitted when solo mining?  You're not on a pool ... right?  If the DevFee cycle hits the block solution, then that wallet address gets the block reward ... all of it.  Pools allow for rewards to be distributed for percentages of work ... not solo.

I did find the answer to my question after searching this thread. (all 1,500 posts )

My guess though is you've never solo mined.  They've had can solo mining on pools for YEARS now.

http://altpool.pro/

In all mining the miner submits shares.  The share is then accepted or denied by the pool.  In the case of solo mining, the accepted submitted share has a chance to solve the block.  In solo pool mining, the share that solves the block gets the reward.  In non-solo pool mining the shares are calculated as a percentage of the block.  What's happening when the DEV part is mining shares are being submitted, but only under the devs mining address.  If they solve the block during that time they get the whole block, I thought there might have been a way to split that percentage-wise in the software, but no, the dev gets the whole block.

Also, as it goes to Claymore's wallet I wouldn't know how many blocks were actually solved by my rigs because the pool only shows my receiving mining address, not his.

So no more solo mining with Claymore for me, at least on certain coins.  For regular pool mining, sure.

Solo mining through a pool is the same result as solo mining directly to the network, but with an added fee.  If you solo mine through a pool, you are a pool of 1.  Shares have no meaning in a pool of 1 because they are all your shares.  You either find a block or you don't.  It's perhaps useful to allow you to see that you are, in fact, making progress on doing the work but nothing else.  In that case, I guess you're paying the pool fee of 1% or so for ... something.  If you're solo and you go through a pool, you're letting them use their wallet in the block's coinbase and at that point, they can deduct their fee and then give you the rest I suppose.  Maybe the fee is worth it to show your progress?  I don't know.  If you were mining directly on the network, your address would go into the coinbase of the found block and you wouldn't submit "shares" to the network ... only block solutions.

Only in pool mining does a miner submit shares.


When the DevFee mines, it may mine on a completely different pool for example.  It is disconnected from the work you're doing on your wallet address.  The DevFee probably hits a shared pool while you are off on a dedicated channel or solo. 

[1714974387]

1714974387

[1714974387]

1714974387

[1714974387]

1714974387

[CryptoMike369]

Miner crashes on a 12gpu rig in this version 11.8 not 11.7 Windows

[iRrromka]

Miner crashes on a 12gpu rig in this version 11.8 not 11.7 Windows

as for me win10pro 1709 & Adrenalin 18.5.1 (NOT 18.5.2) & Clay 11.8 works quite stable with 13 AMD RX588 GPUs

[CryptoMike369]

Also the R1 option for the reboot.bat file fails to work on a 12 GPU rig

[CryptoMike369]

Miner crashes on a 12gpu rig in this version 11.8 not 11.7 Windows

as for me win10pro 1709 & Adrenalin 18.5.1 (NOT 18.5.2) & Clay 11.8 works quite stable with 13 AMD RX588 GPUs

Miner crashes on a 12gpu rig in this version 11.8 not 11.7 Windows

as for me win10pro 1709 & Adrenalin 18.5.1 (NOT 18.5.2) & Clay 11.8 works quite stable with 13 AMD RX588 GPUs

1st you can't run 13gpu on wins pro etc max 12gpu which means your running Linux version of this miner ex: Simplemining or ethOS.

[CryptoMike369]

Miner crashes on a 12gpu rig in this version 11.8 not 11.7 Windows

as for me win10pro 1709 & Adrenalin 18.5.1 (NOT 18.5.2) & Clay 11.8 works quite stable with 13 AMD RX588 GPUs

Miner crashes on a 12gpu rig in this version 11.8 not 11.7 Windows

as for me win10pro 1709 & Adrenalin 18.5.1 (NOT 18.5.2) & Clay 11.8 works quite stable with 13 AMD RX588 GPUs

1st you can't run 13gpu on wins pro etc max 12gpu which means your running Linux version of this miner ex: Simplemining or ethOS.

AMD Drivers only supports 12gpu running on native wins pro etc.........

[iRrromka]

as for me win10pro 1709 & Adrenalin 18.5.1 (NOT 18.5.2) & Clay 11.8 works quite stable with 13 AMD RX588 GPUs

1st you can't run 13gpu on wins pro etc max 12gpu which means your running Linux version of this miner ex: Simplemining or ethOS.

proof
https://yadi.sk/i/_6iEGe5Y3XYZux

[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?

This works on Windows 10, Claymore's Miner v11.8

So I found a way to work around the issue where the -mclock and -cclock options are not applied after the miner stops.  What I discovered is if you modify the value by 1, Claymore's miner will apply the settings to the GPU and overclocking will be successful every time. 

In my mining script I added the following functions and I use the attached config file to setup the miner.

Added to my start.bat file, this is just part of my start.bat script
<------------------------------------------------------------------------------>

setlocal enableextensions
set GCOR=130
set GMEM=700
set GPOW=35
goto SKIPFUNCTIONS

:ADD
Set /a GCOR += 1
Set /a GMEM += 1
Set /a GPOW += 1
Set GCOR=-%GCOR%
Set GMEM=+%GMEM%
Set GPOW=-%GPOW%
echo Fix Added......: 1
echo GMEM=%GMEM%
echo FIX=SUB > %LOC%\FIX.txt
goto RETURN1

:SUB
Set /a GCOR -= 1
Set /a GMEM -= 1
Set /a GPOW -= 1
Set GCOR=-%GCOR%
Set GMEM=+%GMEM%
Set GPOW=-%GPOW%
echo Fix Subtracted.: 1
echo FIX=ADD > %LOC%\FIX.txt
goto RETURN1

:SKIPFUNCTIONS
If Not Exist %LOC%\FIX.txt echo FIX=ADD > %LOC%\FIX.txt
for /f "usebackq delims=" %%x in (%LOC%\FIX.txt) do (set %%x)
echo FIX=%FIX%

If "%FIX%" == "ADD " GOTO ADD
If "%FIX%" == "SUB " GOTO SUB
echo Fix failed, using after burner
start /D %LOC% /WAIT %LOC%\setmsipro.exe %MPRO%
:RETURN1
<------------------------------------------------------------------------------>

config.txt
# WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.
# WARNING! Miner loads options from this file only if there are not any options in the command line!

-epool %POOL%
-ewal %ADDR%
-mode 1
-wd 1
-r 0
-dbg -1
-tt %GTMP%
-fanmin 0
-fanmax %GFAN%
-cclock %GCOR%
-mclock %GMEM%
-powlim %GPOW%
-mport 3333
-mpsw ether
-showdiff 1

[borg9000]

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?

This works on Windows 10, Claymore's Miner v11.8

So I found a way to work around the issue where the -mclock and -cclock options are not applied after the miner stops.  What I discovered is if you modify the value by 1, Claymore's miner will apply the settings to the GPU and overclocking will be successful every time. 

In my mining script I added the following functions and I use the attached config file to setup the miner.

Added to my start.bat file, this is just part of my start.bat script
<------------------------------------------------------------------------------>

setlocal enableextensions
set GCOR=130
set GMEM=700
set GPOW=35
goto SKIPFUNCTIONS

:ADD
Set /a GCOR += 1
Set /a GMEM += 1
Set /a GPOW += 1
Set GCOR=-%GCOR%
Set GMEM=+%GMEM%
Set GPOW=-%GPOW%
echo Fix Added......: 1
echo GMEM=%GMEM%
echo FIX=SUB > %LOC%\FIX.txt
goto RETURN1

:SUB
Set /a GCOR -= 1
Set /a GMEM -= 1
Set /a GPOW -= 1
Set GCOR=-%GCOR%
Set GMEM=+%GMEM%
Set GPOW=-%GPOW%
echo Fix Subtracted.: 1
echo FIX=ADD > %LOC%\FIX.txt
goto RETURN1

:SKIPFUNCTIONS
If Not Exist %LOC%\FIX.txt echo FIX=ADD > %LOC%\FIX.txt
for /f "usebackq delims=" %%x in (%LOC%\FIX.txt) do (set %%x)
echo FIX=%FIX%

If "%FIX%" == "ADD " GOTO ADD
If "%FIX%" == "SUB " GOTO SUB
echo Fix failed, using after burner
start /D %LOC% /WAIT %LOC%\setmsipro.exe %MPRO%
:RETURN1
<------------------------------------------------------------------------------>

config.txt
# WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.
# WARNING! Miner loads options from this file only if there are not any options in the command line!

-epool %POOL%
-ewal %ADDR%
-mode 1
-wd 1
-r 0
-dbg -1
-tt %GTMP%
-fanmin 0
-fanmax %GFAN%
-cclock %GCOR%
-mclock %GMEM%
-powlim %GPOW%
-mport 3333
-mpsw ether
-showdiff 1

This is an interesting approach and a solution to the problem. In my batch file I have almost no additional switches or options enabled and it seems to work just fine with close to default values. Although, the clock and fan speeds are set with Afterburner.

[crypper]

Hi guys,
Sorry for a slight off-topic, but is there anyone kind enough to share a powershell script for fresh windows 10 tweaking for mining, e.g. rename pc, increase virtual memory, set proper power plan, disable windows updates, enable compute mode for amd cards, etc....
Something similar to this bat file: https://1stminingrig.com/best-windows-setup-configuration-tweaks-for-mining/
I'm writing my own, but it's taking more of my time than i'm willing to spend on it...

Thanks in advance; feel free to pm me.

[jaxnatax]

Hallo guys,


Since Claymore v11.7 on Windows 10 - I have been facing with the following issue:

"Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: EthDcrMiner64.exe (1380) consumed 14468136960 bytes"

before 11.7 no such error appeared...
with 11.7 it run with 5-7day before this popped up.
Now with 11.8 it comes earlier - after 3-4 days.

Nothing else have been changed on the system, only the Claymore version.
Paging File is 16GB as it written in the "manual".
No new updates or driver or firmware got updated/installed.

Any idea ?


Regards,
J

[Bulltime]

Hello guys , could you please let me know what is the BEST way to stop windows updates as i normally know that but dont know how my windows 10 updated itself with the "Windows 10 April update bla bla...' and my 10 gpu miner  stopped working etc.....then i reinstalled v.17.09 and all back again.

Usually i am stopping windows update services from the services.msc

But it gets enabled again?

Now i just noticed it was enabled again and i disabled it bit i am sure it will enable itself and will update the windows and will have to reinstall again....

Is anyone else experiencimg the same ?

Thanks for your help in advance, first i a want to solve this and i am upgrafing to 11.8 with the latest AMD drivers.


Thanks

Hey Alex,

There are a few ways to do this but the best way to deal with the update is to have a cheap computer (test system) like your main rigs minus GPU's or if you can afford it one gpu 4GB above.

I say this so you won't need to have a machine down while you figure out software & hardware issues.
*The easy (fast) fix is to limit the OS partition drive of your HDD or a 120GB ssd and max out the VR to50000-60000

My large system has a 120Gb ssd and it tells me every other day or so that an issue needs fix because not enough room to update (learn more) then exit the settings screen but I still see the miner working in the background of that message, so it does not pose an issue atm.

I always suggest if its running with restarts every once and awhile let it go and keep an eye on it through ethermine.org screen to check if your miner is up (15 minute delay in reporting)

The more you learn and take notes of your issues will make you a better problem solver and then sometimes computer hardware & software get a mind of their own-really do,lol

Need any help feel free to ask but must be precise on details.

[kaury1]

Hi guys!

In the miner there is such a parameter "-etht"
"Time period between Ethereum HTTP requests for new job in solo mode, in milliseconds. Default value is 200ms"

Why do we need this parameter and how does it affect the efficiency of mining?
For example, if my ping to the pool is ~ 70ms - does this mean that I should lower the "-etht" parameter from 200ms to, for example, 70ms?
Or is this statement wrong on my part?

Has anyone experimented with this parameter?

Thank you!

P.S.
Sorry for my bad english) 

[TigTex]

The etht parameter only works in solo mode. You are mining on a pool so that option does absolutely nothing!

[singlass]

"you can mine all ETH forks without devfee"

only on win 10 ?

[prostor]

"you can mine all ETH forks without devfee"

only on win 10 ?

2Gb card - all win.
3Gb card - only win10.

[singlass]

"you can mine all ETH forks without devfee"

only on win 10 ?

2Gb card - all win.
3Gb card - only win10.

tnx man

[Xardas2014]

Hello,

I have issue with my rx480 mining rig, it runs before perfect, but i ahve to change ssd, and after the new win10 installation, the miner stuck after detecting pools.

I use latest win10 ltsb, asrock h81 btco pro r2.0 mobo. Onboard display is selected, and gen1 also.
I see my cards at the device manager, also installed the chipset driver, but the miner cannot start.

OverdriveNtool also detect my gpus. Change the mobo and the cpu as well, it isnt solve the issue, any idea?
I think something missing, but i dont have a clue, out of ideas

Disable ULPS from regedit... also, just a little patience, it's not stuck, it just takes a little more time than usual but if you disable the ULPS then it should start faster

Just put 0 instead of 1 and do a restart.

I forget it to write, vut i also disable ULPS, i leave the miner running for 2-4 hours, and it gives, the claymore sign and pools again and again

Then maybe use DDU in Safe mode, disable ULPS again and see if it's working... if not, then is something else wrong there.

I have two rigs that have me baffled. Both are exact copies of each other, other than cards, but anyway all they do is https://ibb.co/cnLC8T which finally goes to https://ibb.co/gvf12o  The 5 minute timer just goes on and on. I have set the EnableULPS to 0 but this prob persists. Any ideas? Sorry but the forum didn't like the image host. Dunno why, but you can copy the links to see the pics.

I have no ideea other than do a DDU in safe mode, install latest drivers and set ULPS to 0 for each card. Are AMD or Nvidia? You have this issue after latest Win10 update to v1803?

Neither rig has taken the v1803 update. At this point I have tried 9 different drivers from the blockchain driver forward. I've used regedit to search "EnableULPS" and set it to zero.(This location can be in different places with different drivers, so use the regedit search feature). Rebooted and CLaymore does the same thing. Nicehash 1.9.0.3 doesn't detect any AMD cards. Right now both rigs are running the flakeyass SMOS, 6 of 8 cards on each rig. SMOS drops caards and spits out too many errors to risk running all 8.

I'm recovering from colon cancer surgery, so it is quite difficult for me to run back and forth testing rigs. I hope someone finds the solution. I did a fresh install of win10 pro disconnected from the net, stopped updates and a host of spying shit, installed drivers and all 8 are detected. Disabled ULPS, ran the ati patcher, set all the cards to compute, set virtual memory to 16k-32k. Connected the net and fired up Claymore only to see the same shit I have been seeing........it won't initialize. Tried nicehash 1.9.0.3 and it still doesn't detect the AMD cards. Back to SMOS and 6 cards until someone finds a solution.

[BogdanCo]

Hello,

I have issue with my rx480 mining rig, it runs before perfect, but i ahve to change ssd, and after the new win10 installation, the miner stuck after detecting pools.

I use latest win10 ltsb, asrock h81 btco pro r2.0 mobo. Onboard display is selected, and gen1 also.
I see my cards at the device manager, also installed the chipset driver, but the miner cannot start.

OverdriveNtool also detect my gpus. Change the mobo and the cpu as well, it isnt solve the issue, any idea?
I think something missing, but i dont have a clue, out of ideas

Disable ULPS from regedit... also, just a little patience, it's not stuck, it just takes a little more time than usual but if you disable the ULPS then it should start faster

Just put 0 instead of 1 and do a restart.

I forget it to write, vut i also disable ULPS, i leave the miner running for 2-4 hours, and it gives, the claymore sign and pools again and again

Then maybe use DDU in Safe mode, disable ULPS again and see if it's working... if not, then is something else wrong there.

I have two rigs that have me baffled. Both are exact copies of each other, other than cards, but anyway all they do is https://ibb.co/cnLC8T which finally goes to https://ibb.co/gvf12o  The 5 minute timer just goes on and on. I have set the EnableULPS to 0 but this prob persists. Any ideas? Sorry but the forum didn't like the image host. Dunno why, but you can copy the links to see the pics.

I have no ideea other than do a DDU in safe mode, install latest drivers and set ULPS to 0 for each card. Are AMD or Nvidia? You have this issue after latest Win10 update to v1803?

Neither rig has taken the v1803 update. At this point I have tried 9 different drivers from the blockchain driver forward. I've used regedit to search "EnableULPS" and set it to zero.(This location can be in different places with different drivers, so use the regedit search feature). Rebooted and CLaymore does the same thing. Nicehash 1.9.0.3 doesn't detect any AMD cards. Right now both rigs are running the flakeyass SMOS, 6 of 8 cards on each rig. SMOS drops caards and spits out too many errors to risk running all 8.

I'm recovering from colon cancer surgery, so it is quite difficult for me to run back and forth testing rigs. I hope someone finds the solution. I did a fresh install of win10 pro disconnected from the net, stopped updates and a host of spying shit, installed drivers and all 8 are detected. Disabled ULPS, ran the ati patcher, set all the cards to compute, set virtual memory to 16k-32k. Connected the net and fired up Claymore only to see the same shit I have been seeing........it won't initialize. Tried nicehash 1.9.0.3 and it still doesn't detect the AMD cards. Back to SMOS and 6 cards until someone finds a solution.

No, it's always in the same location: {4d36e968-e325-11ce-bfc1-08002be10318}
Also, try without running the ati patcher....

[Xardas2014]

Hello,

I have issue with my rx480 mining rig, it runs before perfect, but i ahve to change ssd, and after the new win10 installation, the miner stuck after detecting pools.

I use latest win10 ltsb, asrock h81 btco pro r2.0 mobo. Onboard display is selected, and gen1 also.
I see my cards at the device manager, also installed the chipset driver, but the miner cannot start.

OverdriveNtool also detect my gpus. Change the mobo and the cpu as well, it isnt solve the issue, any idea?
I think something missing, but i dont have a clue, out of ideas

Disable ULPS from regedit... also, just a little patience, it's not stuck, it just takes a little more time than usual but if you disable the ULPS then it should start faster

Just put 0 instead of 1 and do a restart.

I forget it to write, vut i also disable ULPS, i leave the miner running for 2-4 hours, and it gives, the claymore sign and pools again and again

Then maybe use DDU in Safe mode, disable ULPS again and see if it's working... if not, then is something else wrong there.

I have two rigs that have me baffled. Both are exact copies of each other, other than cards, but anyway all they do is https://ibb.co/cnLC8T which finally goes to https://ibb.co/gvf12o  The 5 minute timer just goes on and on. I have set the EnableULPS to 0 but this prob persists. Any ideas? Sorry but the forum didn't like the image host. Dunno why, but you can copy the links to see the pics.

I have no ideea other than do a DDU in safe mode, install latest drivers and set ULPS to 0 for each card. Are AMD or Nvidia? You have this issue after latest Win10 update to v1803?

Neither rig has taken the v1803 update. At this point I have tried 9 different drivers from the blockchain driver forward. I've used regedit to search "EnableULPS" and set it to zero.(This location can be in different places with different drivers, so use the regedit search feature). Rebooted and CLaymore does the same thing. Nicehash 1.9.0.3 doesn't detect any AMD cards. Right now both rigs are running the flakeyass SMOS, 6 of 8 cards on each rig. SMOS drops caards and spits out too many errors to risk running all 8.

I'm recovering from colon cancer surgery, so it is quite difficult for me to run back and forth testing rigs. I hope someone finds the solution. I did a fresh install of win10 pro disconnected from the net, stopped updates and a host of spying shit, installed drivers and all 8 are detected. Disabled ULPS, ran the ati patcher, set all the cards to compute, set virtual memory to 16k-32k. Connected the net and fired up Claymore only to see the same shit I have been seeing........it won't initialize. Tried nicehash 1.9.0.3 and it still doesn't detect the AMD cards. Back to SMOS and 6 cards until someone finds a solution.

No, it is not always in the same location. Using the newest drivers from AMD it moved from \0000 to \0001. It doesn't exist at \0000 in the latest driver. I know because I added a DWORD value for it set to 0 and that did nothing. So I used the regedit search and found it at \0001.