For those who may suffer from this issue here's something to try...rename UserCfg.opt, relaunch the sim and let it create a new. If it starts okay you know you had a corrupted file.

In my case I had quit the sim the previous night and it seemed an orderly shutdown. Next day I launch the sim and after the initial screen when it expands the window to full-frame black I got instant crash.

Ends up it was a corrupted UserCfg.Opt - but how...of course that's one of the great mysteries of MSFS

I found a single setting that had changed (once again, HOW?). The only reason I saw it was that when comparing the corrupt file to one newly generated by MSFS I found this"

{Graphics
    Version 1.1.0
    Preset Custom
    {Texture
        MaxAnisotropy 1
        Quality 0
    }

I was certain I had it set to 16 (which is how it was set in the new UserCfg.opt) so I set it that way, replaced the new UserCfg.opt with the old one with that one change and the sim fired right up.

My ctd occurs on the 40th anniversary screen when the progress bar is at about 50%.  Started doing this a couple days ago.  I'll give your solution a try.

tried it, no go.

Edited February 22, 20233 yr by jjn47

jjn47,

I would not expect my fix to work as it appears MSFS accesses the UserCfg.opt very early in the startup process. Obviously you should try with a completely empty community folder (just rename it and create a new empty one). If that doesn't work rename exe.xml and see if it will start. You could also try the "Repair" function in StartMenu:settings:apps - Left click on MSFS and select "Advanced options" - "Repair" (DO NOT SELECT "RESET"!!!!!)...you won't lose any settings or have to reinstall anything, but it may refresh bad or missing file/s, but it may fix your MSFS startup problem.

Let us know what you find.

All this information is very useful. I have had a recent "factory reset" happen to me on startup one day. I have now screenshotted all my settings and backed up those cfg files. Ironically, MSFS runs miles better since that happened.

I too have been getting a CTD just after the initial colourful splash screen.  It occurs when its about to change to a full screen.  Been doing this on 99% of the sim startups for about 6 weeks.  On second sim start it gets further and I have to click continue on the sim crashed warning.  Event viewer always states its the ntdll.dll that crashed.  Removing cpu or gpu overclocks does not help. Empty Community folder in past also didnt help.  Ill check some suggestions mentioned here.

 

Chris

A bit more info regarding my case:

Nothing I did would make MSFS successfully start UNTIL I logged out of XBOX app, logged out of MS Store, logged back into Store and XBOX, renamed UserCfg.opt then started MSFS from the XBOX app. A couple of things are at play here but I can't put my finger on the exact sequence that makes it not start. I normally start MSFS using the FSUIPC .bat quick start file to make MSFS start without many of the opening splash screens. After I got everything working again I tried using the FSUIPC .bat start again and MSFS won't start. I suspected corruption in the .bat causing a hiccup in MSFS. Unfortunately even reinstalling FSUIPC which installed a new .bat start file MSFS will not start using that method.

I have no idea what happened. The night before I started MSFS as usual using the fast start .bat, did some flying, shut down, and next day it was all broken.

MSFS has been trolling us since at least 2004.

My time with CTD's was finally terminated - I spent this evening re-installing after trying to get out of the beta. It became unbearable, and felt no repulsion in wiping it out. Now everything is working great.

Okay my problem ended up being Process Lasso. I uninstalled it and all was back to normal. Reinstalled Process Lasso and everything still okay. Obviously some incompatibility developed (for whatever reason) that was resolved by uninstall/reinstall.

Faulting module name: WwiseLibPCx64P.dll - was the error I was getting in Event Viewer. I did a search for that and found a couple of related threads on Microsoft MSFS forums, including: https://forums.flightsimulator.com/t/process-lasso/429206

AND: https://flightsimulator.zendesk.com/hc/en-us/articles/4406047820690-How-to-troubleshoot-crashing-on-the-loading-screen-issues

Samples of apps and programs preventing Microsoft Flight Simulator from launching

• Seagate Toolkit
• Nahimic service
• Asus Sonic Studio 2
• Windows Audio Service
• Garmin Express
• WD Backup
• Logitech G Hub
• MSI Afterburner / Riva Tuner Statistics Server
• EVGA Precision
• OBS
• Xsplit
• Discord
• MacType
• Warsaw Banking App
• Wallpaper Engine
• A-Volute Sound studio
• Capture One
• MSI afterburner
• Process Lasso
• FRAPS
• Citrix

Yeah, not to put anyone or their solutions down in this thread, but I don't think any of you have isolated the issue.

As mentioned, the usercfg.opt is loaded very early, so should ideally produce an early crash.

I can't imagine a login loop should be the issue - I had issues with that and it just told me I didn't own MSFS.

And I can't imagine it's Process Lasso either, owing to how many people are having issues with CTDs versus how few people use Process Lasso. I've never even considered using it as it just sticks out in my mind as an old P3D and FSX trick, and I don't need the performance boost.

 

Seems like it's probably a totally unrelated, completely different issue, and you're all reaching a solution that works but probably isn't repeatable.

PLS REMOVE

6 hours ago, mspencer said:

Yeah, not to put anyone or their solutions down in this thread, but I don't think any of you have isolated the issue.

Was there supposed to be some kind of point to your post, because you've offered nothing to anybody here to help solve CTD's.

Keep the discussion civil please. Childish comments will not be tolerated and may result in a holiday.

19 hours ago, mspencer said:

Yeah, not to put anyone or their solutions down in this thread, but I don't think any of you have isolated the issue.

As mentioned, the usercfg.opt is loaded very early, so should ideally produce an early crash.

I can't imagine a login loop should be the issue - I had issues with that and it just told me I didn't own MSFS.

And I can't imagine it's Process Lasso either, owing to how many people are having issues with CTDs versus how few people use Process Lasso. I've never even considered using it as it just sticks out in my mind as an old P3D and FSX trick, and I don't need the performance boost.

 

Seems like it's probably a totally unrelated, completely different issue, and you're all reaching a solution that works but probably isn't repeatable.

I tried Process Lasso years ago, when I had P3D. It immediately screwed up my audio in the sim. I uninstalled it and wouldn't go near it after that. 

On 2/22/2023 at 1:23 PM, somiller said:

jjn47,

I would not expect my fix to work as it appears MSFS accesses the UserCfg.opt very early in the startup process. Obviously you should try with a completely empty community folder (just rename it and create a new empty one). If that doesn't work rename exe.xml and see if it will start. You could also try the "Repair" function in StartMenu:settings:apps - Left click on MSFS and select "Advanced options" - "Repair" (DO NOT SELECT "RESET"!!!!!)...you won't lose any settings or have to reinstall anything, but it may refresh bad or missing file/s, but it may fix your MSFS startup problem.

Let us know what you find.

Thanks for the suggestions.  In the end, I had to reinstall MSFS to get back up and running.  Thanks for taking the time to try and help.