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

Bug Reporting Hub Crashes (CTDs)
1

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

Windows Build Windows 10 Pro

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

GPU EVGA RTX 3090 FTW3 Hybrid

MOBO ASUS ROG Maximus XII Extreme

Window Log Error:

Log Name: Application

Source: Application Error

Date: 2/3/2022 12:17:26 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: PDW0623

Description:

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: 0x13f8

Faulting application start time: 0x01d81928c11f1c25

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: d99fcebf-7931-46db-a317-bdbe3a204a09

Faulting package full name: Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

Event Xml:

1000

0

2

100

0

0x80000000000000

60415

Application

PDW0623

FlightSimulator.exe

0.0.0.0

00000000

FlightSimulator.exe

0.0.0.0

00000000

c0000005

00000000015c1d59

13f8

01d81928c11f1c25

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

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

d99fcebf-7931-46db-a317-bdbe3a204a09

Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe

App

2

Given the amount of recent reports about CTD’s pretty sure the latest patch or the one before has broken the sim. You can psend hours trying to fix it yourself, or just wait for Asobo to get their ■■■■ together. Sucks I know, I just got a Honeycomb Alpha and Bravo but have given up flying since it just CTD’s constantly now. Before the latest patch I had no issues.

6 Likes
3

Yeah, same for me. Prior to this latest patch, no issues for me. I guess I’ll just wait till they send over a hotfix. It’s pretty much unflyable now.

1 Like
4

Try this…check latest WIN10 updates, NVIDIA Driver updates, Sim Nav updates then set you frame rate to 30. Worked for me. Currenly VHHH-YBBN - FL370.

1 Like
5

try the well known hints like remove rolling…cache, empty community-folder, limit fps, etc… we have lots of tips in forum and in official FAQ.

@Trickla601 thanks for the first usefull post in that topic here… the supporters of conspiracy theories are allways present :rofl:

6

Yesterday the sim was working fine for me, then today it would seem that no matter what I tried would result in a CTD right after loading into the aircraft.

I then updated Windows, which included a .NET Framework update. Problem appears to be solved and I now load in without error.

I also updated my GFX drivers, but I doubt that was the issue.

I remember that the .NET Framework updates have fixed CTD issues in the past for me. It would appear this was the same case.

7

World Update so we have to wait for Asobo to figure out what they broke, yet again. This happens EVERY time there is an update, a portion of the users can’t use the software they paid for.

1 Like
8

Same. Shortly after I load in my throttle doesn’t work properly and I ctd on the runway.

I’ve given up on trying to fix anything in this game when they update it.

You get delusional responses telling you to re install everything on your computer and what not. Not my job to do that. It 's actually amazing at this point how updates can break the game so badly for certain rigs.

9

Don’t uninstall/reinstall. The base .exe is borked. It keeps CTD in the install manager.

10

I turned off live weather, deleted rolling cache and set frames to 60. Seems to be fixed for me.

11

so… you get the information about what is wrong with your system… may be your throttle disconnected, may be because of usb issue or whats ever…

also these one… if limit of fps is helpfull, you run may be into overheating issue. Without the limit your system run whole time in full load.

12

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

13

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.

14

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:

15

Yes you’ve misunderstood my comment lol

16

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.

17

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:

18

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%3Alatest_topic
https://forums.flightsimulator.com/search?q=FSUIPC7%20order%3Alatest_topic

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

19

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.

20

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