 Show Posts
|
|
Pages: [1] 2 3 4 5 6 7 »
|
@OP, you should give some updates if this issue had been resolve or still pending as of this moment.
He's not online since April 4, and I'm pretty sure he will post here again if the issue is not yet resolved. But I'm not surprised if he just gives up and then decides to no longer continue his complain here because that doesn't really helped his case. Maybe contacting or posting on Changelly thread is better to get the attention he needs. However, looking at his transaction ID, it seems that the TX itself is not valid due to insufficient funds. So maybe, Changelly doesn't hold enough funds in their hot wallet to send the USDT to OP after he exchanged it? I got my Tether after the 2nd time contacting support. So a bit over 48 hours after reporting problem. Yes, it seems the error was originally caused due to insufficient funds on USDT from their end. Just wanted a quick exchange, would probably not use changelly for bigger exchanges in future. |
|
|
|
|
I contacted Changelly support about a failed transaction from them, they replied within minutes saying they forwarded the transaction number to the technical department.
Anyone have experience with getting their coins from Changelly after a failed transaction? How long did it take to resolve?
|
|
|
|
|
I have my RX560's rock stable on Win 10 LTSB mining either XMR/GRFT, but disappointed they can only do L2+3 stable, bumping up to L3+3 loses hashrate or crashes.
Nearly every RX550 post I see them reported to easily handle L3+3 and some 3+4 plus go very low on the core/voltage for super efficiency.
Do most RX550 Lexa's actually come with stronger memory than RX560 Baffin's ?
|
|
|
|
|
I had stability issues with 0.41 and got it fixed, it looks like my version of win 10 wasn't properly starting the default set variables, changing them to setx and removing the = from each line worked for me.
|
|
|
|
|
For low power rigs I'd recommend pools with low min payout. MiningPoolHub (0.05 min payout) and HashVault (0.11 min payout) are my favorites.
|
|
|
|
I tested higher "thread_delay" settings than the default 319. I found 440 is the highest I could go and still keep the max hashrate. There seems to be less hashrate fluctuation at 440, so I guess it's not just placebo and actually does make the rig a tiny bit more stable  |
|
|
|
|
Oh sorry that sucks, too late for that mobo I guess the only other fix I could think of was to try PCIE expander boards.
|
|
|
|
|
Oh yeah after DDU, disconnect your internet before installing your Adrenalin drivers and reboot, then you can reconnect your internet, that prevents windows from installing generic driver
And last resort you try can the HackFlags 600 registry mod.
|
|
|
|
|
I faced this many times with setting up rigs. You could try installing one card at a time and check bios/windows each time, the moment you have a fail you should reset cmos and start from scratch.
The order in which you install the cards can matter greatly. Going in order from PCIE slot 1,2,3,4,5,6 often doesn't work. Try installing in different orders like for example 1,3,5,2,4,6
|
|
|
|
|
TRM is the best v8 miner for my rig, highest hashrates and lowest power draw.
It seems to be more aggressive on memory compared to SRB and JCE, on some cards I had to underclock memory and increase memory voltage to avoid errors.
|
|
|
|
@doktor83 , hello and ty for your miner . just asking ... i have beta blockchain driver ... should i install one of reccomended drivers ? Thanks .
It should be OK, i have a few rigs i am testing on the BC drivers, and they work OK, newer drivers are the ones that can make s**t. Depressing that AMD can't write good drivers after 18.6.1 Seriously, we might end up needing a modded 18.6.1 to properly use our Navi's and VII's  |
|
|
|
|
"persistent_memory" : true is good for the Heavy algo, I was able to go a bit higher with intensities on my 2gb rx560's.
I also notice Heavy can be tweaked with smaller intensity increments than v8. It can respond to 0.04 increments (like 12.60>12.64>12.68 and so on) to find best hashrates.
|
|
|
|
1.7.0 is working great for me on my 4x RX 560 (XfX 2GB) rig mining CNv8. I'm getting 460-490H/s per card with intensity set to 25.0 and using MSI AB 4.5.0 to set core at 1200, mem at 1900 and 100% PL (running an Anorak powersave BIOS). I really like the restart miner if hashrate drops below a certain value function as it seems that one or both of the middle two cards on this rig will drop in hashrate by about 150H/s every so often.
All in all, I'm happy to pay the dev fee vs. running xmr-stak compiled to have no devfee, as the latter barely did better than 400H/s per card and it had stability problems when it did run. Unfortunately, I am running at a razor thin margin of profitability vs. power cost right now, and it is only because the weather turned cooler recently that I am keeping this rig running at all (everything else was turned off and/or sold earlier this year).
Sounds like a power issue. My rig can exhibit problems like that if I re-apply ODT settings and/or restart the miner several times. It seems like some "power degradation" thingy happens when the cards/system are cycled too many times. The only remedy is to completely power off the rig including the psu for at least 5 minutes then power back on. |
|
|
|
|
SRB tends to auto set the intensity too high for some cards, try to lower it for stability.
|
|
|
|
|
Hey, anybody ever try fine tuning the -ethi parameter using worksize setting instead of flat intensity?
I did and now I can get around 10% more shares per hour, it's a lot of trial and error but IMO it's worth the effort.
It's best to run tests with low difficulty coin like ether-1 and record the shares per hour.
I use 512 increments and found the optimal setting is usually 1 increment under the exact point where errors first happen. For instance with my 2gb rx560 cards they first give error at -ethi -7680 (15 x 512) and when I drop them to -ethi -7168 (14 x 512) they get the best performance.
|
|
|
|
i have watchdog error (opencl call) with claymore
while ETH miner works fine
why?
i love claymore because os less power usage but watchdog error kill me
As far as I can guess, you're either trying to overclock too much or trying to undervolt too much. Adjust your overclocking/undervolting numbers till your GPUs are in the position of handling the work with stability. Are you using Claymore's integrated options or trying to use some driver for that? I kept having this error too on one gpu, was driving me crazy. Finally solved it by replacing the pcie riser which was faulty. Ethash mining is much more sensitive than Cryptonight to bad risers. is there a way to test riser? how we can sure the problem is from riser? why ETH miner has no probem with same OC/undervolting but claymore gives watchdog error? Claymore will break easier and reveal problems that don't come up on ETHminer, when I had a bad riser it did not crash on ETHminer but always gave the watchdog hanging error on Claymore and Phoenix. Try to find out which gpu is hanging and either give it a new riser or move the suspect riser to another gpu and see if it gives problems. so you as same as me believe that i got a weak riser right? claymore react against it but ethminer not? right? Exactly, run Claymore and look when you get the watchdog/opencl hang, it will show the GPU that causes it, and most likely that's where your bad riser is. |
|
|
|
i have watchdog error (opencl call) with claymore
while ETH miner works fine
why?
i love claymore because os less power usage but watchdog error kill me
As far as I can guess, you're either trying to overclock too much or trying to undervolt too much. Adjust your overclocking/undervolting numbers till your GPUs are in the position of handling the work with stability. Are you using Claymore's integrated options or trying to use some driver for that? I kept having this error too on one gpu, was driving me crazy. Finally solved it by replacing the pcie riser which was faulty. Ethash mining is much more sensitive than Cryptonight to bad risers. is there a way to test riser? how we can sure the problem is from riser? why ETH miner has no probem with same OC/undervolting but claymore gives watchdog error? Claymore will break easier and reveal problems that don't come up on ETHminer, when I had a bad riser it did not crash on ETHminer but always gave the watchdog hanging error on Claymore and Phoenix. Try to find out which gpu is hanging and either give it a new riser or move the suspect riser to another gpu and see if it gives problems. |
|
|
|
i have watchdog error (opencl call) with claymore
while ETH miner works fine
why?
i love claymore because os less power usage but watchdog error kill me
As far as I can guess, you're either trying to overclock too much or trying to undervolt too much. Adjust your overclocking/undervolting numbers till your GPUs are in the position of handling the work with stability. Are you using Claymore's integrated options or trying to use some driver for that? I kept having this error too on one gpu, was driving me crazy. Finally solved it by replacing the pcie riser which was faulty. Ethash mining is much more sensitive than Cryptonight to bad risers. |
|
|
|
|
Best bralock setting is 6 for my rx560 2gb cards, only 2-4 H/s gain though. I noticed while testing bralock, it prefers even numbers.
Funny thing is, on Claymore's ETH miner, the best setting was also 6 for dcri tuning, makes me wonder if bralock is the Cryptonight equivalent or something.
|
|
|
|
|
