In the GTX 970/980 thread, Harrison reports the same BIOS on his 970 as the card I was looking to buy, and found discomfort with it.

AgentX20 I wonder if the 980 is actually inherently bad or if the 980 you got had a higher VBIOS revision? I'm going to try and find a 980 with an earliest VBIOS as possible in 2014. The change happened late in 2014 / early in 2015 when the eye strain change took place in the VBIOS, so it would be very easy to buy both around the same time and have one have the bad VBIOS.

      degen Go ahead - it'll be an interesting experiment. Me, I dunno what to report.

      I've had a 980 and a 980ti and had strain with both.

      I've had multiple G1 Gaming 970 cards, some good some not good. The good ones are all V1.0 hardware - and not 1.1. However, I've also got a 1.0 card that is bad - at least last time I tried it.

      I have picked up one discernible difference however with the 1.0 hardware, that is - if I recall correctly the good ones (in my experience) all have hynix ram, and the bad ones have samsung ram. Why that makes a difference I've NO idea. There is a slight discernible difference in the cooling hardware (fins, heatsinks etc) that might suggest a different manufacturer... and hence maybe more differences, say in the output stage?

      Anyway, the main hassle I had with any further analysis is that the BIOS files are now hard to get - in that Gigabyte doesn't list all the versions on their site any more, and it's hard knowing what's what on these other random collections elsewhere.

      • JTL replied to this.

          degen AgentX20 The 980 came out at the same time as the 970 (late 2014) and the 980Ti came out circa mid 2015.

                JTL Yep, exactly, and which is why I tried both the 980 and 980ti to see if they were "good" like my 970. Sadly they were not...

                  3 months later

                  Guys, did we notice yet that last year someone found the working Windows registry key for Nvidia cards to enable and disable temporal dithering at will, and posted it in the official Nvidia forums?
                  https://www.nvidia.com/en-us/geforce/forums/discover/288245/is-it-possible-to-quot-port-quot-dithering-from-nvidia-x-server-to-geforce-driver-/#5934577

                  Sort by "oldest" and just after a few posts the member "Guzz" posts a list of all registry key states. Maybe you knew about it already and I somehow missed this.

                    KM I think I posted about it and others did too last year. IIRC W10 updates kept breaking it, and also results seemed to vary on a card by card basis.

                    • KM likes this.
                      12 days later

                      Gurm

                      "Additionally, WINDOWS has multiple abstraction layers before the output makes its way the screen. Color Profiles, color correction, gamma... all applied at the driver level, the card hardware level, the windows API level, the screen composition level... then again at the input and output phases of the display unit.

                      Windows 10 added ANOTHER layer, called "Composition spaces". The OS support for this began in the Anniversary Edition, which is why many of us find builds 1607+ to be unusable."

                      Can this be of any help?

                      https://github.com/Skymirrh/CompatibilityManager

                      or

                      https://www.nirsoft.net/utils/app_compatibility_view.html

                          4 years later

                          Anyway to disable those win composition layers ? Is there a Linux setup that's better than 1507 win10 / win7?

                          dev