100% reproducible CTD at specific coordinates for months [grammar.pggmod]

Sadly still with SU5 the problem exists.

Got hit with this while about to finish a two part journey, LRSB → OTIL (redirected to OTIZ) and OTIZ->VIDX, ~300 nm to VIDX when following a direct VFR route.

Faulting application name: FlightSimulator.exe, version: 1.18.14.0, time stamp: 0x00000000
Faulting module name: grammar.pggmod, version: 76.0.0.3, time stamp: 0x608bf361

Great topic
 invalid handcrafted BPG ? texture coords don’t match texture file ? mesh got corrupted ? :cat:

There is indiginous people’s witchcraft in some locations of MSFS ? guess ? :grin:

1 Like

I got this months ago. Maybe it will be fixed in the Germany World Update.

1 Like

Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
A32nx, tested without, same error
Are you using Developer Mode or made changes in it?
no
Brief description of the issue:

CTD over Pakistan, at the SAME place (3 flights tested from LFPO to WSSS using SIMBRIEF flight plan (in MCDU for A32NX or on the WORLD MAP for Asobo A320 basic test)

Provide Screenshot(s)/video(s) of the issue encountered:

Detail steps to reproduce the issue encountered:

Just flight , crash between JHANG and NITIV almost over M4 Motorway

Routing
BUBL9X BUBLI UG42 LUVAL UM164 EPL UN491 BEGAR N491 DEGES UN871 GAMSA N871 MADEB N606 ELMEM L607 GEDSO DCT MAGAM DCT ETIDA/K0856F370 Q7 IVGOT L744 UDROS/N0464F370 UM859 KARDE UN644 ROLIN N644 LAGAS M747 SULEL N449 DUKAN B449 DOLOS B475 NINOP A909 LEMOD/N0463F390 N644 DI M875 KAKID M770 OBMOG L515 PUT B579 VPL W531 VIH A464 ARAMA LELI3B

PC specs for those who want to assist (if not entered in your profile)

Build Version # when you first started experiencing this issue:
1.18.5
Are you on the Steam or Microsoft Store version?
Store one
Did you submit this to Zendesk? If so, what is your ticket #?
not for now

I had the same issue just now and that’s why I logged in to the forums to see progresses on ongoing CTD, temperature issue with live weather etc. - great coincidence , I was on my way to Delhi Airport (VIDP) and if I recall correctly I was on the way to IGINO IGIN5F for ILS approach RWY 11.

I did have Self Loading Cargo (with custom sound packs) and also MSFS Mobile Companion App however none of these have caused CTD for me before.

My first inflight CTD after a very long time at cruise level - no error messages, just crashed.

1 Like

can you check windows event viewer message ?

In case you find somewhat with “grammar.pggmod”

we are here:

1 Like

Exactly !!!

Nom de l’application dĂ©faillante FlightSimulator.exe, version : 0.0.0.0, horodatage : 0x00000000
Nom du module défaillant : grammar.pggmod, version : 76.0.0.3, horodatage : 0x608bf361
Code d’exception : 0xc0000005
DĂ©calage d’erreur : 0x0000000004799026
ID du processus défaillant : 0x2380
Heure de dĂ©but de l’application dĂ©faillante : 0x01d79731fd7ec27a
Chemin d’accĂšs de l’application dĂ©faillante : C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Chemin d’accĂšs du module dĂ©faillant: \?\K:\WpSystem\S-1-5-21-3128894557-3031184502-1729666202-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\Official\OneStore\bf-pgg\PGG\grammar.pggmod
ID de rapport : 7bbb6ff8-755f-4898-ab9e-aef4497f14e2
Nom complet du package défaillant : Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
ID de l’application relative au package dĂ©faillant : App

1 Like

And another test at the same location

Nom de l’application dĂ©faillante FlightSimulator.exe, version : 0.0.0.0, horodatage : 0x00000000
Nom du module défaillant : grammar.pggmod, version : 76.0.0.3, horodatage : 0x608bf361
Code d’exception : 0xc0000005
DĂ©calage d’erreur : 0x0000000004799026
ID du processus défaillant : 0x1820
Heure de dĂ©but de l’application dĂ©faillante : 0x01d796c4ed585b83
Chemin d’accĂšs de l’application dĂ©faillante : C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Chemin d’accĂšs du module dĂ©faillant: \?\K:\WpSystem\S-1-5-21-3128894557-3031184502-1729666202-1001\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\Official\OneStore\bf-pgg\PGG\grammar.pggmod
ID de rapport : 1e46ba98-4de5-4e92-9424-fb0d7ca25619
Nom complet du package défaillant : Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
ID de l’application relative au package dĂ©faillant : App

1 Like

then may be the topic can be merged :slight_smile: 
 did you already asked a moderator about ?

1 Like

I will do it today :slight_smile:

Update : done, thanks my dear @OlieTsubasa443 :wink:

2 Likes

I take it grammar.pggmod is used by the sim rather than just a 3rd party mod? Otherwise it should be down to its producers to provide a patch.

Hi @DensestSnail693, I believe it’s related to blackshark ai as per other posts here
so yes, not 3rd party, it’s in the core code. I reckon some small bit of code is off and only used for particular scenery where these crashes are occurring. I tried to place exclusion polygons in a custom scenery, and even tried to overwrite an airfield (OPRQ) which crashes immediately when you approach it (even in Dev Camera mode), but still could not get it to work - so there is something fundamentally wrong in a tiny piece of code that is used in a few small places. I’m hoping with every Sim and World Update that it is fixed since you can reliably reproduce it, but alas, it’s not a big enough of an issue and needs far more voting up.

https://forums.flightsimulator.com/t/ctd-issues-discussion-megathread/150127/338

maybe this?
Possible CTD fix to try, worked for me - Bugs & Issues / CTDs - Microsoft Flight Simulator Forums

Tried, with no luck :frowning: Like I said, reliable if you try to fly from OPRQ. Something in that airport is causing the sim to blow up.

1 Like

Thanks and remind me not to fly there :grin:

1 Like

I can confirm reproducible CTD at 30,77266 72,69942 (NINUK fix), Pakistan.

Ticket sent.

5 Likes

I found another location where this happens last night - CTD at (or very near) -43.70727 -21.26807 (XONOK Waypoint) in Brazil with the following error:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: grammar.pggmod, version: 76.0.0.3, time stamp: 0x608bf361
Exception code: 0xc0000005
Fault offset: 0x00000000046e7715
Faulting process id: 0x1e9c
Faulting application start time: 0x01d7b2f2af0575f5
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: \?\C:\Users\Rich\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\bf-pgg\PGG\grammar.pggmod
Report Id: a35a576c-d1f3-455d-9a20-d1331f3ef702
Faulting package full name: Microsoft.FlightSimulator_1.19.9.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

1 Like

I think I ran afoul of the same CTD, although I place it somewhere around 30.959944, 72.798714 
 at least that is equidistant between the CTD I had Friday night going eastbound from LTBA to VTSB, and yesterday going westbound from VTSP to EDDM.

3 Likes

Same CTD on my world Tour in OPRQ!
System X box Series X and the same Crash on S.

1 Like