Earlier, I posted about the numerous complaints relating GeForce GTX 970 issue with memory allocation and also highlighted some reports of VRAM bandwidth issue. The complaints were very large in numbers and also can be searched easily in GeForce forums. Responsible PC Tech journalists, reviewers and news reporters (like Hardware BBQ) have highlighted this issue and also have put forward possible explanation for this error. But at the same time, the internet was filled with reports and also posted a video of in-game recording with GTX 970 where glitches and stuttering could be easily noticed.
It was also hoped that this might get fixed with maybe a BIOS or drivers, but it seems that the problem is an error in providing technical specification to all news sources and reviewers. As a result, Nvidia corrected its specification for GTX 970.
As a fellow source for responsible and credible information pointed out in much greater detail, one of the four ROP/ memory controllers on the GTX 970 is partially disabled. The original technical marketing materials and even reviewers guide pointed out that all the four ROPs were fully enabled. As a result of correcting their specification, it is now pointed out that GeForce GTX 970 has 56 ROPs and 1.75MB L2 Cache.
But it should be noted that in this diagram, 4GB GDDR5 with all four cores are fully enabled with 4GB DDR5 and 256-bit memory bus. As far as specifications disclosed officially on the packaging of its respected AiB partners are concerned, they are delivering what is promised.
The below images are the original and updated GTX 970 core diagram. You will be able to notice the difference clearly when you see the top-right area of the updated GTX 970 diagram.
While Nvidia updated technical information that’s usually given to news source and review sites, it doesn’t change the end result. GTX 970 is working the way its supposed to work so existing don’t need to worry about. It’s a known fact that once the potential of a core hits the wall, it would show the signs of performance hiccup.
While this isn’t the problem in the core itself, this does probably put Nvidia in its embarrassing position where they have updated their information after the reports from reviewers and users of various resources. What should be appreciated is that large number of GTX 970 owners and responsible reviewers were able to identify the initially thought peculiar stifling performance, followed by sources that covered the issue from the start to finish.
Would this be a closure that all will be satisfied with or will they claim foul play? To each to their own. Had technical information was accurate from the start, this wouldn’t have happened. It’s just one of those days!