 Show Posts
|
|
Pages: [1] 2 3 »
|
Only 584 GPUs stop mining and only on Phoenix. 574 still works. Another miners also still works. It's Phoenix problem.
I confirm that. Problem is with 480 and 580 4Gb cards only. As well as they run with smaller DAG coins on 5.1c Any 470 and 570 4Gb I have, keep working with no problems. |
|
|
|
|
A brief explanation for repeating question" Why my CPU runs slow"
1. The most important value in the miner is -t n (number of threads) which is your CPU L3 cache size divided by 2.
I.e. for 8Mb the optimal is -t 4, for 4Mb it is -t 2, but for L3 3Mb cache -t 2 is also performs well (so you can round up your L3/2 formula result)
2. Of course the perfomance of miner depends on your CPU clock (if it could be overclocked)
3. Owners of the notebooks CPU's (especially ULV) - do not be shocked by low results, your CPU's are "eneregy saving" and are missing performance as they are not designed to work at full run all time. Do not expect desktop's CPU perfomance from your notebook!
4. Windows10 itself also makes a difference with total hashrate (I mean a huge number of services running in backgroud), as well as a lot of shit preinstalled bloatware processes running at newbie's computers.
5. If your computer not mines only (after clean start), but you use it for work at same time, then be ready for up to 20-30% hashrate drop
ADVICE - Run Remote Manger (which is supported by this miner now and included in the package) and look how your CPU (and threads) performs in real time.
|
|
|
|
Try to use -t 4 param. I have i7-4720HQ and 16Gb RAM, which mines at about 150-200 and goes down to 110-120 when I use my computer for work (business needs, not heavy load like 3d rendering or so). So your speed is abnormal.
35-50H/s is ok for old i5-3xxx but not for your CPU
Thanks for the advise. I am running it on 4 threads already and its not helping any. Tried to add -t 4 and the speed is still down. 1. Are you getting "FAST MODE ENABLED!" during miner start? 2. Does your CPU start mining with initialy low spped (see number 1)? 3. Does your CPU start mining woth normal speed and then drop down? In this case it could be kind of CPU power or thermal limitation (according to CPU model you try to mine at notebook). Check you windows power-performance settings etc. |
|
|
|
I have set everything up and followed the instructions pretty closely.
Miner starts with Admin rights, here is the string:
C:\Users\retro\Documents\CryptoEasyMiner\CryptoNoteMiner.exe -o stratum+tcp://us-etn-pool.hashparty.io:7777 -u etnkMV3TAK5M3Q8g6Zk2DbgXpaxyCsqRT3PkXH9NLiQXRdz3nqGedwpNkY12nChjVsJWWgFHk8bpW1o MwumUVy7L3tyUMbgZ6x -p x
Intel i7-7700HQ 16GB RAM getting 38 H/s using 25% of the processing power.
When I mine with my GFX Card I am getting 450 H/s.
Can you give me any advise on how I can fix this?
Try to use -t 4 param. I have i7-4720HQ and 16Gb RAM, which mines at about 150-200 and goes down to 110-120 when I use my computer for work (business needs, not heavy load like 3d rendering or so). So your speed is abnormal. 35-50H/s is ok for old i5-3xxx but not for your CPU |
|
|
|
I don't understand which wallet address to use. My command line is
NsCpuCNMiner64.exe -o stratum+tcp://mine.moneropool.com:3333 -u 449TGay4WWJPwsXrWZfkMoPtDbJp8xoSzFuyjRt3iaM4bRHdzw4qoDu26FdcGx67BMDS1r2bnp7f5hF 6xdPWWrD3Q3Wf7G6 -p x -t 3
And it works fine. But I think that I am mining for the developer. If I change the "449TGay..." key for my address on "my ether wallet" the program returns an error of "invalidaddressusedforlogin".
It returns the same error on other pools using my address, but works fine with the 449TGay... address.
Are you sure that "my ether wallet" is equal to "your MONERO" wallet? Do you know that Etherium and Monero are different and use different wallets? Or you think you can mine any crypto using one wallet? |
|
|
|
Just wanted to stop by, and say thank you for this, I'm sure this has helped a lot of people. Just had a quick question about speed. Samsung Ultrabook, Windows 10, and supposedly in fast mode, and I'm getting around 20 h/s. From what I'm reading, this is nowhere near speeds others are getting. Is there anything you can suggest to get a bit more umph out of this thing?? Besides power cycling regularly, and trying to shut down programs in the background, I'm out of ideas. Thanks in advance for any and all help
What exact CPU installed in your notebook? Such speed is possible with ULV processors Intel i5, 3rd Gen, states 1.7ghz, with "Turbo Boost" to 2.6ghz. I am asking about exact model, but not GHz. Like i7-7700K etc. |
|
|
|
Just wanted to stop by, and say thank you for this, I'm sure this has helped a lot of people. Just had a quick question about speed. Samsung Ultrabook, Windows 10, and supposedly in fast mode, and I'm getting around 20 h/s. From what I'm reading, this is nowhere near speeds others are getting. Is there anything you can suggest to get a bit more umph out of this thing?? Besides power cycling regularly, and trying to shut down programs in the background, I'm out of ideas. Thanks in advance for any and all help
What exact CPU installed in your notebook? Such speed is possible with ULV processors |
|
|
|
v3.9
- fixed issue with devfee failover.
- fixed critical issues in remote management feature (attacker could crash miner even in read-only mode).
- added "-mpsw" parameter.
@Claymore I still have strange messages with your miner, could you please explain what happens? No new jobs were received for 15 mins - something wrong with this pool, disconnect.Speed: 318 h/s, TotalHashes: 45907K, DevHashes: 1146K Mining time: 45:04
12/10/17-19:34:34 - SHARE FOUND (target 50000) - (THR 2 of 4)
Share accepted (63 ms)!
!!!!!!!!!!
No new jobs were received for 15 mins - something wrong with this pool, disconnect.
!!!!!!!!!!
DevFee: Stratum - connecting to 'xmr-eu.dwarfpool.com' <178.32.145.31> port 8050 (unsecure)
Stratum - Connected (unsecure)
DevFee: Pool Diff 50000.2
12/10/17-19:34:57 - New job received from xmr-eu.dwarfpool.com:8050
Speed: 321 h/s, TotalHashes: 45933K, DevHashes: 1147K Mining time: 45:05 |
|
|
|
We as Cizgi Elektronik are the distributor of Asus in Turkey for the last 26 years. Here is the table for Asus Mining RX470-4G OC settings, performance for single Mining and Daul Mining. The mod file (.ROM) also listed here.  Your settings say "100%" power limit. Claymore's -powlim settings are -50 to 50. So what do you mean by that? |
|
|
|
|
Finally happy with latest 17.10.3 drivers (rigs are quite stable) with one exception - I use Claymore's settings for voltages and frequencies (not AfterBurner or something similar) and have to run it twice. This is because of low hashrate after first start for some cards - cards start with 23-25MH, but after stopping the miner and running it again they sdstart at normal rate. It is a clue for me.
|
|
|
|
|
I did a try to install new AMD drivers. The clue is that I am unable to change "GPU workload" setting for one card in a rig. It remains at "Graphics" when I trying change it to "Compute". All other cards (similar ones) switched with no problems.
|
|
|
|
Something strange happens with my miner's monitor
I use Claymore monitor 3.4, miner version 10.0
1 or 2 rigs are constantly loosing connection with monitor. I.e. Monitor turns red and in "lost" state for corresponding miner.
While miner actually works (with pool) but with message:
ETH: GPU0 28.009 Mh/s, GPU1 28.529 Mh/s, GPU2 28.366 Mh/s, GPU3 27.995 Mh/s, GPU4 28.001 Mh/s
server: bind failed with error: 10048 (port for remote management is busy, use different -mport value), next attempt in 20sec...
I tried different -mport values but it doesn't help. It happens since Saturnday. I use read-only mode and internal IP
LOL. I had similar behavior, no any error msg in logs though: single worker (out of multiple ones in the same LAN) was constantly loosing connection. And it seems I just fixed it in a really weird way: get EthMon 2.9, place your config into its dir(to speed things up), remove all related entries from win firewall, run it and allow both public & private profiles = that's it. Have NO idea why it works now... or why it wasn't working before. If I do the same procedure with 3.4 it wont solve the problem... I'm really confused. EDIT: @Kukus Please try and report back. Reporting: I didn't check anything in firewall. Just run ver2.9 and it works. But now, when I've tried 3.4, this mystic software works again. But I have to wait because miner looses connection after 6-10 hours only. |
|
|
|
|
Something strange happens with my miner's monitor
I use Claymore monitor 3.4, miner version 10.0
1 or 2 rigs are constantly loosing connection with monitor. I.e. Monitor turns red and in "lost" state for corresponding miner.
While miner actually works (with pool) but with message:
ETH: GPU0 28.009 Mh/s, GPU1 28.529 Mh/s, GPU2 28.366 Mh/s, GPU3 27.995 Mh/s, GPU4 28.001 Mh/s
server: bind failed with error: 10048 (port for remote management is busy, use different -mport value), next attempt in 20sec...
I tried different -mport values but it doesn't help. It happens since Saturnday. I use read-only mode and internal IP
|
|
|
|
1) After initial rig start (i.e. after powering or resetting the whole rig) Claymore 10.0 runs with lower hashrates (for example about 23-25Mhs with 470/570 cards). After stoping the miner and re-run .bat, I getting normal rates (i.e. miner has to be restarted and operates as expected only after 2nd run, never from the first)
2) Unpredictable hashrate drop during mining for some cards in rig (usually 1 or 2 of them). Rate drops and keeps at 23-25. The only solution I found is to restart Claymore.
I am having a # 1 issue....but on #2 add if using the .bat file --tt 70 --fanmin 50 the reason is that the cards are throttling down due to temp see if that helps I have -tt 70 set (with no fanmin parameter). But I do not see any throttling via HWinfo - it shows same freqs for GPU and memory when hashrate goes down. |
|
|
|
I have 2 issues with Claymore 10.0 (Win10, blockchain drivers, 6card rigs running 570 and 470 cards)
1) After initial rig start (i.e. after powering or resetting the whole rig) Claymore 10.0 runs with lower hashrates (for example about 23-25Mhs with 470/570 cards). After stoping the miner and re-run .bat, I getting normal rates (i.e. miner has to be restarted and operates as expected only after 2nd run, never from the first)
2) Unpredictable hashrate drop during mining for some cards in rig (usually 1 or 2 of them). Rate drops and keeps at 23-25. The only solution I found is to restart Claymore.
Any comments guys?
Same issue here...as mentioned 470's and 570's Has anyone found a fix for this ? I have as instructed tried the timeout and it does not work Thanks in advance Are you talking about problem numbered 1 or numbered 2? As to No.1 I was discussing with few people and they have similar problems, not solved. I am not worry too much as it happens only at first start. But No.2 really makes me headache, because unpredictable. |
|
|
|
did you do anything to fix it or it just worked ?
Nothing, it just cured itself |
|
|
|
no idea to be honest i have 7 more miners with the same settings working without any problems
I had a problem with 2. Works fine now but expereienced this trouble for about 2-3 hours. |
|
|
|
Having a really strange problem , 4 of the miners suddenly stopped working and getting this error always no matter what server or setting ETH: Stratum - Cannot connect to eu1-etc.ethermine.org:14444 Tried all the servers , any idea ? Similar problem today. Could it be because of upcoming fork? |
|
|
|
For point 1, i could be that the batch is starting before the software you use to apply the OC or something like that. You could try adding a few seconds delay in the start of the bat, ex: "timeout 20"
In case described above I do not use OC-ing software, but only options provided by Claymore, i.e. -mvddc -cclock -powlim etc. It works well but from the second run only. It looks a bit strange becuase all settings are apply to cards at first run (according to monitoring software like HWinfo or GPU-Z), but hashrates are lower. |
|
|
|
|
I have 2 issues with Claymore 10.0 (Win10, blockchain drivers, 6card rigs running 570 and 470 cards)
1) After initial rig start (i.e. after powering or resetting the whole rig) Claymore 10.0 runs with lower hashrates (for example about 23-25Mhs with 470/570 cards). After stoping the miner and re-run .bat, I getting normal rates (i.e. miner has to be restarted and operates as expected only after 2nd run, never from the first)
2) Unpredictable hashrate drop during mining for some cards in rig (usually 1 or 2 of them). Rate drops and keeps at 23-25. The only solution I found is to restart Claymore.
Any comments guys?
|
|
|
|
|
