Latest posts of: cmd

Show Posts
Pages: [1]

Alternate cryptocurrencies / Mining (Altcoins) / Re: GMiner v1.97 Equihash/CuckooCycle/Ethash/Eaglesong/Blake2s/Handshake

on: February 21, 2020, 02:09:40 AM

Any response to the question asked a few weeks ago as to why Difficulty in GMiner solo mining BeamHashII is about 2x Difficulty of network?

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 4.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

on: August 14, 2019, 01:51:14 AM

Quote from: jetwalsh on August 14, 2019, 12:01:03 AM I’m running 7x Nvidia 1070s...rock solid at currently 100 hours. What is your virtual memory size? 65536-98304 mb. It's not a virtual memory issue. 1070's have 8gb of memory. I didn't feel like trying to fight the inevitable so I just BIOS flashed my P104's to 8gb with nvflash.... Problem solved.

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 4.5c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

on: August 13, 2019, 02:08:57 PM

Having issue with 4gb Nvidia cards in windows not having enough memory to create the DAG. Its not a virtual memory error

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 4.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

on: April 07, 2019, 03:32:46 PM

Quote from: PhoenixMiner on December 26, 2017, 07:14:26 AM Added parameter to enable or disable driver-specific optimizations on Nvidia GPUs. Use -nvdo 1 (the default is 0) to enable the optimizations. This won't change hashrate (or will change it only slightly) but can make the cards more stable depending on the concrete Nvidia driver. What driver version or versions was this coded for? What are the driver settings the optimizations affect if you dont mind dropping some knowledge? What ever they are they seem to work for stability.

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 4.0b: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

on: January 17, 2019, 11:29:47 PM

I started getting crash on dag creation on one rig some time in the middle of the night running Phoenix Miner 2.8... Now today all my rigs running 2.8 crash... Would think it's something that Windows pushed, even tho I have Windows Update disabled... Hopefully someone can figure it out...

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 3.0c: fastest Ethereum/Ethash miner with lowest devfee (Windows)

on: July 15, 2018, 05:39:05 PM

@ PhoenixMiner I second the request to reverse engineer OhGodACompany's Ethlargment Pill.... If you follow Kristy, she's stated that the software was card locked for the 1080 & 1080ti but works with the 1060 and 1070. From what I've put together if someone figures out how to remove the card lock it would detect the 10 series card and set mem timings appropriately (this maybe incorrect info) but regardless it would show how to inject mem timings without flashing the cards with a SPI programmer & pomona clip. She's under a NDA agreement for the software and from my understanding, cant release it for the 1060 and 1070 until someone else reverse engineers and releases it with or without dev fee. No matter how you look at it it would give you more hashrate on your dev fee and help us compete with what ever FPGA's are out there on ETH and the E3 that's about to ship. Wolf0 aka OhGodAPet already penetrated your miner to take a look earlier in this thread when Claymore accused you of stealing his kernels, so I think its only fair you open it up to take a look if you haven't already...

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)

on: June 08, 2018, 01:32:06 AM

Is anyone else having a issue with reboot.bat not executing when miner crashes?

I've only been having this problem with my 9 card Zotac GTX 1070 AMP Extreme Rig.

Ive been running Phoenix 2.6 up until last week because I had the same problem with the reboot.bat not executing with 2.9e.

I'd say >75% of the time the reboot.bat executes. It makes no sense to me why it gets hung up every once in a while.

With 2.9e it would hang on the windows reboot screen.

Now with 3.0 it hangs on the miner and says "Hit any key to continue".

Log of when 1070 rig crashed and would not execute reboot.bat

Code:

2018.06.07:12:26:08.469: main GPU1: 61C 36%, GPU2: 62C 33%, GPU3: 65C 50%, GPU4: 60C 20%, GPU5: 64C 41%, GPU6: 61C 34%, GPU7: 63C 38%, GPU8: 62C 33%, GPU9: 62C 35%
2018.06.07:12:26:09.282: main Eth speed: 300.204 MH/s, shares: 2537/4/10, time: 23:58
2018.06.07:12:26:09.282: main GPUs: 1: 33.616 MH/s (272) 2: 33.204 MH/s (296) 3: 33.895 MH/s (283) 4: 32.512 MH/s (283) 5: 33.382 MH/s (271/4) 6: 33.917 MH/s (297/6) 7: 34.196 MH/s (304) 8: 31.658 MH/s (251) 9: 33.825 MH/s (284)
2018.06.07:12:26:14.015: GPU9 CUDA error in CudaProgram.cu:329 : unknown error (999)
2018.06.07:12:26:14.015: GPU9 GPU9 search error: unknown error
2018.06.07:12:26:14.030: GPU5 CUDA error in CudaProgram.cu:329 : unknown error (999)
2018.06.07:12:26:14.030: GPU5 GPU5 search error: unknown error
2018.06.07:12:26:14.039: GPU7 CUDA error in CudaProgram.cu:329 : unknown error (999)
2018.06.07:12:26:14.039: GPU7 GPU7 search error: unknown error
2018.06.07:12:26:14.046: GPU6 CUDA error in CudaProgram.cu:329 : unknown error (999)
2018.06.07:12:26:14.046: GPU6 GPU6 search error: unknown error
2018.06.07:12:26:14.062: GPU8 CUDA error in CudaProgram.cu:329 : unknown error (999)
2018.06.07:12:26:14.062: GPU8 GPU8 search error: unknown error
2018.06.07:12:26:14.077: GPU3 CUDA error in CudaProgram.cu:329 : unknown error (999)
2018.06.07:12:26:14.077: GPU3 GPU3 search error: unknown error
2018.06.07:12:26:14.109: GPU2 CUDA error in CudaProgram.cu:329 : unknown error (999)
2018.06.07:12:26:14.109: GPU2 GPU2 search error: unknown error
2018.06.07:12:26:14.109: GPU1 CUDA error in CudaProgram.cu:329 : unknown error (999)
2018.06.07:12:26:14.109: GPU1 GPU1 search error: unknown error
2018.06.07:12:26:14.124: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.06.07:12:26:14.124: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x11ed0298","0xa003d0ed7d6377ff81b08aaf0973061c1b53b7d7878871632b970bef323b56c9"]}

2018.06.07:12:26:14.185: GPU4 CUDA error in CudaProgram.cu:329 : unknown error (999)
2018.06.07:12:26:14.185: GPU4 GPU4 search error: unknown error
2018.06.07:12:26:14.277: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x25b1d008a094b85558eadd5a166e9bd1f714bd6a5275714c86358650a2092dfa","0xc906fa38eca6c8a38bb932db61ca31b42792bf61ccc7603c4709315e71744ae5","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.06.07:12:26:14.743: main Eth speed: 301.052 MH/s, shares: 2537/4/10, time: 23:58
2018.06.07:12:26:14.743: main GPUs: 1: 34.197 MH/s (272) 2: 33.205 MH/s (296) 3: 33.690 MH/s (283) 4: 32.515 MH/s (283) 5: 33.280 MH/s (271/4) 6: 33.916 MH/s (297/6) 7: 33.579 MH/s (304) 8: 32.847 MH/s (251) 9: 33.822 MH/s (284)
2018.06.07:12:26:16.432: wdog Thread(s) not responding. Restarting.

start.bat

Code:

@echo off
echo PhoenixMiner will wait 2 seconds before continuing
timeout /t 2
PhoenixMiner.exe -epool eth-us-east1.nanopool.org:9999 -ewal <wallet address>.miner01/<email@gmail.com> -pass x -coin eth -cdm 0 -nvidia -rmode 2
pause

reboot.bat

Code:

shutdown /r /t 5 /f

The screen hangs on the miner and the miner says "hit any key to continue" at the bottom. When I hit a key it only closed the miner and didn't execute the reboot.bat

I'm running the exact same set up on a 1070 Ti rig and have NOT had any issues so far.

Alternate cryptocurrencies / Mining (Altcoins) / Re: Control NVidia Cards OC / Fan from Windows Command Line?

on: May 05, 2018, 01:29:23 AM

Code:

start C:\Users\miner01\Desktop\nvidiaInspector\nvidiaInspector.exe -setBaseClockOffset:0,0,-200 -setMemoryClockOffset:0,0,775 -setPowerTarget:0,50 -setTempTarget:0,0,80 -setFanSpeed:0,35
start C:\Users\miner01\Desktop\nvidiaInspector\nvidiaInspector.exe -setBaseClockOffset:1,0,-200 -setMemoryClockOffset:1,0,755 -setPowerTarget:1,50 -setTempTarget:1,0,80 -setFanSpeed:1,35
start C:\Users\miner01\Desktop\nvidiaInspector\nvidiaInspector.exe -setBaseClockOffset:2,0,-200 -setMemoryClockOffset:2,0,800 -setPowerTarget:2,50 -setTempTarget:2,0,80 -setFanSpeed:2,43
start C:\Users\miner01\Desktop\nvidiaInspector\nvidiaInspector.exe -setBaseClockOffset:3,0,-200 -setMemoryClockOffset:3,0,625 -setPowerTarget:3,50 -setTempTarget:3,0,80 -setFanSpeed:3,35
start C:\Users\miner01\Desktop\nvidiaInspector\nvidiaInspector.exe -setBaseClockOffset:4,0,-200 -setMemoryClockOffset:4,0,790 -setPowerTarget:4,50 -setTempTarget:4,0,80 -setFanSpeed:4,35
start C:\Users\miner01\Desktop\nvidiaInspector\nvidiaInspector.exe -setBaseClockOffset:5,0,-200 -setMemoryClockOffset:5,0,815 -setPowerTarget:5,50 -setTempTarget:5,0,80 -setFanSpeed:5,35
start C:\Users\miner01\Desktop\nvidiaInspector\nvidiaInspector.exe -setBaseClockOffset:6,0,-200 -setMemoryClockOffset:6,0,850 -setPowerTarget:6,51 -setTempTarget:6,0,80 -setFanSpeed:6,35
start C:\Users\miner01\Desktop\nvidiaInspector\nvidiaInspector.exe -setBaseClockOffset:7,0,-200 -setMemoryClockOffset:7,0,615 -setPowerTarget:7,50 -setTempTarget:7,0,80 -setFanSpeed:7,35
start C:\Users\miner01\Desktop\nvidiaInspector\nvidiaInspector.exe -setBaseClockOffset:8,0,-200 -setMemoryClockOffset:8,0,815 -setPowerTarget:8,50 -setTempTarget:8,0,80 -setFanSpeed:8,35

Then make short cut to batch file and move to Windows start folder.

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)

on: April 19, 2018, 11:13:17 PM

@ PhoenixMiner

Had another crash were reboot.bat wasnt executed using 2.9e with Nvidia 1070 x9 rig.

Code:

2018.04.19:17:05:58.117: GPU8 GPU8: DAG generated in 6.6 s (376.4 MB/s)
2018.04.19:17:05:58.156: GPU9 GPU9: DAG  97%
2018.04.19:17:05:58.156: GPU9 GPU9: DAG generated in 6.4 s (388.9 MB/s)
2018.04.19:17:05:58.185: GPU9 CUDA error in CudaProgram.cu:246 : unspecified launch failure (719)
2018.04.19:17:05:58.191: GPU9 GPU9 search error: unspecified launch failure
2018.04.19:17:05:58.193: GPU1 CUDART error in CudaProgram.cu:127 : unspecified launch failure (4)
2018.04.19:17:05:58.193: GPU1 GPU1 initMiner error: unspecified launch failure
2018.04.19:17:05:58.193: GPU8 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.193: GPU8 GPU8 search error: unspecified launch failure
2018.04.19:17:05:58.193: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.193: GPU2 GPU2 search error: unspecified launch failure
2018.04.19:17:05:58.193: GPU7 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.193: GPU7 GPU7 search error: unspecified launch failure
2018.04.19:17:05:58.209: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.209: GPU3 GPU3 search error: unspecified launch failure
2018.04.19:17:05:58.224: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.224: GPU6 GPU6 search error: unspecified launch failure
2018.04.19:17:05:58.271: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.271: GPU4 GPU4 search error: unspecified launch failure
2018.04.19:17:05:58.287: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.19:17:05:58.287: GPU5 GPU5 search error: unspecified launch failure
2018.04.19:17:05:58.599: wdog Thread(s) not responding. Restarting.

start.bat

Code:

@echo off
echo PhoenixMiner will wait 2 seconds before continuing
timeout /t 2
PhoenixMiner.exe -pool eth-us-east1.nanopool.org:9999 -wal ETH Address.miner01/email address@gmail.com -pass x -coin eth -cdm 0 -nvidia -nvNew 1 -minRigSpeed 287 -tstop 78 -tstart 68 -rmode 2
pause

reboot.bat

Code:

shutdown /r /t 00 /f

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 2.9e: fastest Ethereum/Ethash miner with lowest devfee (Windows)

on: April 18, 2018, 08:36:38 PM

@PheonixMiner Still having issue with 2.9e with Nvidia 1070 not rebooting with reboot .bat when miner crashes 2018.04.18:12:26:33.440: gps0 CUDA error in CudaProgram.cu:168 : unknown error (999) 2018.04.18:12:26:33.440: GPU1 CUDA error in CudaProgram.cu:264 : unknown error (999) 2018.04.18:12:26:33.446: GPU1 GPU1 search error: unknown error 2018.04.18:12:26:33.462: GPU8 CUDA error in CudaProgram.cu:264 : unknown error (999) 2018.04.18:12:26:33.462: GPU8 GPU8 search error: unknown error 2018.04.18:12:26:33.462: GPU7 CUDA error in CudaProgram.cu:264 : unknown error (999) 2018.04.18:12:26:33.462: GPU7 GPU7 search error: unknown error 2018.04.18:12:26:33.468: GPU9 CUDA error in CudaProgram.cu:264 : unknown error (999) 2018.04.18:12:26:33.468: GPU9 GPU9 search error: unknown error 2018.04.18:12:26:33.482: GPU3 CUDA error in CudaProgram.cu:264 : unknown error (999) 2018.04.18:12:26:33.482: GPU3 GPU3 search error: unknown error 2018.04.18:12:26:33.482: GPU6 CUDA error in CudaProgram.cu:264 : unknown error (999) 2018.04.18:12:26:33.482: GPU6 GPU6 search error: unknown error 2018.04.18:12:26:33.494: GPU5 CUDA error in CudaProgram.cu:264 : unknown error (999) 2018.04.18:12:26:33.494: GPU5 GPU5 search error: unknown error 2018.04.18:12:26:33.495: GPU2 CUDA error in CudaProgram.cu:264 : unknown error (999) 2018.04.18:12:26:33.495: GPU2 GPU2 search error: unknown error 2018.04.18:12:26:33.535: GPU4 CUDA error in CudaProgram.cu:264 : unknown error (999) 2018.04.18:12:26:33.535: GPU4 GPU4 search error: unknown error 2018.04.18:12:26:34.158: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]} 2018.04.18:12:26:34.204: wdog Thread(s) not responding. Restarting. 2018.04.18:12:26:34.296: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x8cc4101785c8e5f40e72a0abf5651c3711a3cafd57475f8ba5c2059146633adc","0x5683748fa7f53897f1e1a80a8a321d3693761838135be37d1d132c0cd3d7d937","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 2.6: fastest Ethereum/Ethash miner with lowest devfee (Windows)

on: February 19, 2018, 02:41:23 PM

Quote from: kadok29 on February 18, 2018, 04:26:29 PM Quote from: janding on February 18, 2018, 03:23:56 PM Quote from: kadok29 on February 18, 2018, 02:31:57 PM hi, i'm mining with 12 gpu rig..... all my gpy working ok at 29 mh/s... but when i turn off or disconnect the screen.... mi hashrate on gpu 0 goes to 5 mh/s.... what is the problem? can anyone help? Is your monitor connected to the hdmi port on the GPU that drops speed when you turn it off ? yes, connected on hdmi port on the GPU @ KADOK29 - Have you tried turning on On Board Video in BIOS to use CPU graphics? You may also need a HDMI dummy plug. Newegg and Amazon have them. Other wise even when you use TeamViewer it will pull graphics from the 1st 16x slot. You can check by seeing if Intel HD Graphics is in device manager under Display Adapters.

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 2.6: fastest Ethereum/Ethash miner with lowest devfee (Windows)

on: February 15, 2018, 11:43:04 PM

Quote from: flatounet on February 15, 2018, 09:07:47 PM Quote from: torgamer on February 15, 2018, 12:32:16 PM Hi I have problem with eth-proxy Phoenix miner stuck at Starting GPU Mining please help same here , i stoped to use eth proxy here .... proxy look work , but effective speed at pool was always at 0 .... same i have a doubt here ,im testing 2.7 ( nv cards) im on nanopool : start.bat 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 PhoenixMiner.exe -pool eth-eu1.nanopool.org:9999 -wal 0xMywallet/Rig1 -pass x -log 0 -rmode 1 -wdog 1 but i dont know how to for config.txt for epool.txt POOL: eth-eu1.nanopool.org:9999 dont look work , i just want have the same commande / option like the bat file but with all nanopool mirror (nano have 7 mirror )... eth-eu1 , eth-eu2 ..... im sorry ,it dont look clear for me and may be add more mirror if all nanopool was dead ,switch to another one ( flypool ... ) can you put sample for config.txt & epool.txt in FP like for bat file ? thank's you Try this for your batch file... 1. @echo off 2. echo The program will wait 2 seconds before continuing 3. timeout /t 2 4. PhoenixMiner.exe -epool eth-eu1.nanopool.org:9999 -ewal YOUR_WALLET_ADDRESS.WORKER/YOUR_EMAIL_ADDRESS -pass x -coin eth -cdm 0 -nvidia -rmode 2 5. pause I had the same problem. I fixed with the -epool and -ewal syntax The 2 second delay in the .bat is to give my overclock tool the time to set the over clocks before the miner starts to make the dag file after a reboot. 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 was only needed for AMD 2GB cards as far as I know... It is not needed in the batch file for Nvidia cards.

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 2.6: fastest Ethereum/Ethash miner with lowest devfee (Windows)

on: February 14, 2018, 01:32:22 PM

Quote from: PhoenixMiner on February 14, 2018, 09:47:25 AM Quote from: cmd_whoami on February 12, 2018, 04:16:01 PM The only thing I don't understand is why GPU0 is GPU1. This makes the fan speed and temp readout in the miner not line up with the correct cards. Fan temp on GPU0 = GPU5 in Phoenix Hashrate of GPU0 = GPU1 in Phoenix Fan temp on GPU1 = GPU1 in Phoenix Hashrate of GPU1 = GPU2 in Phoenix Fan temp on GPU2 = GPU2 in Phoenix Hashrate of GPU2 = GPU3 in Phoenix Fan temp on GPU3 = GPU3 in Phoenix Hashrate of GPU3 = GPU4 in Phoenix Fan temp on GPU4 = GPU4 in Phoenix Hashrate of GPU4 = GPU5 in Phoenix Fan temp on GPU5 = GPU6 in Phoenix Hashrate of GPU5 = GPU6 in Phoenix Fan temp on GPU6 = GPU7 in Phoenix Hashrate of GPU6 = GPU7 in Phoenix Fan temp on GPU7 = GPU8 in Phoenix Hashrate of GPU7 = GPU8 in Phoenix Fan temp on GPU8 = GPU9 in Phoenix Hashrate of GPU8 = GPU9 in Phoenix We've seen similar things on AMD cards because of broken support for bus ID in the drivers but not on Nvidia cards. The ordering is based on the bus ID (ascending order) and the fan/temp reporting is matched to the bus ID as well, but in same cases like this one the NVML library obviously doesn't report the correct bus ID for the GPU5 and it ends up as the first. Could you press the 's' key on your keyboard and copy the list of GPUs with their bus IDs (it may be easier to do it from the log file than from the screen)? 17576:08:08:13.086: main Available GPUs for mining: 17576:08:08:13.086: main GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs 17576:08:08:13.086: main GPU2: GeForce GTX 1070 (pcie 2), CUDA cap. 6.1, 8 GB VRAM, 15 CUs 17576:08:08:13.086: main GPU3: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs 17576:08:08:13.086: main GPU4: GeForce GTX 1070 (pcie 4), CUDA cap. 6.1, 8 GB VRAM, 15 CUs 17576:08:08:13.086: main GPU5: GeForce GTX 1070 Ti (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 19 CUs 17576:08:08:13.086: main GPU6: GeForce GTX 1070 (pcie 6), CUDA cap. 6.1, 8 GB VRAM, 15 CUs 17576:08:08:13.086: main GPU7: GeForce GTX 1070 (pcie 8 ), CUDA cap. 6.1, 8 GB VRAM, 15 CUs 17576:08:08:13.086: main GPU8: GeForce GTX 1070 (pcie 9), CUDA cap. 6.1, 8 GB VRAM, 15 CUs 17576:08:08:13.086: main GPU9: GeForce GTX 1070 (pcie 10), CUDA cap. 6.1, 8 GB VRAM, 15 CUs 17576:08:08:13.086: main Eth: Accepted shares 2171 (32 stales), rejected shares 2 (0 stales) 17576:08:08:13.086: main Eth: Incorrect shares 12 (0.38%), est. stales percentage 1.47% 17576:08:08:13.086: main Eth: Maximum difficulty of found share: 76.2 TH (!!!) 17576:08:08:13.086: main Eth: Average speed (5 min): 302.663 MH/s 17576:08:08:13.086: main Eth: Effective speed: 291.26 MH/s; at pool: 290.99 MH/s 17576:08:08:13.086: main 17576:08:08:15.723: main Eth speed: 303.298 MH/s, shares: 2171/2/12, time: 20:43 17576:08:08:15.723: main GPUs: 1: 34.044 MH/s (221/5) 2: 33.216 MH/s (234) 3: 33.701 MH/s (274) 4: 32.071 MH/s (226) 5: 34.033 MH/s (254) 6: 34.187 MH/s (237/7) 7: 34.237 MH/s (260) 8: 33.813 MH/s (230) 9: 33.995 MH/s (237) 17576:08:09:01.576: main GPU1: 51C 35%, GPU2: 63C 35%, GPU3: 48C 35%, GPU4: 61C 49%, GPU5: 59C 35%, GPU6: 51C 35%, GPU7: 59C 35%, GPU8: 49C 35%, GPU9: 56C 35% @PhoenixMiner - Looks like the issue is with the odd card of the rig, the Zotac 1070 Ti AMP Edition. I added that 9th card when Windows did the fall creators update allowing Windows to find more than 8 cards. The other 8 are Zotac 1070 AMP Extremes with a fan speed of 35%. The 1070 Ti, GPU4, GPU5 in Phoenix, is in the GPU4 location of my OC tool ( Nvidia Inspector 1.9.7.8 ) with a fan speed of 49%. (Nvidia Inspector allows Over Clock on more than 8 cards which can be set by batch file or GUI and gives all info that GPUZ provides. On top of that it's more stable than MSI's After Burner). (The ONLY downside to Nvidia Inspector is you can't program a fan curve). WHO EVER QUESTIONS PHOENIX ISN'T AS GOOD IF NOT MORE STABLE THAN CLAYMORE? 12 INCORRECT SHARES IN 20HRS @ 302 MH/s ON 9 CARDS. Edit: I thought only getting 12 incorrect shares was amazing at those speeds....

Alternate cryptocurrencies / Mining (Altcoins) / Re: PhoenixMiner 2.6: fastest Ethereum/Ethash miner with lowest devfee (Windows)

on: February 12, 2018, 04:16:01 PM

Great Work on the miner. Over all I think your miner is better than Claymore's. I've been testing this on two rigs for the last 24hrs. One 9 card Zotac 1070 AMP Extreme rig, and one 9 card Zotac 1070 ti AMP Edition rig . I use NVIDIA Inspector 1.9.7.8 to set OC's using a .bat and short cut of .bat in Windows start folder. I found your miner allows my 1070 AMP Extremes to take a higher and more standard Mem Over Clock across all cards. With Claymore every card had a different Mem OC but with Phoenix miner all but one 1070 likes a standard 850 Mem OC. But for what ever reason there was no change with the 1070 ti rig, it still likes the same OC as Claymore's miner. The only thing I don't understand is why GPU0 is GPU1. This makes the fan speed and temp readout in the miner not line up with the correct cards. Fan temp on GPU0 = GPU5 in Phoenix Hashrate of GPU0 = GPU1 in Phoenix Fan temp on GPU1 = GPU1 in Phoenix Hashrate of GPU1 = GPU2 in Phoenix Fan temp on GPU2 = GPU2 in Phoenix Hashrate of GPU2 = GPU3 in Phoenix Fan temp on GPU3 = GPU3 in Phoenix Hashrate of GPU3 = GPU4 in Phoenix Fan temp on GPU4 = GPU4 in Phoenix Hashrate of GPU4 = GPU5 in Phoenix Fan temp on GPU5 = GPU6 in Phoenix Hashrate of GPU5 = GPU6 in Phoenix Fan temp on GPU6 = GPU7 in Phoenix Hashrate of GPU6 = GPU7 in Phoenix Fan temp on GPU7 = GPU8 in Phoenix Hashrate of GPU7 = GPU8 in Phoenix Fan temp on GPU8 = GPU9 in Phoenix Hashrate of GPU8 = GPU9 in Phoenix I read though all 25 pages and didn't see anyone else mention this.

Pages: [1]