After having done a quick test with a take-off from the 7R of KLAX (IniBuilds scenario) I was happy to find, in addition to an increase of 3/5 fps, above all the disappearance of the stutters, I decided to do a short test flight from KLAS to the 25R of KLAX done many times.

All good at KLAS with fps between 40/45 and without stutter. In flight everything was OK but, it had never happened to me in any other flight before this SU 15, when I was descending about 40 miles from KLAX, I had a CTD with this data obtained from the W11 event viewer:   

+ System 

   - Providers 
    [ Name] Application Error 
    [ Guid] {a0e9b465-b939-57d7-b27d-95d8e925ff57} 
     EventID 1000 
     Version 0 
     Level 2 
     Tasks 100 
     Opcode 0 
     Keywords 0x8000000000000000 
    - TimeCreated 
    [ SystemTime] 2024-05-23T19:31:19.5057674Z 
    EventRecordID 40521 
    Correlation 
   - Execution 
    [ProcessID] 316 
    [ThreadID] 13100 
    Channel Application 
    DESKTOP-3OS8VFF Computer 
   - Security 
    [ UserID] S-1-5-21-1955669761-913088438-1297958667-1001 
 

- EventData 

   AppName FlightSimulator.exe 
   AppVersion 1.37.18.0 
   AppTimeStamp 00000000 
   ModuleName FlightSimulator.exe 
   ModuleVersion 1.37.18.0 
   ModuleTimeStamp 00000000 
   ExceptionCode c0000005 
   FaultingOffset 00000000018f6941 
   ProcessId 0x2ed0 
   ProcessCreationTime 0x1daad41db565a80 
   AppPath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.18.0_x64__8wekyb3d8bbwe\FlightSimulator.exe 
   ModulePath C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.18.0_x64__8wekyb3d8bbwe\FlightSimulator.exe 
   IntegratorReportId 7815444f-6688-47eb-b831-6ffb25fe524e 
   PackageFullName Microsoft.FlightSimulator_1.37.18.0_x64__8wekyb3d8bbwe 
   PackageRelativeAppId App

I would not panic and repeat the flight. I pretty much had at least one CTD with each of the SU's pretty much immediately before, during or after my first flight. 

6 minutes ago, Drumcode said:

I would not panic and repeat the flight. I pretty much had at least one CTD with each of the SU's pretty much immediately before, during or after my first flight. 

Me too. Always problems like this after an update or installation of a new iniBuilds airport.

Don't forget to "sfc /scannow" at least twice a week.

13 minutes ago, Fiorentoni said:

Don't forget to "sfc /scannow" at least twice a week.

You’re the guy they refer to in this Video 😉. 
SFC is not always a fix all.

Edited May 23, 20242 yr by Wise87

5 minutes ago, Fiorentoni said:

Don't forget to "sfc /scannow" at least twice a week.

What?  Please elaborate I'd love to hear why this should be run 2x week as I have never heard this advice before... 

14 minutes ago, Wise87 said:

You’re the guy they refer to in this Video 😉. 
SFC is not always a fix all.

It finds errors twice a week and since I do it I have no real problems with CTDs anymore. So apparently it does fix enough for me. I can't rule out that it might not connected at all, but at least it's not snake oil, but it makes sense from a stability point of view.

Here's more to that: https://forums.flightsimulator.com/t/ctd-fix-info/471880

Edited May 23, 20242 yr by Fiorentoni

9 minutes ago, psolk said:

What?  Please elaborate I'd love to hear why this should be run 2x week as I have never heard this advice before... 

It checks and if necessary repairs Windows system files. These can, if corrupted, lead to CTDs, especially the "random" 0x0000005 ones.

25 minutes ago, Fiorentoni said:

Don't forget to "sfc /scannow" at least twice a week.

That command is utterly pointless, plus you'll always come across corrupted files, even on brand new systems, that's normal. It will rarely to never actually fix an issue.

Edited May 23, 20242 yr by Sethos

Just now, Sethos said:

If you have to run that command twice a week, your computer needs a serious looking at. I've never in my life had to run that command, it's something you might tell a client to run, as some last ditch attempt to fix an obscure Windows issue, nothing else.

Possibly a flaky hard drive maybe. 

1 minute ago, Sethos said:

If you have to run that command twice a week, your computer needs a serious looking at. I've never in my life had to run that command, it's something you might tell a client to run, as some last ditch attempt to fix an obscure Windows issue, nothing else.

What makes you think I have to run it? It finds errors often enough and I know it would also on a client's PC. That doesn't necessarily mean it would cause any trouble, therefore most people don't have to run it. But we're talking MSFS and 0x0000005 CTDs, which no one has found out the exact causes (and no one will). MSFS apparently is much more sensitive to many things, so if that helps me reduce CTDs, I just do it.

I'm not trying to capture this thread and turn in into a sfc /scannow thread. It's just an option for people to try out, take it or leave it.

Just now, Fiorentoni said:

What makes you think I have to run it? It finds errors often enough and I know it would also on a client's PC. That doesn't necessarily mean it would cause any trouble, therefore most people don't have to run it. But we're talking MSFS and 0x0000005 CTDs, which no one has found out the exact causes (and no one will). MSFS apparently is much more sensitive to many things, so if that helps me reduce CTDs, I just do it.

Looking into it, it's completely normal for it to find 'corrupted' files, even on brand new systems. Means nothing and that command is just some throwaway troubleshoot step, because it never really fixes anything. Plus, it's usually used in tandem with the DISM command if you actually want to repair something, not just on its own. I would honestly say, it's an irrelevant junk command in relation to fixing anything in regards to MSFS.

 

1 hour ago, Fiorentoni said:

Don't forget to "sfc /scannow" at least twice a week.

After each W11 update I run in CMD: 

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealt

and then Sfc /Scannow and I did this a couple of days ago after the latest W11 upgrade.

This procedure is to find and fix any errors in W11.

2 hours ago, Drumcode said:

I would not panic and repeat the flight. I pretty much had at least one CTD with each of the SU's pretty much immediately before, during or after my first flight. 

Thanks for the... comfort! 

But for me, it's not a matter of panic but of a surprise considering that since I had MSFS 2020 it's the first time I've had a CTD and a few days ago I finished a world tour with 125 flights in all continents, without having any problems.

However in the meantime I made the reverse flight from KLAX to KLAS without problems and since for me it's almost an hour on May 24th, it's time to go to sleep to start again tomorrow...sorry today to do other tests.