Quote from: alex31 on Today at 12:54:21 PM

Quote from: bategojko74 on Today at 12:37:22 PM

Quote from: alex31 on Today at 12:17:21 PM

Quote from: bategojko74 on Today at 11:45:25 AM

Code:

2020.06.09:11:34:45.506: GPU1 GPU1: Free VRAM: 3.948 GB; used: 0.052 GB <---------
2020.06.09:11:34:45.506: GPU1 GPU1: Allocating DAG for epoch #341 (3.66) GB
2020.06.09:11:34:45.510: GPU1 GPU1: Generating DAG for epoch #341

You obviously can't mine at epoch 351 with the 4GB card that is connected with the monitor because there isn't enough VRAM for both activities. Just exclude it from mining: -gpus 23456 . Remove also your first gt: -gt 26,27,25,25,24
You can run second instance of PM to mine ETH with the first card. Use the same command line parameters, just change the pool with ETH pool (e.g.: -pool ssl://eu1.ethermine.org:5555), change wallet with some ETH wallet (e.g.: -wal 0x...SOME...ETH...WALLET...) and set -gpus 1 -gt 25 for the second instance of PM.

I think that you on wrong way , he has enough vram on first card

He has in theory, but the driver reserves it for the monitor. So in practice he can’t use his last 0.26GB because of the way the driver manages the VRAM when there is monitor attached. If you mine under Linux, maybe you will not have this problem for now.

I has in practice 4 Gb gpus on WIN10 and mined without problems as I told early Roll Eyes

But maybe your monitor is connected to the motherboard video... Not on the mining card...