Search content
Sort by

Showing 7 of 7 results by MarioMBM
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 2.7c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
MarioMBM
on 05/03/2018, 14:39:08 UTC
I have used older and the latest 390.01



you mean 390.77 && 391.01?

Yes 391.01 now, but i have same results with both versions and older versions. I have tried everything.
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 2.7c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
MarioMBM
on 05/03/2018, 14:10:52 UTC
I have used older and the latest 390.01

[/quote]

similar here, just haven't checked w/o OC. i wonder if there's issues with the 1070's and 2.7c .. what version of windows drivers are you using?
[/quote]
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 2.7c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
MarioMBM
on 05/03/2018, 13:48:46 UTC
I keep getting this error , at random times, sometime after 48h sometimes after 20 minutes.
It does not matter if I OC or NO.
I get it with stock and overclock settings , i have changed the risers , checked cables etc. Reinstalled windows set pagefile bigger, added ddr. New nvidia drives old driver does not matter. Tried -eres 0 1 2 does not help.
I also need to mention that i have 2 rigs with 100% same specs , 1 with days of uptime no issue. 1 constantly needs to be rebototed.

My Rig
6x 1070 / 008 risers / 2x HX850i Psu / Biostar BT250 Mobo.
PM 2.7c

PhoenixMiner.exe -pool eu1.ethermine.org:4444 -wal XXXXX.MRORIG02 -proto 3 -cdm 0 -nvidia -eres 0 -minRigSpeed 170 -rmode 2






17595:13:48:32.912: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x0b9f0e5843454c7c5df42b3a5c1b09931866d99dcd4953f6e71f7ce023ec8e6b","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4f5b01"]}
17595:13:48:32.912: eths Eth: Received: {"id":5,"jsonrpc":"2.0","result":["0x0b9f0e5843454c7c5df42b3a5c1b09931866d99dcd4953f6e71f7ce023ec8e6b","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4f5b01"]}
17595:13:48:33.123: eths Eth: Received: {"id":6,"jsonrpc":"2.0","result":true}
17595:13:48:34.039: eths Eth: Received: {"id":0,"jsonrpc":"2.0","result":["0x67114b78abc6a0f415ef5fe733f79589e655abbe1da07798577c931cb34228cd","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4f5b02"]}
17595:13:48:34.039: eths Eth: New job #67114b78 from eu1.ethermine.org:4444; diff: 4000MH
17595:13:48:34.742: main Eth speed: 192.765 MH/s, shares: 61/0/0, time: 0:22
17595:13:48:34.742: main GPUs: 1: 32.327 MH/s (13) 2: 31.662 MH/s (5) 3: 32.451 MH/s (7) 4: 31.978 MH/s (13) 5: 32.355 MH/s (10) 6: 31.992 MH/s (13)
17595:13:48:35.364: GPU2 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.364: GPU4 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.368: GPU2 GPU2 search error: unknown error
17595:13:48:35.368: GPU4 GPU4 search error: unknown error
17595:13:48:35.386: GPU5 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.386: GPU5 GPU5 search error: unknown error
17595:13:48:35.387: GPU1 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.387: GPU1 GPU1 search error: unknown error
17595:13:48:35.388: GPU6 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.388: GPU6 GPU6 search error: unknown error
17595:13:48:35.388: GPU3 CUDART error in CudaProgram.cu:434 : unknown error (30)
17595:13:48:35.388: GPU3 GPU3 search error: unknown error
17595:13:48:35.419: wdog Thread(s) not responding. Restarting.
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 2.7c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
MarioMBM
on 03/03/2018, 12:44:08 UTC
i think answers will be no ,
This is not something a miner can predict. It can't distinguish between software fault (bad overclock, buggy drivers) and hardware issue (bad riser, cat unplugged the riser cable, housefire, apocalypse).
The only thing you can do is to set -rmode 2 and make reboot.bat with "shutdown /s /f" on in it.

I`m a big noob , please elaborate.
How do I do that.
Show the file extensions - google if you don't know how.
Create a new text file.
Add
Code:
shutdown /s /f
inside.
Rename the file to reboot.bat.
Place it inside the miner's folder.
Add -rmode 2 to the command line.

Thanks bro.
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 2.7c: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
MarioMBM
on 03/03/2018, 11:48:03 UTC
i think answers will be no ,
This is not something a miner can predict. It can't distinguish between software fault (bad overclock, buggy drivers) and hardware issue (bad riser, cat unplugged the riser cable, housefire, apocalypse).
The only thing you can do is to set -rmode 2 and make reboot.bat with "shutdown /s /f" on in it.

I`m a big noob , please elaborate.
How do I do that.
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 2.6: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
MarioMBM
on 26/02/2018, 17:29:00 UTC
Phoenix/OP:

i have 2 systems running just fine on Phoenix2.6

but now on a 3rd system with a brand new fresh install of win10 x64. and a single MSI GTX 1080ti im hitting the following error:

Code:
17586:19:01:11.605: GPU1 GPU1: DAG generated in 5.9 s (403.2 MB/s)
17586:19:01:13.312: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17586:19:01:14.641: GPU1 CUDART error in CudaProgram.cu:422 : unspecified launch failure (4)
17586:19:01:14.641: GPU1 GPU1 search error: unspecified launch failure
17586:19:01:15.117: wdog Thread(s) not responding. Restarting.
17586:19:01:17.460: GPU1 GPU1: Starting up...
17586:19:01:17.497: GPU1 CUDART error in CudaProgram.cu:230 : all CUDA-capable devices are busy or unavailable (46)
17586:19:01:17.497: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable

I have DDU'd my driver, and reinstalled to no avail. nvidia driver 390.77, same driver as my other nvidia based rig thats working just fine

i got this error one time , it's about OC for me ....
reset OC ,and re-test or check/change  riser after .....

There was no overclock applied. It was completely stock.

But I don’t know what it was but after updating to the most recent version of Windows 10, the problem seems to have gone away.

Old version: 1511
New version: 1709

Works fine now.

Same as you i have 2 righs completly the same 1070 Dual OCs , they are basicaly mirrors.
1 works fine the other has the error you had, i have the latest windows 10 1709 and i am still getting that error after 10/12 hours of running.
Drives me crazy.

turn off all the nvidia audiodevices in devicemanager. for me it helped to solve some weird (driver i think) related stuff.

Thanks , i`ve just disabled all the audio related devices. and under clocked 1 gpu to the lowest possible and seems stable for 2/3 hours now.
I think i might have a bad riser that stops relaying info to the miner or something.
Post
Topic
Board Mining (Altcoins)
Re: PhoenixMiner 2.6: fastest Ethereum/Ethash miner with lowest devfee (Windows)
by
MarioMBM
on 26/02/2018, 11:11:28 UTC
Phoenix/OP:

i have 2 systems running just fine on Phoenix2.6

but now on a 3rd system with a brand new fresh install of win10 x64. and a single MSI GTX 1080ti im hitting the following error:

Code:
17586:19:01:11.605: GPU1 GPU1: DAG generated in 5.9 s (403.2 MB/s)
17586:19:01:13.312: main Eth speed: 0.000 MH/s, shares: 0/0/0, time: 0:00
17586:19:01:14.641: GPU1 CUDART error in CudaProgram.cu:422 : unspecified launch failure (4)
17586:19:01:14.641: GPU1 GPU1 search error: unspecified launch failure
17586:19:01:15.117: wdog Thread(s) not responding. Restarting.
17586:19:01:17.460: GPU1 GPU1: Starting up...
17586:19:01:17.497: GPU1 CUDART error in CudaProgram.cu:230 : all CUDA-capable devices are busy or unavailable (46)
17586:19:01:17.497: GPU1 GPU1 initMiner error: all CUDA-capable devices are busy or unavailable

I have DDU'd my driver, and reinstalled to no avail. nvidia driver 390.77, same driver as my other nvidia based rig thats working just fine

i got this error one time , it's about OC for me ....
reset OC ,and re-test or check/change  riser after .....

There was no overclock applied. It was completely stock.

But I don’t know what it was but after updating to the most recent version of Windows 10, the problem seems to have gone away.

Old version: 1511
New version: 1709

Works fine now.

Same as you i have 2 righs completly the same 1070 Dual OCs , they are basicaly mirrors.
1 works fine the other has the error you had, i have the latest windows 10 1709 and i am still getting that error after 10/12 hours of running.
Drives me crazy.