Author

Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 351. (Read 784857 times)

newbie
Activity: 48
Merit: 0
Hello,
I can't get my Vega (56&64 reference card) stable. My rig is always crashing.
Could you share your card clock and memory and the best parameters of the minerfor these cards.
Thanks
Vega64 - Strix
OverdriveNtool
Core - P7 852/825mv
Memory - P3 1083/825mv

Thanks ! 852 core frequency ? What is your hashrate with these settings ?

ETH is memory bound, core clock effect is minimal on Vegas.  Instead of setting P7, simply disable all GPU power states above P0 in OverdriveNTool.  Also, your memory clock can go up to 1107  for a 64 and you should be able to use a voltage setting between 806-831mv.  Above 1107, your voltage requirement jumps significantly to around 900mv (due to SOC clock scaling to 1200MHz.)

For a 56, your voltages and core clock would be the same, but your memory clock will have a fuzzier limit than the 64 - somewhere between 900-950MHz most likely.
Hi, i remember u in ryo chat Grin
newbie
Activity: 10
Merit: 0
My 8 sapphire nitro rx570/580 GPU (8GB) rigs (win 10) now have problem mining eth using PM 4.1c today! The GPU driver was 18.5.1 and it was fine in Nov-Jan and I switch to mine CLO recently. It is always one of the 8 GPUs "not responding" during PM starts up and then restart. I tried 19.1.1 driver after clean up drivers with DDU and it did not help. Now it is always no issue mining CLO but crashes at start-up mining ETH. Any thoughts or help solving this would be greatly appreciated.
member
Activity: 340
Merit: 29
Hello,
I can't get my Vega (56&64 reference card) stable. My rig is always crashing.
Could you share your card clock and memory and the best parameters of the minerfor these cards.
Thanks
Vega64 - Strix
OverdriveNtool
Core - P7 852/825mv
Memory - P3 1083/825mv

Thanks ! 852 core frequency ? What is your hashrate with these settings ?

ETH is memory bound, core clock effect is minimal on Vegas.  Instead of setting P7, simply disable all GPU power states above P0 in OverdriveNTool.  Also, your memory clock can go up to 1107  for a 64 and you should be able to use a voltage setting between 806-831mv.  Above 1107, your voltage requirement jumps significantly to around 900mv (due to SOC clock scaling to 1200MHz.)

For a 56, your voltages and core clock would be the same, but your memory clock will have a fuzzier limit than the 64 - somewhere between 900-950MHz most likely.
newbie
Activity: 150
Merit: 0
Hi, i'm using:
- PhoenixMiner 4.1c
- 6 GPUs AMD 570 8G
- Virtual Memory (Page file): 72 GB

But PhoenixMiner show:
Phoenix Miner 4.1c Windows/msvc - Release build
-----------------------------------------------

OpenCL driver version: 17.8-BETA
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 1), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU2: Radeon RX 570 Series (pcie 4), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU3: Radeon RX 570 Series (pcie 5), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU4: Radeon RX 570 Series (pcie 6), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU5: Radeon RX 570 Series (pcie 7), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU6: Radeon RX 570 Series (pcie Cool, OpenCL 1.2, 3 GB VRAM, 32 CUs
Eth: Loading pools from epools.txt
Eth: the pool list contains 4 pools (2 from command-line)
Eth: primary pool: ssl://asia1.ethermine.org:5555
Starting GPU mining
Eth: Connecting to ethash pool ssl://asia1.ethermine.org:5555 (proto: QtMiner)
Eth: Connected to SSL ethash pool asia1.ethermine.org:5555 (172.65.231.156)
Listening for CDM remote manager at port 43333 in full mode
GPU1: 54C 69%, GPU2: 51C 65%, GPU3: 47C 60%, GPU4: 48C 61%, GPU5: 49C 63%, GPU6: 44C 56%
Eth: New job #e2163c3a from ssl://asia1.ethermine.org:5555; diff: 4000MH
GPU1: not enough VRAM for DAG epoch 242
GPU2: not enough VRAM for DAG epoch 242
GPU3: not enough VRAM for DAG epoch 242
GPU4: not enough VRAM for DAG epoch 242
GPU5: not enough VRAM for DAG epoch 242
GPU6: not enough VRAM for DAG epoch 242

https://i.imgur.com/GUPdxyl.jpg

How to fix this problem?  Huh

Thank you!

I think its driver problem. reinstall driver after doing DDU.

i have also same problem, solved by doing DDU
And wrong driver too Wink
newbie
Activity: 14
Merit: 0
Hello
Can I mine Callisto with my RX 550 2GB cards?

 
yes you can mine until DAG lessthan 2GB

Great news! Thanks. What miner do You offer? (rig with 6x Rx550 2G cards)
I mined CN8, but unfortunately, the Asics took controll over this algo again since January. Sad
newbie
Activity: 60
Merit: 0
Hello
Can I mine Callisto with my RX 550 2GB cards?

 
yes you can mine until DAG lessthan 2GB
newbie
Activity: 60
Merit: 0
Hi, i'm using:
- PhoenixMiner 4.1c
- 6 GPUs AMD 570 8G
- Virtual Memory (Page file): 72 GB

But PhoenixMiner show:
Phoenix Miner 4.1c Windows/msvc - Release build
-----------------------------------------------

OpenCL driver version: 17.8-BETA
Available GPUs for mining:
GPU1: Radeon RX 570 Series (pcie 1), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU2: Radeon RX 570 Series (pcie 4), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU3: Radeon RX 570 Series (pcie 5), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU4: Radeon RX 570 Series (pcie 6), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU5: Radeon RX 570 Series (pcie 7), OpenCL 1.2, 3 GB VRAM, 32 CUs
GPU6: Radeon RX 570 Series (pcie Cool, OpenCL 1.2, 3 GB VRAM, 32 CUs
Eth: Loading pools from epools.txt
Eth: the pool list contains 4 pools (2 from command-line)
Eth: primary pool: ssl://asia1.ethermine.org:5555
Starting GPU mining
Eth: Connecting to ethash pool ssl://asia1.ethermine.org:5555 (proto: QtMiner)
Eth: Connected to SSL ethash pool asia1.ethermine.org:5555 (172.65.231.156)
Listening for CDM remote manager at port 43333 in full mode
GPU1: 54C 69%, GPU2: 51C 65%, GPU3: 47C 60%, GPU4: 48C 61%, GPU5: 49C 63%, GPU6: 44C 56%
Eth: New job #e2163c3a from ssl://asia1.ethermine.org:5555; diff: 4000MH
GPU1: not enough VRAM for DAG epoch 242
GPU2: not enough VRAM for DAG epoch 242
GPU3: not enough VRAM for DAG epoch 242
GPU4: not enough VRAM for DAG epoch 242
GPU5: not enough VRAM for DAG epoch 242
GPU6: not enough VRAM for DAG epoch 242

https://i.imgur.com/GUPdxyl.jpg

How to fix this problem?  Huh

Thank you!

I think its driver problem. reinstall driver after doing DDU.

i have also same problem, solved by doing DDU
newbie
Activity: 28
Merit: 2
Hi.
How to make mining software restart after it crashes?
After update to newest phoenixminer with turbo kernerls it crashes more often. I think it is because I only have 120gb ssd. When u combine 13x radeon 580 8gb gpu if requires 99% disk space making the software to crash a few times a week.

I use this simple .bat file on windows:
Remember to delete "pause" command if you use it in your .bat file.

Code:
:START
PhoenixMiner.exe -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal YourEthWalletAddress.WorkerName
GOTO START
newbie
Activity: 27
Merit: 0
Hi.
How to make mining software restart after it crashes?
After update to newest phoenixminer with turbo kernerls it crashes more often. I think it is because I only have 120gb ssd. When u combine 13x radeon 580 8gb gpu if requires 99% disk space making the software to crash a few times a week.

On Windows you can monitor every X minutes with a scheduled task if phoenix is running as windows process, my code:

Code:
echo Check mining process...
SETLOCAL EnableExtensions
set EXE=PhoenixMiner.exe

FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto FOUND
echo The process is not running, starting it!
start /D "C:\Insert_your_path\PhoenixMiner_4.1c" ETH.bat

ping 127.0.0.1 -n 5 > nul
goto END

:FOUND
echo The process is running
ping 127.0.0.1 -n 1 > nul
goto QUIT

:END
ping 127.0.0.1 -n 2 > nul

:QUIT
exit

On start line corret path with your and change "ETH.bat" with your one.
On my case I run the process every 5 minutes
newbie
Activity: 312
Merit: 0
Hi.
How to make mining software restart after it crashes?
After update to newest phoenixminer with turbo kernerls it crashes more often. I think it is because I only have 120gb ssd. When u combine 13x radeon 580 8gb gpu if requires 99% disk space making the software to crash a few times a week.
newbie
Activity: 32
Merit: 0
“-di” command line of claymore miner same what is command line of phoenix miner?
Thank you!

No, in PM it is "-gpus" and the first card has index 1 not 0 like in Claymore.
Thank you!
member
Activity: 220
Merit: 12
“-di” command line of claymore miner same what is command line of phoenix miner?
Thank you!

No, in PM it is "-gpus" and the first card has index 1 not 0 like in Claymore.
member
Activity: 220
Merit: 12
Thanks for your help with the post. I hope i did not sound arrogant lol i have only been looking into this stuff for the past week and this is as far as i have gotten. i assumed what you ment from your last message was to add something inregards to using the nvidia gpu in the command line of the batch file.. i did this and am still getting this error.

...
2019.02.20:20:46:20.091: GPU1 GPU1: DAG  84%
2019.02.20:20:46:21.043: GPU1 GPU1: DAG generated in 7.8 s (379.6 MB/s)
2019.02.20:20:46:23.651: GPU1 CUDA error in CudaProgram.cu:329 : the launch timed out and was terminated (702)
2019.02.20:20:46:23.652: GPU1 GPU1 search error: the launch timed out and was terminated
2019.02.20:20:46:23.963: wdog Thread(s) not responding. Restarting.
2019.02.20:20:46:24.058: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:20:46:26.438: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x3877e351fd6dfbe84ce305257a37883a7580f6ba82cfcd11934efa0c51b2cb97","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9642"]}
2019.02.20:20:46:26.438: eths Eth: New job #3877e351 from eu1.ethermine.org:4444; diff: 4000MH
2019.02.20:20:46:26.443: GPU1 GPU1: Starting up... (0)
2019.02.20:20:46:26.444: GPU1 CUDART error in CudaProgram.cu:57 : all CUDA-capable devices are busy or unavailable (46)
2019.02.20:20:46:26.444: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable
2019.02.20:20:46:29.082: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:20:46:29.597: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.02.20:20:46:29.597: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x5c07dbb3a088fe2d1576b7d3e1224d3b891e957ee633860b92246d1553a4386f"]}

2019.02.20:20:46:29.750: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x3877e351fd6dfbe84ce305257a37883a7580f6ba82cfcd11934efa0c51b2cb97","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9642"]}
2019.02.20:20:46:29.750: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}




Experiment with the values of the parameter -ethi
Start from the lowest negative value -ethi -8192  and add it by some positive step repeatedly (e.g., +512: -8192 + 512 = -7680; -7680 + 512 = -7168; and so on) until your problem is solved.

You don't have DAG generation problem because the log clearly says:
'2019.02.20:20:46:21.043: GPU1 GPU1: DAG generated in 7.8 s (379.6 MB/s)'

The hash searching kernel hits timeout with the default settings because your GPU (980ti) is very slow.
jr. member
Activity: 117
Merit: 3
thanks for the quick response i am completely new to this but spend a good amount of time trying to figure this out yesterday .


ok Just was trying to get you to dig for more info was all. Help you learn...

So try these 2 lines... First to see you can just get a connection working... then try with backup pool if it works. The -v is to help error messaging.

PhoenixMiner.exe -pool stratum+tcp://eu1.ethermine.org:4444 -wal 0x6e9219E93f72D45e4c2043Dc2ee43cE6D3DEB088 -pass x -worker rig -v 3

PhoenixMiner.exe -pool stratum+tcp://eu1.ethermine.org:4444 -pool stratum+tcp://us1.ethermine.org:4444 -wal 0x6e9219E93f72D45e4c2043Dc2ee43cE6D3DEB088 -pass x -worker rig -v 3

newbie
Activity: 32
Merit: 0
“-di” command line of claymore miner same what is command line of phoenix miner?
Thank you!
newbie
Activity: 14
Merit: 0
Hello
Can I mine Callisto with my RX 550 2GB cards?
jr. member
Activity: 117
Merit: 3
newbie
Activity: 6
Merit: 0
thanks for the quick response i am completely new to this but spend a good amount of time trying to figure this out yesterday .

very welcome! Its a fun hobby but can make you want to pull your hair out.

I recommend for that type of card start with 9.x driver not 10 in case its too new for card...

Also make sure virtual memory is not to low. For a few cards no big deal usually.


ok  so if understand correctly i should use 9.xxx instead of the 10... i made sure i had most recent drivers but the new one may not be compatible yet is what you are sayin?


Try 9.x as its newish. The 10 on that model card may be an issue as it may be too new.. Worst case try 10 if still an issue roll back... Up to you.

Ok so i tried both things i rolled back to 9 no change and then updated again i have also switched from get work to stratum i believe but i know have new errors lol here is the log can someone please help me Smiley

2019.02.20:14:49:52.921: main Phoenix Miner 4.1c Windows/msvc - Release build
2019.02.20:14:49:52.921: main Cmd line: -pool eu1.ethermine.org:4444 -pool2 us1.ethermine.org:4444 -wal 0x6e9219E93f72D45e4c2043Dc2ee43cE6D3DEB088.rig
2019.02.20:14:49:53.142: main CUDA version: 10.0, CUDA runtime: 8.0
2019.02.20:14:49:53.168: main No OpenCL platforms found
2019.02.20:14:49:53.168: main Available GPUs for mining:
2019.02.20:14:49:53.168: main GPU1: GeForce GTX 980 Ti (pcie 2), CUDA cap. 5.2, 6 GB VRAM, 22 CUs
2019.02.20:14:49:53.173: main NVML library initialized
2019.02.20:14:49:53.179: main Nvidia driver version: 418.91
2019.02.20:14:49:54.034: main Eth: Loading pools from epools.txt
2019.02.20:14:49:54.034: main Eth: the pool list contains 2 pools (2 from command-line)
2019.02.20:14:49:54.034: main Eth: primary pool: eu1.ethermine.org:4444
2019.02.20:14:49:54.034: main Starting GPU mining
2019.02.20:14:49:54.034: wdog Starting watchdog thread
2019.02.20:14:49:54.035: main Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
2019.02.20:14:49:54.236: main Listening for CDM remote manager at port 3333 in read-only mode
2019.02.20:14:49:54.236: main GPU1: 36C 35%
2019.02.20:14:49:54.645: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (2606:4700:90:0:bda0:4092:8f4f:4658)
2019.02.20:14:49:54.645: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["0x6e9219E93f72D45e4c2043Dc2ee43cE6D3DEB088.rig"]}

2019.02.20:14:49:54.929: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
2019.02.20:14:49:54.929: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.02.20:14:49:55.075: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x993801f5fb3bdf4d745a3ccfdf2f8c465401ac50ec03decf8c46197857e24a5a","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9242"]}
2019.02.20:14:49:55.075: eths Eth: New job #993801f5 from eu1.ethermine.org:4444; diff: 4000MH
2019.02.20:14:49:55.076: GPU1 GPU1: Starting up... (0)
2019.02.20:14:49:55.076: GPU1 GPU1: Generating ethash light cache for epoch #241
2019.02.20:14:49:57.750: GPU1 Light cache generated in 2.7 s (17.3 MB/s)
2019.02.20:14:49:57.978: GPU1 GPU1: Allocating DAG (2.90) GB; good for epoch up to #243
2019.02.20:14:49:57.986: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0xc0e26a88af5b64defdd4a5425f9404a1e56bf3c2e4205b723a12564198250402","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9242"]}
2019.02.20:14:49:57.986: eths Eth: New job #c0e26a88 from eu1.ethermine.org:4444; diff: 4000MH
2019.02.20:14:49:58.211: GPU1 GPU1: Allocating light cache buffer (46.4) MB; good for epoch up to #243
2019.02.20:14:49:58.225: GPU1 GPU1: Generating DAG for epoch #241
2019.02.20:14:49:59.059: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:14:49:59.927: GPU1 GPU1: DAG  19%
2019.02.20:14:50:01.635: GPU1 GPU1: DAG  41%
2019.02.20:14:50:02.600: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x4d42643b718ca1da42569e635439121bfa385a47be9928867f4ae413931f5815","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9242"]}
2019.02.20:14:50:02.600: eths Eth: New job #4d42643b from eu1.ethermine.org:4444; diff: 4000MH
2019.02.20:14:50:03.335: GPU1 GPU1: DAG  63%
2019.02.20:14:50:04.082: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:14:50:04.646: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.02.20:14:50:04.792: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x4d42643b718ca1da42569e635439121bfa385a47be9928867f4ae413931f5815","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9242"]}
2019.02.20:14:50:05.034: GPU1 GPU1: DAG  84%
2019.02.20:14:50:05.983: GPU1 GPU1: DAG generated in 7.8 s (380.5 MB/s)
2019.02.20:14:50:09.107: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:14:50:10.011: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x2532a4b44ffb5f3c676fd9bd4aa411ea538bd9b3243ef3414611aa0367aba04b","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9243"]}
2019.02.20:14:50:10.011: eths Eth: New job #2532a4b4 from eu1.ethermine.org:4444; diff: 4000MH
2019.02.20:14:50:10.442: GPU1 CUDA error in CudaProgram.cu:329 : the launch timed out and was terminated (702)
2019.02.20:14:50:10.442: GPU1 GPU1 search error: the launch timed out and was terminated
2019.02.20:14:50:11.044: wdog Thread(s) not responding. Restarting.
2019.02.20:14:50:13.877: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x487f96427277b848a7d9294af758b43b3492389c6b5fa4031b5d7ef90b5962fa","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9243"]}
2019.02.20:14:50:13.877: eths Eth: New job #487f9642 from eu1.ethermine.org:4444; diff: 4000MH
2019.02.20:14:50:13.897: GPU1 GPU1: Starting up... (0)
2019.02.20:14:50:13.898: GPU1 CUDART error in CudaProgram.cu:57 : all CUDA-capable devices are busy or unavailable (46)
2019.02.20:14:50:13.898: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable
2019.02.20:14:50:14.299: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
2019.02.20:14:50:14.646: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2019.02.20:14:50:14.647: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0","0x100ab6477514dc45f13f1b6dd20cdc4be84166d8e4f9ab11f0207a801fc1841b"]}

2019.02.20:14:50:14.793: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x487f96427277b848a7d9294af758b43b3492389c6b5fa4031b5d7ef90b5962fa","0xfa8b22f3951b9097cafa990738694a808dbc03361c9d55d9b3157b6f9f99de6b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x6e9243"]}
2019.02.20:14:50:14.793: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}



jr. member
Activity: 117
Merit: 3
thanks for the quick response i am completely new to this but spend a good amount of time trying to figure this out yesterday .

very welcome! Its a fun hobby but can make you want to pull your hair out.

I recommend for that type of card start with 9.x driver not 10 in case its too new for card...

Also make sure virtual memory is not to low. For a few cards no big deal usually.


ok  so if understand correctly i should use 9.xxx instead of the 10... i made sure i had most recent drivers but the new one may not be compatible yet is what you are sayin?


Try 9.x as its newish. The 10 on that model card may be an issue as it may be too new.. Worst case try 10 if still an issue roll back... Up to you.
Jump to: