Repeated crash to the Windows desktop

Bug Reporting Hub Install, Performance & Graphics
,
26

YES. I Installed that driver.

27

It is not related to the pilot, yesterday there was another one and it was not working either.

28

thank you, I will go there.

29

Please inform me how to post the event logā€¦Thanks

30
31

Hi Phil, I can locate the event viewer easily enough, I just donā€™t know what to do with the info or how to send it to someone who does

32

It doesnā€™t matter, if you canā€™t do it.

33

Have you tried doing a completely fresh Nvidia driver install by removing it completly and not just doing the update.

34

do you overclock your CPU?

if so, try to disable the oc (reset bios settings to default)

i got the ctd issue after the simupdate3. apparently it doesnā€™t like an oc-ed cpu.

(fyi other games are fine with my oc cpu)

35

Iā€™m getting CTDā€™s now every time after latest update. 40 min flying max, and it crashes. I have nothing in community folder. Iā€™m so turned off setting up any full flight because I now anticipate it will CTD. Pathetic actually.
(i7 10700k, 3080, 32g, no OC)

2 Likes
36

Iā€™ve been having the same problem since the last update. Before then, it was working fine. Then all of a sudden Iā€™m getting all sorts of erratic behavior:

  1. MSFS was loading, then stalling for minutes at something like 360k memory usage. Then it would miraculously go to the opening screen, take forever on that, then if I was lucky would go to the update screens and maybe Iā€™d get a main menu. This seemed to be fixed by upgrading the nVidia graphics driver. Go figure.

  2. Before that was as bad an issue, I had repeated crashes about 40 minutes in. This happened multiple times between Dallas and KMCI, as well as on the West Coast at one point. Still happening.

  3. Now I have an issue where MSFS will load within an appropriate time frame and get to the update screen. At about 75% progress bar it promptly crashes to desktop.

  4. The CTD when starting a second flight is a bug that has been around through at least one update now.

The errors in the application log are next to worthless. The crashes appear to be in seemingly random modules, either FlightSimulator.exe itself, random DLLs (nvwgf2umx_cfg.dl, d3d11.dll, and some desktop core DLL). Asoboā€™s response was the usual form letter saying disable all community mods, disable overclocking, turn off antivirus, run as administrator, and the usual nonsense. None of it works.

The only thing left to do is wipe it and completely reinstall it. Ordinarily Iā€™d have a difficult time believing that the program canā€™t verify its own files, but given what Iā€™ve seen with this rollout nothing surprises me anymore. We have nonfunctional planes, no ability to load and save flight plans in the Garmin, basic aerodynamic oversights, a community mod system produced by Asobo which doesnā€™t perform sanity checking and allows the mods to crash the game with no indication of what went wrong, no error messages which are worth anything, and a default response from the developer to remove all community mods even though theyā€™ve been complicit in them being promoted on the commercial secondary market.

Right now, what weā€™re getting from the developer is basically:

Customer: Your program is crashing with no indication as to why.
Asobo: Turn it off and turn it back on again. Update graphics drivers. Reinstall the entire thing. Uh, reinstall the entire OS.

Iā€™m about ready to go back to X-Plane which, while maybe not pretty, actually works.

3 Likes
37

Itā€™s now become so ā€œunprofessionalā€, it borders on criminal! Itā€™s like this would make a great story about a huge corporate ā€œscamā€ to fleece the public.
Perhaps it never really was ever a finished and tested/proven game? Promises and promos made before release depicting a functional and improved 21st century version of FS. Perhaps it was all intended, to grab millions of dollars, then worry about resolves down the road (where we are today)?
Very very $uspect at this place in time :face_with_monocle:

1 Like
38

Thanks for the idea but unfortunately it is of no use, older generation Nvidia drivers are automatically uninstalled before the new driver is installed.

On the other hand, I noticed that Nvidia now offered ā€œStudio Driverā€ drivers to developers, after having installed them MSF 2020 continues to crashā€¦

39

Thank you for your advice, however I doubt this will work for meā€¦

I presume you had overcklocked your CPU by increasing the bandwidth of the PCI-E bus, is that correct ?? For example by going from 2400 Mhz to 2600 Mhz for the CPU, RAM, graphics card, etc ??

If so, this is the worst overclocking you can do in terms of stabilityā€¦ Iā€™m not surprised you had issues.

Indeed my system is basic overcklocked but using only the unlocked multiplier coeficiant of my CPU (i7-5960X Extreme Edition). It has been operating in a very stable manner for years, without ever having had any problems. I work with this system under Linux which requires much more stable systems than Windows and I have never had any problems.

Another point is that Asus, which is the manufacturer of my motherboard, is overclocking my base processor to 3.5 Ghz with the default bios, this to remedy the loss of computing power since the bios update to address critical security vulnerabilities Meltdown & Spectrumā€¦ So I cannot act on this point.

But thanks for the ideaā€¦ As I am an NT system engineer by profession, I have already gone through the majority of the ideas that could allow me to play MFS 2020 without problemsā€¦

Iā€™m afraid that only Microsoft, Asobo Studios, or Nvidia can really do something about my current problem ;-( We are at H + 48 hours that this problem exists for me and many other users and no fix is currently available ;-( And after at Microsoft, they are surprised that their customers are leaving them for Mac OS or Linuxā€¦

What saddens me the most is that in recent years, we have been sold hyper buggy software worthy of Beta versions, while we have bought software in final version (RTM). Unfortunately, Microsoft does not behave better than the others for thisā€¦ Such processes are totally disrespectful to the end users that we are, so we can only suffer from big bugs and be totally unsatisfied with the way we are being treated ;- (

1 Like
40

and the issue started with it ?.. so we have a possible cause, or ?

Already tried to re-install the former nvidia driver ? ( @Phil995511 you too ? )

Own you also the RTX 3080 ?

41

My overclock was done by modifying the multiplier not the base bandwidth.

I had been having the overclocking also for years without issue with other games and even it worked fine with MSFS before the Sim update 3.

After this simupdate3, I always had crash (CTD) while loading the flight. I tried everything without any luck.

Then, I turned off my overclock and the sim is working fine.. no more CTD. I know this sounds weird, but it works.

42

I removed MSFS, all community mods, and reinstalled. Start time was very much improved. Instead of taking 10+ minutes delay and pacing around, the splash screen came up and it appeared to have been actually doing something. I was plonked on the ground without an issue.

I went and started a flight from KOKC to a strip about 68 miles away. As I approached the runway on final, the program did it's stereotypical ā– ā– ā– ā–  where it halted the sound, suprted twice, and then crashed to the desktop. As usual, the error messages weren't helpful, but this time mentioned VCRUNTIME140.dll.

- System
  • Provider

[ Name] Application Error

  • EventID 1000

[ Qualifiers] 0

Version 0

Level 2

Task 100

Opcode 0

Keywords 0x80000000000000

  • TimeCreated

[ SystemTime] 2021-03-17T17:38:00.6108783Z

EventRecordID 40475

Correlation

  • Execution

[ ProcessID] 0
[ ThreadID] 0

Channel Application

Computer DESKTOP-USQTT9U

Security

Blockquote

  • EventData
    FlightSimulator.exe
    0.0.0.0
    6040b793
    VCRUNTIME140.dll
    14.28.29231.0
    5f4c66c9
    c0000005
    00000000000012de
    6870
    01d71b4e508643f8
    C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
    bca435f3-eaaa-404c-8b55-ad6d93133453
    Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe
    App

Blockquote
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6040b793
Faulting module name: VCRUNTIME140.dll, version: 14.28.29231.0, time stamp: 0x5f4c66c9
Exception code: 0xc0000005
Fault offset: 0x00000000000012de
Faulting process id: 0x6870
Faulting application start time: 0x01d71b4e508643f8
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.29231.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report Id: bca435f3-eaaa-404c-8b55-ad6d93133453
Faulting package full name: Microsoft.FlightSimulator_1.14.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

43

It was the latest patch for MFS 2020 that made the game impossible to play, not the Nvidia driver. Please read the above articles before posting.

1 Like
44

If your overclock was done by modifying the multiplier not the base bandwidth and that your system was 100% stable before that, this raises some questions as to the obscure reason why MFS 2020 will reject overcklocated CPUā€™s !? Especially since we both have series of unlocked multiplier CPUā€™s that have been sold to us as certified valid for overckloking by Intelā€¦

45

After rereading your strange experience, and to be 100% sure, I finally just reset my motherboard bios settings to default, but the problem persists as I expected.