Topic: PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux) - page 430. (Read 784965 times)
April 10, 2018, 03:30:15 PM
I really like this miner. It uses slightly more power then Claymore, but the interface is much better. Maybe a noob question or maybe it has been asked before, but what are the 'degrees' with the exclamation marks ( !!! ). Is it like GH = ( ! ) and TH = ( !!! )?
April 10, 2018, 03:19:06 PM
i think my one nvidia based rig is having a similar issue. it's running 2.8c.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
this is what's happening.
https://i.imgur.com/FwkkBvx.png
normally something like this would just trigger the watchdog, but it crashes in windows and just hangs. so it cant restart itself.
This is exactly what happens to my Riggie 1 too. Even after fresh windows 10 installed.
April 10, 2018, 01:54:42 PM
I'm tired of waiting for a better version of phoenixminer 2.8.c, so I experiment with other miner software a few days I use this software and I like it very well, miners who want to try it may also try to wonder what other people do find the performance the Average hashrate + Shares remains many times higher than phoenixminer and Claymore miner.
Download: https://github.com/digitalpara/WiNETH
Download: https://mirrorace.com/m/1qikt
Download: https://github.com/digitalpara/WiNETH Download: https://mirrorace.com/m/1qiktThat’s not even a miner, just a GUI for ethminer.
GTFO
Oke thanks but it is working verry good and configuration is better
April 10, 2018, 01:08:54 PM
i think my one nvidia based rig is having a similar issue. it's running 2.8c.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
this is what's happening.
https://i.imgur.com/FwkkBvx.png
normally something like this would just trigger the watchdog, but it crashes in windows and just hangs. so it cant restart itself.
lower the OC on GPU 7, i had the same issue working stable now
April 10, 2018, 01:01:25 PM
I'm tired of waiting for a better version of phoenixminer 2.8.c, so I experiment with other miner software a few days I use this software and I like it very well, miners who want to try it may also try to wonder what other people do find the performance the Average hashrate + Shares remains many times higher than phoenixminer and Claymore miner.
Download: https://github.com/digitalpara/WiNETH
Download: https://mirrorace.com/m/1qikt
Download: https://github.com/digitalpara/WiNETH Download: https://mirrorace.com/m/1qiktThat’s not even a miner, just a GUI for ethminer.
GTFO
April 10, 2018, 10:46:09 AM
I'm tired of waiting for a better version of phoenixminer 2.8.c, so I experiment with other miner software a few days I use this software and I like it very well, miners who want to try it may also try to wonder what other people do find the performance the Average hashrate + Shares remains many times higher than phoenixminer and Claymore miner.
Download: https://github.com/digitalpara/WiNETH
Download: https://mirrorace.com/m/1qikt
Download: https://github.com/digitalpara/WiNETH Download: https://mirrorace.com/m/1qikt April 10, 2018, 09:38:38 AM
This does seem quite similar but this happens during normal mining and not during DAG generation so it is less likely to be a power issue. Still, could you try to lower the power limit of your cards and see if this fixes the problem? On our test rigs the PSUs are over-provisioned by at least 50-60% so we never see such problems. Even if the PSU(s) should be enough on theory, some GPUs have momentary peaks in their power consumption which can drop the voltage enough to cause a crash.
We will also investigate why the program doesn't restart as it should (and as it does in many other cases).
We will also investigate why the program doesn't restart as it should (and as it does in many other cases).
Hey, thanks.
I doubt it's a power problem in my case, this system pulls ~780W from the wall, and it's running split between 2 750W platinum HP server supplies. with the motherboard, 1080ti and 2x 1060's running off one PSU, and the other 6 1060's running off the second.
Z270P motherboard
G4400 CPU
4GB DDR4-2133
32GB page file
6x GTX 1060 6GB
1x GTX 1080ti
In any case, I reduced my power limit on the 1060's by 2% (from 70% to 68%)
and reduced the power limit on the 1080ti by 5% (from 80% to 75%)
didn't seem to affect the hashrates and dropped me to 765 from the wall so that's good.
I've also switched back to 2.8b for now. I think it's a problem in 2.8c causing this.
April 10, 2018, 12:48:34 AM
Can anybody tell me why phoenix.exe above 2.7c crashes in 5 seconds when starting on one rig and on my other rig it runs perfect also with latest version.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
Please send us the log file and check if the miner shows "Debugger detected" error before crashing (the "Debugger detected" error will not be printed in the log file). If the console window closes fast after the program crashes, please put a pause command after the line that starts PhoenixMiner in your .bat file (or use the start_miner.bat file that is in the PhoenixMiner .zip file, which already has a pause command).Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
If the error is "Debugger detected" try to add -nvidia to your command line.
Thanks for helping me what to do!
I hope the information below can help.
My bat file:
PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -wal WALLET.Rig1 -proto 3 -nvidia -mi 10
pause
My log file:
Code:
17629:08:48:59.095: main Phoneix Miner 2.8c Windows/msvc - Release
17629:08:48:59.095: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -wal 0x71378f9Ddf59B762CcA6F6E072266fB543ACc26E.Rig1 -proto 3 -nvidia -mi 10
17629:08:48:59.684: main Available GPUs for mining:
17629:08:48:59.684: main GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU2: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU3: GeForce GTX 1070 (pcie 4), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU4: GeForce GTX 1070 (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU5: GeForce GTX 1070 (pcie 6), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU6: GeForce GTX 1070 (pcie 7), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.687: main NVML library initialized
17629:08:48:59.963: main Listening for CDM remote manager at port 3333 in read-only mode
17629:08:48:59.963: main Eth: the pool list contains 3 pools
17629:08:48:59.963: main Eth: primary pool: ssl://eu1.ethermine.org:5555
17629:08:48:59.963: main Starting GPU mining
17629:08:48:59.964: wdog Starting watchdog thread
17629:08:49:00.134: main Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: QtMiner)
17629:08:49:00.192: eths Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (46.105.121.53)
17629:08:49:00.277: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_login","params":["0x71378f9Ddf59B762CcA6F6E072266fB543ACc26E.Rig1"]}
17629:08:49:00.310: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
17629:08:49:00.311: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17629:08:49:00.343: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xfb9bd11be49c953953040d441c85cc39d486c692c11881300ec0c263f449df0c","0xf14c514effe89b62170940fc9de2265eb7e0d18aae7c8198ee5788b20b90e2af","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x526cbc"]}
17629:08:49:00.343: eths Eth: New job #fb9bd11b from ssl://eu1.ethermine.org:5555; diff: 4000MH
17629:08:49:00.343: GPU1 GPU1: Starting up... (0)
17629:08:49:00.344: GPU1 Eth: Generating light cache for epoch #180
17629:08:49:00.344: main GPU1: 50C 45%, GPU2: 47C 44%, GPU3: 46C 43%, GPU4: 49C 44%, GPU5: 46C 43%, GPU6: 43C 41%
17629:08:49:00.360: GPU2 GPU2: Starting up... (0)
17629:08:49:00.376: GPU3 GPU3: Starting up... (0)
17629:08:49:00.391: GPU4 GPU4: Starting up... (0)
17629:08:49:00.408: GPU5 GPU5: Starting up... (0)
17629:08:49:00.423: GPU6 GPU6: Starting up... (0)
17629:08:49:02.450: GPU3 GPU3: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.566: GPU3 GPU3: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:02.693: GPU3 GPU3: Generating DAG for epoch #180
17629:08:49:02.828: GPU5 GPU5: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.835: GPU1 GPU1: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.839: GPU2 GPU2: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.922: GPU1 GPU1: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:02.955: GPU5 GPU5: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:02.960: GPU2 GPU2: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:02.978: GPU4 GPU4: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.994: GPU6 GPU6: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:03.049: GPU1 GPU1: Generating DAG for epoch #180
17629:08:49:03.055: GPU4 GPU4: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:03.065: GPU5 GPU5: Generating DAG for epoch #180
17629:08:49:03.069: GPU2 GPU2: Generating DAG for epoch #180
17629:08:49:03.077: GPU6 GPU6: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:03.167: GPU4 GPU4: Generating DAG for epoch #180
17629:08:49:03.184: GPU6 CUDA error in CudaProgram.cu:220 : unspecified launch failure (719)
17629:08:49:03.184: GPU1 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.184: GPU6 GPU6 initMiner error: unspecified launch failure
17629:08:49:03.184: GPU1 GPU1 initMiner error: unspecified launch failure
17629:08:49:03.220: GPU4 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.220: GPU4 GPU4 initMiner error: unspecified launch failure
17629:08:49:03.266: GPU2 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.266: GPU5 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.266: GPU3 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.266: GPU2 GPU2 initMiner error: unspecified launch failure
17629:08:49:03.267: GPU5 GPU5 initMiner error: unspecified launch failure
17629:08:49:03.267: GPU3 GPU3 initMiner error: unspecified launch failure
17629:08:49:05.283: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17629:08:49:05.283: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
[/quote]17629:08:48:59.095: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -wal 0x71378f9Ddf59B762CcA6F6E072266fB543ACc26E.Rig1 -proto 3 -nvidia -mi 10
17629:08:48:59.684: main Available GPUs for mining:
17629:08:48:59.684: main GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU2: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU3: GeForce GTX 1070 (pcie 4), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU4: GeForce GTX 1070 (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU5: GeForce GTX 1070 (pcie 6), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.684: main GPU6: GeForce GTX 1070 (pcie 7), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
17629:08:48:59.687: main NVML library initialized
17629:08:48:59.963: main Listening for CDM remote manager at port 3333 in read-only mode
17629:08:48:59.963: main Eth: the pool list contains 3 pools
17629:08:48:59.963: main Eth: primary pool: ssl://eu1.ethermine.org:5555
17629:08:48:59.963: main Starting GPU mining
17629:08:48:59.964: wdog Starting watchdog thread
17629:08:49:00.134: main Eth: Connecting to ethash pool ssl://eu1.ethermine.org:5555 (proto: QtMiner)
17629:08:49:00.192: eths Eth: Connected to SSL ethash pool eu1.ethermine.org:5555 (46.105.121.53)
17629:08:49:00.277: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_login","params":["0x71378f9Ddf59B762CcA6F6E072266fB543ACc26E.Rig1"]}
17629:08:49:00.310: eths Eth: Received: {"id":1,"jsonrpc":"2.0","result":true}
17629:08:49:00.311: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
17629:08:49:00.343: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0xfb9bd11be49c953953040d441c85cc39d486c692c11881300ec0c263f449df0c","0xf14c514effe89b62170940fc9de2265eb7e0d18aae7c8198ee5788b20b90e2af","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x526cbc"]}
17629:08:49:00.343: eths Eth: New job #fb9bd11b from ssl://eu1.ethermine.org:5555; diff: 4000MH
17629:08:49:00.343: GPU1 GPU1: Starting up... (0)
17629:08:49:00.344: GPU1 Eth: Generating light cache for epoch #180
17629:08:49:00.344: main GPU1: 50C 45%, GPU2: 47C 44%, GPU3: 46C 43%, GPU4: 49C 44%, GPU5: 46C 43%, GPU6: 43C 41%
17629:08:49:00.360: GPU2 GPU2: Starting up... (0)
17629:08:49:00.376: GPU3 GPU3: Starting up... (0)
17629:08:49:00.391: GPU4 GPU4: Starting up... (0)
17629:08:49:00.408: GPU5 GPU5: Starting up... (0)
17629:08:49:00.423: GPU6 GPU6: Starting up... (0)
17629:08:49:02.450: GPU3 GPU3: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.566: GPU3 GPU3: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:02.693: GPU3 GPU3: Generating DAG for epoch #180
17629:08:49:02.828: GPU5 GPU5: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.835: GPU1 GPU1: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.839: GPU2 GPU2: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.922: GPU1 GPU1: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:02.955: GPU5 GPU5: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:02.960: GPU2 GPU2: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:02.978: GPU4 GPU4: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:02.994: GPU6 GPU6: Allocating DAG (2.42) GB; good for epoch up to #182
17629:08:49:03.049: GPU1 GPU1: Generating DAG for epoch #180
17629:08:49:03.055: GPU4 GPU4: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:03.065: GPU5 GPU5: Generating DAG for epoch #180
17629:08:49:03.069: GPU2 GPU2: Generating DAG for epoch #180
17629:08:49:03.077: GPU6 GPU6: Allocating light cache buffer (38.7) MB; good for epoch up to #182
17629:08:49:03.167: GPU4 GPU4: Generating DAG for epoch #180
17629:08:49:03.184: GPU6 CUDA error in CudaProgram.cu:220 : unspecified launch failure (719)
17629:08:49:03.184: GPU1 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.184: GPU6 GPU6 initMiner error: unspecified launch failure
17629:08:49:03.184: GPU1 GPU1 initMiner error: unspecified launch failure
17629:08:49:03.220: GPU4 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.220: GPU4 GPU4 initMiner error: unspecified launch failure
17629:08:49:03.266: GPU2 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.266: GPU5 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.266: GPU3 CUDART error in CudaProgram.cu:123 : unspecified launch failure (4)
17629:08:49:03.266: GPU2 GPU2 initMiner error: unspecified launch failure
17629:08:49:03.267: GPU5 GPU5 initMiner error: unspecified launch failure
17629:08:49:03.267: GPU3 GPU3 initMiner error: unspecified launch failure
17629:08:49:05.283: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17629:08:49:05.283: main GPUs: 1: 0.000 MH/s (0) 2: 0.000 MH/s (0) 3: 0.000 MH/s (0) 4: 0.000 MH/s (0) 5: 0.000 MH/s (0) 6: 0.000 MH/s (0)
It seem that when all six cards start generating the DAG buffer, the last of them crashes. First, try to increase the virtual memory (page file) size to 32 GB temporarily to be sure that this is not causing the problem. If this doesn't help check the power consumption during the DAG generation. If it is close to the power rating of your PSU, you will have to lower the core clock on (some of) the cards to avoid overloading the PSU during DAG generation.
The shutdown of the miner is also from the start, even with a cold card. My cards never get hotter than 58 degrees. (49-58)
The problem with shuting down appears with and without overclocking.
I will try to re-install the rig soon and see what happens.
Hmm, than this could be a power issue - they usually manifest themselves during DAG generation. How much is the power rating of your PSU (esp. 12V lines)? Other thing to try is to lower the power limit of the cards in Afterburner (or whatever OC software you prefer to use).The problem with shuting down appears with and without overclocking.
I will try to re-install the rig soon and see what happens.
i think my one nvidia based rig is having a similar issue. it's running 2.8c.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
This does seem quite similar but this happens during normal mining and not during DAG generation so it is less likely to be a power issue. Still, could you try to lower the power limit of your cards and see if this fixes the problem? On our test rigs the PSUs are over-provisioned by at least 50-60% so we never see such problems. Even if the PSU(s) should be enough on theory, some GPUs have momentary peaks in their power consumption which can drop the voltage enough to cause a crash.it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
We will also investigate why the program doesn't restart as it should (and as it does in many other cases).
April 09, 2018, 10:17:25 PM
i think my one nvidia based rig is having a similar issue. it's running 2.8c.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
this is what's happening.
normally something like this would just trigger the watchdog, but it crashes in windows and just hangs. so it cant restart itself.
April 09, 2018, 03:55:59 PM
Can anybody tell me why phoenix.exe above 2.7c crashes in 5 seconds when starting on one rig and on my other rig it runs perfect also with latest version.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
add to start.bat file in the end -rmode 1 -nvidia -log 0 -eres 2 -coin eth if u mine ether, save and start, try
Thanks for your advice, but unfortunately phoenix keeps shuting down and don”t restart if something happens.
Some times after 10 times starting Phoernix manualy, it runs untill an autorestart is needed because of some faillure and it says: phoenix.exe isn’t working anymore and shuts down.
I had a similar behaviour one one of my rigs. I finally isolated it to one card running too hot after a while. Check your logs to see if one of the cards shuts itself off near the end of the log. Try reducing the overclocks and see if running a few degrees colder helps. Also check your Pagefile memory. Ensure its set high enough. good luck
The shutdown of the miner is also from the start, even with a cold card. My cards never get hotter than 58 degrees. (49-58)
The problem with shuting down appears with and without overclocking.
I will try to re-install the rig soon and see what happens.
If it is an almost instant no start then could be just bat file or epools settings is incorrect.
Check wallet address, mining worker format, mining url and port. If you have copied it from another mining rig and when you start up it has for example the same worker number from another rig it may just need to be adjusted to be indeed a new worker....
April 09, 2018, 01:07:39 PM
i think my one nvidia based rig is having a similar issue. it's running 2.8c.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
it will run fine for 5-50+hrs, then suddenly it crashes, gets the "unspecified launch failure" error, and doesnt auto-restart. i can see that the watchdog triggered, but then the pheonixminer.exe crashes in windows and it hangs until i manually close it. i usually just reboot the system and it's fine. i run all default parameters except only running the -coin eth command, everything else is defaults.
my AMD based system on 2.8c is rock steady. runs for 300+ hrs and never crashes.
April 09, 2018, 12:11:35 PM
Can anybody tell me why phoenix.exe above 2.7c crashes in 5 seconds when starting on one rig and on my other rig it runs perfect also with latest version.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
add to start.bat file in the end -rmode 1 -nvidia -log 0 -eres 2 -coin eth if u mine ether, save and start, try
Thanks for your advice, but unfortunately phoenix keeps shuting down and don”t restart if something happens.
Some times after 10 times starting Phoernix manualy, it runs untill an autorestart is needed because of some faillure and it says: phoenix.exe isn’t working anymore and shuts down.
I had a similar behaviour one one of my rigs. I finally isolated it to one card running too hot after a while. Check your logs to see if one of the cards shuts itself off near the end of the log. Try reducing the overclocks and see if running a few degrees colder helps. Also check your Pagefile memory. Ensure its set high enough. good luck
The shutdown of the miner is also from the start, even with a cold card. My cards never get hotter than 58 degrees. (49-58)
The problem with shuting down appears with and without overclocking.
I will try to re-install the rig soon and see what happens.
May be too high intensity? (-gt parameter)
April 09, 2018, 11:58:47 AM
Can anybody tell me why phoenix.exe above 2.7c crashes in 5 seconds when starting on one rig and on my other rig it runs perfect also with latest version.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
add to start.bat file in the end -rmode 1 -nvidia -log 0 -eres 2 -coin eth if u mine ether, save and start, try
Thanks for your advice, but unfortunately phoenix keeps shuting down and don”t restart if something happens.
Some times after 10 times starting Phoernix manualy, it runs untill an autorestart is needed because of some faillure and it says: phoenix.exe isn’t working anymore and shuts down.
I had a similar behaviour one one of my rigs. I finally isolated it to one card running too hot after a while. Check your logs to see if one of the cards shuts itself off near the end of the log. Try reducing the overclocks and see if running a few degrees colder helps. Also check your Pagefile memory. Ensure its set high enough. good luck
The shutdown of the miner is also from the start, even with a cold card. My cards never get hotter than 58 degrees. (49-58)
The problem with shuting down appears with and without overclocking.
I will try to re-install the rig soon and see what happens.
April 09, 2018, 11:49:24 AM
Hello phoenixminers, I have a question among the users who have experience with this farmbatchbot download link: https://github.com/Undertrey/FarmWatchBot/releases
have used these with phoenixmniner 2.8.c
please share.
===================================================================================
where is actually phoenixminer version 2.9
===================================================================================
have used these with phoenixmniner 2.8.c
please share.
===================================================================================
where is actually phoenixminer version 2.9
===================================================================================
PM mentioned yesterday they were a few days away from a first release... In teh past he`s been pretty spot on I would estimate by weeks end we see newest alpha version...
April 09, 2018, 11:28:21 AM
Hello phoenixminers, I have a question among the users who have experience with this farmbatchbot download link: https://github.com/Undertrey/FarmWatchBot/releases
have used these with phoenixmniner 2.8.c
please share.
===================================================================================
where is actually phoenixminer version 2.9
===================================================================================
have used these with phoenixmniner 2.8.c
please share.
===================================================================================
where is actually phoenixminer version 2.9
===================================================================================
April 09, 2018, 08:54:24 AM
So far using this miner .. i dont feel my hash been drop so often .. really nice and clean .. so far still trying on the stable side of it ..and power consumption is slighty lesser and more stable ..
Yvmen
Yvmen
April 09, 2018, 04:12:43 AM
Really impressed by this miner! At 1240/2200 with cv/mvddc at 900 I am hashing with my RX580 SE Nitro+ above 31.5mh/s really stable! Incredible, just flawless performance! Best ETH miner out there!
P.S - I am mining on a completely reinstalled rig with the latest AMD drivers, just fyi, do not know if that's helped for the hash increase.
P.S - I am mining on a completely reinstalled rig with the latest AMD drivers, just fyi, do not know if that's helped for the hash increase.
April 08, 2018, 04:33:24 PM
Can anybody tell me why phoenix.exe above 2.7c crashes in 5 seconds when starting on one rig and on my other rig it runs perfect also with latest version.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
add to start.bat file in the end -rmode 1 -nvidia -log 0 -eres 2 -coin eth if u mine ether, save and start, try
Thanks for your advice, but unfortunately phoenix keeps shuting down and don”t restart if something happens.
Some times after 10 times starting Phoernix manualy, it runs untill an autorestart is needed because of some faillure and it says: phoenix.exe isn’t working anymore and shuts down.
I had a similar behaviour one one of my rigs. I finally isolated it to one card running too hot after a while. Check your logs to see if one of the cards shuts itself off near the end of the log. Try reducing the overclocks and see if running a few degrees colder helps. Also check your Pagefile memory. Ensure its set high enough. good luck
April 08, 2018, 03:27:35 PM
Can anybody tell me why phoenix.exe above 2.7c crashes in 5 seconds when starting on one rig and on my other rig it runs perfect also with latest version.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
add to start.bat file in the end -rmode 1 -nvidia -log 0 -eres 2 -coin eth if u mine ether, save and start, try
Thanks for your advice, but unfortunately phoenix keeps shuting down and don”t restart if something happens.
Some times after 10 times starting Phoernix manualy, it runs untill an autorestart is needed because of some faillure and it says: phoenix.exe isn’t working anymore and shuts down.
April 08, 2018, 07:07:32 AM
...
appreciate the time comparing and clear justification, i am looking forward to see 2.9 outperform Claymore.
what i like about PM is that it could maximize my GPU's capability to hash up to 31.2Mhs for 580's which has a difference of .5 Mhs from Claymore.
having 1-2% of stale share is reasonable enough to shift to PM, i am still trying out other settings using PM though.
thanks and appreciate your feedback.
PhoenixMiner 2.9 should be released withing a few days (the internal test results for AMD cards are quite good but we are still tuning up the CUDA kernels).appreciate the time comparing and clear justification, i am looking forward to see 2.9 outperform Claymore.
what i like about PM is that it could maximize my GPU's capability to hash up to 31.2Mhs for 580's which has a difference of .5 Mhs from Claymore.
having 1-2% of stale share is reasonable enough to shift to PM, i am still trying out other settings using PM though.
thanks and appreciate your feedback.
PhoenixMiner I owe you a beer, my mistake in the comment where I suspected that there was a bag in your miner, and it was a MITM attack. Sorry ser.
Thanks a lot, we will drink a Heineken (or three) in your honor 
The SSL will get rid of these attacks, it's a pity that only ehtermine supports it yet - if fact, if it weren't for their initiative, the SSL support wouldn't happen for a long time.Any plans for CryptoNote miner or integration or a seperate miner?
Already answered here (sorry but we don't have more specific answer for now):Any plans for CryptoNote miner or integration, would be great?
Not in the immediate future but in a few months a lot could and probably would change. 
Hi Guys,
Can I specify the logfile name and maximum size (i.e. 75MB)?
Unfortunately not yet, but we will try to add this in 2.9 as it is overdue (it is sitting in our TODO list for at least a month).Can I specify the logfile name and maximum size (i.e. 75MB)?
I have question regarding to stale share:
I located in US, would my stale rate be higher if I connect to EU server than connect to US server?
I've been tested this many times with Claymore in a 24-hour continue mining period.
Connecting to US or EU, I forgot to record all the stale rate, but eth/hour stay nearly identical.
Theoretically, yes because the network latency will be higher. However, these things should be put in perspective. The average time between jobs on ethermine is about 12 seconds, so every 50 ms two-way round trip time increase would increase your stale shares by about 0.4% (50/12000). If you are mining a coin with bigger block time, the stale shares decrease proportionally.I located in US, would my stale rate be higher if I connect to EU server than connect to US server?
I've been tested this many times with Claymore in a 24-hour continue mining period.
Connecting to US or EU, I forgot to record all the stale rate, but eth/hour stay nearly identical.
Also I have another question regarding using -cclock 1150 -mclock 2100 -cvddc 900 -mvddc 900 arguements on RX 580.
I used to be able to use them on claymore prior to blockchain beta driver. But ever since I upgrade to blockchain beta, the setting will no long stay very long. It is able to set them correctly via claymore, after mining for awhile, it will reset to default some the hashrate will drop, power usuage and temperature will go up as result.
Some people mention 18.3.4 driver fix the problem so I can use claymore 11.6 to control OC setting again like before. But I still haven't apply the new AMD driver yet because: 1) It took a lot of time to get driver correctly installed (2~3 hours, most times longer) 2) not sure the new driver is as stable as the old one (My rigs have been running for a month now w/o hang, so I don't really need to do anything to interrupt that streak unil something is broken)
Anyway, can I use -cclock 1150 -mclock 2100 -cvddc 900 -mvddc 900 arguements on RX 580 with Phoenix 2.8c on Blockchain beta driver?
Yes but they will probably be unstable. The ADL support (which is responsible for the overclocking and voltage control) in the beta blockchain drivers is quite broken. Only the 18.x.x drivers fixed most of its problems. If you want to remain with the blockchain drivers the best way is to use MSI Afterburner or something similar to control the clocks and voltages.I used to be able to use them on claymore prior to blockchain beta driver. But ever since I upgrade to blockchain beta, the setting will no long stay very long. It is able to set them correctly via claymore, after mining for awhile, it will reset to default some the hashrate will drop, power usuage and temperature will go up as result.
Some people mention 18.3.4 driver fix the problem so I can use claymore 11.6 to control OC setting again like before. But I still haven't apply the new AMD driver yet because: 1) It took a lot of time to get driver correctly installed (2~3 hours, most times longer) 2) not sure the new driver is as stable as the old one (My rigs have been running for a month now w/o hang, so I don't really need to do anything to interrupt that streak unil something is broken)
Anyway, can I use -cclock 1150 -mclock 2100 -cvddc 900 -mvddc 900 arguements on RX 580 with Phoenix 2.8c on Blockchain beta driver?
Hi Phoenix, FWIW, here's a small "potential bug" I found:
I use Monitorig to keep track of all my rigs:
https://bitcointalksearch.org/topic/windows-mining-monitoring-tool-v2-beta-open-beta-1448855
Everything goes fine, except for single GPU rig, where for some weird reason Monitorig won't pick it up.
I'd be inclined to 'blame' Monitorig, but here's the catch: I switched all single GPU rigs back to Claymore, and they worked fine!
My guess: it has something to do with your log file format, because that's how Monitorig output the information.
***If you could please change/mimic Claymore's in your future updates, that'd be great!***
Thanks and keep up the good work! I have to switch back to Claymore for now for single GPU rigs though
Unfortunately, this is quite unlikely to happen because: a) we would be unable to add new statistics and information and we have such plans; and b) a lot of users actually like our console output better, so we would be giving up one of our advantages. Hopefully, in time most remote control and monitoring applications will support PhoenixMiner fully (there are a lot that support us already but not all).I use Monitorig to keep track of all my rigs:
https://bitcointalksearch.org/topic/windows-mining-monitoring-tool-v2-beta-open-beta-1448855
Everything goes fine, except for single GPU rig, where for some weird reason Monitorig won't pick it up.
I'd be inclined to 'blame' Monitorig, but here's the catch: I switched all single GPU rigs back to Claymore, and they worked fine!
My guess: it has something to do with your log file format, because that's how Monitorig output the information.
***If you could please change/mimic Claymore's in your future updates, that'd be great!***
Thanks and keep up the good work! I have to switch back to Claymore for now for single GPU rigs though
Hi there
I added one more Ellesmere card to my rig (4 now) and Phoenix Miner stopped controlling fan speeds.
-tt and -fanmin stopped working.
I tried to use only one value or assigning a value to each card, but it won't work.
Claymore's works as usual.
Any ideas?
If you are using the blockchain drivers, all bets are off. If you are using 18.x.x drivers, please tell us the model of the card that is giving you problems (and the version of the driver).I added one more Ellesmere card to my rig (4 now) and Phoenix Miner stopped controlling fan speeds.
-tt and -fanmin stopped working.
I tried to use only one value or assigning a value to each card, but it won't work.
Claymore's works as usual.
Any ideas?
HI Dev,
can you put genom coin to the devfee list to avoid dag switch?
Will try to add it in the next release.can you put genom coin to the devfee list to avoid dag switch?
Can someone help to resolve this error?
I had internet connection problem and after connetion went up again, the miner did not connect again.. I had to restart miner.
Is there any resolve for this issue? Why is phoenix connection to port 4444 nad not 5555 ssl?
You have forgotten to change the wallet address from the default YourWallet in the example command lines. Ethermine doesn't like the invalid ethash address (obviously YourWallet is not a valid ethash address) and disconnects with error "Invalid user provided". After three unsuccessful attempts, the miner switches to the next pool, which is not using SSL. To fix the problem, paste your real ethash address into the command line (or in the epools.txt file).I had internet connection problem and after connetion went up again, the miner did not connect again.. I had to restart miner.
Is there any resolve for this issue? Why is phoenix connection to port 4444 nad not 5555 ssl?
Code:
17628:09:32:51.214: unkn Eth: Can't resolve host ssl://eu1.ethermine.org:5555
17628:09:32:51.214: unkn Eth: Giving up after 3 retries, switching to next pool
17628:09:32:51.214: unkn Eth: Reconnecting in 20 seconds...
17628:09:32:55.514: GPU2 Unable to submit share - pool disconnected
17628:09:33:04.989: GPU3 Unable to submit share - pool disconnected
17628:09:33:09.973: GPU4 Unable to submit share - pool disconnected
17628:09:33:11.222: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
17628:09:33:11.256: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (188.165.239.100)
17628:09:33:11.256: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-O8QC2F8"]}
17628:09:33:11.277: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
17628:09:33:18.794: main GPU1: 54C 72%, GPU2: 54C 56%, GPU3: 49C 49%, GPU4: 54C 64%, GPU5: 57C 64%, GPU6: 43C 70%
17628:09:33:21.952: GPU2 Unable to submit share - pool disconnected
17628:09:33:43.568: GPU5 Unable to submit share - pool disconnected
17628:09:33:46.704: main GPU1: 55C 73%, GPU2: 54C 56%, GPU3: 49C 48%, GPU4: 54C 64%, GPU5: 58C 64%, GPU6: 43C 70%
17628:09:33:55.839: GPU4 Unable to submit share - pool disconnected
17628:09:34:04.807: GPU4 Unable to submit share - pool disconnected
17628:09:34:09.682: GPU5 Unable to submit share - pool disconnected
17628:09:34:11.873: GPU5 Unable to submit share - pool disconnected
17628:09:34:14.941: main GPU1: 54C 73%, GPU2: 54C 56%, GPU3: 49C 48%, GPU4: 55C 64%, GPU5: 58C 64%, GPU6: 42C 70%
17628:09:34:30.878: GPU3 Unable to submit share - pool disconnected
17628:09:34:42.992: main GPU1: 54C 73%, GPU2: 54C 56%, GPU3: 49C 47%, GPU4: 54C 64%, GPU5: 58C 64%, GPU6: 42C 70%
17628:09:34:48.490: GPU3 Unable to submit share - pool disconnected
17628:09:34:51.279: eths Eth: Connection closed by the pool
17628:09:34:51.279: eths Eth: Reconnecting in 20 seconds...
17628:09:35:11.097: main GPU1: 55C 73%, GPU2: 54C 56%, GPU3: 49C 47%, GPU4: 54C 64%, GPU5: 58C 64%, GPU6: 42C 70%
17628:09:35:11.285: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
17628:09:35:11.308: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (188.165.226.213)
17628:09:35:11.308: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-O8QC2F8"]}
17628:09:35:11.329: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
17628:09:35:22.780: GPU6 Unable to submit share - pool disconnected
17628:09:35:39.343: main GPU1: 54C 73%, GPU2: 54C 57%, GPU3: 49C 47%, GPU4: 54C 64%, GPU5: 57C 64%, GPU6: 42C 70%
17628:09:36:02.016: GPU4 Unable to submit share - pool disconnected
17628:09:32:51.214: unkn Eth: Giving up after 3 retries, switching to next pool
17628:09:32:51.214: unkn Eth: Reconnecting in 20 seconds...
17628:09:32:55.514: GPU2 Unable to submit share - pool disconnected
17628:09:33:04.989: GPU3 Unable to submit share - pool disconnected
17628:09:33:09.973: GPU4 Unable to submit share - pool disconnected
17628:09:33:11.222: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
17628:09:33:11.256: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (188.165.239.100)
17628:09:33:11.256: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-O8QC2F8"]}
17628:09:33:11.277: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
17628:09:33:18.794: main GPU1: 54C 72%, GPU2: 54C 56%, GPU3: 49C 49%, GPU4: 54C 64%, GPU5: 57C 64%, GPU6: 43C 70%
17628:09:33:21.952: GPU2 Unable to submit share - pool disconnected
17628:09:33:43.568: GPU5 Unable to submit share - pool disconnected
17628:09:33:46.704: main GPU1: 55C 73%, GPU2: 54C 56%, GPU3: 49C 48%, GPU4: 54C 64%, GPU5: 58C 64%, GPU6: 43C 70%
17628:09:33:55.839: GPU4 Unable to submit share - pool disconnected
17628:09:34:04.807: GPU4 Unable to submit share - pool disconnected
17628:09:34:09.682: GPU5 Unable to submit share - pool disconnected
17628:09:34:11.873: GPU5 Unable to submit share - pool disconnected
17628:09:34:14.941: main GPU1: 54C 73%, GPU2: 54C 56%, GPU3: 49C 48%, GPU4: 55C 64%, GPU5: 58C 64%, GPU6: 42C 70%
17628:09:34:30.878: GPU3 Unable to submit share - pool disconnected
17628:09:34:42.992: main GPU1: 54C 73%, GPU2: 54C 56%, GPU3: 49C 47%, GPU4: 54C 64%, GPU5: 58C 64%, GPU6: 42C 70%
17628:09:34:48.490: GPU3 Unable to submit share - pool disconnected
17628:09:34:51.279: eths Eth: Connection closed by the pool
17628:09:34:51.279: eths Eth: Reconnecting in 20 seconds...
17628:09:35:11.097: main GPU1: 55C 73%, GPU2: 54C 56%, GPU3: 49C 47%, GPU4: 54C 64%, GPU5: 58C 64%, GPU6: 42C 70%
17628:09:35:11.285: unkn Eth: Connecting to ethash pool eu1.ethermine.org:4444 (proto: EthProxy)
17628:09:35:11.308: eths Eth: Connected to ethash pool eu1.ethermine.org:4444 (188.165.226.213)
17628:09:35:11.308: eths Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"eth1.0","params":["YourWallet.DESKTOP-O8QC2F8"]}
17628:09:35:11.329: eths Eth: Received: {"id":999,"jsonrpc": "2.0","result": false,"error": "Invalid user provided"}
17628:09:35:22.780: GPU6 Unable to submit share - pool disconnected
17628:09:35:39.343: main GPU1: 54C 73%, GPU2: 54C 57%, GPU3: 49C 47%, GPU4: 54C 64%, GPU5: 57C 64%, GPU6: 42C 70%
17628:09:36:02.016: GPU4 Unable to submit share - pool disconnected
not sure if already mentioned but there is an typo when starting your miner
Oops, thanks for catching this 
I found a bug: if I start Claymore CryptoNight with some card and then start PhoenixMiner with all the other card then Phoenix crash...
I tried then to start first Phoenix and then Claymore and I saw the problem: I was using the same port (3333)... opsss I forgot to change it!
So if the port 3333 is busy PhoenixMiner crash.
I have also a request: can you add to the line of server name also the time when the connection occurred (or a counter)? I ask it because some time my internet connection go down and then up and I need to search on the log if this happened
*** 0:50 ***************************************************
Eth: Mining ETH on eth-eu1.nanopool.org:9999 from 13:00:00 07/04/2018
Eth speed: 183.484 MH/s, shares: 57/0/0, time: 0:50
I'm using your software from a few months and I'm very happy... I'm waiting for version 2.9!
Thank you for using PhoenixMiner! We will add the time and date as requested. As for the second problem, we have tested in such scenario and it shouldn't crash but print an error message. We will investigate further and fix the problem in the next release.I tried then to start first Phoenix and then Claymore and I saw the problem: I was using the same port (3333)... opsss I forgot to change it!
So if the port 3333 is busy PhoenixMiner crash.
I have also a request: can you add to the line of server name also the time when the connection occurred (or a counter)? I ask it because some time my internet connection go down and then up and I need to search on the log if this happened
*** 0:50 ***************************************************
Eth: Mining ETH on eth-eu1.nanopool.org:9999 from 13:00:00 07/04/2018
Eth speed: 183.484 MH/s, shares: 57/0/0, time: 0:50
I'm using your software from a few months and I'm very happy... I'm waiting for version 2.9!
17617:12:22:59.708: main Phoneix Miner 2.8b Windows/msvc - Release
17617:12:22:59.708: main Cmd line:
17617:12:22:59.708: main config.txt: -pool eu1-etc.ethermine.org:4444 -pool2 us1-etc.ethermine.org:4444 -wal 0xd07e049700388d961068b92e28a9a86064b67986.letjen2 -clkernel 2 -amd
17617:12:23:00.302: main Available GPUs for mining:
17617:12:23:00.302: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.330: main ADL library initialized
always stuck like that. From v6 to v8b, how to fix it? Let me know, tk u
17617:12:22:59.708: main Cmd line:
17617:12:22:59.708: main config.txt: -pool eu1-etc.ethermine.org:4444 -pool2 us1-etc.ethermine.org:4444 -wal 0xd07e049700388d961068b92e28a9a86064b67986.letjen2 -clkernel 2 -amd
17617:12:23:00.302: main Available GPUs for mining:
17617:12:23:00.302: main GPU1: Radeon RX 570 Series (pcie 1), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU2: Radeon RX 570 Series (pcie 2), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU3: Radeon RX 570 Series (pcie 3), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU4: Radeon RX 570 Series (pcie 4), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU5: Radeon RX 570 Series (pcie 5), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.302: main GPU6: Radeon RX 570 Series (pcie 6), OpenCL 2.0, 8 GB VRAM, 32 CUs
17617:12:23:00.330: main ADL library initialized
always stuck like that. From v6 to v8b, how to fix it? Let me know, tk u
I still have the same problem when i install a new windows version i have 7 rigs 3 of them don't want to work with phoenix after a new windows instalation and the other 4 works fine tell me please where is the exactly problem and how to bypass it and if it need install some package tell me please
Waiting for your reply devs
PhoenixMiner we are waiting 2.9, any news?
Will be ready in a few days. We want to be sure that everything works fine as there are a lot of changes in the kernels.Can anybody tell me why phoenix.exe above 2.7c crashes in 5 seconds when starting on one rig and on my other rig it runs perfect also with latest version.
Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
Please send us the log file and check if the miner shows "Debugger detected" error before crashing (the "Debugger detected" error will not be printed in the log file). If the console window closes fast after the program crashes, please put a pause command after the line that starts PhoenixMiner in your .bat file (or use the start_miner.bat file that is in the PhoenixMiner .zip file, which already has a pause command).Both rigs are identical with 6 gtx1070 8gb cards each and windows 10.
I didn’t read anything here about this problem.
If the error is "Debugger detected" try to add -nvidia to your command line.
This is my problem and i added -amd too
http://prntscr.com/j2gt6n
Please i want to bypass this problem
Thanks in advance
Jump to: