Read this if you can't mine ETC with PhoenixMiner: important message for everyone that is running older versions of PhoenixMiner (before 4.2) - this was already posted here a few times in the last few weeks:
IMPORTANT! The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. ETC has reached epoch 266 already, and ETH will reach epoch 266 in little more than a month. To ensure uninterrupted operation, please upgrade to 4.2. If you are mining other coins, you can safely disregard this message.
The reason for this limitation is that we need to perform some quite complex calculations for each future DAG epoch in order to increase the hashrate of the optimized kernels. Recently we have added more computational resources and PhoenixMiner 4.2 will work without problems up to DAG epoch 329. We will increase this number significantly (e.g. 400 or more) in the next version.
Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 340. (Read 784965 times)
May 06, 2019, 12:12:21 AM
May 05, 2019, 03:07:01 PM
Hi,
I have issues with PhoenixMiner 4.2c version(Win10 x64 1703). Problem is; Phoenix giving error message "software stopped working" after a few hours. Sometimes not stopping but not giving share too, going to offline. What is the problem?
I have issues with PhoenixMiner 4.2c version(Win10 x64 1703). Problem is; Phoenix giving error message "software stopped working" after a few hours. Sometimes not stopping but not giving share too, going to offline. What is the problem?
More info needed.
What is start script?
add -v 3 to it so we get more verbose messaging. Hardware how much ram? how much pagefile memory? What are you running AMd or nvidia?
May 05, 2019, 10:34:20 AM
Hi,
I keep getting multiple instances of Phoenixminer running/restarting at the same time immediately after crashes... with the error message being "Waiting 15 s for previous instance to close".
How do I keep this from happening? Please help.
Thank you.
I keep getting multiple instances of Phoenixminer running/restarting at the same time immediately after crashes... with the error message being "Waiting 15 s for previous instance to close".
How do I keep this from happening? Please help.
Thank you.
what drivers are you using? amd or nvidia cards? what os? what is your start up command line?
Either 1060 or 1070 running on Nvidia 391.35 on either Win 7 or Win 10.
Command line parameters:
-rmode 1 -wdog 1 -cdm 2
And oh, I'm using Awesome Miner for my rigs.
I've tried -gswin 0 and -wdog 0 to no avail. Any suggestions are very much welcome, thank you again.
Ideally the whole command line would help. You should add -v 3 to it to show more verbose messages. Never used Awesome miner so cant speak to it.
Do you have lots of page file swap space? Can you try running card not overclocked?
May 05, 2019, 03:57:27 AM
Code:
Important message for everyone that is running older versions of PhoenixMiner (before 4.2):
IMPORTANT! The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. ETC will reach epoch 266 in less than a week, and ETH will reach epoch 266 in about 45 days. To ensure uninterrupted operation, please upgrade to 4.2 before epoch 266. If you are mining other coins, you can safely disregard this message.
Post what is said above is not true at all almost all versions of phoenixminer from the start version works very well with AMD GPU, if you use nvida gpu then it is true from start version to 3.5 version no longer works. For clarity
-nvf
-nvf option, if I choose -nvf 3 then the hasrate is the highest, someone has a bit more experience with this option and what the disadvantage of this is, I see much higher steel shares than this is true for others, please do more explanation of the PM dev and where is a new version of Phoenix
May 04, 2019, 11:21:47 PM
Hi,
I keep getting multiple instances of Phoenixminer running/restarting at the same time immediately after crashes... with the error message being "Waiting 15 s for previous instance to close".
How do I keep this from happening? Please help.
Thank you.
I keep getting multiple instances of Phoenixminer running/restarting at the same time immediately after crashes... with the error message being "Waiting 15 s for previous instance to close".
How do I keep this from happening? Please help.
Thank you.
what drivers are you using? amd or nvidia cards? what os? what is your start up command line?
Either 1060 or 1070 running on Nvidia 391.35 on either Win 7 or Win 10.
Command line parameters:
-rmode 1 -wdog 1 -cdm 2
And oh, I'm using Awesome Miner for my rigs.
I've tried -gswin 0 and -wdog 0 to no avail. Any suggestions are very much welcome, thank you again.
May 04, 2019, 10:24:44 PM
Hi,
I keep getting multiple instances of Phoenixminer running/restarting at the same time immediately after crashes... with the error message being "Waiting 15 s for previous instance to close".
How do I keep this from happening? Please help.
Thank you.
I keep getting multiple instances of Phoenixminer running/restarting at the same time immediately after crashes... with the error message being "Waiting 15 s for previous instance to close".
How do I keep this from happening? Please help.
Thank you.
what drivers are you using? amd or nvidia cards? what os? what is your start up command line?
May 04, 2019, 09:06:25 PM
Hi,
I keep getting multiple instances of Phoenixminer running/restarting at the same time immediately after crashes... with the error message being "Waiting 15 s for previous instance to close".
How do I keep this from happening? Please help.
Thank you.
I keep getting multiple instances of Phoenixminer running/restarting at the same time immediately after crashes... with the error message being "Waiting 15 s for previous instance to close".
How do I keep this from happening? Please help.
Thank you.
May 04, 2019, 07:04:05 AM
-nvf Nvidia kernel sync (0: never, 1: periodic; 2: always; 3: forced; default: 1). You may specify this option per-GPU. 
??
-nvf option, if I choose -nvf 3 then the hasrate is the highest, someone has a bit more experience with this option and what the disadvantage of this is, I see much higher steel shares than this is true for others, please do more explanation of the PM dev and where is a new version of Phoenix
??-nvf option, if I choose -nvf 3 then the hasrate is the highest, someone has a bit more experience with this option and what the disadvantage of this is, I see much higher steel shares than this is true for others, please do more explanation of the PM dev and where is a new version of Phoenix
May 04, 2019, 06:54:09 AM
"stratum thread not responsive
exit code 347"
phoenixminer 4.2c
what does this code mean? why miner just stops working?
exit code 347"
phoenixminer 4.2c
what does this code mean? why miner just stops working?
May 03, 2019, 12:44:51 PM
I'm new to mining...have been doing this for less than 2 months.
OS Win10, 19.4.1 AMD drivers.
I have a rig equipped with RX570's that I've been using Phoenixminer with for a month now, and it's been working great (29.8MH/s per card). I've used the PM settings to set my core and mem clocks as well as the cvdcc and mvdcc to 850. However, checking wattmeter, each card is pulling around 110W from the wall. If I apply a further -115mV with Sapphire Trixx, my power usage drops to 90W.
I tried reducing cvdcc tp 750 to see if that would be equivalent, but the power usage only drops to 105W.
Am I misunderstanding the relationship between cvdcc and the sapphire Trixx GPU undervolt setting? Is there some other way that I can automatically apply those settings that reduce my power consumption?
OS Win10, 19.4.1 AMD drivers.
I have a rig equipped with RX570's that I've been using Phoenixminer with for a month now, and it's been working great (29.8MH/s per card). I've used the PM settings to set my core and mem clocks as well as the cvdcc and mvdcc to 850. However, checking wattmeter, each card is pulling around 110W from the wall. If I apply a further -115mV with Sapphire Trixx, my power usage drops to 90W.
I tried reducing cvdcc tp 750 to see if that would be equivalent, but the power usage only drops to 105W.
Am I misunderstanding the relationship between cvdcc and the sapphire Trixx GPU undervolt setting? Is there some other way that I can automatically apply those settings that reduce my power consumption?
May 03, 2019, 12:43:49 PM
Available GPUs for mining:
GPU1: Radeon RX 580 Series (pcie 1), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU2: Radeon RX 580 Series (pcie 3), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU3: Radeon RX 580 Series (pcie 4), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU4: Radeon RX 580 Series (pcie 5), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU5: Radeon RX 580 Series (pcie 6), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU6: Radeon RX 580 Series (pcie 7), OpenCL 1.2, 8 GB VRAM, 36 CUs
GPU1: 43C 65%, GPU2: 47C 65%, GPU3: 47C 65%, GPU4: 45C 65%, GPU5: 47C 65%, GPU6: 50C 65%
Current -gt 71,71,71,71,71,71
Eth: Accepted shares 9095 (3 stales), rejected shares 282 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.03%
Eth: Maximum difficulty of found share: 11.4 TH (!!!)
Eth: Average speed (5 min): 0.000 MH/s
Eth: Effective speed: 53.04 MH/s; at pool: 51.45 MH/s
Eth speed: 0.000 MH/s, shares: 9095/282/0, time: 49:06
GPUs: 1: 0.000 MH/s (1541) 2: 0.000 MH/s (1541) 3: 0.000 MH/s (1600) 4: 0.000 MH/s (1512) 5: 0.000 MH/s (1580) 6: 0.000 MH/s (1603)
I don't know why but at some point phoenix miner starts to show 0 hash rate, but it mines correctly on the pool, the share number increases with 0 hash.
I'm using ubuntu 18.04.
kernel: 4.20.6-042006-generic #201901310331 SMP Thu Jan 31 08:33:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
amd driver: amdgpu18.40-676022
Phoenix Miner 4.1c
At the fastest this issue happens after 15 hours of mining, but It popped up even after 4 days.
I also notice this in dmesg, but not every time, sometimes this error is there sometimes is not
kern :info : [Sun Apr 21 10:41:04 2019] traps: phoenix[9096] trap divide error ip:550ac1 sp:7ffdb110f230 error:0 in PhoenixMiner[400000+740000]
kern :info : [Mon Apr 22 09:23:49 2019] traps: phoenix[20905] trap divide error ip:550ac1 sp:7ffe62664970 error:0 in PhoenixMiner[400000+740000]
Try other amd drivers. RX580 works perfectly with amd 18.10, 18.20 ok too.
May 02, 2019, 06:56:47 AM
The latter error is not related to crash, the first is, either lower your memory clock or bump voltage.
Memory is running at stock clock. No OC only underclock, I confirm second error is when gpu is recovering. After 40min running at 1373Mhz and 800mv, only 90Mh one the pool, miner report 142,87..
Quote
*** 0:41 *** 5/1 12:08 **************************************
Eth: Mining ETH on solo-eth.2miners.com:6060 for 0:41
Eth speed: 142.958 MH/s, shares: 15/0/0, time: 0:41
GPUs: 1: 71.495 MH/s (6) 2: 71.462 MH/s (9)
Eth: Accepted shares 15 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 367.3 GH (!)
Eth: Average speed (5 min): 142.939 MH/s
Eth: Effective speed: 96.85 MH/s; at pool: 96.85 MH/s
Eth: Mining ETH on solo-eth.2miners.com:6060 for 0:41
Eth speed: 142.958 MH/s, shares: 15/0/0, time: 0:41
GPUs: 1: 71.495 MH/s (6) 2: 71.462 MH/s (9)
Eth: Accepted shares 15 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 367.3 GH (!)
Eth: Average speed (5 min): 142.939 MH/s
Eth: Effective speed: 96.85 MH/s; at pool: 96.85 MH/s
Did you update the vii s bios to latest version?
https://www.amd.com/en/support/radeonvii-vbios-eula
I've tried but my cards are Sapphire and they already have latest bios
May 01, 2019, 09:52:01 PM
The latter error is not related to crash, the first is, either lower your memory clock or bump voltage.
Memory is running at stock clock. No OC only underclock, I confirm second error is when gpu is recovering. After 40min running at 1373Mhz and 800mv, only 90Mh one the pool, miner report 142,87..
Quote
*** 0:41 *** 5/1 12:08 **************************************
Eth: Mining ETH on solo-eth.2miners.com:6060 for 0:41
Eth speed: 142.958 MH/s, shares: 15/0/0, time: 0:41
GPUs: 1: 71.495 MH/s (6) 2: 71.462 MH/s (9)
Eth: Accepted shares 15 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 367.3 GH (!)
Eth: Average speed (5 min): 142.939 MH/s
Eth: Effective speed: 96.85 MH/s; at pool: 96.85 MH/s
Eth: Mining ETH on solo-eth.2miners.com:6060 for 0:41
Eth speed: 142.958 MH/s, shares: 15/0/0, time: 0:41
GPUs: 1: 71.495 MH/s (6) 2: 71.462 MH/s (9)
Eth: Accepted shares 15 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 367.3 GH (!)
Eth: Average speed (5 min): 142.939 MH/s
Eth: Effective speed: 96.85 MH/s; at pool: 96.85 MH/s
Did you update the vii s bios to latest version?
https://www.amd.com/en/support/radeonvii-vbios-eula
May 01, 2019, 07:11:33 AM
The latter error is not related to crash, the first is, either lower your memory clock or bump voltage.
Memory is running at stock clock. No OC only underclock, I confirm second error is when gpu is recovering. After 40min running at 1373Mhz and 800mv, only 90Mh one the pool, miner report 142,87..
Quote
*** 0:41 *** 5/1 12:08 **************************************
Eth: Mining ETH on solo-eth.2miners.com:6060 for 0:41
Eth speed: 142.958 MH/s, shares: 15/0/0, time: 0:41
GPUs: 1: 71.495 MH/s (6) 2: 71.462 MH/s (9)
Eth: Accepted shares 15 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 367.3 GH (!)
Eth: Average speed (5 min): 142.939 MH/s
Eth: Effective speed: 96.85 MH/s; at pool: 96.85 MH/s
Eth: Mining ETH on solo-eth.2miners.com:6060 for 0:41
Eth speed: 142.958 MH/s, shares: 15/0/0, time: 0:41
GPUs: 1: 71.495 MH/s (6) 2: 71.462 MH/s (9)
Eth: Accepted shares 15 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Maximum difficulty of found share: 367.3 GH (!)
Eth: Average speed (5 min): 142.939 MH/s
Eth: Effective speed: 96.85 MH/s; at pool: 96.85 MH/s
May 01, 2019, 06:37:54 AM
are running linux or windows?
what motherboard are you running? processor?
what motherboard are you running? processor?
I'm running Linux, proc: i7-7820x motherboard: Asrock x299 XE taichi
Quote
[33871.752337] amdgpu 0000:19:00.0: [gfxhub] no-retry page fault (src_id:0 ring:158 vmid:2 pasid:32776, for process PhoenixMiner pid 17761 thread PhoenixMiner pid 17761)
[33871.752339] amdgpu 0000:19:00.0: in page starting at address 0x0000004069576000 from 27
[33871.752341] amdgpu 0000:19:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0020113D
[33871.752347] amdgpu 0000:19:00.0: [gfxhub] no-retry page fault (src_id:0 ring:158 vmid:2 pasid:32776, for process PhoenixMiner pid 17761 thread PhoenixMiner pid 17761)
[33871.752349] amdgpu 0000:19:00.0: in page starting at address 0x00000006858c8000 from 27
[33871.752350] amdgpu 0000:19:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0020113D
[33871.752339] amdgpu 0000:19:00.0: in page starting at address 0x0000004069576000 from 27
[33871.752341] amdgpu 0000:19:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0020113D
[33871.752347] amdgpu 0000:19:00.0: [gfxhub] no-retry page fault (src_id:0 ring:158 vmid:2 pasid:32776, for process PhoenixMiner pid 17761 thread PhoenixMiner pid 17761)
[33871.752349] amdgpu 0000:19:00.0: in page starting at address 0x00000006858c8000 from 27
[33871.752350] amdgpu 0000:19:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0020113D
Quote
[34620.085313] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.309602] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.533916] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.758159] [drm] schedcomp_1.2.0 is not ready, skipping
By the way this are errors when running gpu is hanging [34620.309602] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.533916] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.758159] [drm] schedcomp_1.2.0 is not ready, skipping
May 01, 2019, 06:18:34 AM
are running linux or windows?
what motherboard are you running? processor?
what motherboard are you running? processor?
I'm running Linux, proc: i7-7820x motherboard: Asrock x299 XE taichi
Quote
[33871.752337] amdgpu 0000:19:00.0: [gfxhub] no-retry page fault (src_id:0 ring:158 vmid:2 pasid:32776, for process PhoenixMiner pid 17761 thread PhoenixMiner pid 17761)
[33871.752339] amdgpu 0000:19:00.0: in page starting at address 0x0000004069576000 from 27
[33871.752341] amdgpu 0000:19:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0020113D
[33871.752347] amdgpu 0000:19:00.0: [gfxhub] no-retry page fault (src_id:0 ring:158 vmid:2 pasid:32776, for process PhoenixMiner pid 17761 thread PhoenixMiner pid 17761)
[33871.752349] amdgpu 0000:19:00.0: in page starting at address 0x00000006858c8000 from 27
[33871.752350] amdgpu 0000:19:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0020113D
[33871.752339] amdgpu 0000:19:00.0: in page starting at address 0x0000004069576000 from 27
[33871.752341] amdgpu 0000:19:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0020113D
[33871.752347] amdgpu 0000:19:00.0: [gfxhub] no-retry page fault (src_id:0 ring:158 vmid:2 pasid:32776, for process PhoenixMiner pid 17761 thread PhoenixMiner pid 17761)
[33871.752349] amdgpu 0000:19:00.0: in page starting at address 0x00000006858c8000 from 27
[33871.752350] amdgpu 0000:19:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x0020113D
Quote
[34620.085313] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.309602] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.533916] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.758159] [drm] schedcomp_1.2.0 is not ready, skipping
By the way this are errors when running gpu is hanging [34620.309602] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.533916] [drm] schedcomp_1.2.0 is not ready, skipping
[34620.758159] [drm] schedcomp_1.2.0 is not ready, skipping
April 30, 2019, 07:38:28 PM
Anyone else running into problem with multiple Radeon vii's? When I have 1 card running it seems to be working fine but as soon as I go to 2+ GPU1 hash rate is super low or non existent
I noticed when GPU1 wanted to start up the DAG was taking a considerable amount of time to load. 5+ times as long as GPU2.
Anyone have any thoughts on this or similar issues?
I noticed when GPU1 wanted to start up the DAG was taking a considerable amount of time to load. 5+ times as long as GPU2.
Anyone have any thoughts on this or similar issues?
Well I've received my second Radeon VII, depending of voltage, card will just not mine at all.
- 1150Mhz 750mv (1 of 2 working)
- 1250Mhz 760mv (2 of 2 working)
are running linux or windows?
what motherboard are you running? processor?
April 30, 2019, 09:36:06 AM
Anyone else running into problem with multiple Radeon vii's? When I have 1 card running it seems to be working fine but as soon as I go to 2+ GPU1 hash rate is super low or non existent
I noticed when GPU1 wanted to start up the DAG was taking a considerable amount of time to load. 5+ times as long as GPU2.
Anyone have any thoughts on this or similar issues?
I noticed when GPU1 wanted to start up the DAG was taking a considerable amount of time to load. 5+ times as long as GPU2.
Anyone have any thoughts on this or similar issues?
Well I've received my second Radeon VII, depending of voltage, card will just not mine at all.
- 1150Mhz 750mv (1 of 2 working)
- 1250Mhz 760mv (2 of 2 working)
April 29, 2019, 03:27:37 AM
I was mining with Claymore miner from the beginning but now I tried this miner and it's better - more hash, less power draw, less fee. Thank you. 
April 29, 2019, 12:37:52 AM
Repeating the important message for everyone that is running older versions of PhoenixMiner (before 4.2):
IMPORTANT! The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. ETC will reach epoch 266 in less than a week, and ETH will reach epoch 266 in about 45 days. To ensure uninterrupted operation, please upgrade to 4.2 before epoch 266. If you are mining other coins, you can safely disregard this message.
The reason for this limitation is that we need to perform some quite complex calculations for each future DAG epoch in order to increase the hashrate of the optimized kernels. Recently we have added more computational resources and PhoenixMiner 4.2 will work without problems up to DAG epoch 329. We will increase this number significantly (e.g. 400 or more) in the future releases.
IMPORTANT! The versions of PhoenixMiner before 4.2 only support DAG epoch up to 265. ETC will reach epoch 266 in less than a week, and ETH will reach epoch 266 in about 45 days. To ensure uninterrupted operation, please upgrade to 4.2 before epoch 266. If you are mining other coins, you can safely disregard this message.
The reason for this limitation is that we need to perform some quite complex calculations for each future DAG epoch in order to increase the hashrate of the optimized kernels. Recently we have added more computational resources and PhoenixMiner 4.2 will work without problems up to DAG epoch 329. We will increase this number significantly (e.g. 400 or more) in the future releases.
Jump to: