PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

[pinamalina]

Hi.

I'm getting below error from time to time.
As you can see, miner was running fine for more than 2 days (on 3.0a).
My setup: 7 x 1070, power limit 62, core +140, memory +650.
Can you please advise?

Code:

2018.06.03:02:58:27.401: eths Eth: New job #3732dc6c from eu1.ethermine.org:4444; diff: 4000MH
2018.06.03:02:58:27.585: main Eth speed: 223.248 MH/s, shares: 12366/0/0, time: 62:40
2018.06.03:02:58:27.585: main GPUs: 1: 31.880 MH/s (1722) 2: 31.892 MH/s (1845) 3: 31.899 MH/s (1776) 4: 31.885 MH/s (1756) 5: 31.894 MH/s (1742) 6: 31.911 MH/s (1756) 7: 31.887 MH/s (1769)
2018.06.03:02:58:31.106: GPU2 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.112: GPU2 GPU2 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU1 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU1 GPU1 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU3 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU3 GPU3 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU4 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU4 GPU4 search error: an illegal memory access was encountered
2018.06.03:02:58:31.147: GPU5 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.147: GPU5 GPU5 search error: an illegal memory access was encountered
2018.06.03:02:58:31.148: GPU6 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.148: GPU6 GPU6 search error: an illegal memory access was encountered
2018.06.03:02:58:31.148: GPU7 CUDA error in CudaProgram.cu:328 : an illegal memory access was encountered (700)
2018.06.03:02:58:31.148: GPU7 GPU7 search error: an illegal memory access was encountered
2018.06.03:02:58:32.055: wdog Thread(s) not responding. Restarting.

Reduce core to -150 (minus 150) or even - 200
Increase mem gradually in 20 increments... I have it at +820. Hashing at 33.2 MH/s

[1714033446]

1714033446

[1714033446]

1714033446

[1714033446]

1714033446

[1714033446]

1714033446

[1714033446]

1714033446

[mrpcrp]

for 1060 3.0a more stable then 3.0c and allow more memory overclocking

[human75]

for 1060 3.0a more stable then 3.0c and allow more memory overclocking

That means your cards will. spend more. power and will. be come. more. unstable :-)

[giorgiokaan]

Hi, I am having an issue where my miner just stops after:

main Phoenix Miner 2.9e Windows/msvc - Release

It has been happening since today and it does it on 3.0, 2.7c and 2.9e.

Also for some reason the first 3 gpus in my 6 card rig just seem to turn off after boot. While the rig is booting their lights are on etc, when the pc is booted the lights go off and sometimes randomly blink. I have reinstalled the latest amd drivers as well after ddu.

[lesjokolat]

Hi, I am having an issue where my miner just stops after:

main Phoenix Miner 2.9e Windows/msvc - Release

It has been happening since today and it does it on 3.0, 2.7c and 2.9e.

Also for some reason the first 3 gpus in my 6 card rig just seem to turn off after boot. While the rig is booting their lights are on etc, when the pc is booted the lights go off and sometimes randomly blink. I have reinstalled the latest amd drivers as well after ddu.

if you are using risers make sure the cards are all firmly in place and not tilted in. is your power supply sufficient or did you add new cards in recently.


also driver info as well as os. do you have enough virtual memory

[pinamalina]

GPU3: unable to get fan speed - Unknown Error (999),what is the problem, the driver 390.65,PhoenixMiner_3.0b??

Hi! and Welcome to the club.
I've search a little bit on the internet and there are a lot of people with this error and  you will have also the nvlddmkm error event id 14 if you look in logs on windows.
Just a short history and why I think it's not the OC the principal issue because there are some with this issue without OC....

1. before Phoenix I've run with Claymore (my brother still use Claymore 11.6 and we have the same GPU's - 1070 G1 Gaming - Micron memory)
Short description on 1070 G1 Gaming OC
Claymore 11.6 - TDP 60%, 0 CC, +800 Memory with Afterburner and it's working flawlessly for weeks without a crash - 226 Mh/s for 7 GPUs 
Phoenix Miner - TDP 60%, -150CC, +780 Memory with Afterburner and it's working like 2-5 days and then restart - 230.1 Mh/s for 7 GPUs
I've lost days from my life to search about this issue and how to solve the problem ...
If you look on nvidia forum it's full of people with this issue and they are not mining, no OC...

2. I have 2 RGIs, same setup and same hardware (TDP 60%, -150CC, +780 Memory, Phoenix Miner 2.9e)
1st RIG - windows 10 1709 (10.0.16299.400 and something..460/462... :?) / nvidia 391.35 - 230.1 Mh and no problem with error 999, working ok.
On the second RIG was funny, windows 1803 and couple of drivers ... no way, restart after 20 min so I've choose to install again 1709, a version with January updates...just what I've found.

I've tried to:
- increase the virtual memory
- different drivers (5 or 6 drivers.... :@)
- something with replace of nvlddmkm.sy_ and use this command "EXPAND.EXE nvlddmkm.sy_ nvlddmkm.sys" (search on google)
- TdrDelay in registry (also search on google)
- bios update fo MB
- disable SLI
- prefer maximum power (nvidia inspector)
- DSR factor x2 in nvidia control panel ... something what I've found on google for mining... I don't know if it's important or not but trust me...you will try everything just to get rid of that error )))

At the end, after 2 days of pain...find on geforce forum something about driver 387.92 to be the solution to nvlddmkm.sys error.

2nd RIG - windows 10 1709 (10.0.16299.192) / driver 387.92 / same overclock settings (60%/-150/+780) - run for 10-11 hours (I was happy finally!!!!) and after that the error appear again, no restart after another 2-3 hours but I wanted to try another driver.

Now, I'm on the same track but with and oldest driver (384.76), the driver from the Gigabyte website and install just the driver without hd audio, gf experinece, psysX, etc...and wait to see how it's working.
With other drivers I have the error from the begging, after 5-10 min of running... I'm sure it's something with windows and nvidia drivers.

What it's very strange ... it's ok on Claymore with +800 memory and working for weeks but I have this error with Phoenix even on +750...

Another problem, on the other rig it's working very well with 391.35, I have a restart after 3-4 days but...it's ok, I can lower the OC but I don't have that error.

I'm still searching how to solve this.

Regards.

 

I have been tuning my cards by increasing the mem clock. 650, 660... 880. Staying at one freq. for 1 day... At - 200,+880. About four hours into start two cards got the error above.. So decreasing my OC a bit down removed the issue completely. Haven't seen it since.

[giorgiokaan]

All firmly seated, I have 2 1000W gold rated psus with 3 gpu's each so power is not an issue. I believe the new windows 10 update might have messed everything up. I tried to roll back windows and now I get a kmode exception not handled bsod on boot.

I'm gonna try reinstall windows from scratch at this point.

[restless]

After more tests, it seems auto-tuning IS working ...

But I can't make the -cvddc switch to work
If I run Claymore for a minute, it sets correct core voltage, I stop it and run Phoenix - doesn't matter if I use cvddc or not - it will use what Claymore had set. Same if set with Afterburner.

Are there some requirements for OS/Driver combo in order to use this switch? I tried on 7 and 10, relatively older drivers because I don't update what runs ok.

[didouday]

Moved from 2.9e to 3.0,
Version 3 is ok for my 470s, but crashed for my 1080ti's every couple of 10min with same command line. didnt disable the autotune yet
Tested with Clay 11.7 and Phoenix 2.9e with no issues

[Digital_Seytan]

Moved from 3.0.b to 3.0.c,
Version 3.0.c is ok for my gtx 1050ti,1060 and 1070, but crashed some time with NVIDIA Driver Version: 397.93 ,but works verry good with NVIDIA Version:390.65 for my Rig's with same command line. didnt disable the autotune yet but autotune not work with NVIDIA Cards why it not work DEV  

Claymore and Ethminer No DAG files  make with Phoenixminer to - No DAG files.
-------------------------------------------------------------

WiNEther Miner is a graphical interface to use with ethminer with advanced watchdog options and monitoring................. . .. Download : https://github.com/digitalpara/WiNETH

[Soliqesh]

3.0a average shares for last 24h 1266(1hour) of all farms, 2.9e result 1299(1hour) for last 24h, every hour I lose about 30 shares with ph 3.0a, unfortunately will have to return to 2.9e.

[rongphuongnam]

I tested v3.0c, some cards dropped 0 hashrate and restart, back to 2.9e.

[reasec]

Hello, im having serius issues with connecting to ethermine pool for devfee shares. Do you have any solution to this?

[Digital_Seytan]

 

I have on a rig 3 x Inno3D iChill GeForce GTX 1060 X3 6GB of which only 1 GPU at 25 Mh works the other two run at up to 20.950 Mh, win10 64, afterburn 3.50, which I also try the other two Inno3D iChill GeForce GTX 1060 X3 6GB do not want to run faster, who o who has the same problem, on ethminer, claymore and phoenixminer the same result.love all opinions are welcome.

[Digital_Seytan]

I tested v3.0c, some cards dropped 0 hashrate and restart, back to 2.9e.

the same problem I have had a couple of times on a gtx 1060 6gb, why do not we know Dev

[wotteam]

Hi,

Any plans for linux (hiveos) version?

[shosafed]

top of total summary miner have a info:

***TIME*** 6/4 Loc.Time ****************

What is this 6/4 

[Pronexx]

top of total summary miner have a info:

***TIME*** 6/4 Loc.Time ****************

What is this 6/4 

June, 4th

[shosafed]

top of total summary miner have a info:

***TIME*** 6/4 Loc.Time ****************

What is this 6/4 

June, 4th

Tnx!!! I could not think. we first write a number, and then a month, apparently there is another format for writing numbers & date.

[Souran]

All firmly seated, I have 2 1000W gold rated psus with 3 gpu's each so power is not an issue. I believe the new windows 10 update might have messed everything up. I tried to roll back windows and now I get a kmode exception not handled bsod on boot.

I'm gonna try reinstall windows from scratch at this point.

This might be worth trying.
I had an issue with 2 of my rigs, sudden crashes to a point that I thought the cards might be bricked.

Anyways, turns out that I had CSM turned on in the motherboard's bios,, once disabled, everything worked like a charm