Author

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

hero member
Activity: 2100
Merit: 562
IM using windows 10 1709 build with 12 amd cards
I notice that my gpu 10 hangs opencl, I'll check all the cables and riser but all are okay, but Im using old driver.. Is my driver version is the reason why my card hang? What is the better amd driver is capable of this 11.7 version of claymore? Any help will appreciated!!
newbie
Activity: 37
Merit: 0
Has anyone tried dualmining on 1080ti with ethlargement pill?

Does this pill increase share count, not hash rate?
jr. member
Activity: 251
Merit: 6
Has anyone tried dualmining on 1080ti with ethlargement pill?
newbie
Activity: 74
Merit: 0
The most stable driver for Nvidia 1060 6g?
jr. member
Activity: 42
Merit: 8
small bugreport:

mining didn't start if you set this two options at the same time:
-allcoins -1
-nofee 1

Did you read the readme? "-allcoins" and "nofee" section?

Some real-world advice.
If you're not going to pay for it, don't bitch about your issues!

If you don't like the rules, (see the readme), you have very clear instructions right there.
"you should find some other miner that meets your requirements, just don't use this miner instead of claiming that I need " etc etc.

You might not like it, but it's honest, and you can't say you were not informed up front, and had a choice from the start.



newbie
Activity: 56
Merit: 0
Claymore, first of all, thank you for all your great miners! I've been using them for a while, for various crypto currencies, but this must be the one I've been expecting the most.
jr. member
Activity: 42
Merit: 8
Does anyone has challenged with asrock h110 pro btc?

Hey, was this rig ever stable?
To put it another way, is this a new issue, and previously this rig was stable?

One thing I wanted to post on, PSUs, deserves it's own post, so check back in 30 min, I'll write it up now.
Good luck btw.

Yes, it was stable with 10 AMD RX. Now it's working for 14 hours. But yesterday there were 3 sudden reboots in one hour
...

Of course, given payback time mining, it WAS worth it, but one can only say that with hindsight, and I've actually settled on 8GPU as a max per rig, (with 1000W PSUs), simply because I can build that up to super stable in half a day, and have a pretty high certainty it will be mining after 5 hours, and at what hash rate.

The problem is, with more and more GPU per rig, down time REALLY starts to hurt more and more.
Even rebooting a 13GPU rig, that is 13 GPU doing nothing.

...

+100500! Even starttime for 13 GPUs is terrible:)

Thx a lot and good luck to you.


Hahahaha, Oh man, I feel your pain.
Oh, one last thing, the PCIe slots on the asrock h110 pro btc are REALLY close together.

One of the problems I observed was how easy it was to introduce instability by dislodging the PCIe cards in the slots.
I'd start out with one problem, and introduce another because the USB3 cables can easily unseat, or rotate the PCIe cards in the slots.

I decided to string them all together, as they have 1 hole in the over-hang, and I used nylon standoffs, to "bolt" all the PCIe cards into a single bank.

I used these

https://www.amazon.co.uk/260pcs-Black-Spacers-Stand-off-Assortment/dp/B01GVD146I/ref=sr_1_1?ie=UTF8&qid=1526890885&sr=8-1&keywords=nylon+standoffs

Of course it's not quite so easy to change a failed PCIe, as you have to remove the whole bank as one, but it only adds a minute or two, and the added stability, (and chance to rule out that failure variable) is well worth it.

I wonder, with the asrock h110 pro btc, the slots are SO close to each other, if it's possible for the USB socket on one PCIe card, to tip/tilt over, and short on the back of the adjacent card?

Anyway, something to check, think about.

Good luck.


 



jr. member
Activity: 42
Merit: 8
my Claymore's is stuck and my pool is nanopool, what the problem ? any one help? im not the only one who have this problem. thanks!




Log File?


this my log file :


08:57:41:807   1864   Check and remove old log files...
08:57:41:807   1864   args: -epool eth-asia1.nanopool.org:9999 -ewal ****/****@gmail.com -epsw x -mode 1 -ftime 10
08:57:41:807   1864   
08:57:41:807   1864   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
08:57:41:823   1864   º                Claymore's Dual GPU Miner - v11.7               º
08:57:41:823   1864   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
08:57:41:823   1864   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
08:57:41:823   1864   
08:57:41:823   1864   b583
08:57:42:042   1864   ETH: 5 pools are specified
08:57:42:042   1864   Main Ethereum pool is eth-asia1.nanopool.org:9999
08:58:14:862   388   
08:58:47:667   388   
08:59:20:472   388   
08:59:53:277   388   
09:00:26:082   388   
09:00:58:887   388   
09:01:31:692   388   
09:02:04:497   388   
09:02:37:302   388   
09:03:10:107   388   
09:03:11:138   388   Miner cannot initialize for 5 minutes, need to restart miner!
09:03:12:747   388   Restarting OK, exit...






That looks painful. Without knowing anything about your rig, hardware, os etc.
Two things come to mind.

1: Set log to debug mode "-dbg 1" see if you get more clues.
2: Check your hardware. Power down, bleed down), (search for my previous post, "bleed" for explanation on that topic).
Hardware Checks: Remove all GPUs except 1, see if Claymore gets further through the init.

(You should be seeing it initialise OpenCL or Cuda at that point).
If it were a driver issue, you'd see that "missing" and you don't, so I'm thinking your issue is more likely hardware than OS/driver, and it's not Claymore for sure.

I don't know what debug will print out in this situation as I have never encountered it, but debug is certainly the very first thing you should try, because if you have a permanent fault condition, you want to gather as much data as you can, while the fault is present, BEFORE you start to change anything, or reboot etc.

In terms of fault finding, permanent fault conditions are easy to track down compared to seemingly random, intermittent type issues.

If you don't get any further, post a summary of your RIG spec, (look at the post from iRrromka, because his post is how you do that correctly).

Good luck
newbie
Activity: 37
Merit: 0
Does anyone has challenged with asrock h110 pro btc?

Hey, was this rig ever stable?
To put it another way, is this a new issue, and previously this rig was stable?

One thing I wanted to post on, PSUs, deserves it's own post, so check back in 30 min, I'll write it up now.
Good luck btw.

Yes, it was stable with 10 AMD RX. Now it's working for 14 hours. But yesterday there were 3 sudden reboots in one hour
...

Of course, given payback time mining, it WAS worth it, but one can only say that with hindsight, and I've actually settled on 8GPU as a max per rig, (with 1000W PSUs), simply because I can build that up to super stable in half a day, and have a pretty high certainty it will be mining after 5 hours, and at what hash rate.

The problem is, with more and more GPU per rig, down time REALLY starts to hurt more and more.
Even rebooting a 13GPU rig, that is 13 GPU doing nothing.

...

+100500! Even starttime for 13 GPUs is terrible:)

Thx a lot and good luck to you.
jr. member
Activity: 42
Merit: 8
Does anyone has challenged with asrock h110 pro btc?

Hey, was this rig ever stable?
To put it another way, is this a new issue, and previously this rig was stable?

One thing I wanted to post on, PSUs, deserves it's own post, so check back in 30 min, I'll write it up now.
Good luck btw.

Yes, it was stable with 10 AMD RX. Now it's working for 14 hours. But yesterday there were 3 sudden reboots in one hour

Your RIG and component selection/quantity is very similar to one of my RIGs.
Actually, I have scaled back from 13GPU, max 4x RX580 per 1000W Corsair, (assuming 1 PSU is also powering MB).
I did build a 13GPU rig for someone, and it IS super stable, but it was a long fight to get there, and I'd estimate it cost at least 1 month of downtime before I felt that is really stable.
That is 1 month of lost mining time, and a LOT of my time, Given it was super stable at 10GPU, loosing so much time for the 11th, 12, and mostly 13th GPU makes me consider if that was worth it.

Of course, given payback time mining, it WAS worth it, but one can only say that with hindsight, and I've actually settled on 8GPU as a max per rig, (with 1000W PSUs), simply because I can build that up to super stable in half a day, and have a pretty high certainty it will be mining after 5 hours, and at what hash rate.

The problem is, with more and more GPU per rig, down time REALLY starts to hurt more and more.
Even rebooting a 13GPU rig, that is 13 GPU doing nothing.

Don't get me wrong, I learned a lot from that 13GPU project, it's actually a Asus B250, so has another 6 slots free, but adding in Nvidia at this stage, means shutting it down, 13x GPU doing nothing.
Now, if it was unstable right now, that might be different, but it's super stable, I don't even reboot it, I was hoping for a new run-time record on it actually, but had a damn power cut last week, but it still holds the record in all my rigs, (170 hours) nonstop (until the power cut), and that is Claymore too of course, no restarts even.

Anyway, good luck, and kudos on the 13GPU rig man :-)






newbie
Activity: 2
Merit: 0
my Claymore's is stuck and my pool is nanopool, what the problem ? any one help? im not the only one who have this problem. thanks!

https://ibb.co/eVNsO8


Log File?


this my log file :


08:57:41:807   1864   Check and remove old log files...
08:57:41:807   1864   args: -epool eth-asia1.nanopool.org:9999 -ewal ****/****@gmail.com -epsw x -mode 1 -ftime 10
08:57:41:807   1864   
08:57:41:807   1864   ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
08:57:41:823   1864   º                Claymore's Dual GPU Miner - v11.7               º
08:57:41:823   1864   º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
08:57:41:823   1864   ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
08:57:41:823   1864   
08:57:41:823   1864   b583
08:57:42:042   1864   ETH: 5 pools are specified
08:57:42:042   1864   Main Ethereum pool is eth-asia1.nanopool.org:9999
08:58:14:862   388   
08:58:47:667   388   
08:59:20:472   388   
08:59:53:277   388   
09:00:26:082   388   
09:00:58:887   388   
09:01:31:692   388   
09:02:04:497   388   
09:02:37:302   388   
09:03:10:107   388   
09:03:11:138   388   Miner cannot initialize for 5 minutes, need to restart miner!
09:03:12:747   388   Restarting OK, exit...



jr. member
Activity: 42
Merit: 8
OVERLOAD!

Background:
In the early days of my mining project, I had managed to get 2 rigs stable.
They were built in succession, so the RIG1 had been running non-stop for some 7~8 weeks, ahead of RIG2.

These rigs used a few different PSUs, all Corsair 1000W, RM1000x, HX1000, HX1000i.

At about the 3 month point, RIG1, hit a bump, "random" reboot, (it's was running a USB watchdog, so I was unsure if this was the trigger, and disabled it for testing purposes), equally, event logs only mentioned kernel power, which is pretty vague.
Fortunately, things went downhill fast, and I stripped the rig down for inspection.

Cutting to the chase here, the problem was traced to the SATA/Peripheral 6pin plug on the PSU itself.
In this case, the connector was melted on the 12V pin, the pin welded into the cables socket, and all the insulation crumbled on the plug/socket, and melted some 2cm up the wire itself.

Now, I had failed to appreciate a number of things, and these are worth sharing.
The plugs are rated 10A, but in reality, one should not assume to work anywhere close to that "limit" for 24/7 operation.
Usually about half that is a safe maximum.

Why I didn't pay attention to a glaringly obvious stupidity on the part of Corsair is my own fault.

The Corsair, (and cables of all the PSU vendors for that matter), all have 4 Molex connectors in parallel. Now each Molex is rated to 10A, so how can one expect to pull half that, x4, (20A) through a single 10A plug/socket on the PSU?
Or if you want kindergarten logic, pull 4x 10A (molex) (40A) through a single 10A outlet?

I had stupidly assumed the PCIe risers were mostly inert, as power would in the whole come direct to the GPU.
WRONG!

In all cases I had used all 4 of those cable headers, whether those be molex or SATA power, and in all cases there were clear signs or damage after 3 months. (<2 months on rig2!)

I've rewired all my rigs, maximum 2 devices (PCIe risers, SSD, relay, fan-banks) per cable.

The Corsair PSU in all cases failed to trip safety cutouts, at least the HX1000i didn't log that it had, the RM1000x and HX1000, have no datalink so maybe they did, I have no way to tell.
But equally, this kind of failure is unlikely to cause a trip out, because the PSU is actually delivering LESS power, as current flow is inhibited by the degrading plug/socket!

I shipped 3 PSU back to Corsair.

Signs to look for.
Has a previously stable rig, become unstable, and you didn't change anything, drivers, hardware, etc?
Do you have more than 2 devices on a single power cable?

Checks/Inspections
Power off all PSUs, remove AC plugs, then remove the cable-sockets from the PSU outlet plugs.
Inspect the pins in the PSU outlet plugs.

Warning signs include: Pins no longer shiny/silver/gold, but dull, oxidised, black or burned.
Gently flex the cable near the FAR end of the cable, (farthest from the PSU), this should give you a feel for GOOD cable flex, (normal for THAT cable). Now repeat that flex-test at the other end of the cable, (right where it comes out of the PSU plug).
If you feel less flex, or it could be like a solid rod, no flex, that is a clear sign of overload.

This is a vicious cycle, as you overload, the wires heat up, they expand and abraid on each other, and oxidise. They do this more, right next to any connection, because there is a break in the insulation, allowing the ingress of air, and the oxygen component accelerates the oxidisation. The cables loose flexibility because of this, and also heat up more, accelerating their demise, in extreme cases this will melt away the wire insulation, and even the plug/socket.
If there was ANY human element during manufacture, (skin oils on the wires during handling, crimping, poor stripping, stand damage, poor crimping, bruising), these will drastically increase the likelihood of failure, especially if you pull more current through them.

ALL these signs were present on all my RIGs!!!

All have been rewired 2 PCIe risers per power cable, and 6 weeks on, all reinspected and there were no signs of degradation. A further inspection was done 2 months later, and again there were no signs of overload.

I have a feeling there will be MANY miners out there, who didn't give much thought to plug/socket ratings, and trusted the vendors would be using safe practice, WRONG!

Think: National Lampoons Christmas Vacation, (the Christmas lights scenes), because Evga, Corsair, and all the other vendors are shipping time bomb cables, and NO WARNINGS on them, or the PSU manuals.

Using 3 of the 4 headers might be ok, I opted for maximum of 2, because this is standard/safe practise in situations like this.


REPEAT:
Signs to look for.
Has a previously stable rig, become unstable, and you didn't change anything, drivers, hardware, etc?
Do you have more than 2 devices on a single power cable?

Finally: Don't jump to conclusions about Claymore or OS, or drivers, until you're satisfied the hardware is OK!


Good luck everyone.
newbie
Activity: 37
Merit: 0
Does anyone has challenged with asrock h110 pro btc?

Hey, was this rig ever stable?
To put it another way, is this a new issue, and previously this rig was stable?

One thing I wanted to post on, PSUs, deserves it's own post, so check back in 30 min, I'll write it up now.
Good luck btw.

Yes, it was stable with 10 AMD RX. Now it's working for 14 hours. But yesterday there were 3 sudden reboots in one hour
jr. member
Activity: 42
Merit: 8
Does anyone has challenged with asrock h110 pro btc?

I have one config on

0. Win10Pro 1709
1. Clay 11.7
2. AMD 18.3.4
3. 13 AMD RX 580 8 GB
4. 8 gb RAM
5. 80 gb virtual memory
6. 3 PSU Corsair HX1000

It can mine for hours and reboots twice in a minutes.


Hey, was this rig ever stable?
To put it another way, is this a new issue, and previously this rig was stable?

One thing I wanted to post on, PSUs, deserves it's own post, so check back in 30 min, I'll write it up now.
Good luck btw.

member
Activity: 182
Merit: 13
Hi guys,which coin is worth in dual mining?
newbie
Activity: 21
Merit: 0
small bugreport:

mining didn't start if you set this two options at the same time:
-allcoins -1
-nofee 1
newbie
Activity: 21
Merit: 0
last week i have this problem on amd hd 7950 and 280x with 3gb gddr
OS: windows 7
Code:
13:18:31:718	84c	Setting DAG epoch #187 for GPU2
13:18:31:843 aa4 GPU0, OpenCL error -4 (0) - cannot create DAG on GPU
13:18:31:859 84c GPU2, OpenCL error -4 (0) - cannot create DAG on GPU
I use them to mining not ethereum coin (like pirl). And I have to set the parameter "-nofee 1"
newbie
Activity: 1
Merit: 0
Does anyone has challenged with asrock h110 pro btc?

I have one config on

0. Win10Pro 1709
1. Clay 11.7
2. AMD 18.3.4
3. 13 AMD RX 580 8 GB
4. 8 gb RAM
5. 80 gb virtual memory
6. 3 PSU Corsair HX1000

It can mine for hours and reboots twice in a minutes.


Your problem is windows and the solution is Simple Mining OS 😉
newbie
Activity: 37
Merit: 0
Does anyone has challenged with asrock h110 pro btc?

I have one config on

0. Win10Pro 1709
1. Clay 11.7
2. AMD 18.3.4
3. 13 AMD RX 580 8 GB
4. 8 gb RAM
5. 80 gb virtual memory
6. 3 PSU Corsair HX1000

It can mine for hours and reboots twice in a minutes.
jr. member
Activity: 42
Merit: 8
my Claymore's is stuck and my pool is nanopool, what the problem ? any one help? im not the only one who have this problem. thanks!




Log File?
Jump to: