22 minutes ago, SayAgain said:

Will try to make time this weekend … can you PM me the SimBrief export?  739 or 739ER?

Highly recommend trying the same flight with everything in the EXE.XML disabled … if you can.

When you were back at the desktop, did you check OS Event Viewer for errors?

FYI, ever since the SimAppPro/WinCTRL installs, I get a crash message when I shutdown Win11 …

”PilotsDeck.exe”: exception unknown … PilotsDeck.exe is a StreamDeck plug-in (I use 4 StreamDecks) … not related to your issue and doesn’t impact MSFS but something I need to get resolved and don’t understand why I started getting those errors after install SimAppPro/WinCTRL … possibly some conflict?

Nothing in event viewer after the freeze, neither while MSFS is still up or after I nuke it Task Manager.

Can't help with WIN11 as my system can't run it - stuck on WIN10 till upgrade.

2 minutes ago, P_7878 said:

Hi:

No, I was referring to very recent reporting of WASM related freezes and such in cases of PMDG 737 NG, that have started late 2025 and early 2026.

For example, here, below are 2 threads, in Feb. itself, right here in the Forum, but I understand there are others to be found on-line and in the PMDG Forum.

 

 

Thanks P_7878 but I have never had a WASM crash, mine are a sim freeze with sounds still playing.

57 minutes ago, somiller said:

mine are a sim freeze with sounds still playing

Hmmm … that tends to point to a GPU crash or audio conflict with GPU drivers.  But if it consistently (100% of the time) can be triggered at a specific waypoint, then seems unlikely a GPU issue.  

A GPU crash can be recoverable which would allow you back to desktop, BUT that would normally create a Application event error you would see in the OS Event Viewer.

A WASM crash would also trigger and OS Event Viewer entry.

Really odd that you don’t get any OS Event Viewer entry when you force MSFS to End Task via Task Manager … that should always create at least one entry.  Are you absolutely sure there are no critical or warning entries in the OS Event Viewer?

I did a couple more test flights today.

1.) Only MSFS2024 running with only PMDG739 in community folder. Took off from BWI after loading only fuel and passengers in the FMC - did not load a route or anything. I hand flew direct to BRUNC waypoint climbing to FL100 and got the predictable freeze turning at BRUNC.

2.) Closed MSFS2024, restarted my computer, launched MSFS2024 with only the TDFI MD-11 in community folder and hand flew direct to BRUNC as before with the freeze occurring during the turn at BRUNC.

So clearly it is not aircraft specific, and not related to any other addon, as none were active. Seems to be something in MSFS2024, but what, I have no idea.

At the moment of freeze CPU utilization was 27%, temp 53C, GPU 34% at 59C 64% VRAM at 64C, and 43% of 32GB sys mem usage. Response time graph in RTSS was a solid straight line - not a single spike.

No errors or warnings in event viewer within hours of my sim session.

I'm baffled by how predictable it is, what with the freeze at virtually the exact same location, or very close to it. I was hand flying both these tests so there was obviously slight variation in location, but it was close.

Weeks ago I did a flight to KBUF and experienced the same thing, repeatable freeze at close to the same location every time I tried it. Always relatively close to destination airport. For all these flights I flew tests with and without the airport addon, and cleared scenery indexes before each session and the freezes happen with and without addon airport.

I had considered that maybe it had something to do with Navigraph AIRAC in MSFS - but I uninstalled it before testing the above two flights.

And no I don't use any rolling cache.

3 hours ago, somiller said:

I'm baffled by how predictable it is, what with the freeze at virtually the exact same location, or very close to it.

Frequency of predictability is actually a good thing ... if it can be repeated by others (preferably an MS/Asobo QA person that would replicate and pass it along to the development queue).

Since BRUNC is Washington DC area ... only other suggestion would be to check to see if you have scenery installed such as Drzewiecki Design Washington Landmarks V2 or freeware Washington Landmarks.

 

Interested where this investigation will lead to…

At least, the a/c (PMDG included) have been ruled out so far.

It seems like a complex interaction between the PC or/and the scenery addons (?) of @somiller and MSFS2024.

10 hours ago, P_7878 said:

Interested where this investigation will lead to…

At least, the a/c (PMDG included) have been ruled out so far.

It seems like a complex interaction between the PC or/and the scenery addons (?) of @somiller and MSFS2024.

My most recent 2 test flights no addons were active in the community folder other than the aircraft I was flying.

I finally figured it out after uninstall/reinstall of 2024, DDU graphics driver and reinstall. After the reinstall of 2024 with nothing in community, no EXE.xml and new user.cfg I flew my standard test to see if I'd get the freeze and indeed it did freeze. I terminated MSFS2024 with taskmanager and I was looking in all MSFS 2024 content folders for potential suspects. In the WASM directory I found a subdirectory named bt_trains - instantly suspected I found the culprit. I had purchased FS Trains North America on the Marketplace and forgotten that I had it and the reason I never saw it was because it is streamed. I disable it in content manager, deleted the bt_trains dir. in WASM and flew my test flight with no pause.

I'm going to download that content and install it in my addons directory and link it with AddonsLinker and see if it works. Whether it works or not, at least I found the problem.

Nice bit of detective work, though the process has been probably rather exasperating...

Hi,

I observed and suffered from similar problems. They vanished after an update of the mainboard BIOS.

 

18 hours ago, P_7878 said:

Nice bit of detective work, though the process has been probably rather exasperating...

Indeed it was, including an unnecessary reinstall of 2024 and display driver DDU and reinstall.

Thanks to all for submitting suggestions - one of the benefits of AVSIM!!

Awesome troubleshooting and I must say, some highly knowledgeable help from @SayAgain 😎

I've fallen for similar tricks of the problem addon being in the official or streamed folders, and not Community.  I had foolishly believed that those folders were divine an incorruptable 😄

My sim will crash if I have Verticalsim Spartanburg in the official or streamed folders, even just when overflying it.    I had it disabled in MSFS2024 but I recently did a whopping great cache clean, content.xml and sceneryindex clean and it had (naturally) been re-enabled.

On 3/3/2026 at 12:15 PM, somiller said:

Indeed it was, including an unnecessary reinstall of 2024 and display driver DDU and reinstall.

Thanks to all for submitting suggestions - one of the benefits of AVSIM!!

You're a true warrior of the SIM...🙂...supported by a bit of handholding from the knowledgeable folks here...