Quote from: Sandro6666 on April 08, 2018, 06:59:01 AM

Quote from: Sandro6666 on April 07, 2018, 06:37:04 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 didnt 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).

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]
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.

Quote from: Sandro6666 on April 09, 2018, 04:58:47 PM

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).

Quote from: gsrcrxsi314 on April 09, 2018, 06: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.

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).