Topic: [Cast XMR] high speed XMR/CryptoNight miner for RX Vega GPUs (2 KHash/s) - page 136. (Read 206406 times)

Is there anything that can be done to reduce "outdated" shares on NiceHash?  I think the only way to do this is to reduce the difficulty and as far as I know there is no way to do this with NiceHash.

Also I still get random drops on my Vega 56 from 1950 H/s to 1710 H/s after some period of time.  I'd really like to figure this out, it's going to be a big problem as I scale up my Vegas.  Does Cast XMR have an API to monitor hash rates?  I could just restart things on a timed basis but that is a kludge and not very efficient.

Figured it out. The newb that I am was trying to run the .exe

Thanks

It is so cool (pun intended) with how cool and power saving CryptoNight is.  My RXs are running like 40W lower and much cooler than when mining ETH, let alone dual mining, and my profit is much higher.  Man I hope this continues for at least a few months.

It was a rough last couple of months for mining but things are looking up at the moment.

It doesn't even work on an RX 560, I tried.

For shits and giggles I tried this on my old old Radeon 6990 GPU, didn't work.

I think your user name is wrong.  I just use BTCwalletaddress.workername

Everything else looks ok I think.  This is my command line (BTC address changed to protect my privacy):

cast_xmr-vega -G 0 --opencl 1 -S cryptonight.usa.nicehash.com:3355 -u 1Ljdskfhsjdhfjsdfhkjsdhfkdshfksd.castxmr

Does anyone know how (or if) you can use Cast 0.6 on Nicehash? I'm not getting how to set up the .bat file correctly.

I have:
 
This results in "no pool server and username configured."

you probably have unstable gpu  oc you ram to much ?

looks like stop hashing and restart

I expresses the same concerns as you a few posts back. The reported rates from cast-xmr and way higher than what my pools (more than 1) report after long periods (24hrs).

In my case, there is about 4.4% unaccounted hashrate loss on average.

I my case, I too see these long periods with no hashes sent to the pool followed by a normalization.

Also, at times the fans of the cards will go suddenly from 3200 rpm to 4400 rpm for about 30 seconds then normalize. This is what happens when they're reloaded with new kernels. I think however this is normal (fee collection on another pool and / or the resync of the ndqueue that cast seems to do to speed things up).

However, where's that 4.4% lost ? I don't know. I'm currently using it *only* because it's more stable with my rigs. It does eat more energy than stak howeve (in my case).

Yesterday i test my Rx Vega 56 8gb Powercolor on a  win10 system with blockchain drivers from AMD.

The weird thing happen with gpu-z, on win7 it shows that vega has got micron ram and on win10 system it shows Samsung ram, right now i dont really know which one is it.

Results:

Win7 with latest Crimson driver
35mhs at ETH with 165watt
700hs at MONERO with 155 watt
200-250hs at ZEC with 160 watt

Win10
38mhs at ETH with 170watt
1070hs at MONERO with 170 watt
400hs at ZEC with 160 watt

I will do even more testing but the only thing that bugs me is that GPU-Z because i am not sure which RAM i have and if i want to mod the card how and with which mod should i do it?

Is it possible to downgrade a Vega 64 to get the same hashes and power consumption as a Vega 56?

According to http://www.gandalph3000.com/cast_xmr/howto-mine-monero-rx-vega/ Vega 56 has the exact same hash rate with 50W less, so I wonder if anyone tried Vega 64 with the same frequencies as 56 etc.?

Why: Because Vega 64 are available here, 56 are not.. and I wouldn't like to spend more bucks on a worse card

Thanks for this great thread!

Hello.
Thank you for your work.
Some time I have 0 (zero) hashrate on one card.
Will be great if in future release you add zero hashrate detector for restarting miner.

you use GPU-z or other similar soft?

Okay, I've had the miner pretty stable at 2040 H/s for the past day. The same two errors appeared, but a quick close/run or reboot solved them both.

The strange 1950 H/s dips every few reports - closing and rerunning the algorithm seems to fix it. I don't know what is doing it. It just happened now when I opened Calculator, and then it stopped when I closed it... I don't know why calculator would have anything to do with it, but I was literally just calculating my daily hashrate and watched it start misbehaving! Lol.

The 200 H/s drop, down to 1850 H/s - rebooting is the only thing that fixes this once it starts, it seems. I've tried reinitializing HBCC, and it's not enough. I haven't tried going into registry and disabling/reenabling the card, which Mythic mentions in his Oct.27 post if you want to look that up.

I have a new concern though...

https://i.imgur.com/m1SMKmb.png

What's going on with this miner? Is this how the dev fee is implemented? I'd love more information about the workings of this algorithm. Does anyone else have dry spells with no shares? I'm literally having another one while writing this post, it's been almost two minutes with no shares submitted. It's very odd for this card... I get consistent shares between 20-40 seconds, sometimes faster, but to then jump to a 4 minute dry spell seems very odd.

Maybe you tried it already, but looking at your settings I would bump the GPU up to 900 to 904 (keep it at 1400-1408, e.g., 1405/900), and on memory keep 850 but try dropping to 1070 (1070/850).

I've tried both XMR-STAK and Cast.  Both are stable in my particular setup.  I think Cast gives just slightly better total speed and just a hair less power usage.  3 cards so far but adding more this weekend.

After a bit more than 24 hours of running, I don't really see the point of using this.
While my xmr stak setup was running like a champ for weeks, with the same settings this thing is just not stable. Had to restart 4 times during that time - all after several hours of working, because suddenly one card freezes and starts hashing at 0 for a few seconds, and then the program freezes. That thing happened to 3 different cards. And these same cards were running at these settings for weeks with XMR Stak with no issues ...

The output hashrate looks higher, but with the sudden drops of hashrate for every card in the rig (all at different times) the average hashrate looks only around 100 H/s higher (for the whole rig).
That at the time when the miner is running, the ~1 hour I lost to downtimes + the payment system of nanopool cost me far more than this.
Not to mention, that on top of that xmr stak has 1 (or even 0% fee) and a slightly lower rejected shares rate, than the one I am having with the cast.

The neat feature for showing temps I like a lot, but that cannot compensate all the drawbacks. So I moved back.

I must mention, that it was working good on a single Vega 64 at 1407/870 1100/850 , expect the random hashrate drops that I mentioned earlier with a screenshot (same as on the 6 card rig). So it had 50 H/s more before calculating fee and higher % stale/rejects.

Still - with some work on the code, the program might be worth trying again. I will defnitely follow it and give it a try with next versions, but several things just need to be improved. Starting with:

1) Adjustable intensity settings.
2) Fix or at least explanation for these random hashrate drops. Is this being cause by collection of the dev fee? This is my suspicion, and if this is the case ... Well, it looks like the fee is not 1.5% but way higher.
The program gives no indication when this dev fee is being collected anyway ...

3) Lower dev fee I don't mind paying 1% tbh, at least for some time, but 1.5% is just too high, when there is a cheaper (and probably better) client on the market.
4) Maybe a way of restarting the program, or even the rig if nothing is happening for some time.

i guess that might be the case yes.

So in order to increase my hashrate i should change OS ?

I think I heard somewhere that the blockchain driver doesn't play well with claymore miner in Win 7 even though it has no issues in Win 10, maybe you set claymore at startup which makes it crashes right away?

IT IS broken under Win 7, there's an alternative though, you can refer to this link https://community.amd.com/thread/219303

thanks

this thing crashed instantly as i get into win7, i cant even get a picture with this driver, any suggestion why is that?