sniper31

Well, so much for SU14 now. Out of two flights conducted, same friggin' SU13 CTD error code. I give up....all different hardware, complete reinstall, vanilla MSFS and same old CTD as SU13 and SU14. Argh.....

Yes, Jack, I am. That is the only way to test and see if the CTD is the same (if it happens at all....hopefully it won't). 😉

So, I have returned from a ski trip the other day, and have got MSFS all updated with SU14. I have loaded up a flight and just let it sit there for a few hours while I was doing other tasks around the house, and no CTD. BUT, and I stress but, I have not yet had the time to conduct an actual flight from point A to B to see if I get the old SU13 style CTD. I should be able to get one in later today or tomorrow. We'll see what happens.

Great stuff Vincent! Thanks for all of your efforts 🙂

I guess you have not read the entire (long) thread, or you would have seen that I tried changing out ALL hardware and I STILL got the same CTD. So, doing what you suggest is not going to accomplish anything in my situation. Thanks for the suggestion anyway. I have been out of town for the last week, so I cannot do any troubleshooting right now. But, there is nothing left to do, as I have shown, except wait for SU14 or Asobo to fix the issue.

One of my favorite things about flight simming is being able to jump in my aircraft of choice and fly anywhere in the world that I fancy at that given time. As for this time of year, I LOVE winter (that's why I live in Colorado) and winter means ski season to me, so I am all about the snow. And I don't mind shoveling as I just put in my earbuds and treat it like a little gym workout. No biggie. 🙂

Interesting!

It's all good, I appreciate the support from all the peeps in this thread. You are right, that error code is very much a non-answer, and AS/MS has not helped me at all either. Focus on your moving, as that is way more important than my sim issues 😉

Gotcha

In my case, NO, not during final approach. It happens to me right when I hit the Fly Now button, sometimes in mid-flight at cruise altitude, or after I have landed and have reached a parking spot (at either a busy or completely empty airport). This is the exact same SU13 CTD error code I have been getting.

There is a lengthy thread over on the MSFS official forum, with a vote button.

Well, just for gits and shiggles, I gave this potential solution a shot. Well, NoGo, it did not work for my SU13 CTD issue. On my very first flight, about 2 hours in, MSFS CTD with the same error code I have always gotten since SU13 was released listed in my Event Viewer. So, yet again, another arrow pointing to a SU13 coding problem. So far, the only successful work around that has worked for me is cutting my NIC's data speed way down, to 100Mbps Half Duplex. <sigh>

Don't know what I quoted my own post.

No worries 🙂

Thanks for the post Andy. And thanks to our friend that passed it on. However, a couple things regarding my CTD. First off, mine is not of the zoom in/zoom out variety. I can spend hours on the MSFS flight planning map and zoom in/out to my heart's content without any problems whatsoever. My CTD happens either A) when I hit the FlyNow button or B) when I am in mid-flight. Secondly, I am not in Windows 10. I have been running Windows 11 for about 8 months now. So, the error code that I am getting is the error code that I am getting. I don't think my CTD error is related to the MSVCP140.dll as I don't get that faulting module listed in my Event Viewer. Lastly, somebody several pages ago suggested that I reintstall/upgrade my Microsoft Visual C++ and I already looked into that. Again, appreciate the help, but I really don't think my CTD is the same as what you are experiencing. They could both be products of SU13, that would not surprise me. But I believe the zooming CTD and the in flight CTD are not the same. Just my opinion based on all my troubleshooting and research.

This video covers it: (1) 🚀⚙️ How to change Link Speed of Ethernet Adapter Windows 11 ✅ - YouTube

Yeah, I'll get them all installed eventually. But, I am a methodical troubleshooter, so I am not going to install them all in one big whop. Install, some test flights, rinse and repeat. I don't want to change the variables too much at once. At this point, the limiting my NIC data speed to 100Mbps Half Duplex workaround, and I stress, workaround-not solution, seems to be the answer right now. I can only hope that Asobo/MS fix the coding issue that they introduced with SU13, and I can put my NIC back on Auto-Negotiation and leave it there so I can enjoy my high data speeds that I am paying for.

My bad...should have read your quoted text. Sorry.

Not the cause of my CTD's because I get it even with a vanilla install of MSFS and no WU's installed.

I do not have any version of MS Office installed on my sim PC. Yes, I have sent the crash report to Asobo. No response at all. I have tried both DX11 and DX12 (pretty sure you've already asked me that;) ) Tried all kinds of different GPU drivers, old, new, middle.

I do indeed have Nvidia "stuff"... I have an MSI RTC 4090 GPU (listed in my sig). But, no Windows updates anywhere around the time of SU13. Drivers, Windows updates, GeForce settings etc, those are all in the early stages of my troubleshooting and things I have checked off more than a few times already. Here is a copy of my Event Viewer notification when I get the CTD: AppName FlightSimulator.exe AppVersion 1.34.16.0 AppTimeStamp 00000000 ModuleName FlightSimulator.exe ModuleVersion 1.34.16.0 ModuleTimeStamp 00000000 ExceptionCode c0000005 FaultingOffset 00000000023f9441 ProcessId 0x18d8 ProcessCreationTime 0x1da14d700431f8e AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe ModulePath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe IntegratorReportId 37124043-c1b6-49d7-96b0-231872851dac PackageFullName Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe PackageRelativeAppId App The only thing that changes when I get this CTD is the Faulting Offset code...that one is different every time I get the CTD.

Haha!!!!!!! Good one! 😁

I will have to check this one out! I have been happy with every one of your other sceneries that I have tried 🙂

I have not installed all the WU's yet. I have three WU's installed (both USA ones and a Europe one) and everything else still default. I am wanting more successful flights before I add anything else. When I do start adding stuff, it will either be one at a time or small groups of items (like scenery). But, I am nowhere near ready to start that yet. All that said, I pretty much ruled out addons being the cause way back when I had a brand new fresh install of MSFS during this process and still was getting the same CTD. So, think conflict all you want, but when I had a fresh new install of MSFS, there was nothing to conflict with, and I still would get the CTD. I am telling you, it is something within the SU13 code that is affecting some of us. There is nothing else it can be at this point.

Yes, agreed, it is indeed a rather vague error code. From what I can surmise, and also based on all of my testing and research, it at least tells me it's a software error code of some sort(s). In my situation, I have ruled out hardware, which if you have followed this thread are more than aware, but you are right. Trying to nail down what software issue the code is pointing to has proven extremely difficult. Maybe if I climb on top of my PC desk and do a kabooki dance, burn some incense, and chant in basic programming language, the solution will present itself. 😁 It's getting to that level....geez, I need a vacation...lol.