Search content
Sort by
Showing 17 of 17 results by sirkorro
Re: PhoenixMiner 4.6c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
I have 8 x GTX 1050 Ti 4GB on Windows 10.
I get the the DAG creation error.
Any idea how to resolve this, the DAG is only 3.3GB I believe
My Virtual Memory is more than enough to cover all of my cards in the rig.
Play with below switches:I get the the DAG creation error.
Any idea how to resolve this, the DAG is only 3.3GB I believe
My Virtual Memory is more than enough to cover all of my cards in the rig.
-eres Allocate DAG buffers big enough for n epochs ahead (default: 2) to
avoid allocating new buffers on each DAG epoch switch, which should improve DAG switch stability
-lidag Slow down DAG generation to avoid crashes when swiching DAG epochs
(0-3, default: 0 - fastest, 3 - slowest).
Re: PhoenixMiner 4.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
there are other coins that you can mine with your 1080ti that are nearly 100% more profitable than ETH
Name one.Re: PhoenixMiner 4.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
LOL? For 9 Cards you need 1.3 GB ram? And you think 4 new cards use more than 2,7gb ram? 
4GB Ram is enough for up to 16 Cards
With 9 cards I have ~500M remaining. Remember OS.4GB Ram is enough for up to 16 Cards
Re: PhoenixMiner 4.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
Hi.
I'm using Phoenix on top of HiveOS.
Currently I'm running 9 P106 cards.
Phoenix memory usage in this setup is ~1.3GB.
Is there a way to reduce Phoenix memory usage?
I'm about to extend my rig by 4 cards and most probably my 4GB of ram will be exhausted.
I'm using Phoenix on top of HiveOS.
Currently I'm running 9 P106 cards.
Phoenix memory usage in this setup is ~1.3GB.
Is there a way to reduce Phoenix memory usage?
I'm about to extend my rig by 4 cards and most probably my 4GB of ram will be exhausted.
Re: PhoenixMiner 4.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
using hiveos running with the latest hive OS
anyone has encountered these error
phoenixminer exited, waiting to cooldown a bit
Had the same issue. It's related to wrong miner config.anyone has encountered these error
phoenixminer exited, waiting to cooldown a bit
Here is mine:
https://i.postimg.cc/HLssN5Fy/Greenshot-2019-05-23-09-28-58.png
Re: PhoenixMiner 3.5d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
"PhoenixMiner.exe is not reconized as an internal or external command, operable program or batch file"
Bat file needs to sit next to phoenix exe file, meaning same folder.Re: PhoenixMiner 3.5d: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)
so I used this comand:
-gpus <012345678>
Hi. -gpus <012345678>
According to OP, first card has numer 1, not 0.
Edit. and don't use brackets.
Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Good news! 
Almost every message after releasing new version is about problems (which is quite normal and alright), so it's quite nice to get a few positive reports. Don't hesitate to write us with any ideas for improvements, etc.
Did you see: https://bitcointalk.org/index.php?topic=2647654.msg43145022#msg43145022 Almost every message after releasing new version is about problems (which is quite normal and alright), so it's quite nice to get a few positive reports. Don't hesitate to write us with any ideas for improvements, etc.Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Quote
On vacation? He already accumulated lots eth from dev fee. Maybe cashed out some just to be away from this crypto slum.
Enjoying his lambo.Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Hi.
Thanks for great piece of software.
While I appreciate Claymore-like API, maybe it would be good to create something better.
I would like to have something similar to Excavator devices endpoint. https://github.com/nicehash/excavator/tree/master/api#devices-get
You can also add hash rates to each GPU and maybe hash per watt since all the data is there.
OC settings for Nvidia would be appreciated too.
Regards.
Thanks for great piece of software.
While I appreciate Claymore-like API, maybe it would be good to create something better.
I would like to have something similar to Excavator devices endpoint. https://github.com/nicehash/excavator/tree/master/api#devices-get
You can also add hash rates to each GPU and maybe hash per watt since all the data is there.
OC settings for Nvidia would be appreciated too.
Regards.
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Reduce core to -150 (minus 150) or even - 200
Increase mem gradually in 20 increments... I have it at +820. Hashing at 33.2 MH/s
Thanks. You are actually suggesting to OC memory even more.Increase mem gradually in 20 increments... I have it at +820. Hashing at 33.2 MH/s
Does it mean that core clock OC is causing those errors?
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Hi.
I'm getting below error from time to time.
As you can see, miner was running fine for more than 2 days (on 3.0a).
My setup: 7 x 1070, power limit 62, core +140, memory +650.
Can you please advise?
I'm getting below error from time to time.
As you can see, miner was running fine for more than 2 days (on 3.0a).
My setup: 7 x 1070, power limit 62, core +140, memory +650.
Can you please advise?
Code:
2018.06.03:02:58:27.401: eths Eth: New job #3732dc6c from eu1.ethermine.org:4444; diff: 4000MH
2018.06.03:02:58:27.585: main Eth speed: 223.248 MH/s, shares: 12366/0/0, time: 62:40
2018.06.03:02:58:27.585: main GPUs: 1: 31.880 MH/s (1722) 2: 31.892 MH/s (1845) 3: 31.899 MH/s (1776) 4: 31.885 MH/s (1756) 5: 31.894 MH/s (1742) 6: 31.911 MH/s (1756) 7: 31.887 MH/s (1769)
2018.06.03:02:58:31.106: GPU2 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.112: GPU2 GPU2 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU1 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU1 GPU1 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU3 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU3 GPU3 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU4 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU4 GPU4 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU5 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU5 GPU5 search error: an illegal memory access was encountered
2018.06.03:02:58:31.148: GPU6 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.148: GPU6 GPU6 search error: an illegal memory access was encountered
2018.06.03:02:58:31.148: GPU7 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.148: GPU7 GPU7 search error: an illegal memory access was encountered
2018.06.03:02:58:32.055: wdog Thread(s) not responding. Restarting.
2018.06.03:02:58:27.585: main Eth speed: 223.248 MH/s, shares: 12366/0/0, time: 62:40
2018.06.03:02:58:27.585: main GPUs: 1: 31.880 MH/s (1722) 2: 31.892 MH/s (1845) 3: 31.899 MH/s (1776) 4: 31.885 MH/s (1756) 5: 31.894 MH/s (1742) 6: 31.911 MH/s (1756) 7: 31.887 MH/s (1769)
2018.06.03:02:58:31.106: GPU2 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.112: GPU2 GPU2 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU1 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU1 GPU1 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU3 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU3 GPU3 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU4 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU4 GPU4 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU5 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU5 GPU5 search error: an illegal memory access was encountered
2018.06.03:02:58:31.148: GPU6 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.148: GPU6 GPU6 search error: an illegal memory access was encountered
2018.06.03:02:58:31.148: GPU7 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.148: GPU7 GPU7 search error: an illegal memory access was encountered
2018.06.03:02:58:32.055: wdog Thread(s) not responding. Restarting.
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Or do you waste 5-10mins of sub optimal hashrates at the beginning of every time you start the miner?
How often do you restart your miner?Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Power limit is 65%
Core clock is 0
Memory clock depend on GPU but 750-750-715-750-700-800 for Rig 1 and 800-750-730-750-750-750 for Rig 2
Thanks. Very nice fine-tuned setup.Core clock is 0
Memory clock depend on GPU but 750-750-715-750-700-800 for Rig 1 and 800-750-730-750-750-750 for Rig 2
How long can Phoenix run without crash at you end?
My max was 5 days (7x1070), still trying to find my OC sweet spot.
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
I increased the memory clock of all 12 GPU's (GTX 1070) with +/- 3-5%.
Hi. What's your power limit, core and memory clocks?
Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
I can see big HR improvements on some of my 1070. From 31 to 35 which is great.
Actually, after restart, values are back to 31.Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)
Hello.
I can see big HR improvements on some of my 1070. From 31 to 35 which is great.
Prior to 3.0, value after "Eth speed:" in console was submitted to pools as reported hashrate.
Now as "Eth speed:" I have 241, but on ethermine reported HR is 223 (same as "Average speed(5 min)" on console).
Is that intentional?
Thanks.
I can see big HR improvements on some of my 1070. From 31 to 35 which is great.
Prior to 3.0, value after "Eth speed:" in console was submitted to pools as reported hashrate.
Now as "Eth speed:" I have 241, but on ethermine reported HR is 223 (same as "Average speed(5 min)" on console).
Is that intentional?
Thanks.