ZoranC

Piers123
It's a fresh install on an entirely new PC ... [Windows 11] is essentially a UX/UI update for Windows 10 and little else more. 

Windows 11 is far from "UI update for Windows 10 and little else more". To say that requires lack of even basic understanding for architecture underneath. Even if one could argue that Win11 is type of upgrade from Win10 the way say Win10 21H1 is to 1909 or older point remains that every time there are changes underneath the surface some things will break, it will take time to sort them out, and in the meantime those that jump early on will live on the bleeding edge and naturally some of them will ... well ... cut themselves.
 
Equally importantly you have also installed it -straight- on -completely- -new- build which means:
 
a) you haven't assured your system is overall stable when running something that is known as stable (Win10), and
 
b) you don't seem to realize brand new install of Win11 turns on by default certain security features that are turned off by default in Win10 and there are reports of people having Win11 stability issues until they are turned off.
 
Way I see it there are too many things in your build that are all under question mark at the same time for you to be able to start looking in the direction of video card and its drivers. If I were you I would, like I said, rebuild system from scratch as Win10, thoroughly test it, and take it from there.

ZoranC

Piers123
It's a fresh install on an entirely new PC ... [Windows 11] is essentially a UX/UI update for Windows 10 and little else more. 

Windows 11 is far from "UI update for Windows 10 and little else more". To say that requires lack of even basic understanding for architecture underneath. Even if one could argue that Win11 is type of upgrade from Win10 the way say Win10 21H1 is to 1909 or older point remains that every time there are changes underneath the surface some things will break, it will take time to sort them out, and in the meantime those that jump early on will live on the bleeding edge and naturally some of them will ... well ... cut themselves.
 
Equally importantly you have also installed it -straight- on -completely- -new- build which means:
 
a) you haven't assured your system is overall stable when running something that is known as stable (Win10), and
 
b) you don't seem to realize brand new install of Win11 turns on by default certain security features that are turned off by default in Win10 and there are reports of people having Win11 stability issues until they are turned off.
 
Way I see it there are too many things in your build that are all under question mark at the same time for you to be able to start looking in the direction of video card and its drivers. If I were you I would, like I said, rebuild system from scratch as Win10, thoroughly test it, and take it from there.

1. In terms of how the OS handles a GPU, Windows 11 is essentially the same as Windows 11.
2. As for how the user perceives Windows 11, it's a new UX and UI with few new features. Both operating systems sharing the the same kernel is telling, or should be. There are minor revisions, but I stand by my statement. You are free to label that as a "lack of even basic understanding for architecture underneath" if you wish.
3. Yes, a completely new machine that was purchased as a complete build which was extensively tested with Windows 10.
4. All components are certified for Windows 11 and all have drivers for Windows 11.
5. I have assured the system is stable, and it's been stability tested in Windows 10 and 11 at stock and overclocked (including AMP/XMP/DOCP which is, of course, overclocking).
6. I do realise that Windows 11 brings some new security features as that's part of the reason a TPM is required along with Secure Boot. None of the new security features should interfere with the clocks of the GPU in certain conditions, though I'm open to the idea which is why EVGA requested an email so it could be sent to engineers in Taiwan as, once again, EVGA states this is not normal behaviour for a GPU, regardless of OS.
7. Had you bothered to ask, rather than make vast assumptions, there would be fewer "things" you feel the need to question. I could have mentioned the Windows 10 testing, but it's not relevant as there are no other reports of this card with this BIOS having the same issue ion Windows 11, hence EVGA's interest. That being said and as stated above, I'm open to the idea of a conflict somewhere but I would have expected to see many more reports of the same issue.

Piers123

Sajin

Piers123
The same exact thing has just happened with Civ 6 - clocks down to lowest possible idle clocks (210).

Even with prefer max performance set? Something is definitely up.

That was using Nvidia's default 'out of the box' settings, so no Maximum Performance setup, but it still shouldn't clockdown during a 100% load. This time, it caused the game to crash (which is understandable). I then added it to the list in Nvidia Control Panel and changed to 'prefer maximum performance'.
 
It could be Windows 11-related, but I can't find a single report anywhere of this sort of thing happening. I can find plenty of reports of the clocks not being 100% if the load doesn't require it, which is entirely reasonable (my example above somewhere of GTA V at 4K high/ultra settings but with vsync turned on means much lower clocks).