Hi, just upgraded from a 1650S to a 2060 and now I get CTD halfway through initial loading screen, no error message. Never had this problem with the 1650S.
I emptied community folder and disconnected joysticks. Drivers up to date through the Geforce app.
The 2060 runs fine on another game. It’s manufacturer refurbished (Gigabyte). Maybe there’s some background settings I need to reset that weren’t done in refurbishment?
Pls help.
What psu do you have? I had an issue where it would ctd halfway through loading up so I reinstalled the sim and that worked for me.
Thermaltake 750W Smart BX1 80 Plus Bronze Non-Modular
What does the error log say?
Check all cables are correctly connected and do a bios reset. While you are there check that you have the latest available.
How do I see the error log?
I went to bios, clicked optimize default settings and now when I go to boot up I get 3 screens:
Gigabyte - Diagnosing your PC
Gigabyte - Preparing Automatic Repair
Windows blue screen - Automatic Repair - Your PC did not start correctly bla bla
So I think I just made this problem a whole lot worse 
I suggested you click RESET to default settings, optimize usually will look for a profile which might be the problem. Once you’ve rebooted you might need to switch from onboard graphics to PCI-E.
While you are in Bios take a note of it’s version as the new card might need a newer version
After all that I suggest you update all of your mainboard’s drivers, especially chipset and then reinstall the GPU.
why ? 
You mentioned in generaly works your PC fine with the new card. Only MSFS run into an issue.
A possible error message can you find within the “Windows Event Log”.
Now you have to bring your PC / windows back to a normal running state. In case you changed some settings in BIOS try to revert. As mentioned is “default” often a good choice. Stay away from OC settings…
If you back to a normal running state and other games / app works again without problems, we can start to check whats possible wrong with MSFS. May be it can not handle these hardware change and reset of msfs is necessary, or it might help to only remove some existing config files ( e.g. UserCfg ).
Ok seems I fried the mobo so I’m back with new mobo, cpu & ram. Unfortunately the problem still remains. I put my 1650S back in and no problems. In the process of frying the mobo I also reinstalled windows, the game and drivers.
Also tried running as administrator.
By Windows Event Log do you mean Event Viewer? If so, what do I look out for in there?
And how do I remove the existing config files?
Thanks for your help.
Stupid question I’m sure but does the 2060 have extra power cables and if so are they enabled in bios?
(PS. not being familiar with all cards or boards I don’t really know if such settings really exist)
yes, I meant Windows Event Viewer. In case of Crash there should be errors logged ( currently the only ‘log’ we have for MSFS ).
To be sure: can you confirm, that the 2060 works in other applications / games quite well ?
If so, may be it is a invalid entry within the msfs config. I remember similar cases ( not exact same )…
At first you can open your UserCfg.cfg file and check which “Video Adapter” is configured.
( %AppData%\Microsoft Flight Simulator )
We had some topics about “clean setup”. It depends which version you own:
Not sure where in Event Viewer I go to see any crashes. Or should it pop up right in front of me if there is one?
I tried the 2060 on another game, Cyberpunk 2077, and it crashed upon initial load up, just like FS.
Put the 1650 back in and no problem.
So thinking I have a faulty card?
that sounds not good and more to a not MSFS specific issue. It can be a faulty card… ( if power etc. all correct connected ).
But also in this case you should can find a specific error in windows event viewer.
I link to a post with an image and a howto link:
I assumed you deleted the windows shader cache and (re)installed the nvidia driver using the advanced mode to remove the old driver?
These are probably not essential for some games as they rebuild shader cache automatically but MSFS may not know you changed GPU so I would say these are essential. Worth a try.
Also if you ever overclocked the old card, maybe some software might be doing the same to the new?
this brings me to an additinal idea…
In case you use Gerforce Experiance, check that you have disabled the Auto-Optimize Feature. The app should determine the GPU ‘switch’, but who knows ( Its allways recommendation to disable it ).
Worked out how to use it and I’m getting the following errors:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3
Faulting module name: d3d11.dll, version: 10.0.19041.746, time stamp: 0xfc177b9d
Exception code: 0xc0000005
Fault offset: 0x00000000001764a0
Faulting process id: 0x2aac
Faulting application start time: 0x01d78210cf35b679
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report Id: 793dd183-ecf4-43fb-9f9a-17ac7a5bfc54
Faulting package full name: Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
&
Display driver nvlddmkm stopped responding and has successfully recovered.
&
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3
Faulting module name: nvwgf2umx_cfg.dll, version: 30.0.14.7141, time stamp: 0x60ebe111
Exception code: 0xc0000005
Fault offset: 0x00000000002cd472
Faulting process id: 0x5a8
Faulting application start time: 0x01d7820ffe635227
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5d5c294bb8d17217\nvwgf2umx_cfg.dll
Report Id: f5ee3269-5a7e-4d7b-a00b-b8e86801b0fe
Faulting package full name: Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
If I google those errors there’s plenty of results, a whole new can of worms to try, don’t know where to start 
I have now, no luck.
Confirmed it was not set to auto-optimize.
Tried uninstalling drivers and reinstalling again, no luck.
… we know these error usually in hardware-issue situations ( or overclocking ).
But together with this “nvwgf2umx_cfg.dll”… hmmm… it can be also driver stuff. But you already re-installed just “all”.
Your windows is full up2date and 21H1 ?
I still feel this could be nvidia driver problem which is what this line is saying.
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_5d5c294bb8d17217\nvwgf2umx_cfg.dll
Did you run the reinstall as admin, did it ask you to reboot twice. I did do a manual reinstall a while back as I has some issues also. Also make sure you are not overclocking your memory (GPU and system).
I tried a clean install of the drivers again and used 452.06 instead of the latest. This time I managed to get to main menu and start a flight but as soon as it panned to my aircraft it crashed. Event Viewer said:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3
Faulting module name: VCRUNTIME140.dll, version: 14.29.30035.0, time stamp: 0x608dc4a3
Exception code: 0xc0000005
Fault offset: 0x00000000000014d3
Faulting process id: 0x1448
Faulting application start time: 0x01d782d02598a10b
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\microsoft.vclibs.140.00.uwpdesktop_14.0.30035.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report Id: 6c613c0b-29a0-4bc6-9441-acdc8ea1b48f
Faulting package full name: Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
&
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: FlightSimulator.exe (5192) consumed 18112638976 bytes, MsMpEng.exe (4000) consumed 236449792 bytes, and explorer.exe (5504) consumed 223109120 bytes.
I increased the minimum & maximum page file size and I got similar again:
Display driver nvlddmkm stopped responding and has successfully recovered.
&
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60c0b1e3
Faulting module name: nvwgf2umx_cfg.dll, version: 27.21.14.5206, time stamp: 0x5f34699f
Exception code: 0xc0000005
Fault offset: 0x0000000000042938
Faulting process id: 0x2dc0
Faulting application start time: 0x01d782d3c96afe5f
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_ba8c9c14f3d320cb\nvwgf2umx_cfg.dll
Report Id: d956cc1b-d871-4191-8b0d-32db24a5a442
Faulting package full name: Microsoft.FlightSimulator_1.17.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Thanks for the help everyone but I think I’ve run out of patience. Time to return the 2060, put the 1650S back in and hope SU5 brings the boost I need.
Maybe I’ll buy a 3000 series when prices come back to earth and hope that works.
may be these card have realy an issue… in meanwhile it looks like that…
I still think the card isn’t getting enough power … make sure it’s power connections are not daisychained but use totally separate feeds from the PSU or mainboard whichever is applicable.