Author

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

member
Activity: 66
Merit: 10
Hello

I was mining Zcash but now I've gone to ETH, I ask that it is better to mine ETH alone or with SIA or DECRED?

I use 4 * GTX 1060 + 1 GTX 1070

Thank you

In my case ETH+DCR
newbie
Activity: 25
Merit: 0
Error using Claymore v10 on Windows 10 after Creators update (windows version 1703)

Error when launching: The application was unable to start correctly (0xc000007b).

I've tried reinstalling nvidia drivers, .net 2012 (x64 and x86 and deleting msvcr110.dll and msvcp110.dll) from system32 and reinstalled .net. I've added exclusions to Defender and tried running as Admin.
Any suggestions would be appreciated. Thank you
newbie
Activity: 25
Merit: 0
use whattomine.com and use the ETH+x up top and type in your numbers to see
member
Activity: 88
Merit: 10
Hello

I was mining Zcash but now I've gone to ETH, I ask that it is better to mine ETH alone or with SIA or DECRED?

I use 4 * GTX 1060 + 1 GTX 1070

Thank you
sr. member
Activity: 467
Merit: 252
Your miners work ok after fork?

Actually difficulty on Eth has dropped drastically. I'm noticing my profits go up by the hour here. This is awesome news for us miners. Anyone else notice?

Difficulty dropped, making block time shorter. So, more blocks.

Reward also dropped, so, less revenue per block.

Net result is almost no difference in mining profitability - as intended in the upgrade.

Correct I hear ya, but unless Ethermine's stats are off, it's telling me I'm making more.....Time will tell I guess.
member
Activity: 83
Merit: 10
Your miners work ok after fork?

Actually difficulty on Eth has dropped drastically. I'm noticing my profits go up by the hour here. This is awesome news for us miners. Anyone else notice?

Difficulty dropped, making block time shorter. So, more blocks.

Reward also dropped, so, less revenue per block.

Net result is almost no difference in mining profitability - as intended in the upgrade.
sr. member
Activity: 467
Merit: 252
Your miners work ok after fork?

Actually difficulty on Eth has dropped drastically. I'm noticing my profits go up by the hour here. This is awesome news for us miners. Anyone else notice?

I noticed that too, so good News!

Lets hope it stays like this for a while....that was pretty shitty what they did with the diff bomb being implemented too early.
member
Activity: 66
Merit: 10
Your miners work ok after fork?

Actually difficulty on Eth has dropped drastically. I'm noticing my profits go up by the hour here. This is awesome news for us miners. Anyone else notice?

I noticed that too, so good News!
member
Activity: 88
Merit: 16
Guys

Need some help

I have one rig thats driving me nuts

8 x Gigabyte Aorus 4gb Rx570's some with ELPIDA and some with Hynix
Asus z270-a
g4400
ddr 8gb
windows 10 fresh install
Blockchain drivers

My biggest issue is that when i make changes to the batch file the computer freezes..i get the blue screen with an error "Thread stuck in Device Driver"

I have swapped out motherboard with a new one...added more power...re installed windows several times....did clean DDU driver uninstalls several times etc...ONLY after i make a change and reboot it it MIGHT start hashing correctly....by correctly i mean it will always hash but at the stock clocks. I then need to resstart Claymore several times until it gets the overclocks.

I normally use the claymore batch file for all of my overclocks and undervolts...so i have tried several versions of MSI AB and its the same thing....

Am i doing something wrong ir is it these particular cards ? I even changed to Claymore 9.8 but that lowers the hash every so often to 14mh acroos all the cards ?


Also Compared to my other rigs this one is using a lot of electricity over 150w per card

I have used Polaris Editor 1.62 to change timings

Im at my wits end and can use some help if someone has run into these issues before

Thanks in advance
sr. member
Activity: 467
Merit: 252
Your miners work ok after fork?

Actually difficulty on Eth has dropped drastically. I'm noticing my profits go up by the hour here. This is awesome news for us miners. Anyone else notice?
full member
Activity: 533
Merit: 100
I have 2 issues with Claymore 10.0 (Win10, blockchain drivers, 6card rigs running 570 and 470 cards)

1) After initial rig start (i.e. after powering or resetting the whole rig) Claymore 10.0 runs with lower hashrates (for example about 23-25Mhs with 470/570 cards). After stoping the miner and re-run .bat, I getting normal rates (i.e. miner has to be restarted and operates as expected only after 2nd run, never from the first)

2) Unpredictable hashrate drop during mining for some cards in rig (usually 1 or 2 of them). Rate drops and keeps at 23-25. The only solution I found is to restart Claymore.


Any comments guys?



Same issue here...as mentioned 470's and 570's
Has anyone found a fix for this ?
I have as instructed tried the timeout and it does not work
Thanks in advance


Are you talking about problem numbered 1 or numbered 2?
As to No.1 I was discussing with few people and they have similar problems, not solved. I am not worry too much as it happens only at first start.
But No.2 really makes me headache, because unpredictable.

I am having a # 1 issue....but

on #2 add if using the .bat file --tt 70 --fanmin 50

the reason is that the cards are throttling down due to temp

see if that helps



Put these in the config file:

-r 0
-minspeed

by using those commands, miner will restart if it cannot reach X hashrate in 5 minutes.
this is tried and tested as per my experience.


Friends and my MSI 570 with Hynix chips are snaping today like crazy.
We use Claymore 10.0, AB 4.4.0. beta 16, Driver 9.14.10.01293. Crismon BETA
Until today everything was ok.
What's happening?
newbie
Activity: 57
Merit: 0
Something strange happens with my miner's monitor

I use Claymore monitor 3.4, miner version 10.0
1 or 2 rigs are constantly loosing connection with monitor. I.e. Monitor turns red and in "lost" state for corresponding miner.

While miner actually works (with pool) but with message:
ETH: GPU0 28.009 Mh/s, GPU1 28.529 Mh/s, GPU2 28.366 Mh/s, GPU3 27.995 Mh/s, GPU4 28.001 Mh/s
server: bind failed with error: 10048 (port for remote management is busy, use different -mport value), next attempt in 20sec...

I tried different -mport values but it doesn't help. It happens since Saturnday. I use read-only mode and internal IP


LOL. I had similar behavior, no any error msg in logs though: single worker (out of multiple ones in the same LAN) was constantly loosing connection. And it seems I just fixed it in a really weird way: get EthMon 2.9, place your config into its dir(to speed things up), remove all related entries from win firewall, run it and allow both public & private profiles = that's it. Have NO idea why it works now... or why it wasn't working before.
If I do the same procedure with 3.4 it wont solve the problem... I'm really confused.

EDIT: @Kukus Please try and report back.

Reporting:
I didn't check anything in firewall. Just run ver2.9 and it works. But now, when I've tried 3.4, this mystic software works again. But I have to wait because miner looses connection after 6-10 hours only.
sr. member
Activity: 857
Merit: 262
Which drivers you guys using?
On the first page still say 372. But they are so old

For Nvidia you can just use the latest drivers - it will be fine.
sr. member
Activity: 857
Merit: 262
Something strange happens with my miner's monitor

I use Claymore monitor 3.4, miner version 10.0
1 or 2 rigs are constantly loosing connection with monitor. I.e. Monitor turns red and in "lost" state for corresponding miner.

While miner actually works (with pool) but with message:
ETH: GPU0 28.009 Mh/s, GPU1 28.529 Mh/s, GPU2 28.366 Mh/s, GPU3 27.995 Mh/s, GPU4 28.001 Mh/s
server: bind failed with error: 10048 (port for remote management is busy, use different -mport value), next attempt in 20sec...

I tried different -mport values but it doesn't help. It happens since Saturnday. I use read-only mode and internal IP


LOL. I had similar behavior, no any error msg in logs though: single worker (out of multiple ones in the same LAN) was constantly loosing connection. And it seems I just fixed it in a really weird way: get EthMon 2.9, place your config into its dir(to speed things up), remove all related entries from win firewall, run it and allow both public & private profiles = that's it. Have NO idea why it works now... or why it wasn't working before.
If I do the same procedure with 3.4 it wont solve the problem... I'm really confused.

EDIT: @Kukus Please try and report back.
sr. member
Activity: 756
Merit: 250
Which drivers you guys using?
On the first page still say 372. But they are so old
sr. member
Activity: 857
Merit: 262
Did something happen that hit CUDA mining particularly hard that last DAG change? The hashrate on the MSI GTX 1070 GAMING X in my gaming rig dropped almost 2Mh/s but the RX 480s were unaffected.  Huh
I have an issue with my 1070 Gaming X too.
Hashrate seems to remain the same, but effective hashrate is much lower.

There was no changes for my 1060s whatsoever.
I'm still plagued though with whatever it is (see below) on workers with 8*amd and some Nvidia
Code:
21:22:19:597	117c	CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.
21:22:20:299 7ec GPU 9, GpuMiner cu_kd failed 30 (4), unknown error
21:22:20:299 7ec GPU 9, Calc DAG failed!
21:22:20:424 7ac GPU 10, GpuMiner cu_kd failed 30 (4), unknown error
21:22:20:440 f48 NVML: cannot get current temperature, error 999 (an internal driver error occurred)
21:22:20:440 f48 NVML: cannot get fan speed, error 999 (an internal driver error occurred)
sr. member
Activity: 518
Merit: 250
I am a meat Popsicle
Lol how to get profit with mining. I have loss so much money for electric  Cry

Unless you know what to mine. Take the new Baikal for instance: https://altmininggear.com/shop/baikal-giant-x10/ , it mines @ 10 gh/s on x11, BUT it can also mine on other algorithms with much lower difficulty rates. Or you could mine different coins on the same algorithm. So the most used purpose of such a machine would be to mine dash. As for now, you would able to mine about $73 @ $0.20 per kW/h, worth of dash every week. But you could also choose to mine cannabis coin, which uses the same algorithm. Now you're mining $75 @ $0.20 per kW/h . Not a huge difference. But still $104 per year.

That Miner costs twice as much as the D9 and has 50% less hashing power and is less efficient electricity wise. Anyone who buys that miner, as soon as the D9's come online in November will lose any chance to make ROI on that thing

I'm only finding info for D3s; where can we find info on D9s?
Sorry Meant to write D3's  D3 is up to 15GH 1200w  and 1250usd at BITMAIN when available
newbie
Activity: 15
Merit: 0
Lol how to get profit with mining. I have loss so much money for electric  Cry

Unless you know what to mine. Take the new Baikal for instance: https://altmininggear.com/shop/baikal-giant-x10/ , it mines @ 10 gh/s on x11, BUT it can also mine on other algorithms with much lower difficulty rates. Or you could mine different coins on the same algorithm. So the most used purpose of such a machine would be to mine dash. As for now, you would able to mine about $73 @ $0.20 per kW/h, worth of dash every week. But you could also choose to mine cannabis coin, which uses the same algorithm. Now you're mining $75 @ $0.20 per kW/h . Not a huge difference. But still $104 per year.

That Miner costs twice as much as the D9 and has 50% less hashing power and is less efficient electricity wise. Anyone who buys that miner, as soon as the D9's come online in November will lose any chance to make ROI on that thing

I'm only finding info for D3s; where can we find info on D9s?
newbie
Activity: 57
Merit: 0
Something strange happens with my miner's monitor

I use Claymore monitor 3.4, miner version 10.0
1 or 2 rigs are constantly loosing connection with monitor. I.e. Monitor turns red and in "lost" state for corresponding miner.

While miner actually works (with pool) but with message:
ETH: GPU0 28.009 Mh/s, GPU1 28.529 Mh/s, GPU2 28.366 Mh/s, GPU3 27.995 Mh/s, GPU4 28.001 Mh/s
server: bind failed with error: 10048 (port for remote management is busy, use different -mport value), next attempt in 20sec...

I tried different -mport values but it doesn't help. It happens since Saturnday. I use read-only mode and internal IP
jr. member
Activity: 41
Merit: 3
Your miners work ok after fork?
Jump to: