Topic: Claymore rigs unhandled crushes (Read 577 times)
Do they just offer some generic answers or they actually are trying to help you if you have some specific issue? Can you give us a list of those pools?
I know some Mining Pool that assists you 24/7 if you mine with them. They are pretty awesome tho, a lot of good feedback from the community.
Thank you for your feedback. I will give it a try because I also have a problem with Claymore recently (but I don't have the same error as you had).
Of cause I use claymore only in miner pc 
If it has virus (but Windows Defender still not say anything) I don't worry about this.
Also, I still use this path, it is working fine and crushes gone!
I am really happy. It takes too many time to solve this problem
If it has virus (but Windows Defender still not say anything) I don't worry about this.
Also, I still use this path, it is working fine and crushes gone!
I am really happy. It takes too many time to solve this problem
Some people mine on their desktop PC, the only computer they have, so they don't have much choice. No one can guarantee that malware isn't inserted in this modified miner's code.
I'm not worried about the hash rate and small % that miner can take. I'm afraid of key loggers that can help hackers to steal all you have in wallets, exchanges...
I'm pretty sure that any clever miners wont use his mining rigs as a (spendable) wallet.If there's a real threat, it will be his privacy.
unless if there's something in the code/file.
I'm glad you solved your problem, but is this solution safe? This is unofficial fix, right? Are you sure that code is virus-free?
Thank you for your worry. Of cause I can't be sure about safe. But in last 6 days approx I don't see any changes in hashrate all work stable and like original Claymore. So I leave it as is and if something happened later I leave a message here
I'm glad you solved your problem, but is this solution safe? This is unofficial fix, right? Are you sure that code is virus-free?
Thank you for your worry. Of cause I can't be sure about safe. But in last 6 days approx I don't see any changes in hashrate all work stable and like original Claymore. So I leave it as is and if something happened later I leave a message here
I'm glad you solved your problem, but is this solution safe? This is unofficial fix, right? Are you sure that code is virus-free?
Looks like I found solution.
Few days I use this patch in 6 rigs (in different places)
https://github.com/proxymanext/claymore-srv-fix
At this moment crushed end's. Hash rate stable and same to original claymore.
Today I try update other rigs to this version, hope it help to me.
Few days I use this patch in 6 rigs (in different places)
https://github.com/proxymanext/claymore-srv-fix
At this moment crushed end's. Hash rate stable and same to original claymore.
Today I try update other rigs to this version, hope it help to me.
I'm using 11.5 and 11.9 versions of Claymore for Ethereum. They are working very stable and give approximately the same hashrate as latest Phoenix miner. I think that problems appear if there are very strong overclocking and small size of the swap file.
I've just checked and saw that latest Claymore miner is over a year old https://mega.nz/#F!P0ZjFDjC!Cmb-ZRqlbAnNrajRtp4zvA. Maybe it has some compatibility issue with the latest Windows build. You guys should try some other miner.
Hello there!
Today all my rigs with claymore dual miner crushed.
Rigs have different versions of claymore, starting from 11.5 up to 11.9.
What happend:
In a hour approx all rigs stops, but, windows still running. Just miner software crush without any errors, watch dog does not help.
Windows updates fully disabled. I don't touch most of rigs more then half of year (and few more then year).
Also rigs stored in fully different places and don't have any relation
I don't see any helpful logs. Looks like it is just stop working. Windows logs also don't have any thing.
After restarting all rigs, I have few crushed again in a 2 hours after restart.
What happend? Anybody facing something equal???
Today all my rigs with claymore dual miner crushed.
Rigs have different versions of claymore, starting from 11.5 up to 11.9.
What happend:
In a hour approx all rigs stops, but, windows still running. Just miner software crush without any errors, watch dog does not help.
Windows updates fully disabled. I don't touch most of rigs more then half of year (and few more then year).
Also rigs stored in fully different places and don't have any relation
I don't see any helpful logs. Looks like it is just stop working. Windows logs also don't have any thing.
After restarting all rigs, I have few crushed again in a 2 hours after restart.
What happend? Anybody facing something equal???
Hie,
I have the same problem too... windows is running good but miner crashes and all other mining programs are working except claymore 11.X. i have tried all claymore versions, i have checked all other ways. please help me in finding solution.my virtual memory is 50GB. i have tried phoenix miner, it is good
I facing same issue two days ago.
It looks very equal to Dzeronimo's answer but now. It is different problem and I don't find same in Claymore thread.
I still try to google it and check all my rigs/internet/electricity and now I can say, it is problem with Claymore it self.
May be virus, but it working from network, not from local OS
It looks very equal to Dzeronimo's answer but now. It is different problem and I don't find same in Claymore thread.
I still try to google it and check all my rigs/internet/electricity and now I can say, it is problem with Claymore it self.
May be virus, but it working from network, not from local OS
You are not the only one with that issue. This post is two years old https://bitcointalksearch.org/topic/m.17167363 so it's not a new issue. Try to ask for help in the official Claymore thread.
Hello there!
So in most of rigs I have many many rows in logs like this part:
So after this logs program just crush
So in most of rigs I have many many rows in logs like this part:
Code:
00:55:15:210 1a4c srv pck: 34
00:55:15:210 1a4c srv: remove pck 456
00:55:15:226 1a4c srv bs: 456
00:55:15:226 1a4c srv pck: 34
00:55:15:242 1a4c srv: remove pck 421
00:55:15:257 1a4c srv bs: 421
00:55:15:257 1a4c srv pck: 34
00:55:15:273 1a4c srv: remove pck 386
00:55:15:273 1a4c srv bs: 386
00:55:15:289 1a4c srv pck: 34
00:55:15:289 1a4c srv: remove pck 351
00:55:15:304 1a4c srv bs: 351
00:55:15:304 1a4c srv pck: 34
00:55:15:320 1a4c srv: remove pck 316
00:55:15:335 1a4c srv bs: 316
00:55:15:335 1a4c srv pck: 34
00:55:15:351 1a4c srv: remove pck 281
00:55:15:351 1a4c srv bs: 281
00:55:15:367 1a4c srv pck: 34
00:55:15:382 1a4c srv: remove pck 246
00:55:15:382 1a4c srv bs: 246
00:55:15:398 1a4c srv pck: 34
00:55:15:414 1a4c srv: remove pck 211
00:55:15:414 1a4c srv bs: 211
00:55:15:429 1a4c srv pck: 34
00:55:15:429 1a4c srv: remove pck 176
00:55:15:445 1a4c srv bs: 176
00:55:15:445 1a4c srv pck: 34
00:55:15:460 1a4c srv: remove pck 141
00:55:15:460 1a4c srv bs: 141
00:55:15:476 1a4c srv pck: 34
00:55:15:492 1a4c srv: remove pck 106
00:55:15:492 1a4c srv bs: 106
00:55:15:507 1a4c srv pck: 34
00:55:15:507 1a4c srv: remove pck 71
00:55:15:523 1a4c srv bs: 71
00:55:15:523 1a4c srv pck: 34
00:55:15:539 1a4c srv: remove pck 36
00:55:15:554 1a4c srv bs: 36
00:55:15:554 1a4c srv pck: 34
00:55:15:570 1a4c srv bs: 0
00:55:31:235 16ac GPU0 t=47C fan=28%
So after this logs program just crush
Guys, thank you for all again!
But I try check all described things. It is really looks like magic.
More important! Today my friend told me same story. He have some less rig count, and all they crush like my.
But he say about some logs and promise me send it later, so I waiting for review and post it.
Also I enable logs in few my rigs, but I have new crushes in another rigs So I need some time for enable logs in all rigs for find problem.
I post back when get any information
But I try check all described things. It is really looks like magic.
More important! Today my friend told me same story. He have some less rig count, and all they crush like my.
But he say about some logs and promise me send it later, so I waiting for review and post it.
Also I enable logs in few my rigs, but I have new crushes in another rigs
So I need some time for enable logs in all rigs for find problem.I post back when get any information
DAG size became too large, you have to increase your virtual memory. The size of the swap file must be more than sum of all memory of your GPUs.
Depending on your previous response, it looks like the only one left unchecked is the Operating System if all of your rigs uses the same.
Must be (still) a problem with Windows Update, it can still find a way to self-enable depending on your OS's version (especially Windows10).
Unfortunately, I can't help you with it since I'm not using W10 due to the same issue.
And...
Must be (still) a problem with Windows Update, it can still find a way to self-enable depending on your OS's version (especially Windows10).
Unfortunately, I can't help you with it since I'm not using W10 due to the same issue.
And...
Today all my rigs with claymore dual miner crushed.
It was beyond repair
Are all those rigs connected to the same pool? Maybe pool had some problem that caused miner to crash. You can leave Claymore on some rigs and use another miner on the rest of rigs (use the same pool). If again only the rigs with Claymore crash you definitely have a problem with the miner.
Jump to: