CTD intermittent, i.e., load, on ramp 3 minutes, etc

nVidia released a new hotfix. Seems to be helping, but too early to say for sure.

It’s nothing to do with my system. Nothing was overheating and the throttle problem is apparently a bug with addon planes they haven’t fixed.

I do not have hardware problems this entire forum is reporting problems after the update but thanks.

question: have I misunderstood your post ? I thought you enabled the throttle ( I understand the piece of hardware you touch ) and it ctd ?

If so, please report for which airplane it happens, the installed mods, apps running in parralel, and if its a diiferent kind of error-code (…005) than the OP reported please also post the log.

it’s a little bit overstatet :wink:

Yes you’ve misunderstood my comment lol

okay… then may be add the additional informations that we can narrow down the problem.

I have no issues here with my usually used airplanes like the M20, junkers, etc … also the h135 mod works fine.

Still having the same CTD issues. Have suspended my Community Folder (renamed it and let MSFS create new one with nothing in it), taken all Windows Updates, etc., and still getting the following:

Processor Intel(R) Core™ i9-10900K CPU @ 3.70GHz 3.70 GHz

Windows Build Windows 10 Pro (64)

21H2

OSBuild 19044.1503

Installed RAM 32.0 GB (31.9 GB usable)

Memory CORSAIR Dominator Platinum

System type 64-bit operating system, x64-based processor

DISC Samsung 980 Pro 1 TB, Samsung SSD QVO 870 2 TB, Samsung 960 Pro 1 TB, Western Digital 500G Spinning

GPU EVGA RTX 3090 FTW3 Hybrid

MOBO ASUS ROG Maximus XII Extreme

Display ASUS ROG PG35VQ

Window Log Error:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000

Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x00000000015c1d59

Faulting process id: 0x51f0

Faulting application start time: 0x01d81c2fea1c324f

Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Report Id: 2b796096-b89d-484b-9516-099b0a667025

Faulting package full name: Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Faulting application name: FSUIPC7.exe, version: 7.2.1.5, time stamp: 0x61efef58

Faulting module name: KERNELBASE.dll, version: 10.0.19041.1503, time stamp: 0xb2acaea9

Exception code: 0xc0000409

Fault offset: 0x000000000008ead3

Faulting process id: 0x54a4

Faulting application start time: 0x01d81c302d870e45

Faulting application path: F:\FSUIPC7\FSUIPC7.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report Id: 6e4136e3-69de-41bc-87cb-9d275558fbff

Faulting package full name:

Faulting package-relative application ID:

ahh… now it becomes more hot :wink:

I assume with these you can find some topics and hints :
https://forums.flightsimulator.com/search?q=FSUIPC7.exe%20order:latest_topic
https://forums.flightsimulator.com/search?q=FSUIPC7%20order:latest_topic

PS: therefore we asking for parallel installed applications :slight_smile:

Well, I contacted John Dawson at FSUIPC. He looked at the logs both from Windows and the FSUIPC log. He replied that the error from FSUIPC is normal when MSFS ends abnormally. There is NOT an issue with FSUIPC.

now, its all we have for now… you can try some test-flights without. Otherwise we can only recommend the usually things, like limiting max fps, or playing with some multiplayer settings, etc…

At least, not 100% sure for the moment, it seems there is a relation to @BalloonJarl8918 topic with may be same tool / device in usage : Odd sound, then MSFS freezes, But only when looking to the left using track IR

I had to submit a ticket through Zendesk in which the AI stated it was a credential issue. Try logging out of the Xbox app, reboot, and then log back into Xbox. If that does not fix it then you will need to go through the process at Zendesk to have the AI reset your credentials.

I uninstalled and reinstalled MSFS and it would crash in the installer. Based on the information, this was caused by Xbox thinking I did not own MSFS. Yeah, that is right they don’t give you are warning or nothing, they just CTD the software when there is a credential issue. Weird in that it would start fine then CTD later.

Two days fighting with this game because of lousy DRM.

Roll back Nvidia drivers to 497.29 and try again. Fixed my problems so far.

I’ll try this. Nothing else has worked so far.

Follow these steps…

Have you Zendesked this yet?

They eventually got me fixed. It was a credential issue with the Xbox server.

Everyone here will assume it is your computer. For me it was not the computer, my computer ended up being just fine. Something happened on this last update that caused my credentials to become corrupted. Once I sent them the info to prove I owned MSFS they reset something and MSFS has been working just fine. With the DXDiag and HWINFO files, they were able to figure out it was a credential issue.

I also signed out of my XBox account, rebooted, and signed back it.

I didn’t resort to Zendesk due to this seeming to be an inherent problem that would only be solved with a new patch/fix/update. I’ll try that. I had tried the sign out of XBOX and back in last week to no avail.

Contacted Zendesk. They want me to remove everything (even though everything was working flawlessly before last update) and put in vanilla state. I removed my Community folder and flew a 172 for an hour without a problem, loaded my Community folder back and just received a different crash, but it didn’t go to desktop, just froze screen. Looks like I need to go back to Mr. Lawson at FSUIPC.
Faulting application name: FSUIPC7.exe, version: 7.2.1.5, time stamp: 0x61efef58
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1503, time stamp: 0xb2acaea9
Exception code: 0xc0000409
Fault offset: 0x000000000008ead3
Faulting process id: 0x6e8
Faulting application start time: 0x01d821e8b96665fb
Faulting application path: F:\FSUIPC7\FSUIPC7.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 340a0a62-23d6-42ef-8f25-e0838984af2a
Faulting package full name:

1 Like

Did you try reverting your video drivers as I suggested?

Yeah, I did that first before all the other tools you recommended that I ran. Still same error on 497.29. I have the 511.72 that NVIDEA put out last week as a fix and flew the 172 yesterday with my community folder empty without any error. So, it must be something in my community folder.

:laughing:

a note… I checked website and it seems there is a newer version present ( v7.2.16 ) … may be…

OK. I’ll try that. I’ve scanned, run check utilities, updated to latest NVIDEA driver today (that others say is working fine) dumped my community folder and still getting CTD. Still unflyable. I guess I’ll try the new version of FSUIPC now. The other thing I noticed is that the frequencies for my airport - KADS are all wrong when I have a blank community folder. That’s very wierd!

Well, I didn’t even get to the ramp this time before it CTD’d. I think I’m going to try to uninstall MSFS and start over loading back my mods one at a time.