 Show Posts
|
|
Pages: [1] 2 »
|
Yes you can Can I mine eth and verge coin in the same time?
|
|
|
|
Any one, need help
Amd openCl platform not found
No Nvidia cuda gpus detected
No amd open cl ar nvidia cuda gpus found, exit
Just over night happen
Any problems related to a driver, the gpus are not being detected. it's just windows updated ( cumulative one ). DDU etc... If you updated to 1803 you need to roll back. This has been discussed earlier in the forum. you do not need to roll back any more, just after the update use DDU and then install latest AMD drivers, it works fine now |
|
|
|
v11.2:
- some improvements in AMD GPU kernels, it can increase hashrate a bit in some cases.
- reduced some delays, it will cause a bit less stale shares.
why on both links only see v. 11.1, can't find 11.2 ? |
|
|
|
xvgminingclub.info is protected with anti ddos from now  is this the reason for the 5% missing XVG per block ? 24 ours ago 1 block 1560XVG now 1 block 1478 XVG ? Fixed already. There was some glitch hidden fee from every block great, now you'll have all my rigs |
|
|
|
xvgminingclub.info is protected with anti ddos from now is this the reason for the 5% missing XVG per block ? 24 ours ago 1 block 1560XVG now 1 block 1478 XVG ? |
|
|
|
Guys, if you have problems with XVG pools, try ours :
-dcoin blake2s -dpool stratum+tcp://mining.oxo.rs:4444 -dwal <WALLET_ADDRESS> -dpsw c=XVG
time ti try this mining.oxo.rs:4444 XVG pool, other full or down or steal ... |
|
|
|
There's no good pool for XVG? Unimining gives about 40% of what it should give...EVEN IF Whattomine is not full accurate, the diference is too Huge...With 4600MH/s im getting only 12, 13 coins/day.
Antminepool doesnt work here on the last 5 or 6 days...instant disconnect on both ports.
You can use NLpool.nl now ... working and fast. The address for XVG VERGE - Blake2s is: stratum+tcp://mine.nlpool.nl:5766 -u <WALLET_ADDRESS> -p c=XVG The address for Shield Blake2S is: stratum+tcp://mine.nlpool.nl:5766 -u <WALLET_ADDRESS> -p c=XSH If you have any questions or other coins you want added to the pool please e-mail us. The e-mail address is displayed on our website nlpool.nl Example .bat : EthDcrMiner64.exe -epool us2.ethermine.org:14444 -ewal <YOURETHADDRESS> -epsw x -gser 1 -lidag 1 -r 1 -dcri 40 -cclock 1150 -mclock 2125 -dpool stratum+tcp://mine.nlpool.nl:5766 -dwal <YourVergeAddress> -dcoin blake2s -dpsw c=XVG I've just switched 15 rigs to your pool, lets hope for great income :-) |
|
|
|
it's a new pool, needs time and hash power, very soon will start to find blocks |
|
|
|
has anyone experienced gpu # 0 with zero hash rate? after a few seconds the miner will restart and will be stuck at open cl initializing. I have 7 rigs and only 2 rigs are experiencing this problem. I tried going back to v 10.5 but the problem persists! I did not have this problem prior to closing V 10.5 then running V11.0 with the same bat file. pls help.
after downgrade to 10.5 try to reboot, it helps in my case |
|
|
|
ok guys it seems 3gb cards have officially stopped working on eth network. Dag erro etc etc, the 6gb cards in the same rigs are doing fine. surprising though is that under stats its says 2.4gb used for dag.
one by one all the 3gb rigs gave up.
or am i missing something?
increase your swap size with 10 ot 20 GB |
|
|
|
Hey folks,
Wondering if any one has experienced this problem:
Adding 9th GPU only on Windows 10 v1709 I get "Cuda error 11-Cannot build dag file"
Setup: all other cards are polaris RX 580, 480 etc with blockhain drivers. Rig runs perfectly fine with 8 cards.
tried using dstm 0.5.8 and all 9 cards hash perfectly fine (>300 sols/ s).
Ive tried the following steps to troubleshoot with no success:
1) Set virtual memory to 20,000mb in Windows up form 16,000mb
2) -lidag 3 to lower dag intensity.
3) launched multiple instances of the miner (tried launching ethminer and claymore) no help
4) 9th card is running at stock settings no overclock whatsoever (cant adjust in AB since it only shows max 8 cards).
5) Tried Claymore 10.1 and 10.6 both give same Cuda error code 11
Can anyone help or know any steps I can try to get this card to hash in claymore.
Thanks.
for 9 cards you need more virtual memory, DAG i 2.3G now ( 9x 2.3 = 20.7g ), set virtual memory initial 24G, max 44G |
|
|
|
Whats about memory ? You only got 4 GB of RAM ?
Little less ?
4 gb ram and 33 GB swap tryed 8 gb ram, this just used little less swap, no difference on the problem |
|
|
|
Hi Claymore,
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
Please send me some logs so I can check the reason. ... Ok I see big delays now. What CPU do you have? What average CPU load in Task Manager? No more PM, so I write here, after sending logs, CPU model: Celeron G3930 CPU LOAD: 53%-56% normaly taken by EthDcrMiner64.exe, everything else is up to 5% MB: ASRock H110 Pro BTC+ RAM: 4gb ddr4 no change with new version ( with high priority ), I tryed and with other CPU act the same way when 12 cards What CPU did you try? Try to specify "-tt 0" option to disable temperature control, does it help? CPU Pentium G4400 -tt 0 did not change anything |
|
|
|
Hi Claymore,
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
Please send me some logs so I can check the reason. ... Ok I see big delays now. What CPU do you have? What average CPU load in Task Manager? No more PM, so I write here, after sending logs, CPU model: Celeron G3930 CPU LOAD: 53%-56% normaly taken by EthDcrMiner64.exe, everything else is up to 5% MB: ASRock H110 Pro BTC+ RAM: 4gb ddr4 no change with new version ( with high priority ), I tryed and with other CPU act the same way when 12 cards if possible send me e-mail to write you there |
|
|
|
Hi Claymore,
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
Please send me some logs so I can check the reason. ... Ok I see big delays now. What CPU do you have? What average CPU load in Task Manager? No more PM, so I write here, after sending logs, CPU model: Celeron G3930 CPU LOAD: 53%-56% normaly taken by EthDcrMiner64.exe, everything else is up to 5% MB: ASRock H110 Pro BTC+ RAM: 4gb ddr4 |
|
|
|
Hi Claymore,
I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.
Is this a know issue? Are there any workarounds?
Thanks!
Please send me some logs so I can check the reason. I have the same problem with eth manager too, all rigs up to 6 cards work perfect, all ( 6 rigs ) with 12 cards timeout constantly and reconnect after 10sec to 10 min for couple of secconds before it timeouts again |
|
|
|
i am trying 9.5 claymore
6x 1060 3gb mining constantly 23.3 mh
6x 1060 3gb mining gpu0 20mh others 23.3 why the gpu0 lose hashrate?
23.3 Mh with moded BIOS, OC or stock ? if possible send OC settings |
|
|
|
Anyone else having trouble with this version? hast rate is up and down like a yoyo unfortunately.
I have the same problem, with windows, drivers 17.3.3 with 8.1 it was stable ( both rigs 8xRX480 in total ) with 9.0 ETH hashrate goes up and down, dcr is stable, nomatter the -dcri |
|
|
|
|
All crashes on 3 rigs with RX480/470 fixed:
1. use amdcleanuputility.exe
2. install Radeon-Software-Crimson-ReLive-16.12.2-Dec19
works great with -i 8
|
|
|
|
|
the good side of burst is that you can use every hdd/ssd you have, even with realocated or bad blocks or ready to fail ( smart problem ) disks
as long as you can read from it, it generate Burst with no penalty
the other 2 you need to run over raid1 ( mirror ) if you don't want to lose money
with 18Tb on Burst for 1 mounth I have 17000 bursts
you can do the math with currect price
|
|
|
|
|
