This is more overclocking and/or PSU releated. If your cards are overclocked, during the DAG generation they may fail as DAG generation is more computationally intensive than the normal ethash computation. Another possible reason is a PSU(s) that are at the limit. During the DAG generation the cards will draw more power and if the PSU is near it's limit, the voltages may drop too much and the cards will crash. We will add the -gser option to serialize the DAG generation to solve the second problem in the next release.
[/quote]

Hi PM,

First of all thanks for the advice; thought I'd give some feedback on the above.
Just to put into context, the cards I'm mining with are 1x1080Ti and 3x1050ti; power usage normally is 410W at the wall; the PSU is good up to 750W so this shouldn't be the issue.
I have however reset to 0 the Core and Mem clock settings  in Afterburner[from +150Core and +1000Mem, effectively going back to 80MH/s from 105.5MH/s] prior to the DAG update this evening and can confirm that the miner hasn't crashed.
During the next few weeks I'll endevour to see which overclock settings would not cause any problems during DAG update; will start with 140/900; at the moment performance is @ 103.5MH/s so will see in about 5 days how it goes.

Cheers,
Greg

At DAG update [so every 5 days and a few hours] I'm running into the issue as per the screenshot:

https://pasteboard.co/HlSWewG.png

I tried to find in readme file whether there's a fix for this; I already have 16 GB of virtual memory allocated so that shouldn't be the issue.

The cards in question are all nvidia, so the codes suggested won't work [as it says in title only for AMD].

Any help is appreciated!

Cheers,

Greg

Hi Everyone,
First post on the forum, started mining as a hobby a few months ago.
Changed to PhoenixMiner over the weekend as Claymore crashed out after a few minutes when using the EthLargement pill [I have an 1080TI in my rig].
PhoenixMiner doesn't crash when on the pill and the hashrates are also a bit higher, so far so good [apart from when Windows Defender ignores the fact that PhoenixMiner is added to the exclusions].
The issue I'm having is that every now and then the reported hashrate on nanopool drops to 0 and stays there until I reboot the miner.
The start_miner.bat I'm using looks like below:

setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100

PhoenixMiner.exe -pool eu1.nanopool.org:9999 -wal 0xe"myethadress"19e2e58/gaming1

Do I miss something from the bat file?

The rig is running windows 10 64 bit.

Any insight as to where I go wrong is appreciated!