omg that s the same i use currently 
Yeah, I’ve stated this a bit ago:
“575 branch shows much better results in inference workloads across the board (well, not ~next week’s 1st deployment 575 driver, but later May/June 575 branch drivers) and MS upcoming thingy… just hold on, folks”
If folks here still, after I urged them caution on the 1st driver of this branch, 575, before the likes of Jay even had a clue to this 1st driver (or any future drivers’ access results) deployment results of the 575 branch driver, downloaded and utilized the current driver without that consideration… WELP! 
I don’t see you urged anyone about Nvidia drivers and the associated problem highlighted by Jay, you posted under the bench marking section something about 575 drivers which I assume was a beta release that no one would run on a production system.
You said nothing technically relevant for anyone to head a warning.
1 Like
Ofc, YOU don’t. And Jay did NOT highlight
anything that wasn’t already known, to the inform for weeks of its deployment, that Jay, and others lack. But… that said, it’s ok to cheer for Jay and his clicks/viewers’ numbers.
Instead of responding with silly comments maybe explain better what you are warning us of ?
Silly? Strong word, fella.
There’s a 576.15 hotfix driver out now.
1 Like
I’m still on 537.58 since they introduced a deal-breaking bug after that. They still have not fixed it as far as I know.
522.xx, 527.xx, 537.xx, & 552.xx are the go-to drivers for Turing up to Lovelace SKUs!
Cant find the hotfix on Nvidia or Nvidia app yet.
1 Like
AFAIK they don’t deliver hotfix drivers through the app or the driver search page.
They usually have a stickied post in the driver forum:
https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/
I noticed you edited the post I replied to by a huge amount.
I’ve waited a week for you to collate your caution with evidence.
…and you should’ve also “noticed” that the OG post that I appended here was from the thread that I posted from (which you could look at that date when the last time the OG’s post was edited).
No witch hunt here. 
I’ll ask again, post the caution you warned us all of.
You appended nothing from OG post
TO
I posted the link to Jay’s findings in good faith for the community on here as I considered it a very serious issue. You on the other hand seem to have an ego complex about my post claiming you warned us all of this before Jay knew of it, yet to date you provide nada.
I’ve made my point and will close this now.
For what?! Uhm… I don’t work for you, fella! 
Only a few folks that I would even consider assisting here, now. Keep following your YTers, ect.
Now, I’m done with your frivolous mindset.
