CTD on every play

brags8124 · December 5, 2024, 12:04pm

Hi everyone,

I’m experiencing constant crashes in MSFS 2024 and I’m hoping someone can help. The sim crashes every flight, without exception, and the error always points to the “grammar.pggmod” module.

Here’s what I’ve tried so far:

Disabled Realtek audio: Saw this suggested as a potential fix, but no luck.
Fresh install of MSFS 2024: Completely uninstalled and reinstalled the sim.
Empty Community folder: Removed all mods and add-ons.
Checked for Windows Updates: Made sure my system is fully up-to-date.

The crashes happen in all modes, including free flight and career mode. Interestingly, MSFS 2020 runs perfectly fine on my system, even on long flights.

Here are my system specs:

OS: Windows 11 (English)
CPU: i9 14900K
GPU: RTX 4080 Super
RAM: 32GB DDR5 6200 Mhz

Could this be a compatibility issue with my hardware or Windows 11? Has anyone else encountered this “grammar.pggmod” error? Any help would be greatly appreciated!

Additional Information to Consider Including:

MSFS 2024 Version: Standard from Gamepass
Drivers: Nvidia Game ready 566.14
Overclocking: No.
Crash Log:

Faulting application name: FlightSimulator2024.exe, version: 1.1.10.0, time stamp: 0x00000000
Faulting module name: grammar.pggmod, version: 76.0.0.3, time stamp: 0x63ee0f54
Exception code: 0xc0000005
Fault offset: 0x000000000502d30c
Faulting process id: 0x0x7C70
Faulting application start time: 0x0x1DB452E55C98DAA
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: \\?\C:\PROGRAM FILES\WINDOWSAPPS\MICROSOFT.LIMITLESS_1.1.10.0_X64__8WEKYB3D8BBWE\Packages\bf-pgg\PGG\grammar.pggmod
Report Id: 41817072-bf7e-4e8e-944d-0c1193561bca
Faulting package full name: Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

OldpondGL · December 5, 2024, 12:08pm

That might be an old bug related to the location you are flying from. Try another location.

brags8124 · December 5, 2024, 12:14pm

I tried. It happens in KSFO, SBBH (career mode), and others airports as well

OldpondGL · December 5, 2024, 12:15pm

I am wondering if this might be localization issues. Is your system standard US keyboard English, etc.? @Zeanuck Looping you in since you have similar issues.

brags8124 · December 5, 2024, 12:17pm

No. My keyboard is set to English - International. And system locale is set to Brazil - dates and time appear in DD/MM/YYYY and HH:MM

Zeanuck · December 5, 2024, 1:46pm

I’m in Canada and using US keyboard settings.

Also where does one find the crash log? My CTDs just shut the sim down or more often than not freeze the whole system requiring a hard reboot.

When did flight simmers become debuggers?

OldpondGL · December 5, 2024, 2:55pm

Right click Start, Event Viewer, Administration Events, look for the one just before you boot after the crash.

KnowSoupForYou · December 5, 2024, 3:23pm

I have fixed my crashes by doing two things (not sure which one fixed the issue):

I was wondering if I might be getting processor core over voltage. I disabled processor core affinity for cores 16-31.

Steps to do this: (I have Windows 11)

Open Windows Task Manager
Select details section from the options on the left hand side.
Right click the FlightSimulator2024.exe process
Select Set Affinity
Uncheck CPU 16 through CPU 31
Changed the games rolling cache limit to 64GB.

Steps to do this:

Go to game settings
Select Online
Scroll down to Rolling Cache Limit (GiB) and change the value to 64.0

I have done about 10 missions since I did this with no crashes.

Hope this helps someone else.

SylvesterRocket · December 6, 2024, 7:04am

I have seen recommendations like this now many times. I might give it a try.

It is only sad that you have to limit the resources of your expensive System just to play a new developed game.

I have seen people changing their 4090 card to a 2070ti, ripping out 32gb RAM, reducing cores like you did, use VPN just to get a stable connection (game should not crash if it does not receive data in time - just my opinion), downgrading driver despite MS is recommending the exact opposit, and many other “solutions” like this.
In my mind this is just poor coding.

Anyhow thank you for your suggestion, worth another try.

Edit: I did start up my system and noticed there is a new NVIDIA driver available. After a DDU and fresh installation the sim did start and I was able to start a flight. - FYI

brags8124 · December 6, 2024, 5:31pm

I disabled cores 16-31 and now I am able to complete flights. Thanks @KnowSoupForYou! I have also upgraded the Nvidia driver and no problems so far.

It’s really a shame to have to disable features from the CPU to be able to play a game. Later on I’ll test if with the new driver and not disabling any features I shall have any CTD.

KnackBretzel · December 6, 2024, 6:33pm

unfortunately this did not solve my problem, I have CTD since this evening, I have an empty community, I reinstalled, updated Nvidia, I deactivated multiplayer as well as real-time air traffic always ctd at the start of a flight, I modified to taa or dlss to dlss I was able to hold 10 seconds and then ctd, I specify that I did not modify anything I flew all day without problem, I quit via the button, turned off the PC and restarted it an hour later and since then I have CTD, incomprehensible.

all2easy · December 7, 2024, 1:33am

Search engine says:

[The 0xc0000005 error occurs when an application tries to read, write, or execute an invalid memory address.]

SPilot95 · December 7, 2024, 4:14am

I am getting crashes every single time. This is even after completely wiping my M.2, formatting and new clean install of Windows 11 24H2. I have been very methodical about reinstalling software and updates. It wasn’t until I installed MSFS 2024 and tried to run it that I get repeated CTD’S and blue screens for various reasons. I’ve never had so much trouble with a product as MSFS 2024.

Faulting application name: FlightSimulator2024.exe, version: 1.1.10.0, time stamp: 0x00000000
Faulting module name: VCRUNTIME140.dll, version: 14.40.33728.0, time stamp: 0xf3e8e773
Exception code: 0xc0000005
Fault offset: 0x000000000000fb13
Faulting process id: 0x3498
Faulting application start time: 0x1DB4851DCFBD18E
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.VCLibs.140.00.UWPDesktop_14.0.33728.0_x64__8wekyb3d8bbwe\VCRUNTIME140.dll
Report Id: 62c21be3-ebc6-4ecb-90be-fe123d616cfa
Faulting package full name: Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Faulting application name: FlightSimulator2024.exe, version: 1.1.10.0, time stamp: 0x00000000
Faulting module name: FlightSimulator2024.exe, version: 1.1.10.0, time stamp: 0x00000000
Exception code: 0xc0000096
Fault offset: 0x0000000001ce054d
Faulting process id: 0x3550
Faulting application start time: 0x1DB485B42D29186
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Report Id: ef306909-b700-4d4e-ba00-bd78ea5788e1
Faulting package full name: Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Faulting application name: FlightSimulator2024.exe, version: 1.1.10.0, time stamp: 0x00000000
Faulting module name: nvrtum64.dll, version: 32.0.15.6614, time stamp: 0x672bcb29
Exception code: 0xc0000409
Fault offset: 0x000000000163d8ed
Faulting process id: 0xD20
Faulting application start time: 0x1DB485C73764CE9
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\WINDOWS\system32\DriverStore\FileRepository\nv_dispi.inf_amd64_adf5a840df867035\nvrtum64.dll
Report Id: a2fde3de-ca1f-4066-a992-0646713b8326
Faulting package full name: Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

KnackBretzel · December 7, 2024, 6:53am

that’s the code i have in the asoforeport-crash file

/!/ CRASH /!/TOML
[OnCrash]
Msg=“_handleSEH”
Type=“SEH”
Code=0xC0000005
[Engine]
ReportVersion=10
ExitApp=false
TimeUTC=2024-12-07T06:45:18Z
BuildVersion=“1.1.10.0”
UnscaledDeltaTimeMs=24.991899
TimeSpentRunningMs=236592.394912
TimeSpentPauseOffMs=236592.394912
TimeSpentTurnedOnMs=236592.394912
ContextUID=0x7EC2542BD12CE634
MemInfoUID=0x4FE68B335E15F102
DebuggerAllowed=false
AllocatedMem=23691509760
FrameCount=57127
IsMSIXVC=true
Purpose=“[default purpose]”

SPilot95 · December 8, 2024, 4:59am

OK I seemed to have made significant progress tonight eliminating CTD’s. In my case I found the following causes…

My computer was repeatedly getting corrupt system files even after a clean install of Windows 11 24H2 twice. I was having crashes and instability on random apps and always MSFS 2024 after about a day or two of stable behavior. Attempting DISM, sfc /scannow and other repair routines was not solving things nor was Windows repair and restore. Eventually my pc would not boot into Windows anymore. It would blue screen with a critical process died error. I concluded that my Nvme M.2 drive was failing so I bought a new one and started over. Everything ran fine after that.
The Realtek audio drivers were conflicting with my Nvidia audio driver leading to sim crashes and bsod’s. I disabled the Realtek audio drivers in device manager under audio and sound menus. This stopped MSFS 2024 CTD while loading into the sim.
I updated Realtek .NET driver with the latest one as this was the cause of at least one crash.

We’ll see whether there will be any more CTD’s such as when using Varjo or Flyptmover. Preliminary results show none.

PeriferalEffect · December 9, 2024, 5:57pm

Faulting application name: FlightSimulator2024.exe, version: 1.1.10.0, time stamp: 0x00000000
Faulting module name: CoherentUIGT.dll, version: 2.9.5.0, time stamp: 0x6723a4da
Exception code: 0xc0000005
Fault offset: 0x000000000014ed49
Faulting process id: 0x0x887C
Faulting application start time: 0x0x1DB4A58A115801B
Faulting application path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe\FlightSimulator2024.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe\CoherentUIGT.dll
Report Id: 34fd5d08-6b5c-4825-9f23-8cec04f3af1f
Faulting package full name: Microsoft.Limitless_1.1.10.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

SPilot95 · December 12, 2024, 4:36am

I seemed to have solved my last crash issue where I get the “Your graphics card has encountered a problem…” I had texture quality set on ultra. This is apparently too much even for a 4090 in VR. Setting it on high or a lower setting stopped that message from appearing. I have now been able to consistently perform flights without the sim crashing for me in free flight mode. This is with no addons running other than flyptmover, openxr toolkit, openxr motion compensation, and a Varjo headset.

dkgolfnut · December 12, 2024, 10:48pm

I changed the affinity by unchecking the CPU Cores 16-32, however it didn’t stick for some reason. When I reopened the affinity to validate the changes stuck and the CPU Cores were checked again. I tried it a few times and it seemed to have the same behavior of allowing me to uncheck them but in looking again, they were checked.

I think the enlargement of the Rolling Cache to 64GB fixed my CTD issue. I was finally able to complete a mission and get another endorsement certification. I hope it continues to work. Thanks for the suggestions!

Update: this was a temp fix and CTD’s returned for me. Bios update was needed to correct the issue

SylvesterRocket · December 13, 2024, 6:30am

Short update from my side.

I checked again for BIOS Updates and as it turned out there was a new one from December 6th.
This one I did update and since then, I have had 5 successful starts where I could get on the runway. Had no time for a “longer” flight. But at least I am beyond the point it recently did CTD.

For your information my system specs are:

Intel(R) Core™ i9-14900K (32 CPUs)
ASUS ROG MAXIMUS Z790 HERO
64GB RAM Corsair Dominator
NVIDIA GeForce RTX 4090

Going to perform some test flights over the weekend and see if it still stays this way.

Good luck for all of you.

Skylord5190 · December 16, 2024, 5:19am

I have the same “grammar.pggmod” file causing CONSTANT CTD !! Driving me nuts, ever since patch 3 !! …Did limiting the cores fix it for you long-term? Do you have to re-apply it every session?