The problems of Lack of Rops that had been reported on other NVIDA cards are also affecting the RTX 5080.

Some NVIDIA RTX 5080 also have less Rops than they should

During the past week, some users observed how their RTX 5070 TI He had less rops than he should. And it seems that this problem has not only affected the last card that Nvidia has launched to the market, but is something general of The entire RTX 5000 series.

Without going any further, a Reddit user shared a GPU-Z capture this weekend, in which he showed that His RTX 5080 showed symptoms of lack of Ropsthus joining those who had already reported from the RTX 5090 and RTX 5070 TI.

Now, Nvidia has confirmed that this problem is real, although according to its data, it is something that “alone” has affected 0.5% of cards that have occurred. The good thing is that Ben Berraondo, Global Director of Public Relations of Geforce, has confirmed that all those who are suffering this problem will be able to request a replacement.

After a deeper investigation, we have identified that an early production version of the GPU GeForce RTX 5080 was also affected by the same problem. Affected consumers can contact the plate manufacturer to obtain a replacement.

Based on the data that have been reported in recent days, it seems that it would be quite easy to determine their Nvidia cards are being affected or not by this problem. Using the GPU-Z applicationwe could see that the Rops units would mark the following:

  • RTX 5090: 168 ROP instead of 176 rop
  • RTX 5080: 104 ROP instead of 112 rop
  • RTX 5070 TI: 88 ROP instead of 96 rop

In addition, Nvidia has also confirmed that this absence of Rop is a “Average impact on graphic performance of 4%without affecting the workloads of AI and processes », as well as reiterating that those who have been affected by the problem request a replacement.

We recommend you best market graphics cards.

We will have to see that all this ends, but what is clear is that the launch of the RTX 5000 is being much more spectacular than we could have expected at first.

Shares:
Leave a Reply

Your email address will not be published. Required fields are marked *