On 2/24/2023 at 6:23 AM, somiller said:

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

Quick thanks for this - I've been troubleshooting this same crash and it also ended up being process lasso. 100% repeatable if I've got PL setting affinity for MSFS. 

 

 

A long shot but try starting the sim as admin.  It changes the initial startup procedure.

sp

2 hours ago, KL Oo said:

Quick thanks for this - I've been troubleshooting this same crash and it also ended up being process lasso. 100% repeatable if I've got PL setting affinity for MSFS

No, the problem is not Process Lasso, but users who run with settings they do not understand!

2 hours ago, mwe_EDVK said:

No, the problem is not Process Lasso, but users who run with settings they do not understand!

I presume thats some kind of an insult but instead of retorting I'll just simply ask - What am I doing wrong? I'll I'm doing in PL is setting FLIGHTSIMULATOR.EXE affinity to CORE 0 - 5 (on my 7900X3D). Please enlighten me. MSFS will load just fine if PL isn't running when MSFS is launched. If PL is running MSFS won't launch. Launching PL after MSFS has hit the main menu is fine and casues no issues. Fill me in oh smart one. 

@Sky_Pilot071 Thanks for the suggestion but running FLIGHTSIMULATOR.EXE as ADMIN still results in a crash. 

Running with Process Lasso just fine but with an Intel 13900.  I set MSFS on the power cores exclusively, with every other app I find running on to the E-cores (Tobii, FSRealistic etc.).  They still run at 4Ghz, on the E-cores, and everything is fine.

The only thing I do not mess with is Windows (Explorer.exe) and 'system'  in the list.  No affinities are set for these, as explorer.exe it is known to want to pick its own cores, and crashes if you mess with them.  There is a note in the Process Lasso documentation to leave expolorer.exe alone.

My sim definitely works better / smoother WITH Process Lasso, so either I am very lucky, or it is just down to the different PC configurations and programs running, which we know it normally is.

Edited March 26, 20233 yr by bobcat999

17 hours ago, KL Oo said:

FLIGHTSIMULATOR.EXE affinity to CORE 0 - 5 (on my 7900X3D

wait, you have a 12c/24t cpu and you want to run MSFS at 3 cores…

Why?

8 minutes ago, mwe_EDVK said:

wait, you have a 12c/24t cpu and you want to run MSFS at 3 cores…

Why?

No, I have a 12C CPU (with SMT off) and I want to run MSFS on the 6 X3D cores....hence why I said Cores 0 - 5. 

Now, please enlighten me what I'm doing wrong. 

Edited March 27, 20233 yr by KL Oo

Sorry, I can't help you with this specific new CPU. 

There is almost no info or experience on the net regarding this processor.

I for one would let windows and amds v-core optimizer do their job without additionally limiting the cores.

Or I would try to assign CPU Sets in Process Lasso to MSFS so that MSFS uses these preferred cores but is not limited to them.