PhoenixMiner 4.1c is the new stable release. You can find the download link and other information in the first post of this thread. If you have already downloaded and installed it, there is no need to do this again - there is no change from 4.1c that was published as a beta version.

Quote from: pp55 on January 15, 2019, 12:41:02 PM

I can`t see if I can use -Kernel option per GPU. Is it impossible at all or it is miner limitation?
I have a rig with one RX580 8Gb and four RX570 4Gb and wanna try turbo kernels. Any suggestions?

Yes, you can use -clkernel 3 only for some of the GPUs. Even if you set -clkernel 3, if given GPU doesn't have
enough video memory for double DAG, it will switch to -clkernel 1. For example if you want to use the turbo kernels for
the first GPU only from a five GPU rig, use the following command line option: -clkernel 311111

Quote from: thameur on January 15, 2019, 03:42:34 PM

Hi

have there real problems, when mines with R9 390 u. R9 390X GPU's .....
For some months, the hashrate is decreasing continuously from formerly about 33 Mhs / s to about 25.9 Mhs / s even though the R9 390 (X) of the DAG Epoch problem should not be affected at all ...
have any idea to get back 33 Mh/s
Resiste the DAG Epoch

This is caused by the size of the TLB, which is too small for the current DAG sizes and causes constant eviction from the TLB cache. AMD released the "compute mode" fix for RX4x0 and RX5x0 cards, which simply increased the memory page size. However there is no such fix for 290/390 cards. Probably there is no way to increase the page size on these cards because of hardware limitations but only AMD knows for sure. You can either mine coins with lower DAG (basically everything except ETH and ETC), or accept the hashrate drop (but it will get gradually worse over time).

Quote from: bitcoinminer0319 on January 17, 2019, 01:43:56 AM

2019.01.16:19:39:00.717: main Phoenix Miner 4.0b Windows/msvc - Release build
2019.01.16:19:39:00.717: main Cmd line: -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal 0x008c26f3a2Ca8bdC11e5891e0278c9436B6F5d1E.Rig001
2019.01.16:19:39:00.717: main No CUDA driver found
2019.01.16:19:39:06.406: main Unknown OpenCL driver version! Hashrate and stale shares may suffer
2019.01.16:19:39:06.406: main OpenCL platform: OpenCL 2.1 AMD-APP (2766.5)
2019.01.16:19:39:06.406: main Available GPUs for mining:

how do i fix this problem?

You have upgraded your driver to version that is not yet supported by PhoenixMiner (see the line Unknown OpenCL driver version! Hashrate and stale shares may suffer in the log, it will be printed as yellow warning on your screen when the miner starts). It is not a good idea to update to drivers that are newer than the release of PhoenixMiner you are using because this means we weren't able to test this release of PhoenixMiner with these drivers and they probably won't work well (or at all). To fix the problem either upgrade to PhoenixMiner 4.1c, which supports AMD drivers up to and including 19.1.1.

Quote from: Batmaxpt on January 17, 2019, 09:34:09 AM

hi

all good with PhoenixMiner until some hours ago i have more than one rig all nvidia and all with these error any idea with ?

Quote from: marko330 on January 17, 2019, 10:54:57 AM

Have the same problem since 4 hours. My rig works pver year without problems but today i've seen error with CUDA.

CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
GPU1 initMiner error: an illegal memory access was encountered
CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
GPU2 initMiner error: an illegal memory access was encountered

or

CUDART error in CudaProgram.cu:127 : an illegal memory access was encountered (77)
CUDA error in CudaProgram.cu:102 : an illegal memory access was encountered (700)
GPU2 initMiner error: an illegal memory access was encountered
GPU1 initMiner error: an illegal memory access was encountered

Anyone know what to do with this? Virtual memory is fine.

Quote from: cmd_whoami 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...

(also to all miners experiencing problems with PhoenixMiner 3.5 and below versions when trying to create the DAG):

The versions of PhoenixMiner before 4.0 only support DAG epoch up to 235. ETC passed epoch 235 a few weeks ago, and recently ETH also passed DAG epoch 235 and is now on 236. The unfortunate result is that the old version(s) of PhoenixMiner won't be able to create DAG or mine ETH or ETC any more - you must upgrade to PhoenixMiner 4.x.
We have printed this warning here during the release of PhoenixMiner 4.0 but admittedly we could have done much better job with making it visible. We will pin this message in the first post too.

Quote from: Joncatch on January 17, 2019, 03:00:43 PM

After trying I also found 4.0b version does work now although it wasnt working well before additionally it runs my rtx2070s hash a bit slower than versions 3.5 did

We are working on RTX20x0 optimizations but they won't be ready until the next release.