Original Post — Direct link

Does anyone else have this issue with the new nvidia driver 522.25?

about 2 years ago - Ubi-Milky - Direct link

Hello @S3lll thanks for noting this issue with the benchmark on Windows 11 using an Nvidia 522.25 driver.

Would you be able to specify which exact GPU model it is you use, so we can document this with our Division team to make them aware of the missing info?

about 2 years ago - Ubi-Perseids - Direct link

@S3lll Thank you for the information! Can you test to see if rolling back the driver helps to fix this issue with the benchmark, or if it still persists when using the older driver as well? Thanks!

about 2 years ago - Ubi-TheBerry - Direct link

Hey @chacachaca13,

Thanks for letting us know.

Please could you confirm the driver version number so we can note this to the team too?

As well as the GPU model you're using?

Thank you!

about 2 years ago - Ubi-TheBerry - Direct link

Thanks for getting back to us @chacachaca13.

GPU drivers are not necessarily made for specific titles - nor do they apply any sort of updates directly to any games.

Rather, they're designed in mind of improving performance for core titles. This is why you often see a driver noting it's ready for a new release game - as Nvidia have ensured their hardware can run it to the best of it's ability - it's not directly tied to the game in any capacity.

522.25 notes it's ready for some new titles, including Gotham Knights for example - when the previous driver was launched, these titles weren't out, so GPUs would be able to run them, but perhaps not to the best capacity or make use of the full GPU's capabilities. So these new drivers tell the GPUs how to best handle these new games, as well as support titles who use features such as DLSS.

But as a focus can be put into a select few titles, there can be elements which negatively impact older titles, as we may be seeing here. As noted - when drivers are developed, game devs are not working alongside them for every driver release to support every game, so in occasion there are some conflicts and performance may drop.

That's where improvements can be made to the game itself to allow it to better perform under that driver - or it can be noted for the next driver release (this isn't a stage we're involved in so the outcome can vary, we wouldn't be able to say for certain).

I hope this provides a bit more insight on drivers / games / and how they're made for a massive variety of GPU hardware and game software.

As for the core issue at hand here, regarding the benchmark;

  • @S3lll - have you yet tried reinstalling The Division 2? If not - please could you give this a try and let us know if the GPU metrics are still missing in the Benchmark test?
  • @chacachaca13 - We have an investigation open into PC crashes already which I feel would better suit your report and you didn't note checking the benchmark before rolling back - so I'll pass your report on as part of that.


We have a Pinned Thread tracking these crashing reports here, so please watch that for updates.

Thank you!

about 2 years ago - Ubi-Milky - Direct link

Thank you for your reply @S3lll and thanks for trying this, we will pass this information back onto our QA team investigating this issue, thanks again for your help.

almost 2 years ago - Ubi-Perseids - Direct link

@S3lll Awesome! Thanks for letting us know that the latest driver fixed this issue for you. 🙂