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

Bug Reports & Wishlist Resolved
, ,
#122

Yes, sadly still CTD

Faulting application name: FlightSimulator.exe, version: 1.23.12.0, time stamp: 0x00000000
Faulting module name: grammar.pggmod, version: 76.0.0.3, time stamp: 0x61977cfe
Exception code: 0xc0000005
Fault offset: 0x0000000003ee25a3
Faulting process id: 0x2a98
Faulting application start time: 0x01d82f51e0ca0883
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.23.12.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: \?\C:\Users\khurr\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\bf-pgg\PGG\grammar.pggmod
Report Id: 8ecc605d-ae62-4954-800b-0010f73b6ea0
Faulting package full name: Microsoft.FlightSimulator_1.23.12.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

#123

100% repeatable

#124

Hi
Did you come up to any solution flying from OPFA towards opmt or even opkc coz i have the same issue as soon as fly from opfa towards ninuk it crashes. pleae check the images. I can see you had this issue since SU4 and now it is SU8 and issue is still there . I have already reported as a bug and was hoping that this will fix in SU 8 but its still there

OPFAOPMT
OPFAOPMT1920×1955 249 KB
. I did every thing on my part as i reported this issue to zendesk and they come up with same traditional answer i-e
empty community folder
should be in vanilla state
and this obviously is nopt working.
please let me know if issue has been solved
thank you
A Akram

#125

My workaround is to replace the suspected files as per this post

1 Like
#126

Submitted to Support

Faulting application name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Faulting module name: grammar.pggmod, version: 76.0.0.3, time stamp: 0x61977cfe
Exception code: 0xc0000005
Fault offset: 0x0000000003ee25a3
Faulting process id: 0x25a0
Faulting application start time: 0x01d840b461b805c2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: \?\C:\Users\pettersmr\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Official\OneStore\bf-pgg\PGG\grammar.pggmod
Report Id: f2d80686-4824-4951-bb8c-b086d3d17c9e
Faulting package full name: Microsoft.FlightSimulator_1.24.5.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

1 Like
CTD in CJ4 and CRJ700 when ascending over FL330, 1Mar22 module faulting
#127

Flight Plan VIAR/16 DCT LAXEB Z303 QT DCT OIKB right turn off R16.
Did 2 flights CJ4 CTD at about FL350 coords (from LittleNavMap) 31 24 0.08N,
73 38 34.30E 43.5M from GOJRA, Baron CTD at 3800ft coords 31 24 31.07N,
73 42 30.20E close to 45M from GOJRA had outside view at the time a number of villages but nothing outstanding.

image
image940×529 67.4 KB

image
image940×529 58.9 KB

1 Like
CTD in CJ4 and CRJ700 when ascending over FL330, 1Mar22 module faulting
#128

Try my workaround here @AchyRook58584 - the files listed in the above posts are the culprits, and so far no patch has been created to fix this from Asobo despite Zendesk tickets raised.

#129

Jepp,Screenshot 2022-04-04 183922
I got that too on my way from EDDF to WSSS. I recon it is somewere around airway 466

1 Like
#130

Thanx, @reklesskarnage, your workaround helped for Pakistan Area.

#131

SU9 - still failing!!!

when is this nightmare going to end?!?!?

#132

Once reported to Zendesk, it’s probably best if you fly from somewhere else till that is fixed.

I assume you have reported this defect?

#133

I discovered this CTD when flying from OPKC to OPLA and it occurs exactly around the area as discussed so many times in this thread. Starting a flight at OPRQ, straight to CTD.

I tried workaround by @reklesskarnage but it no longer works after SU9. I guess I have to do it again.

The workaround stopped CTD but the “non existent terrain” kept following my flight for 3/4th of the flight from OPLA to OPKC.

Reported to Zendesk and got their usual response.

This thread has 41 votes so I’m not sure if this will be looked at.

Any action would be greatly appreciated.

#134

Tried to fly a route from EKKA to LSZH three times, but CTDs around FL190, location
55° 47’ 17.33" N 9° 7’ 14.75" E
otherwise I don’t used to experience CTDs.
route

Denmark bush trip - crash to desktop around EKBI
#135

Have a look in the Event Viewer for the crash. I would be interested to see what the faulting module is.

Before you say it, it will have created an event, trust me.

I just overflew TOMGU, and had no crash.

image

#136

Just had the same error at lat/lon 30.94739, 73.29072 on a flight from OPKC - OPIS. Restarting the sim and spawning it at the lat/lon gives an almost instant crash to desktop again every time.

#137

imagine getting such a responds from a MS/Asobo mod or even dev :upside_down_face:

something similar happens close to EKBI on the approach 27

#138

this issue is in meanwhile so old and validated for so many places.

I mean, I not expect that all places in the world with a seemingly invalid data can be found and fixed. But why not determine the root-cause ( “what kind of data” cause that ) , catch the error in this situation and e.g. ignore the invalid data ( a resulting terrain spike is even better, as a crash ).

I not want to know how many users reported a crash and where we not asked "happens it each time at same location ? then look here … " . And so the users not vote here , but are un-happy about a crash.

There is no better situation as bugs like this: allways reproducable and so much easier to find in implementation and faster to fix :slight_smile:

#140

Just had a CDT in the middle of a 12 hour long haul over waypoint NITIV in Pakistan, loading an autosave and flying over that point gives the same crash.

Log Name:      Application
Source:        Application Error
Date:          07/06/2022 02:06:19
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-1U89IS2
Description:
Faulting application name: FlightSimulator.exe, version: 1.25.9.0, time stamp: 0x00000000
Faulting module name: grammar.pggmod, version: 76.0.0.3, time stamp: 0x61977cfe
Exception code: 0xc0000005
Fault offset: 0x0000000003ee25a3
Faulting process ID: 0xdcc
Faulting application start time: 0x01d879e5dc9a1a4e
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: \\?\C:\Users\vurpl\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\bf-pgg\PGG\grammar.pggmod
Report ID: 3483949e-bd6f-4c37-a0b5-723c544c1743
Faulting package full name: 
Faulting package-relative application ID: 
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="2022-06-07T07:06:19.2569000Z" />
    <EventRecordID>4095</EventRecordID>
    <Correlation />
    <Execution ProcessID="6256" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-1U89IS2</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>1.25.9.0</Data>
    <Data>00000000</Data>
    <Data>grammar.pggmod</Data>
    <Data>76.0.0.3</Data>
    <Data>61977cfe</Data>
    <Data>c0000005</Data>
    <Data>0000000003ee25a3</Data>
    <Data>dcc</Data>
    <Data>01d879e5dc9a1a4e</Data>
    <Data>C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe</Data>
    <Data>\\?\C:\Users\vurpl\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam\bf-pgg\PGG\grammar.pggmod</Data>
    <Data>3483949e-bd6f-4c37-a0b5-723c544c1743</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>
#141

Guys!! MSFS and Asobo team finally linked this thread to their SU10 Beta release notes! It might mean that in the beta and in the upcoming SU10 the crashes at specific locations e.g. the one near Lahore, Pakistan might have been fixed! Can anyone check? Would finally enable me to do transcontinental flights while transiting through that area :smiley:

1 Like
#142

Downloading and installing right now…will report back.