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

[Bathmat]

I have 8 x GTX 1050 Ti 4GB on Windows 10.
I get the the DAG creation error.
Any idea how to resolve this, the DAG is only 3.3GB I believe
My Virtual Memory is more than enough to cover all of my cards in the rig.

Play with below switches:

  -eres <n> Allocate DAG buffers big enough for n epochs ahead (default: 2) to
      avoid allocating new buffers on each DAG epoch switch, which should improve DAG switch stability
  -lidag <n> Slow down DAG generation to avoid crashes when swiching DAG epochs
      (0-3, default: 0 - fastest, 3 - slowest).

also try "-rvram -1"

[j2james]

Dear PM dev, as I understand, GPU auto tunning still does not work for 1070 on Win 7? I have default value 15 for all cards.

May be something wrong with my config and because of it auto tunning does not work? My config:

-nvidia
-cdm 2
-cdmport 3333
-cdmpass xxxxx
-minRigSpeed 186
-rmode 2
-tstop 65
-tstart 40
-logsmaxsize 0
-nvf 2
-hstats 2

Available GPUs for mining:
GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU2: GeForce GTX 1070 (pcie 2), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU3: GeForce GTX 1070 (pcie 3), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU4: GeForce GTX 1070 (pcie 4), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU5: GeForce GTX 1070 (pcie 5), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU6: GeForce GTX 1070 (pcie 6), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU1: 42C 46% 106W, GPU2: 41C 46% 106W, GPU3: 43C 46% 105W, GPU4: 41C 45% 105W, GPU5: 49C 49% 109W, GPU6: 41C 45% 106W
GPU1: cclock 1683 MHz, cvddc 800 mV, mclock 4452 MHz, p-state P2, pcap power
GPU2: cclock 1670 MHz, cvddc 812 mV, mclock 4437 MHz, p-state P2, pcap power
GPU3: cclock 1620 MHz, cvddc 843 mV, mclock 4363 MHz, p-state P2, pcap power
GPU4: cclock 1657 MHz, cvddc 812 mV, mclock 4428 MHz, p-state P2, pcap power
GPU5: cclock 1695 MHz, cvddc 843 mV, mclock 4417 MHz, p-state P2, pcap no
GPU6: cclock 1620 MHz, cvddc 825 mV, mclock 4353 MHz, p-state P2, pcap no
GPUs power: 637.2 W
Current -gt 15,15,15,15,15,15

[reb0rn21]

Is there API command to disable/enable GPU over it?

[iRonNuke]

I havn't tried PhoenixMiner that much before on my 12x Polaris rig. It works just fine, but I don't get that high hashrate with the miner, as of another miner. Anyone have some tips for me to increase hashrate. I have tried -clnew -clkernal 1-3. Doing autoconfig aswell.

I'm getting like 29.8-30.2 MH/s at 1110 MHz Core and ~2050 MHz Mem.

[Guigs321]

I havn't tried PhoenixMiner that much before on my 12x Polaris rig. It works just fine, but I don't get that high hashrate with the miner, as of another miner. Anyone have some tips for me to increase hashrate. I have tried -clnew -clkernal 1-3. Doing autoconfig aswell.

I'm getting like 29.8-30.2 MH/s at 1110 MHz Core and ~2050 MHz Mem.

which GPU exactly? I get 30 MH/s with RX470 if you have 8GB of VRAM you can use "-clkernel 3" and try "-mt 2" it's changing the timing but if you cards are already flashed you will have a lower hashrate.

I get better hashrate with the other miner and option -rxboost and -strap, but it's a little bit less stable and need lower frequencies.

For exemple with this other miner I get 33,1 MH/s with RX580 8Gb and 30,5 MH/s with RX470 4GB.

[bategojko74]

I havn't tried PhoenixMiner that much before on my 12x Polaris rig. It works just fine, but I don't get that high hashrate with the miner, as of another miner. Anyone have some tips for me to increase hashrate. I have tried -clnew -clkernal 1-3. Doing autoconfig aswell.

I'm getting like 29.8-30.2 MH/s at 1110 MHz Core and ~2050 MHz Mem.

which GPU exactly? I get 30 MH/s with RX470 if you have 8GB of VRAM you can use "-clkernel 3" and try "-mt 2" it's changing the timing but if you cards are already flashed you will have a lower hashrate.

I get better hashrate with the other miner and option -rxboost and -strap, but it's a little bit less stable and need lower frequencies.

For exemple with this other miner I get 33,1 MH/s with RX580 8Gb and 30,5 MH/s with RX470 4GB.

Use amd memory tweak and you will get higher hashrate than the other miner

[UnclWish]

On 8Gb 580 cards with -clKernel 3 gains additional speed about 0,5-0,7MH, but ONLY with new finded -gt parameter.

[wishxy]

I have problem with error in CudaProgram, can not continue mining.
Its 6x GTX 1050ti rig, Windows 10.
Any help?

2019.09.23:13:13:10.914: GPU5 CUDA error in CudaProgram.cu:204 : out of memory (2)
2019.09.23:13:13:10.914: GPU5 GPU5: Failed to initialize search buffers: out of memory
2019.09.23:13:13:10.914: GPU5 GPU5 initMiner error: Unable to initialize CUDA miner
2019.09.23:13:13:10.917: GPU6 CUDA error in CudaProgram.cu:204 : out of memory (2)
2019.09.23:13:13:10.917: GPU6 GPU6: Failed to initialize search buffers: out of memory
2019.09.23:13:13:10.917: GPU6 GPU6 initMiner error: Unable to initialize CUDA miner
2019.09.23:13:13:10.920: GPU4 CUDA error in CudaProgram.cu:204 : out of memory (2)
2019.09.23:13:13:10.920: GPU4 GPU4: Failed to initialize search buffers: out of memory
2019.09.23:13:13:10.920: GPU4 GPU4 initMiner error: Unable to initialize CUDA miner
2019.09.23:13:13:10.933: GPU3 CUDA error in CudaProgram.cu:204 : out of memory (2)
2019.09.23:13:13:10.933: GPU3 GPU3: Failed to initialize search buffers: out of memory
2019.09.23:13:13:10.933: GPU3 GPU3 initMiner error: Unable to initialize CUDA miner
2019.09.23:13:13:11.232: GPU1 GPU1: DAG  88%

[iRonNuke]

I havn't tried PhoenixMiner that much before on my 12x Polaris rig. It works just fine, but I don't get that high hashrate with the miner, as of another miner. Anyone have some tips for me to increase hashrate. I have tried -clnew -clkernal 1-3. Doing autoconfig aswell.

I'm getting like 29.8-30.2 MH/s at 1110 MHz Core and ~2050 MHz Mem.

which GPU exactly? I get 30 MH/s with RX470 if you have 8GB of VRAM you can use "-clkernel 3" and try "-mt 2" it's changing the timing but if you cards are already flashed you will have a lower hashrate.

I get better hashrate with the other miner and option -rxboost and -strap, but it's a little bit less stable and need lower frequencies.

For exemple with this other miner I get 33,1 MH/s with RX580 8Gb and 30,5 MH/s with RX470 4GB.

Sapphire RX 570/580 8 GB. But I'm running my GPUs at low clocks ~1100 MHz Core/~2000 MHz Mem @ 800 mV. What frequency/voltage do you run to achive 33 MH/s, it can't draw low power?

At another miner I'm getting 30.5 MH/s at same clocks/voltage.

[Guigs321]

MSI RX580 8 Go Armor 1220/2200@900

[UnclWish]

Phoenix, you added memory straps applying some versions back. Can you add using REF parameter like Claymore's rxboost?
And 2nd: Can you add additional parameter to force releasing videomemory on start and on stop of miner?

[xsoft]

Hi,
is still Phoenix 4.6c compatible with eth-prox?
Im using Phoenix 4.6c on EthOS (linux),
with proxy eth-proxy (python, linux) https://github.com/Atrides/eth-proxy

Ive tried also -proto 1..4, same result. Miner dont get work from proxy. Maybe its on proxy side, maybe its asking in bad way by miner, I dont know.
Ive tried also other eth-proxy (that GO version from dwarf, none success either).

ANY tips, ... like ANY for working eth proxy for linux is welcomed. Ive tried, search and run all kind of them, none is working now (they worked .. maybe .. at 2017, but not today).


=== ETH PROXY ===

Code:

2019-09-24 13:38:44,790 DEBUG proxy logger.get_logger # Logging initialized
2019-09-24 13:38:44,791 WARNING proxy eth-proxy.main # Ethereum Stratum proxy version: 0.0.5
2019-09-24 13:38:44,791 WARNING proxy eth-proxy.main # Trying to connect to Stratum pool at ***pool***:9999
2019-09-24 13:38:44,819 INFO stats stats.print_stats # 1 peers connected, state changed 1 times
2019-09-24 13:38:44,819 DEBUG protocol protocol.connectionMade # Connected 11.22.33.44
2019-09-24 13:38:44,819 DEBUG protocol protocol.connectionMade # Resuming connection: []
2019-09-24 13:38:44,820 INFO proxy eth-proxy.on_connect # Connected to Stratum pool at ***pool***:9999
2019-09-24 13:38:44,820 DEBUG protocol protocol.writeJsonRequest # < {"worker": "Proxy_0.0.5_debug", "jsonrpc": "2.0", "params": ["0x111**eth**address**1111", "mail@xxx.com"], "id": 2, "method": "eth_submitLogin"}
2019-09-24 13:38:44,883 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'id': 2, u'result': True}
2019-09-24 13:38:44,884 WARNING proxy eth-proxy.main # -----------------------------------------------------------------------
2019-09-24 13:38:44,885 WARNING proxy eth-proxy.main # PROXY IS LISTENING ON ALL IPs ON PORT 9995
2019-09-24 13:38:44,885 WARNING proxy eth-proxy.main # -----------------------------------------------------------------------
2019-09-24 13:38:44,885 WARNING proxy eth-proxy.main # Wallet: 0x111**eth**address**1111
2019-09-24 13:38:44,886 WARNING proxy eth-proxy.main # Worker ID enabled: True
2019-09-24 13:38:44,886 WARNING proxy eth-proxy.main # Email monitoring on mail@xxx.com
2019-09-24 13:38:44,886 WARNING proxy eth-proxy.main # Failover enabled: False
2019-09-24 13:38:44,886 WARNING proxy eth-proxy.main # -----------------------------------------------------------------------
2019-09-24 13:38:44,887 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'id': 0, u'result': [u'0xae27dd3d0e2444e3751e5d67e7df3621538d6559e59d70183cd823b2a86ab16b', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']}
2019-09-24 13:38:44,887 DEBUG proxy jobs.replace_job # NEW_JOB MAIN_POOL [u'0xae27dd3d0e2444e3751e5d67e7df3621538d6559e59d70183cd823b2a86ab16b', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']
2019-09-24 13:38:44,888 DEBUG protocol protocol.writeJsonRequest # < {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
2019-09-24 13:38:44,930 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'id': 0, u'result': [u'0xae27dd3d0e2444e3751e5d67e7df3621538d6559e59d70183cd823b2a86ab16b', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']}
2019-09-24 13:38:57,547 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'id': 0, u'result': [u'0x841f10a65d21c09c0ff56504dcd02e53ee3abc6c163faf9e856076533cccad33', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']}
2019-09-24 13:38:57,547 DEBUG proxy jobs.replace_job # NEW_JOB MAIN_POOL [u'0x841f10a65d21c09c0ff56504dcd02e53ee3abc6c163faf9e856076533cccad33', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']
2019-09-24 13:39:00,035 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'id': 0, u'result': [u'0x352491bfda90c75fc64493ce652ae599e1e8f22302eefe7f99036aa55c5aa962', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']}
2019-09-24 13:39:00,035 DEBUG proxy jobs.replace_job # NEW_JOB MAIN_POOL [u'0x352491bfda90c75fc64493ce652ae599e1e8f22302eefe7f99036aa55c5aa962', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']
2019-09-24 13:39:14,973 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'id': 0, u'result': [u'0xc0369d09d2b193d6a512b3a83294fbcd2695189e013c49e726f7ebc4b53d2c3b', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']}
2019-09-24 13:39:14,974 DEBUG proxy jobs.replace_job # NEW_JOB MAIN_POOL [u'0xc0369d09d2b193d6a512b3a83294fbcd2695189e013c49e726f7ebc4b53d2c3b', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']
2019-09-24 13:39:19,068 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'id': 0, u'result': [u'0xb72f95084a2b3d08af2982a6af2af99c85247ae21138316a2e2d4b627b357212', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']}
2019-09-24 13:39:19,069 DEBUG proxy jobs.replace_job # NEW_JOB MAIN_POOL [u'0xb72f95084a2b3d08af2982a6af2af99c85247ae21138316a2e2d4b627b357212', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']
2019-09-24 13:39:20,723 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'id': 0, u'result': [u'0xf4c9af8d4335123441575ede1386af24dca947565dab442c1ac755718e459e57', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']}
2019-09-24 13:39:20,723 DEBUG proxy jobs.replace_job # NEW_JOB MAIN_POOL [u'0xf4c9af8d4335123441575ede1386af24dca947565dab442c1ac755718e459e57', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']
2019-09-24 13:39:25,431 DEBUG protocol protocol.lineReceived # > {u'jsonrpc': u'2.0', u'id': 0, u'result': [u'0x59d60386d40f286d32be141326e147e888b0e3b20bce331e6d764a89b841c8d0', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']}
2019-09-24 13:39:25,432 DEBUG proxy jobs.replace_job # NEW_JOB MAIN_POOL [u'0x59d60386d40f286d32be141326e147e888b0e3b20bce331e6d764a89b841c8d0', u'0xcf687705ea66f2ff6244a1b9e0505fa881ff467228ab6c1d4d183b8d97d9655d', u'0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116']

=== PHOENIX ===

Code:

*** 0:02 *** 9/24 15:38 **************************************
Eth: Mining Unknown on >small2.iidx.cz:9995 for 0:00
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 0.000 MH/s
Eth: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s

Eth: Connecting to ethash pool small2.iidx.cz:9995 (proto: EthProxy)
Eth: Connected to ethash pool small2.iidx.cz:9995 (46.101.171.231)
Eth: Send: {"id":1,"jsonrpc":"2.0","method":"eth_submitLogin","worker":"MINER123","params":["0x111**eth**address**1111","x"]}

GPU1: 25C 100% 38W, GPU2: 25C 100% 38W, GPU3: 25C 100% 40W, GPU4: 27C 100% 39W, GPU5: 25C 100% 39W
GPUs power: 194.0 W
GPU1: 25C 100% 38W, GPU2: 24C 100% 38W, GPU3: 25C 100% 40W, GPU4: 26C 100% 40W, GPU5: 25C 100% 38W
GPUs power: 194.0 W

*** 0:03 *** 9/24 15:39 **************************************
Eth: Mining Unknown on >small2.iidx.cz:9995 for 0:00
Eth: Accepted shares 0 (0 stales), rejected shares 0 (0 stales)
Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
Eth: Average speed (5 min): 0.000 MH/s
Eth: Effective speed: 0.00 MH/s; at pool: 0.00 MH/s
...
Eth: Connection closed by the pool
Eth: Reconnecting in 20 seconds...

[j2james]

GPU1: 25C 100% 38W, GPU2: 25C 100% 38W, GPU3: 25C 100% 40W, GPU4: 27C 100% 39W, GPU5: 25C 100% 39W

My comment is not related to your question. But. Are you shure that it makes sence to set 100% of FANs speed? The lifetime of FANs will be greatly reduced. My be it makes sence to add additional big FANs? In fact, it should be cheaper.

[Semtex72]

Performance Video in my testing so far: 481mh @ 1062w for a 8x 5700 XT rig. https://twitter.com/BitsBeTrippin/status/1174169921250631682

But probably going to settle for 474mh @ 1058, as few of the cards not showing 100% stability with settings. Once I see it clean for 24h will post how I got there in video.

Again, please share your stable settings checked vs the pool

I run like this 100% stable:

-tt 58 -cvddc 750 -cclock 1300 -fanmin 0 -mclock 910 -amd -mode 1 -clKernel 1 -clNew 1

[Semtex72]

I own now 2x Sapphire 5700XT.

I have used Adrenaline 1.9.2.2 and classic setting posted on this topic; -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 it gives 52,x MH but it fails in minutes.

I have tried lower or bigger -cvvdc between 750 and 900mV, even lower/higher -tt, it fails randomly showing 0.00MH.

I tried also to keep memory stock (875MHz), it fails randomly, same problem and miner stays locked, mouse too, just hard reset works.

When I have removed -hstats 2 command, keeping just  -tt 62  -cclock 1300 -cvddc 800 -mclock 900, it worked fine 12 hours but I just tried last sollution: I have deleted all commands -tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2 from ,bat file and I have used just Msi Afterburner 4.6.2 beta 2           https://www.guru3d.com/files-details/msi-afterburner-beta-download.html        wich full controls power limit, voltage and frequency, now I left voltage unattended (1187mV), GPU frequency stock, memory increased at 900MHz and power limit down to -43 or even -44%.

Works flawless.

It looks as the much commands gived to the miner (tt 62  -cclock 1300 -cvddc 800 -mclock 900 -hstats 2), especially -hstats 2,  gives driver error (atimtag.dll) and locks the miner...

So, I keept settings as in picture attached and .bat file as simple, without extra commands ex:  PhoenixMiner.exe -pool ssl://eu1.ethermine.org:5555 -pool2 ssl://us1.ethermine.org:5555 -wal your wallet adress.rig name, and is rock solid.

https://i.postimg.cc/RhtKXjtg/Best-settings.jpg

Seems to be these issues are related to nicehash (even if that is not mentioned here).

[riqtroy]

Need help.
Everything was fine until one week ago, when suddenly I'v start getting these errors:

12 GPU: "CUDA error in CudaProgram.cu:407 : out of memory" with "-eres" more than "0" (default 2);
12 GPU: "CUDA error in CudaProgram.cu:195 : out of memory" on 92% DAG with "-eres 0";
11 GPU: same as 12 GPU
10 GPU: "CUDA error in CudaProgram.cu:407 : out of memory" with "-eres" more than "0" (default 2);
10 GPU: Works fine with "-eres 0";

also I don't remember when, but sometimes I get:
"CUDA error in CudaProgram.cu:173 : out of memory",
"CUDA error in CudaProgram.cu:204 : out of memory".

RIQ:
Windows 10 64 (can't install win7 bcuz then motherboard won't support all gpu's)
mb: Asus B250
cpu: G4560
gpu: 1050TI x 12
ram: 8GB
ssd: 128GB (virtual memory set to 98304mb)

[riqtroy]

I have problem with error in CudaProgram, can not continue mining.
Its 6x GTX 1050ti rig, Windows 10.
Any help?

2019.09.23:13:13:10.914: GPU5 CUDA error in CudaProgram.cu:204 : out of memory (2)
2019.09.23:13:13:10.914: GPU5 GPU5: Failed to initialize search buffers: out of memory
2019.09.23:13:13:10.914: GPU5 GPU5 initMiner error: Unable to initialize CUDA miner
2019.09.23:13:13:10.917: GPU6 CUDA error in CudaProgram.cu:204 : out of memory (2)
2019.09.23:13:13:10.917: GPU6 GPU6: Failed to initialize search buffers: out of memory
2019.09.23:13:13:10.917: GPU6 GPU6 initMiner error: Unable to initialize CUDA miner
2019.09.23:13:13:10.920: GPU4 CUDA error in CudaProgram.cu:204 : out of memory (2)
2019.09.23:13:13:10.920: GPU4 GPU4: Failed to initialize search buffers: out of memory
2019.09.23:13:13:10.920: GPU4 GPU4 initMiner error: Unable to initialize CUDA miner
2019.09.23:13:13:10.933: GPU3 CUDA error in CudaProgram.cu:204 : out of memory (2)
2019.09.23:13:13:10.933: GPU3 GPU3: Failed to initialize search buffers: out of memory
2019.09.23:13:13:10.933: GPU3 GPU3 initMiner error: Unable to initialize CUDA miner
2019.09.23:13:13:11.232: GPU1 GPU1: DAG  88%

Have you tried to set "-eres 0"? It helps me with 10 gpu's or less

[PhoenixMiner]

Because of the GTX1050Ti (and other 4 GB Nvidia cards) problems under Windows, here is a special release that will solve the issue for a few more weeks. That's the best that can be done, because Nvidia drivers just won't allow to allocate enough VRAM even when it is available. Note that if you don't have 4 GB Nvidia cards, there is no point to use the 4.7a - there are only some small fixes for rare bugs. You can download PhoenixMiner 4.7a from here:

(MEGA links are no longer active)

If you want to check the integrity of the downloaded file, please use the following hashes (you need the last file PhoenixMiner_NVRTC_Windows.zip only if you want to mine BCI with Nvdia cards under Windows):

Code:

    File: PhoenixMiner_4.7a_Windows.zip
    ===================================
   SHA-1: c4448eef92538ff9745a8cd6a79e9f1dbd9d3f20
 SHA-256: 18077c9e18b66a43add6f65eceaad5c56359dffec3e5a0b2bdf609fb8cbb1340
 SHA-512: 45b87fa6f6e80b616bbf97ef02d572fac499660d4b8e854bc3624df6682276aae4341dfe24c04d460d5a44f1c986f6df54ad909ff03861fb4c656d21e716d324


    File: PhoenixMiner_NVRTC_Windows.zip
    ====================================
   SHA-1: ff6fa5e018adbd52caf631c42b7c2fac7ce48a51
 SHA-256: 8087757169405d51ea8ba818347fb05d0450aef985c29272165070346eb5a54a
 SHA-512: 7b2d832f7f40578bb1f501d5174467f5ae06612e601dab769fd56d39da48a471b18c6373435a485155f70fec4017d8378797bf1e1dfe5d62fee30fa6a1d992c4

Here are the new features for this release:

• Reduced VRAM usage for Nvidia cards on Windows to allow slightly longer operation of 4 GB cards under Windows 10 (few weeks to a month, then the problem will appear again)
• Other small improvements and fixes.

Remember to add -rvram -1 -eres 0 to your command-line or config.txt file in order to lower the memory usage as much as possible.

[PhoenixMiner]

Here are some notes about the Windows 10 out of memory problems:

• While they are present both on AMD and Nvidia GPUs, the problem with Nvidia is much worse. The 4 GB AMD GPUs will work without problems under Windows 10 at least until DAG 350, while the best that can be expected from Nvidia is DAG 293. And this is not entirely Windows 10 fault because even under Linux the 1050Ti won't be able to go beyond DAG 340 or a little higher.
• The first thing to do after encountering out of memory error is to add -rvram -1 -eres 0 to your command-line or config.txt file in order to lower the memory usage as much as possible.
• Again, there is no point to upgrade to PhoenixMiner 4.7a if you don't have 4 GB Nvidia cards and there are no out of memory problems

[riqtroy]

Here are some notes about the Windows 10 out of memory problems:

• While they are present both on AMD and Nvidia GPUs, the problem with Nvidia is much worse. The 4 GB AMD GPUs will work without problems under Windows 10 at least until DAG 350, while the best that can be expected from Nvidia is DAG 293. And this is not entirely Windows 10 fault because even under Linux the 1050Ti won't be able to go beyond DAG 340 or a little higher.
• The first thing to do after encountering out of memory error is to add -rvram -1 -eres 0 to your command-line or config.txt file in order to lower the memory usage as much as possible.
• Again, there is no point to upgrade to PhoenixMiner 4.7a if you don't have 4 GB Nvidia cards and there are no out of memory problems

Hello, PhoenixMiner!
So basically 1050ti can live under Windows 10 only until 293 which is 22 october 2019 or 8790000 block?
And the best way to go until the end with 1050ti is Linux? No way to make 383 even with Linux?
ps Thank you for 4.7a, 12 gpu's works fine.