Win10 user here with a single RTX 2060 Super, and 24GB of virtual memory page file already configured on my gaming PC.
Recently upgraded to Phoenix Miner 5.2e for testing on Nicehash & ETH on Ethermine, but I am still getting the same problem as before when I was on 5.1c - Phoenix would simply crash at random with no warning or errors after several hours of mining. I have looked at the logs and the common theme I've been seeing is that it crashes during the DAG file creation process. Below is a sample of the final moments as captured by the Phoenix log just before the miner crashes.
2020.11.29:17:55:13.444: GPU1 GPU1: Starting up... (0)
2020.11.29:17:55:13.444: GPU1 GPU1: Generating ethash light cache for epoch #0
2020.11.29:17:55:14.044: GPU1 Light cache generated in 0.6 s (26.7 MB/s)
2020.11.29:17:55:15.614: GPU1 GPU1: Allocating DAG for epoch #0 (1.00) GB
2020.11.29:17:55:15.642: GPU1 GPU1: Generating DAG for epoch #0
2020.11.29:17:55:15.749: main Eth speed: 0.000 MH/s, shares: 45/0/0, time: 0:32
2020.11.29:17:55:16.418: eths Eth: Received: {"id":null,"method":"mining.notify","params":["0000000047936db6","0000000000000000000000000000000000000000000000000000000000000000","fe24abd0fd26cde9dda8a15fc6cb485f248494a864bf37cce71afef0e36744d9",true]}
This problem also occurs at random epochs, regardless of the pool, or any
-eres or
-lidag values I use in the config file. I tried to mitigate this with the
-rmode parameter (wdog is enabled by default) but it does not work. The problem also manifests itself with or without the NiceHash Miner client running....
The OC is what I would consider relatively mild - 1650mhz cclock (+100) / 765mV vCore (53% power limit) / 7650mhz mclock (+650), and has been working very stable for me in the past. I have also specified
-nvdo 1 on the config settings and also rolled back my NVidia drivers back to v432.00, and I also confirm that the Phoenix Miner EXE file is on my AntiVirus exception list.
I am at a complete loss and appear have hit a brick wall (yet again) - any suggestions or ideas on what else would be causing this problem?