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

[sevan]

Hi,

I often encounter the "Temperature control thread hangs, need to restart miner!"

Appreciate anyone to help..

would you know what causing this and how to prevent it? as I am loosing time in mining due to restarting.

Thank you!

[1714638975]

1714638975

[1714638975]

1714638975

[1714638975]

1714638975

[1714638975]

1714638975

[1714638975]

1714638975

[1714638975]

1714638975

[leonix007]

Hi,

I often encounter the "Temperature control thread hangs, need to restart miner!"

Appreciate anyone to help..

would you know what causing this and how to prevent it? as I am loosing time in mining due to restarting.

Thank you!

Try to lower your clocks,

post your GPU hardware types and your existing clock configurations in order to help you more

Include also your OS and drivers your are using

[SackofFluor]

Hey Guys


I have a little problem...

After some tinkering i was able to bring my RX580 8GB cards to stable 29-30Mh/s. I have 5 of those cards and 1 of the 4GB version (which is also pretty good i have to admit).

But now to my problem, if i start the cards all individually they all bring the same performance, maybe +- 0,1 Mh/s, but when i start all of them together two of my cards need longer for the DAG creation 7200ms instead of the other 4900-5500ms .

And they only hash at around 20-22Mh/s.... I have no idea what i can do to bring some up with their buddies and like written further up.... on their own they are entirely capable of going 29-30 ....

Does anybody has any idea what i can do to improve my little problem ?



Sincerely

Sack

Try adding -gser 2 setting and increase this value if it does not work

Hey Spirit

Yes i thought so as well so i tried to  all kind of settings up to -gser 5 but as before , two of them dont care

[sevan]

Hi,

I often encounter the "Temperature control thread hangs, need to restart miner!"

Appreciate anyone to help..

would you know what causing this and how to prevent it? as I am loosing time in mining due to restarting.

Thank you!

Try to lower your clocks,

post your GPU hardware types and your existing clock configurations in order to help you more

Include also your OS and drivers your are using

My Details are:

Aferburner: 1070 Seahawk, i5-4460 3.2GHz, 8GB RAM
         Power limit  - 65%
         Temp limit  - 80 c
         Core Clock  - 0
         Mem Clock  - +650
         Fan Speed   - Auto
Im using WIN10 Enterprise - 64bit, Nvidia driver is 388.59, virtual memory is 16384 for both initial and maximum

heres how my .bat file looks like

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
_______________________________________________________________________________ _

Before when I was using the older claymore (10.0) and Win10 Home 64bit I didnt encounter this problem. Should I insert "-wd 0" to disable watchdog? will it still be safe when disabling watchdog?

Thank you!

[leonix007]

Hi,

I often encounter the "Temperature control thread hangs, need to restart miner!"

Appreciate anyone to help..

would you know what causing this and how to prevent it? as I am loosing time in mining due to restarting.

Thank you!

Try to lower your clocks,

post your GPU hardware types and your existing clock configurations in order to help you more

Include also your OS and drivers your are using

My Details are:

Aferburner: 1070 Seahawk, i5-4460 3.2GHz, 8GB RAM
         Power limit  - 65%
         Temp limit  - 80 c
         Core Clock  - 0
         Mem Clock  - +650
         Fan Speed   - Auto
Im using WIN10 Enterprise - 64bit, Nvidia driver is 388.59, virtual memory is 16384 for both initial and maximum

heres how my .bat file looks like

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
_______________________________________________________________________________ _

Before when I was using the older claymore (10.0) and Win10 Home 64bit I didnt encounter this problem. Should I insert "-wd 0" to disable watchdog? will it still be safe when disabling watchdog?

Thank you!

Try to lower the mem clock at +500, increase your virtual mem to 16,000MB initial and 30,000MB max are you using Risers? if yes, try to replace them.

If you have multiple GPU, try to install single GPU only unto 16xPCIE slot for troubleshooting purpose.

Disabling -wd wont help, it will also freeze your system when GPU fails, I would suggest to look for the root cause of your problem.

If still wont work, try to reinstall ladrivers

[NewbieMiner17]

I recently put a machine on ETC and updated the drivers to the blockchain drivers, so the machine mines faster now, but is more unstable, even when I shut off dual mining.  Can anyone share with me their run parameters for a Sapphire rx nitro (non-plus) 480 8g card?  I am running windows 10 with v 10.2 with the August 23rd blockchain drivers.  Would love a suggestion on how to get this to run stable and not have cards tripping out.  I have tried raising and lowering voltages, lowering ethi to 1, and turning off dual mode, but not really found a stable set up.  Appreciate any thoughts.
Thanks

I'm using this config.

Code:

-epool eu1.ethermine.org:4444
-ewal xxxxx
#-eworker
-epsw x
-esm 0
-allpools 1
-mode 1
-estale 1
-ethi 16
-gser 2
-wd 1
-r 0
-dbg -1
-tt 75
-ttdcr 80
-ttli 85
-tstop 90
-cclock 900
-cvddc 800
-mclock 1750
-mvddc 800
-powlim -10

Works like a charm on my 6x480 rig

Thanks know this was for someone else but I tried adding.
-allpools 1
-mode 1
-estale 1
-ethi 16
-gser 2
-wd 1
-r 0
-dbg -1

to my file and I'm back up to 28MH from the 19 it was weirdly running at. Will remove one at a time this weekend and try to find out which one saved the day. Also is gser and rdg new ones for v10.2? Don't remember them from last time I read it all.

[BSAlex]

Thanks but don’t think this is it. With the blockchain drivers we should avoid epoch issues. Have you updated to blockchain driver?

UPDATE: So I swapped the hard drives around the rigs and now the other rig is running with 19MH instead... I'm pretty sure all my settings are exactly the same... Is there something windows could have changed after a few too many crashes?

Just clone the good one and forget :-) Surely Windows can accumulate errors, and usually it is much easier to reinstall/clone then to find the error.
PS If it is not too much to ask please let me know what actual EPOCH # are used by the miner in each case. I am still trying to understand what's wrong with my case.

[deadsix]

Hey guys,
me again!

So. I'm still running 6x RX480 4gb saph nitro+. Blockchain drivers, Memshift Anorak Bios, OC with AB.

So out of two rigs with exactly the same setup I've recently been mining on nicehash with around 28MH per card. On Nanopool dual mining ETH/SC I've been getting around 25MH. After the whole nicehash hack I've had to go back to nanopool until they get the systems back up and running.

Thats all fine and one rig is running golden. My other rig however has now decided that it will not mine at anything higher than 19MH with the same settings. I've tried reinstalling the drivers, reupdating the Bios, playing with OC, went back to V10 claymore, etc but no luck the cards are just refusing to run at over 19MH. Does anyone have any idea what could be causing this? I think I'm going to switch the hard drives around tonight to see if that does anything but short of that I'm stumped. Guess it would mean a fresh windows install if it does solve it.

PS. when I tried powersave bios on half the cards it did drop it even further to 16MH. previously on powersave I was getting around 22.

Looking forward to hearing what ideas you guys might have.

Please check what EPOCH is used in both cases. I have a miner that use different EPOCH randomly, and mining speed is completely different: from 9.5Mh to 23Mh (!!!). Did not find any possibility to control what EPOCH is used so in my case the problem is unresolved :-(

Thanks but don’t think this is it. With the blockchain drivers we should avoid epoch issues. Have you updated to blockchain driver?

UPDATE: So I swapped the hard drives around the rigs and now the other rig is running with 19MH instead... I'm pretty sure all my settings are exactly the same... Is there something windows could have changed after a few too many crashes?

Epoch changes affected DAG size which caused us to see performance drops. This was because of the way AMD drivers address graphics memory, it did not affect performance in games etc, but crippled Ethash mining. With the blockchain drivers AMD fixed this.
In newer drives, you have to go to AMD settings - gaming - global settings and switch to compute mode from the default gaming mode. This fixes hashing performance.

[ohyouha]

Hi i'm trying to mining firstime
i load CM.V10.2
and put this ...
EthDcrMiner64.exe
-epool eth-asia1.nanopool.org:9999
-ewal (mywallet)
-epsw x -dcoin sia -dpool sia-asia1.nanopool.org:7777
-dwal (mywallet)
-dpsw x
-mode 0
-tt 70
-ftime 10 -r 90

when start it they say
"No pool specified"
then close off
i try to change 1-2 new pool but still not work.
 so how to fix this?

ps. i use 1070 win10

[whitrzac]

Has anyone had a 570 that wouldn't do 2050mhz memory with 1500/1click fix straps?  I have 1 570 that gets a ton of invalid lbry shares when dual mining, but has no invalids or issues with ETH.

[evertec]

Does anyone know a way to set the compute setting in the new drivers without going through the gaming section of the control panel, such as an ini file or registry setting? The control panel crashes for me whenever I go to the gaming tab.

[keyboardwalking]

so looks like cant disable devfee, least for me. command doesnt work.

Doesnt work for me either, actually ive had that is my bat for a few weeks, didnt notice it wasnt taking affect anymore until you said. My hashrate is less too like it still truncates your hash ability but also gives the dev money. doesnt even make sense.

[Cryptographertm]

so looks like cant disable devfee, least for me. command doesnt work.

Doesnt work for me either, actually ive had that is my bat for a few weeks, didnt notice it wasnt taking affect anymore until you said. My hashrate is less too like it still truncates your hash ability but also gives the dev money. doesnt even make sense.

Yea, I searched around a bit, and it seems that the nofee option is BS and he lied about it

https://bitcointalk.org/index.php?topic=2064326.0

[herkie]

I am having a very weird issue. I just set up my 2nd miner with the following specs

ASUS Prime Z270-A mobo
8GB ram
5 MSI RX580 Gaming X 8G GPU
SSD drive
Windows 10
Blockchain driver
1000W EVGA PSU gold+

All pretty standard stuff. I flashed all the GPUs and updated bios on the mobo and turned on 4G, etc. Everything is running correctly while it is plugged into ethernet. I ran Claymore 10.2 and all 5 cards shows up and running with around 29.5Mh/s. I let it run for about an hr and all is good. I then switched the network to a wifi repeater and plugged the rig into the wifi repeater via ethernet and let that run for 30 mins and everything is still fine.

So now I pick up the rig and move it to another location to run it as headless with the wifi repeater next to it and all hell broke lose. Claymore hangs with GPU0, restart miner messages. Figured out with card is GPU0, unplugged. Thought maybe it was a bad riser. Reboot, same thing. GPU0(represented by a different card now) hangs, restart miner. Unplug again and reboot, now getting GPU0, GPU2 hang errors. Also claymore takes forever to startup. When all 5 cards were running, it was drawing about 750W at the wall. So definitely not a power issue. It had the same hang issue when I only have 4 cards plugged in.

I haven't moved it back to my bench yet and plugged the monitor back in. But does going headless with Win10 affect how claymore sees the cards? Any ideas?

Thanks in advance!

[Cryptographertm]

Also after 48 hours of running this, the pool is reporting 60% of my hashrate in console despite having nofee1

[Marvell2]

Also after 48 hours of running this, the pool is reporting 60% of my hashrate in console despite having nofee1

60 percent huh, claymore is 2 percent max

[syncis]

Guys, Does anyone know if you are able to run 12x rx580 or 12xgtx1070 in windows with claymore without issues?
I know that ati released new drivers that would allow you to do this for rx580, but I am not sure, and certainly not sure about nvidia.
I am right now using h110 pro btc, but planning on getting b250 mining expert motherboard if that help.

[Claymore]

Note about latest drivers version: I confirmed that AMD broke fan management again.
I have contacted them and hope they will fix it soon. Right now don't use 17.12.1 drivers if you want to manage GPU fan/temperature.

[herkie]

Guys, Does anyone know if you are able to run 12x rx580 or 12xgtx1070 in windows with claymore without issues?
I know that ati released new drivers that would allow you to do this for rx580, but I am not sure, and certainly not sure about nvidia.
I am right now using h110 pro btc, but planning on getting b250 mining expert motherboard if that help.

I tried 9 MSI RX580 cards on the ASUS mining expert mobo with the latest AMD driver and Windows10 and yes, it does recognize all the cards but I was not able to get it to run stable. Also the hashrate was not great, with the latest AMD driver, I got only 27-28 Mh/s with the same cards that got 29-30Mh/s using the blockchain driver. And it was very unstable, lots of openCL hang errors and a few hard windows crashes(completely frozen) that required manual reboot. So the latest driver is not quite ready for primetime. Went back to the blockchain driver and only 8 cards and my rig has been up with no hard crashes for over a week now.

[BSAlex]

Epoch changes affected DAG size which caused us to see performance drops. This was because of the way AMD drivers address graphics memory, it did not affect performance in games etc, but crippled Ethash mining. With the blockchain drivers AMD fixed this.
In newer drives, you have to go to AMD settings - gaming - global settings and switch to compute mode from the default gaming mode. This fixes hashing performance.

And what to do with Nvidia to avoid epoch-connected hashrate issues? No "compute" switch for 9xx Nvidia cards :-(
BTW not even half videomemory was used in either case.