very very good information Captain. Many thanks.
1 Like
Im on a 1080ti
For me 457.30 driver works the best for MSFS in VR and my other flight sims in VR.
All the later drivers are prone to hard crash with my other flight sims with VR sticking with 457.30 driver is a no brainer for now.
This theory about sticking with one particular driver may be fine if all your doing is playing MSFS. For a while anyway. The reality is that eventually you will be running with an extremely old graphics driver which could cause other underlying performance issues somewhere within your system.
Your best bet is to remember the driver version that you prefer and currently use. When a new driver update is issued, update the driver, like you should do. It takes all of two minutes to do. If you donāt like the result, then roll back. Again, it takes all of two minutes to do. A couple of clicks of a button.
Eventually you ARE going to find a driver that gives better performance then what you have installed. If not, you may need a newer video card. If you are unfamiliar with the pitfalls or risks of running old and outdated drivers, do some research. The information is out there. Iām really beginning to believe that computer laziness is the underlying problem with a lot of people.
2 Likes
For whatever itās worth, I was stuck on 457.30. On one Nvidia driver update attempt Windows went unstable and I had to rebuild but used my original Windows 10 media when I did it that was 4-5 years old. Still could not upgrade past 457.30. Iād get the really bad performance, stutters, etc.
I was ok staying at 457.30 until Nvidia announced that there was a huge security issue with drivers before 466.11. Tried updating again but still got stutters and bad performance.
Decided to rebuild Windows again but discovered that there had been about 12 versions of install media since mine was minted so I downloaded a new windows.iso direct from Microsoft and put it on a USB drive and did a full install of Windows again.
A fresh install of Windows from new install media fixed everything. I was immediately able to update the Nvidia driver to what was the latest at the time and am now at 466.47 (I think thatās the number but not certain - not at my system right now).
When I installed from my old media there were lots of updates before it was done. From the new .iso there were only a few updates but both versions were fully patched before I installed the Nvidia driver.
While configuring Windows I noticed the privacy and security menus for Windows had lots more granularity and options than I had ever seen before. Windows was fundamentally different in some way. Whatever the differences, the only change was building Windows from new vs old install media.
I believe from this experience that there are actually a number of versions of Windows 10 depending on the version of install media used to build it. I also think (but donāt know) that after 457.30, with the introduction of the 3000 series Nvidia made some change to how their drivers interact with Windows - either using new features or dropping old - and those new ways cause incompatibility with older heritage Windows installs.
All I know is building Windows from old media stopped me from updating past 457.30. A new build with new Windows media and my system works fine with new drivers. Same hardware. Same software other than Windows install media used to build it.
Microsoft and Nvidia need to sort this. Itās not reasonable to expect users to blow away and rebuild Windows to be able to update Nvidia drivers.
I wonāt tell others to do the same thing since itās a fair amount of work and pain to reinstall Windows, but if anyone is to the point of rebuilding anyway, use the latest .iso from Microsoft. Donāt use your original media. And please, please, let us know if it made a difference. So far it has for one other person who has tried it. They did a repair using new media instead of a full reinstall.
For anyone looking at this, I used Rufus to burn the .iso to a USB stick and Macrium Reflect (free version) to back up all my important Windows and user files.
2 Likes
The ā3 Big Liesā;
1- The check is in the mail
2- Iām from the government and Iām here to help
3- This version of software/firmware/driver will fix ALL of your problems
I was suffering from uncounted CTDās with 466.63 and decided to try the 457.30, because it could not get worse. Playing for app. 3 hours and not even a single CTD. Thank you so much guys.
1 Like
Not nice to hear.
I say they either get their act together and get their driver mess properly on track, or I will just buy an Xbox and they will not see me again the next 10-20 years. Did it before, will do it again. I am in just no mood for this endless tinkering with Windows/Nvidia combinations. Especially now that you pay a small fortune for a graphics card. Only to spend days on tweaking after being ripped off? I spend money to just play, thank you very much. Recently got my old Nintendo 3DS out. Was perfectly fine, relaxing and nice to play on the couch. No need to spend hours deciphering the latest&greatest mess of drivers and whatnot.
They should be aware that they do not have infinite credit and they will lose me as their most valuable customer. I hate to put that kind of pressure on them and apologize in advance for the late night emergency meetings at management level that my post will trigger 
actually, even better: I will buy pLAysTatIoN! Just to make sure MS/Nvidia are completely gone from my life.
isnāt that the truth 
1 Like
This is great news!
And the fact that latest update is finally on par with the > 1 year old version is also, well, kinda hilarious.
We all have different HW and SW configurations. Canāt we all agree on 1 benchmarking method? Isnāt there one? Iām assuming 1 fixed GFX config + 1 short flight plan all on autopilot + Afterburner recording the fps data. Then we can differentiate between drivers for one HW+SW config.
Indeed (wow I didnāt know.. what issue..)
My bottom line, if it works for you.. install 466.63 newer=better especially for xx80 and xx80 Ti boards..
at least give it a try,
When it does not work you can always roll back
Hereās a link to the security information about security fixes in 466.11. Privilege escalation is really bad because that gives malicious apps the ability to do whatever they want to a system.
Side note - computer compromises, ransomware, etc, are all on the rise and country vs. country tensions around the internet are also rising. Best to keep your systems as secure as you can.
I tried searching and didnāt see this posted. NVIDIA has a form where users can inform them of driver problems so that they can investigate. I suggest that we all let them know the problems weāre seeing and maybe then they will fix it once they realize how widespread our problems are.
(Here is the link to this Google Form on the NVIDIA website, if youāre cautious about random Google Forms)
GeForce 457.30 Game Ready Driver | NVIDIA GeForce Forums
For example, i just figured out that my CTDs are caused by NVIDIA panicking and restarting.
Getting the following warning in Event Viewer:
Display driver nvlddmkm stopped responding and has successfully recovered.
Followed immediately by CTD Error:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7
Exception code: 0xc0000005
Fault offset: 0x0000000001cb1d12
Faulting process id: 0x3380
Faulting application start time: 0x01d75df96d99d7e0
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: b254281d-db08-426c-921a-b9621bb9de1c
Faulting package full name: Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.