Quote from: hustleman on Today at 02:22:49 AM

Quote from: swogerino on June 30, 2021, 08:38:13 PM

Quote from: makipsee on June 30, 2021, 06:01:53 PM

Quote from: hustleman on June 30, 2021, 02:47:39 AM

So mining with an earlier verson of phxminer. If I start the miner with the overclocks applied on the 3070s and 3060ti, one of these cards gets nothing but invalid shares. So i have to shut the miner down, set msi afterburner settings to default, restart the miner and let the DAGS build to 100%, then after this apply the overclockings. This is a pain in the ass, especially if the miner faults and restarts.

My question is has this been fixed with the newest version of Phxminer?

I have this same problem. But I created some cmd/bat files that work on timers. So when I call up one file it calls up Phoenixminer and also opens another bat file with a timeout command until the DAGs are built then it calls up MSI afterburner to my set profile. But I wish there was a way to call up files when using EZIL so I can cancel the overclocks when it's switching coins.

I had the same exact problem with RX 6800 XT-s,any time the DAG were to be recreated while cards being overclocked it would stop mining or disable one of the cards,usually the card with the error.I fixed this by using the command line argument in start-miner bat file which adds up to 14 DAG-s to come mining without problems.The command is : -eres 2-14(number of Epochs) 14 is the maximum,I set it to 6 or 8 usually.No problems after applying this so far.

Looking again at the reread me file... It appears phx created a command of -mcdag that puts the overclocking to default till after the dag is built. Will have to give this a try in the bat.file

This only works If you are using the overclocking within phoenixminer. If you use an external program it won't work