Update: rails going bananas and attempted solutions added to the OP.
I don't think it is the card in and of its self as I think the OP stated he tried the offending card in a different PC and there was no issue.
Just reread OP posts and actually trying the card in a different PC was never mentioned but I would recommend doing so if it is possible???
I've been in the process of persuading a friend to let me install the offending GPU in his rig. It's a little tricky for us to get together as we're usually very busy but we'll try to do it sometime this weekend.
I must add that I really appreciate your efforts to validate and address the issue as well as other members', including
@FYFI13 and
@Vya Domus
Look man, (yes, I'm back) I've given you a very informative response on the end of page 1 with several suggestions and most of all, means to *exclude* things on the list of possible causes, which is always helpful to narrow down to the real cause and actually fix something. I didn't even read this particular comment of yours earlier... but have you noticed how ever since I was gone, other members have ALSO pushed you towards trying to update things and actually guide us through what you've tried and what it does?
You may not like my tone of voice, but I'm not talking out of my ass here.
Your tone on that message remained neglecting and its contents as predictably redundant as your explanation about actual problem solving on your last post - as if it were remotely necessary.
As far as real fixes are concerned, you didn't really suggest any NVCP settings for instance, you just elaborated on their mere existence in a condescending way.
By "I would love to see your NVCP settings" you didn't ironically mean "omg you may barely know what NVCP settings are and/or yours must be a mess, next I'm being silly enough as to explain how NVCP works", did you? Because that's how it went.
You hadn't come up with anything that wasn't common sense to the very OP and certainly hadn't led me to trying anything different or anything at all for that matter, let alone "PUSHED" me into that.
"Pushing" doesn't work for me by the way, which you can't seem to notice but it sure isn't your most relevant perception flaw in the context of this thread, unlike dismissing artifacts as normal rendering issues.
Perhaps you have actually helped out other people, who knows, but your main take on this thread didn't acknowledge its mandatory particularities and ended up aiming the clueless - however relevant it may be to an "education of sorts" for random lurkers, it's not what I'm looking for, sorry.
Fortunately, I can't see that grand influence of yours over the actually aiding members as they sound quite the opposite.
In short, you didn't "ALSO push" me into action. As a matter of fact, you only offered me a potential piece of advice after having updated your very last post.
So nope, I haven't noticed how things started to flow ever since you were gone (not that it doesn't sound lulzy), it's just that some of the other members' suggestions demand more time, availability and logistics planning from myself and my friends in order to be carried out.
Although concise, the last post on page #1 turned out to be more informative/"an education of sorts" than the one you pointed out.
At the same time, your tone of voice is also one that alludes to the reason you've not solved the issue yet: you gotta get a bit more open minded towards the suggestions offered.
All suggestions were welcomed from the very beginning and I'm still open to them. They've been (and some will be) carried out as soon as possible.
I even tested my build on regular monitors in spite of the fact that my PC absolutely always worked just great along with my TV prior to the issues - still does with my HD 7990.
As you can see, I'm acid trip open-minded.
Regardless, you know, overly recurring suggestions already accepted plus obvious statements/criticism due to thread info neglect get tiring sometimes.
And am I really a guru now? I feel flattered man, all I try to do is make sense. All I said was, that these issues are not new in gaming, can be card/game/API specific, and this sentiment is echoed throughout this thread.
Don't hide behind your otherwise wondrous words, humble Guru3D.com.
Nice to know that you're being echoed like you deserve... Except you're not. People aren't that uneducated, they can think for themselves with the info provided.
I wish it weren't necessary to put it this way, but your first message is a poor overview of the OP
main link. In other words, although it seemed to pass for really pertinent, that post had nothing new or even somewhat unknown to offer to this thread in particular from the very start.
You made "great" sense when you tried to dismiss my thread right away as if I perceived regular rendering issues as aberrations.
One perhaps useful thing to add: if your card was working fine in the same games before, and still works fine in several games today that you've now also narrowed down to OpenGL titles, then your card hasn't suddenly died, it is the *least* likely issue. Save yourself the shipping cost, and look at software - or SOMETIMES - just give it some time, like a month, update your stuff again and watch magic happen as a bug has been fixed.
As for DirectX, you can try manually installing it but as far as I know, this is also part of Windows 10 upgrades and thus is already entirely up to date.
Even
EVGA OC Scanner returned no errors at all as already mentioned a couple of times. Yep, my card is not dead.
If my GPU happens to work properly on my friend's PC, I'll follow your suggestion, otherwise I'll RMA the thing to rule it out. It may be almost as silly as trying a different monitor, but I can't stand these issues anymore so I'm taking serious action.
As nobody else could replicate the errors, chances are that the GPU itself could be faulty though.
Only DX<12 can be reinstalled in W10 as mentioned but it didn't solve the issues, unfortunately.
I appreciate your edit despite our past divergences.