The problem is on some cards, the OC doesn't even have to be that aggressive for it to lose its mind.

Anyone with RTX cards having issues with invalid shares with Phoenix?  I just picked up an RTX 3060 TI for my htpc, and the only way I can get Phoenix to work without spamming invalid shares is to start it up with no OC applied, then apply overclock when it starts hashing.  Otherwise, it will just repeatedly generate invalid shares.  This workaround would be semi-acceptable except that after an indeterminate amount of time, it will fall back into repeated invalid share generation, which requires stopping the miner, removing overclock settings, restarting, and again re-applying overclock after it starts hashing again.  I've tried the last 3 releases and various driver versions, and nothing fixes it.

It seems like other people have had the same problem for months: https://www.reddit.com/r/EtherMining/comments/khi084/rtx_3060_ti_incorrect_eth_share/

Anyone seeing decreased performance with 1080 Ti now? 1070s have had reduced performance for a while, but 1080 Ti seemed to be hanging in there pretty strong with eth pill.  Now, I'm only getting 34-35 MH/s per card; down from 40.

You're only the second person I've seen that stated nVidia is aware of this issue and acknowledged it's a driver problem.  Can you share a link?

I'm curious if anyone knows why GTX 1070 performance has dropped on Eth.  I still have a bunch of them on various Windows and Linux rigs.  They all easily hit over 30 MH/s in the past and many were in the 32-33 MH/s range.  Now, they are lucky to to hit 30 and many are 28-29.  This is the case with both Claymore (with and without strap settings) and Phoenix.   Oddly, my 8GB RX 580s still chug along happily at 30-31 MH/s (i.e. they don't seem to have been affected by whatever is responsible for slowing down my 1070s).

These new supercharged versions (both 14.6 and beta versions) have been pretty frustrating for me on GTX 1070s.  Some of my cards simply cannot be made stable even with straps set to 4, sintensity set to 1, and cards using stock settings.  Anyone else run into this?

* Edit * Going back a bit, seems like others with 10 series are having issues as well.  Bit of a dud release for 10 series, IMO.  Not worth an extra ~10% hash when it's this flaky.