tkemp66

MSFS 2024 SU 3 - I've tried with multiple default aircrafts from inibuilds A350 and they all crash the sim. Once with a BSOD. Other third-party aircrafts work fine: Faulting application name: XboxPcTray.exe, version: 2508.1001.27.0, time stamp: 0x689413da Faulting module name: XboxPcTray.exe, version: 2508.1001.27.0, time stamp: 0x689413da Exception code: 0xc0000409 Fault offset: 0x000000000012ed8e Faulting process id: 0x20BC Faulting application start time: 0x1DC152E2EFEA542 Faulting application path: C:\Program Files\WindowsApps\Microsoft.GamingApp_2508.1001.27.0_x64__8wekyb3d8bbwe\XboxPcTray.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.GamingApp_2508.1001.27.0_x64__8wekyb3d8bbwe\XboxPcTray.exe Report Id: c4f63386-5adb-434c-a1ef-467e88ecc003 Faulting package full name: Microsoft.GamingApp_2508.1001.27.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: Microsoft.Xbox.App

Issue Resolved! I believe I’ve finally sorted out the problem. I experienced two cockpit freezes with the A350 in MSFS 2024, and was also dealing with GPU crashes when flying aircraft from another respected developer—FENIX! To get the A350 running smoothly again, here’s what worked for me: Uninstalled the NVIDIA driver. Reset MSFS 2024 via Settings > Apps > Installed Apps. (Resetting through the Xbox App didn’t work at all.) This reset will likely require you to reinstall or re-link content in your Community folder. Third-party apps may also need to be reinstalled. MSFS settings will revert to default, including your cache file location. Controller settings may remain intact. If you happen to have 12 drives like I do (not necessary, but helpful), this process is much easier to manage. Disabled Shader Cache in the NVIDIA Control Panel. If the driver is already uninstalled, you won’t be able to do this step. But if you disabled it beforehand, run Disk Cleanup: Select drive 😄 Check DirectX Shader Cache and Temporary Internet Files Click OK Before reinstalling the driver, I deleted: MSFS 2024 Rolling Cache Contents of the DXCache and GLCache folders located at: C:\Users\USERNAME\AppData\Local\NVIDIA (You may need to restart Windows to fully clear these.) Reinstalled the NVIDIA driver, restarted the PC, and re-enabled Shader Cache. Then I verified that: DXCache and GLCache folders were empty Rolling Cache is deleted RUN MSFS2024 to rebuild indexes, then exit Reinstalled and re-linked all MSFS 2024 game files (if you opted to reset the sim). Resetting MSFS isn’t mandatory, but although it’s a hassle, it’s incredibly effective for resolving persistent issues. Configured driver settings using: NVIDIA Control Panel NVIDIA Inspector NVIDIA App (Yes, I use all three!) Pro Tip: I always install NVIDIA drivers using nvcleanstall, located here - https://www.techpowerup.com/download/techpowerup-nvcleanstall/ for a cleaner and more customized setup. After all that—my A350 flew flawlessly! Now for the strange part... After completing a successful flight with the A350, I exited MSFS 2024 and launched a new flight using the A320 from FENIX at KJFK (via iniBuilds). Same settings, same setup—but the sim instantly crashed with a graphics error and gave me a BSOD. Yikes! No panic though—I repeated just these steps: Deleted Rolling Cache Disabled Shader Cache Ran Disk Cleanup Cleared DXCache and GLCache Rebooted PC Re-enabled Shader Cache And just like that—perfect flight. Final Thoughts I’m now convinced that whenever: MSFS 2024 receives a major update A new GPU driver is installed Microsoft pushes a system update Third party developer updates …it’s almost always necessary to repeat those key cleanup steps to avoid crashes and instability. Hope this helps fellow simmers keep their skies smooth and their flights flawless!

Same!!! But I have no clue where to find my log file

Just got myself another error also after flying more than 4hrs from KMIA-KSFO, in a default A350 (white livery) and stilll about 300nm to go: Faulting module name: grammar.pggmod, version: 76.0.0.3, time stamp: 0x63ee0f54 I took PMDG 772 in the skies on Friday night and completed an 11 hour flight no problem. Either way, I'm not sure what/who to blame at this point.

I woke up this morning and saw my sim crashed with the WTF.dll error. I'm also runnning V1.09. This flight was from LTFM-KMIA. I haven't completed a flight yet with the A350 in 2024.

I've also tried these options listed and still no change. I don't have anything external mapped to the rudder axis. I've uninstall and reinstalled moments ago to see if this resolved the issue.

Same thing for me. This all just occured with the latest update and can't figure why its happening.

Ok I tested it but its a bit strange. Here is what I did: 1). Tune to Clearance on (Captain side) - Ask for Clearance ( I get nothing) 2) Tune to Clearance on (First Officer side) - Ask for Clearance ( I get nothing) 3) I went back and forth between the two for a couple of minutes and got nothing. 3) Tune to ATIS Captain Side for 5 sec, then immediately switched back to Tuning to Clearance 4) Asked for Clearance (Captain side) - WORKS FINE I know it makes sense to tune into ATIS first before asking to Clearance is realistic in the real world. I just didn't think the sim would care. Is it designed to work this way or is there still a problem? Thanks again. Troy

However, the only problem I'm facing is that ProAtc/SR is not communicating. I can hear ATIS, but tuning to Clearance I get nothing. Not sure if this is an Ini problem or ProAtc, but this has not happened with the A310. Any thoughts? By the way, beautiful aircraft and no other issues thus far. Great work Ini Team. Troy

Same here. Just tried it a second ago and it stops right in the middle of the "r"

Never mind. I got it to work. Had to uninstall and reinstall lax. But I was referring to GSX, the external plugin. Thanks.

I'm not sure what's going on but so far this in the only airport where I am not getting any AI or where GSX does not operates. KJFK work fine and so does many others. Not sure where to look to fix issue. Can anyone help? Troy