5 hours ago, Bobsk8 said:

Well I thought I had solved the problem, with the Garmin fix, but it is back again. This simulator has more bugs than a flop house bed. I am going to seriously consider going back to P3D, because this just isn't any fun anymore, it looks great until it screws up. . 

I feel your pain. I was in middle of a round the world tour prior to the last update, but now it takes me 3 or 4 tries to successfully complete even a short hop in the 172. I'm just gonna go back to airliner flying on X-Plane until the next update is out with the hope that it fixes this problem. 

7 hours ago, Maladoror said:

ctd with vcruntime140.dll.

I feel for all you guys with CTDs. For this specific one due to vcruntime there may be a possible fix (aka straw) which I followed and which increased my situation, especially for those on an older Win10 installation: delete ALL vcruntimes from Win10 Settings —> Apps and then only reinstall the latest ones from MS. There is a link to the latest ones at the MS forum. I found that there were quite some fancy runtime libraries from the 90ies almost on my system since every piece of software wants to install one. 

This helped me prior to WU3 even though I cannot bind my loss of CTDs purely to this fix. For WU3 I did a complete reinstall of Win10 on a brandnew ssd anyway and since then no CTDs. 

EDIT: more on the runtimes:

 

Edited March 6, 20215 yr by DAD

6 hours ago, Bobsk8 said:

Well I thought I had solved the problem, with the Garmin fix, but it is back again. This simulator has more bugs than a flop house bed. I am going to seriously consider going back to P3D, because this just isn't any fun anymore, it looks great until it screws up. . 

seems only to be the case for certain ppl tho..its very stable here.

7 hours ago, Bobsk8 said:

Well I thought I had solved the problem, with the Garmin fix, but it is back again. This simulator has more bugs than a flop house bed. I am going to seriously consider going back to P3D, because this just isn't any fun anymore, it looks great until it screws up. . 

Stick with it @Bobsk8 we will get it solved at some point. Yesterday was my first day for a week without any CTD during a flight.

I have the same CTD (0xc0000005), where just before the crash, the sound stutters, less than a second, but noticable. The first time this error occured was just after the world update or patch to 1.9.50 in October. At first it happened infrequently, but since December I can only do short flights since any long flight will eventually CTD.

• The longer the flight is, the most likely it will CTD at some time.
• It happens even with an empty community folder and without using external software (was using Litle Navmap, NeoFly) to eliminate a simconnect problem.
• Disabling ATC and/or AI seems to help but does not eliminate the problem. I just can fly longer.
• Windows is up to date, scanned for errors with SFC and DISM but all is fine.
• All mainboard drivers are up to date.
• Tried older Nvidia drivers, now on 457.30 but problem still occurs.
• System is not overclocked (but AMD PBO is on). FPS is mostly limited by mainthread, even after disabling AI and ATC.
• Disabled power management on all USB devices.
• After reinstalling MSFS (downloading everything again) the problem appeared to be solved, but on longer flights it still CTD with the exact same error.

After running out of options, I installed a 2nd Windows installation on the same hardware (dualboot), just for MSFS. Here, the problem is actually WORSE:

• During installation of MSFS I had my yoke and quadrant not plugged in, but my pedals were.
• MSFS starts fine without yoke and quadrant connected. However, MSFS crashes the moment I plug them in.
• When yoke and quadrant ARE connected, the sim has the same CTD while still starting.
• The settings for the USB controllers are stored in the c:\Users\XXXXX\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\ folder I believe. If I remove these the sim gives a message during startup that it is syncing my settings from the cloud.
  • If I let it sync, it restores the USB settings, and crashes at the same point during starting up.
  • If I cancel the cloud sync, MSFS starts fine. I can change all settings, go to the market but before flying I need to redo all controller profiles off course.
  • The next boot, I still get the sync message. As long as I cancel it, the sim starts fine but I have to redo setting the profile every time.
  • Any time I forget to cancel syncing my settings from the cloud, it crashes unless I do not have the yoke or throttle quadrant plugged in, and keeps doing that until I delete that folder again.

There is another thread on these forums where someone did a reinstall and had similar issues, which were related to his xbox.profile. If he ran MSFS using another account it would do so fine. Too bad there is no option to reset your MSFS cloud settings.

In the first few months, MSFS was rock stable on my system. I didn't have CTD's until after the 1.9.50 update. After that, it seems to get worse with every new update.

My specs:

• Motherboard: MSI MEG X570 Unify
• CPU: AMD 3900x (not OC) with Scythe Mugen 5 cooler
• Memory: G.Skill F4-3600C16D-32GTZNC (2x16)
• GPU: Gigabyte Aorus Geforce RTX 3090 Master 24G
• PSU: Corsair RM850
• Storage: 2 XPG SX8200 Nvme (2 TB), 1 x Samsung 970 EVO Nvme (1 TB)
• Monitors
  • Gsync (100hz) at 3440x1440 (21:9)
  • Regular at 1920x1200 (16:10)
• Controllers / USB devices:
  • MFG Crosswind rudder pedals
  • Fulcrum One yoke
  • CH Products throttle Quadrant.
  • Wooting 2 keyboard
  • Logitech Mouse
  • Sony PS3 eye  and Logitech webcam

I sometimes use the same system for work, which means the CPU is running 100% (all cores) for almost 24 hours. It doesn't have any issues with that. Other games, while not CPU limited but quite demanding on the GPU also run fine.
Most people who don't have issues blame the hardware, or the drivers. The only hardware problem I can think of is AMD, so switching to Intel might be a solution. I am thinking about the i9 11900k, but that means spending almost a €800 to solve this.

At the moment there are still a few things I want to try, if I have the time for it:

• Disabling first core (affinity trick)
• Disabling PCIe 4.0 on motherboard
• Disabling Windows audio service
• Using an addon PCIe USB 3.0 card. I have one ordered.

What bothers me is that quite a lot of people have this same error, especially in the official forums. Most fixes that are posted have no relation with each other, and they fix it for some, but not for everyone. Often a fix which seemed to work at first proves not to be after a few flights
Asobo is no help at all, if you create a ticket you get the same list of possible solutions to try. Some of these seem to help but after a few flights the problem is still there.

Since some of these fixes, like disabling ATC or AI seem to help the CTD occur less often it might be memory leak that's the issue. After switching to my RTX 3090 24GB (was using a 1060 6GB before) the problem seems to occur more often. Since more Vram also uses up more of your main memory this may indicate it is indeed caused by a memory leak However, the problem seems to be USB related as well. Off course I could have more than one problem but they all CTD in the same way, with the same 0xc0000005 error.

In the past year I had invested quite a lot of money in hardware and purchased new controllers to enjoy flightsim again. However, these days the urge to go flying is not there anymore. I gives me a chance to play other games a lot more but everytime I think about flying I thing about problem solving instead of enjoying the virtual world.

Allard.

 

Edited March 6, 20215 yr by orchestra_nl
clarity

@orchestra_nl I disabled PCIe 4.0 previously, but it made no difference for me. Just had another 1.5 hr flight (without tempteing fate, no CTD yet)

13 minutes ago, Car147 said:

@orchestra_nl I disabled PCIe 4.0 previously, but it made no difference for me. Just had another 1.5 hr flight (without tempteing fate, no CTD yet)

What did you do get there? Wish you it remains like that

8 minutes ago, DAD said:

What did you do get there? Wish you it remains like that

Just disabled it through the bios, it reverts to PCIE 3.0. most GPU's coming out in the past year were PCIE 4.0, , certainly from AMD , not so sure on Nvidia.

1 minute ago, Car147 said:

Just disabled it through the bios, it reverts to PCIE 3.0. most GPU's coming out in the past year were PCIE 4.0, , certainly from AMD , not so sure on Nvidia.

But you said that did not the trick, did it? I rather meant other measures which let you do the 2-3 flights without a CTD - knock on wood

2 minutes ago, DAD said:

But you said that did not the trick, did it? I rather meant other measures which let you do the 2-3 flights without a CTD - knock on wood

I don't think i explained enough sorry, all i have done is completely delete rolling cache, and left off, stopped using the VFR Map, as that was causing stutters, And i only load into the community folder the files required for that flight.. nothing else.

The bit about the PCIe 4.0 etc was tried weeks ago, it made no difference.

Too bad disabling PCIe 4.0 did not help. I do wonder if everyone that has these issues is using an AMD platform. AMD is currently researching a possible issue with their X570 USB controller which might be related since most other games I play only need keyboard and mouse.

On the other hand, not everyone with these errors is using an X570 motherboard. I am not even sure if it is limited to the AMD platform.

What worries me too is that a fresh windows installation caused even more problems, so what will happen if I would try different hardware?
It seems the settings (including USB controller profiles) are stored in the cloud so you can reinstall the sim but you can never start from scratch entirely since these settings are copied back unless you use a different account.

Since all my purchases are linked to my current account that would mean purchasing hundreds of euros of addons for a second time.

Edited March 6, 20215 yr by orchestra_nl

One thing is for sure: I won't be buying a new PC to solve my own rebooting problem... A lot of you use hardware that I have on my shopping list but the idea of buying that new PC and then ending up with CTD's... that's just as bad as my rebooting problem. Every now and then I manage to do (a part of) a short flight and I think I'll have to be happy with that. I won't buy the JF Arrow nor the CRJ anytime soon. First I'll wait until these kind of problems are (sort of) solved, then I might get a new PC and then I might enjoy MSFS again and buy some quality addons. But for now I am afraid MSFS has sunken to a lower priority level. Too much problems to my liking. Such a shame. I started out great but sunk pretty low. Lower then I expected a few months ago...

Edited March 6, 20215 yr by tup61

First flight of the day around 90 miles. Made it about 80 miles.......CTD....

 

Log Name:      Application
Source:        Application Error
Date:          3/6/2021 9:53:06 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-7AJT4EM
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x6038d404
Exception code: 0xc0000005
Fault offset: 0x00000000005a721c
Faulting process id: 0x1d08
Faulting application start time: 0x01d71292c800dc52
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 9d684cbc-efd7-4e68-83d2-f08dafba6d51
Faulting package full name: Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-03-06T14:53:06.3036013Z" />
    <EventRecordID>7754</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-7AJT4EM</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>6038d404</Data>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>6038d404</Data>
    <Data>c0000005</Data>
    <Data>00000000005a721c</Data>
    <Data>1d08</Data>
    <Data>01d71292c800dc52</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>9d684cbc-efd7-4e68-83d2-f08dafba6d51</Data>
    <Data>Microsoft.FlightSimulator_1.13.17.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

If you donot have any problems, I'd recommend not changing your hardware if possible. If you do have (regular) CTD's, it is wise not to invest in both hardware and addons unless the cause of these CTD's is found. It might be months or forever before that happens though. Asobo has done a great job with MSFS but for a few of us who are experiencing these blocking issues.

Too bad, because I too had that JF Arrow on the shopping list, and a few others as well.

3 minutes ago, orchestra_nl said:

If you donot have any problems, I'd recommend not changing your hardware if possible. If you do have (regular) CTD's, it is wise not to invest in both hardware and addons unless the cause of these CTD's is found. It might be months or forever before that happens though. Asobo has done a great job with MSFS but for a few of us who are experiencing these blocking issues.

Too bad, because I too had that JF Arrow on the shopping list, and a few others as well.

I am seriously considering downloading P3D V5 today. My guess is it will not CTD once.