I got my MSI Gaming 970 today, upgraded from a Windforce 670. I wanted to go for the Gigabyte 970 as it looks so much better, but the fanless operation of the MSI won me over. Silence is king.
First impressions are a little iffy; upon installation I noticed the card sagged a bit. The cooler seems pretty dense and for the life of me I cannot understand why they omitted a backplate. The card also suffers from coil whine; it is very faint at idle where it's inaudible if my ear is not right up against the card, and gets louder under load. Still, I should stress that it is not at all intrusive when my case fans turn on as the CPU is stressed.
The MSI logo on the side looks pretty cool as it lights up, although, again I favor the Gigabyte in this respect.
Overclocking-wise I think my chip is kind of average; Fire Strike began artifacting when the core clock exceeded 1500MHz boost. Haven't tested memory extensively yet, but it is currently sitting at 7600Mhz. Forgot to save the score, but as I recall it was something like 11200 with 13500 GPU and 12500 Physics.
I don't currently have a whole lot of games on hand to test, but a part of me is hoping the chip will allow me to increase core clock further while remaining game-stable.
Played a quick round of BF4, which now runs at a constant 60 (vsync on) on Ultra (2x MSAA) @ 1440p; I think that is very impressive.
The cards' fans have been behaving rather strangely. Setting a custom fan profile in Afterburner apparently results in one fan not spinning at all, while the other ramps up to 100% regardless of the fan speed value I assign in AB.
GPU-Z reports the same fan speed % as the value I set in AB, while displaying RPM=0.
I've now disabled the option to set user defined fan curve in AB, which means the card reverts to the default fan profile. This results in the card reaching the high 60s under load; I know that is well within safe limits, but a possible SLi config could be in the not-too-distance future where a more aggressive approach to cooling might be required.
Not sure if anyone else has experienced this issue, but I'd be interested in a possible fix.
That pretty much summarizes my impressions thus far.