 Show Posts
|
|
Pages: [1] 2 »
|
|
Do any of you use ethOS in combination with nvidia gtx 1070 series and PhonixMiner.
What kind of hashrate do you have?
If possible, also write down your settings. I'm thinking of installing ethos from windows.
Thank you to everyone who will give concrete answers
|
|
|
|
Dear Phoenix.
DAG splitting can fix Nvidia 1070-1080 series problem? Have you tried this?
Thanks.
Love this idea if it's technically possible I agree with this idea. I hope to see this post @PhonixMiner. Edit: Ethash DAG vs hashrate    |
|
|
|
|
@PhoenixMiner
will be some improvements for the Nvidia GTX 10x0 as well?
|
|
|
|
|
I try new version PM 5.2a on my gtx 1070 rig. So far I don't notice any changes compared to the version 5.0e
|
|
|
|
2 days ago hashrate droped on my miner 10mh/each nvidia gpu.
settings are the same .
w 7 os
any ideea?
Go to Win 10 pro I have a same problem and I have win 10 pro GPUs 1070 Any idea why do this? Use driver from the time the card was produced I have drivers 388.43 My rig working normally last 2 years. Last 3 months I have “big” problems with droped hasrate. 194,6 (hasrate last 2 years) now is 184,1 (last 3 months) IDK what going wrong Last 2 years there was many changes. And in mining too. DAG size all time growing, computing algorithms changes in drivers... Miners updates to work with new drivers, not older. Don't you think you need to try update your drivers before all?.. happens to me the same on p106 and GTX1070, maybe they are already worn out, on rx 470 have same hashrate like 1 day works now 2 years + nvidia rigs with p106 works in 2017 210Mhs, 25.2/pcs gtx1070 32Mhx now 21-22 and 25-27Mhs i use driver V38253. When i restart miner works 185 then drop to 175Mhs long time i cant OC cards like i have before It's exactly the same with me. Same I cant OC cards like before. Maybe they are worn out. What are the alternatives to gtx 1070? |
|
|
|
2 days ago hashrate droped on my miner 10mh/each nvidia gpu.
settings are the same .
w 7 os
any ideea?
Go to Win 10 pro I have a same problem and I have win 10 pro GPUs 1070 Any idea why do this? Use driver from the time the card was produced I have drivers 388.43 My rig working normally last 2 years. Last 3 months I have “big” problems with droped hasrate. 194,6 (hasrate last 2 years) now is 184,1 (last 3 months) IDK what going wrong |
|
|
|
2 days ago hashrate droped on my miner 10mh/each nvidia gpu.
settings are the same .
w 7 os
any ideea?
Go to Win 10 pro I have a same problem and I have win 10 pro GPUs 1070 Any idea why do this? |
|
|
|
I have win 10 and 6x 1070 GPUs, and i using last PM version Hasrate contanstly falling. Until today I using nvidia drivers 388.43 today I change (update) drivers to 442.59. Hasrate is still falling. My OC settings are  Current PM settings: PhoenixMiner.exe -pool eth-eu1.nanopool.org:9999 -pool2 eth-eu2.nanopool.org:9999 -wal ETHaddress.rig01/mymail@mymail.me -epsw x -ftime 10 -rmode 2 -lidag 2 -wdog 1 -astats 1 -proto 2 -logsmaxsize 1 Does anyone have any idea why hasrate falling. Last 3 maybe 4 months I have avg. hasrate aournt 187 to 189 MH/s 6 months ago constantly 194.7 MH/s. Tnx for all you answers and tips. |
|
|
|
Anyone else getting a huge jump in stale shares. I normally only get 1% stale but just recently it jumped to 6% with all the same settings, OC and UV. Anyone else experience a bit jump?
I also noticed that there are many stales shares last day maybe 2 days. And IDK I have 1070 GPUs and hasrate drops for 5-6 MH/s per rig. |
|
|
|
|
I trt this new PM 4.5 beta on nvidia rig and works perfect for now. Great job
|
|
|
|
3.5a won't start at all, 3.0c working perfectly since release
Original PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001 Try this PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 - ewal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001 |
|
|
|
Hi,
have maybe someone .bat file for automatic relaunch PM if miner crashed or stopped working?
Just a few minutes to take a look on the first post and you will find out. It's that simple... I saw this -rmode <n> Selects the restart mode when a GPU crashes or freezes: 0: disabled - miner will shut down instead of restarting 1: restart with the same command line options - this is the default 2: reboot (shut down miner and execute reboot.bat) but when I download PM not include reboot.bat file. You can just copy your start_miner.bat and rename it to reboot.bat. Same parameters  Ok I will try this advice, I hope to will be working this 4play, If you want to restart your rig you should use -rmode 2 and to create a reboot.bat file and put this line command "shutdown /r /t 5 /f". Also, you need to disable windows error reporting, if you search a few posts / pages back (page 115, post #2291) you will find some links and a bat file for tweaks. Regards This is my reboot file REM
REM Example bat file for starting PhoenixMiner.exe to mine ETH
REM
shutdown /r /t 5 /f
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
REM IMPORTANT: Replace the ETH address with your own ETH wallet address in the -wal option (Rig001 is the name of the rig)
PhoenixMiner.exe -pool eth-eu1.nanopool.org:9999 -pool2 eth-eu2.nanopool.org:9999 -ewal ethadress.rig01/mymail@gmail.com -epsw x -ftime 10 -rmode 2 -lidag 2 -wdog 1 -nvidia
pause I hope to this correct It's enough if you put only "shutdown /r /t 5 /f" command (without comma) in your reboot.bat file (and of course...to have your reboot.bat file in the same directory with miner files and again....disable windows error reporting). You can test if you want ... try to OC a GPU a little bit more just to have an error. 1000x times tnx its working. Really tnx a lot |
|
|
|
Hi,
have maybe someone .bat file for automatic relaunch PM if miner crashed or stopped working?
Just a few minutes to take a look on the first post and you will find out. It's that simple... I saw this -rmode <n> Selects the restart mode when a GPU crashes or freezes: 0: disabled - miner will shut down instead of restarting 1: restart with the same command line options - this is the default 2: reboot (shut down miner and execute reboot.bat) but when I download PM not include reboot.bat file. You can just copy your start_miner.bat and rename it to reboot.bat. Same parameters Ok I will try this advice, I hope to will be working this 4play, If you want to restart your rig you should use -rmode 2 and to create a reboot.bat file and put this line command "shutdown /r /t 5 /f". Also, you need to disable windows error reporting, if you search a few posts / pages back (page 115, post #2291) you will find some links and a bat file for tweaks. Regards This is my reboot file REM
REM Example bat file for starting PhoenixMiner.exe to mine ETH
REM
shutdown /r /t 5 /f
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
REM IMPORTANT: Replace the ETH address with your own ETH wallet address in the -wal option (Rig001 is the name of the rig)
PhoenixMiner.exe -pool eth-eu1.nanopool.org:9999 -pool2 eth-eu2.nanopool.org:9999 -ewal ethadress.rig01/mymail@gmail.com -epsw x -ftime 10 -rmode 2 -lidag 2 -wdog 1 -nvidia
pause I hope to this correct |
|
|
|
Hi,
have maybe someone .bat file for automatic relaunch PM if miner crashed or stopped working?
Just a few minutes to take a look on the first post and you will find out. It's that simple... I saw this -rmode <n> Selects the restart mode when a GPU crashes or freezes: 0: disabled - miner will shut down instead of restarting 1: restart with the same command line options - this is the default 2: reboot (shut down miner and execute reboot.bat) but when I download PM not include reboot.bat file. You can just copy your start_miner.bat and rename it to reboot.bat. Same parameters Ok I will try this advice, I hope to will be working this |
|
|
|
Hi,
have maybe someone .bat file for automatic relaunch PM if miner crashed or stopped working?
Just a few minutes to take a look on the first post and you will find out. It's that simple... I saw this -rmode <n> Selects the restart mode when a GPU crashes or freezes: 0: disabled - miner will shut down instead of restarting 1: restart with the same command line options - this is the default 2: reboot (shut down miner and execute reboot.bat) but when I download PM not include reboot.bat file. |
|
|
|
|
Hi,
have maybe someone .bat file for automatic relaunch PM if miner crashed or stopped working?
|
|
|
|
I using PM 3.0c and every 5 sometimes 6 days PM stop working. What happend and how to fix this? Have maybe someone .bat file for auto restar/reboot PM if PB stop working? 2018.07.26:00:42:06.959: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xda40f35db43beeb3a7e6b66304068bbc0ca9ef3c25c4a8d68dad6a7de14835f0","0x0565d880e378b22250f35f260bac49983734114a9d338b7d7bacea1985c67dd4","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.07.26:00:42:06.959: eths Eth: New job #da40f35d from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.07.26:00:42:07.210: GPU3 GPU3: Starting up... (0)
2018.07.26:00:42:07.210: GPU3 Eth: Generating light cache for epoch #201
2018.07.26:00:42:07.370: GPU2 GPU2: Starting up... (0)
2018.07.26:00:42:07.396: GPU4 GPU4: Starting up... (0)
2018.07.26:00:42:07.396: GPU5 GPU5: Starting up... (0)
2018.07.26:00:42:07.422: GPU1 GPU1: Starting up... (0)
2018.07.26:00:42:07.429: GPU6 GPU6: Starting up... (0)
2018.07.26:00:42:10.009: GPU6 GPU6: Generating DAG for epoch #201
2018.07.26:00:42:10.009: GPU5 GPU5: Generating DAG for epoch #201
2018.07.26:00:42:10.010: GPU3 GPU3: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU4 GPU4: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU2 GPU2: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU1 GPU1: Generating DAG for epoch #201
2018.07.26:00:42:11.238: main Eth speed: 0.000 MH/s, shares: 3574/0/22, time: 52:09
2018.07.26:00:42:11.238: main GPUs: 1: 0.000 MH/s (582) 2: 0.000 MH/s (595) 3: 0.000 MH/s (591) 4: 0.000 MH/s (596) 5: 0.000 MH/s (592) 6: 0.000 MH/s (618/22)
2018.07.26:00:42:11.511: GPU5 GPU5: DAG 19%
2018.07.26:00:42:11.515: GPU2 GPU2: DAG 19%
2018.07.26:00:42:11.515: GPU3 GPU3: DAG 19%
2018.07.26:00:42:11.518: GPU4 GPU4: DAG 19%
2018.07.26:00:42:11.528: GPU6 GPU6: DAG 19%
2018.07.26:00:42:12.519: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.07.26:00:42:12.546: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xda40f35db43beeb3a7e6b66304068bbc0ca9ef3c25c4a8d68dad6a7de14835f0","0x0565d880e378b22250f35f260bac49983734114a9d338b7d7bacea1985c67dd4","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.07.26:00:42:13.011: GPU5 GPU5: DAG 41%
2018.07.26:00:42:13.036: GPU6 GPU6: DAG 41%
2018.07.26:00:42:13.223: GPU3 GPU3: DAG 44%
2018.07.26:00:42:13.225: GPU2 GPU2: DAG 44%
2018.07.26:00:42:13.230: GPU4 GPU4: DAG 44%
2018.07.26:00:42:13.698: GPU1 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.700: GPU1 GPU1 initMiner error: unspecified launch failure
2018.07.26:00:42:13.711: GPU3 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.711: GPU3 GPU3 initMiner error: unspecified launch failure
2018.07.26:00:42:13.711: GPU4 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.711: GPU4 GPU4 initMiner error: unspecified launch failure
2018.07.26:00:42:13.785: GPU6 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.785: GPU6 GPU6 initMiner error: unspecified launch failure
2018.07.26:00:42:13.801: GPU2 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.801: GPU5 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.801: GPU2 GPU2 initMiner error: unspecified launch failure
2018.07.26:00:42:13.801: GPU5 GPU5 initMiner error: unspecified launch failure
I would mitigate this problem using the option -lidag: -lidag <n> Slow down DAG generation to avoid crashes when switching DAG epochs (0-3, default: 0 - fastest, 3 - slowest). You may specify this option per-GPU. Currently the option works only on AMD cards So try with "-lidag 2". From your above logs the problem with the gpus happened during the DAG generation. DAG generation is more intensive compared to normal hashing and when your OC is on the limit, it will crash the GPUs. Tnx for advice. I will try this. Thx a lot |
|
|
|
Many people have this problem, i think they all clock ther nvidia cards to high. I had the same problem in the past, makes no errors for a couple of days and then restarts with the same error. I clock 1 of my cards lower, now it works perfect.
The problem is, on nvidia cards we can not see hardware errors in hwinfo like we can see it on amd. this is my opinion and i working with over 100 gpu´s.
I see you have 22 incorrect shares on gpu 6, another indication of excessive overclocking.
Tnx for your answer. I know for GPU 6 I have still problem with this GPU. This GPU 6 it's already less OC if I compare other GPUs on this rig. Maybe it would make sense this GPU 6 still to drop OC settings? |
|
|
|
I using PM 3.0c and every 5 sometimes 6 days PM stop working. What happend and how to fix this? Have maybe someone .bat file for auto restar/reboot PM if PB stop working? 2018.07.26:00:42:06.959: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xda40f35db43beeb3a7e6b66304068bbc0ca9ef3c25c4a8d68dad6a7de14835f0","0x0565d880e378b22250f35f260bac49983734114a9d338b7d7bacea1985c67dd4","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.07.26:00:42:06.959: eths Eth: New job #da40f35d from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.07.26:00:42:07.210: GPU3 GPU3: Starting up... (0)
2018.07.26:00:42:07.210: GPU3 Eth: Generating light cache for epoch #201
2018.07.26:00:42:07.370: GPU2 GPU2: Starting up... (0)
2018.07.26:00:42:07.396: GPU4 GPU4: Starting up... (0)
2018.07.26:00:42:07.396: GPU5 GPU5: Starting up... (0)
2018.07.26:00:42:07.422: GPU1 GPU1: Starting up... (0)
2018.07.26:00:42:07.429: GPU6 GPU6: Starting up... (0)
2018.07.26:00:42:10.009: GPU6 GPU6: Generating DAG for epoch #201
2018.07.26:00:42:10.009: GPU5 GPU5: Generating DAG for epoch #201
2018.07.26:00:42:10.010: GPU3 GPU3: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU4 GPU4: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU2 GPU2: Generating DAG for epoch #201
2018.07.26:00:42:10.011: GPU1 GPU1: Generating DAG for epoch #201
2018.07.26:00:42:11.238: main Eth speed: 0.000 MH/s, shares: 3574/0/22, time: 52:09
2018.07.26:00:42:11.238: main GPUs: 1: 0.000 MH/s (582) 2: 0.000 MH/s (595) 3: 0.000 MH/s (591) 4: 0.000 MH/s (596) 5: 0.000 MH/s (592) 6: 0.000 MH/s (618/22)
2018.07.26:00:42:11.511: GPU5 GPU5: DAG 19%
2018.07.26:00:42:11.515: GPU2 GPU2: DAG 19%
2018.07.26:00:42:11.515: GPU3 GPU3: DAG 19%
2018.07.26:00:42:11.518: GPU4 GPU4: DAG 19%
2018.07.26:00:42:11.528: GPU6 GPU6: DAG 19%
2018.07.26:00:42:12.519: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}
2018.07.26:00:42:12.546: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0xda40f35db43beeb3a7e6b66304068bbc0ca9ef3c25c4a8d68dad6a7de14835f0","0x0565d880e378b22250f35f260bac49983734114a9d338b7d7bacea1985c67dd4","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.07.26:00:42:13.011: GPU5 GPU5: DAG 41%
2018.07.26:00:42:13.036: GPU6 GPU6: DAG 41%
2018.07.26:00:42:13.223: GPU3 GPU3: DAG 44%
2018.07.26:00:42:13.225: GPU2 GPU2: DAG 44%
2018.07.26:00:42:13.230: GPU4 GPU4: DAG 44%
2018.07.26:00:42:13.698: GPU1 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.700: GPU1 GPU1 initMiner error: unspecified launch failure
2018.07.26:00:42:13.711: GPU3 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.711: GPU3 GPU3 initMiner error: unspecified launch failure
2018.07.26:00:42:13.711: GPU4 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.711: GPU4 GPU4 initMiner error: unspecified launch failure
2018.07.26:00:42:13.785: GPU6 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.785: GPU6 GPU6 initMiner error: unspecified launch failure
2018.07.26:00:42:13.801: GPU2 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.801: GPU5 CUDART error in CudaProgram.cu:188 : unspecified launch failure (4)
2018.07.26:00:42:13.801: GPU2 GPU2 initMiner error: unspecified launch failure
2018.07.26:00:42:13.801: GPU5 GPU5 initMiner error: unspecified launch failure
|
|
|
|
|
