Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

737NGX SP1c Crash

Featured Replies

Hi,installed the SP1c today, everything worked fine. First flight was without problems, later that day, I started another one. Destination Innsbruck (LOWI). After a disastrous approach, I executed a G/A due to weather and set Munich (EDDM) as new destination with an ILS approach. The FMC legs page now showed in the first line no waypoint, followed by a discontinuty and the FAF (BEGEN) for the ILS. My intention was to create a custom designed waypoint to intercept the ILS. I entered BEGEN230/5 in the FMC and wanted to set it in first line of the LEGS page. With pressing LSK1 flight simulator stopped working, sound continued, but no reaction, no crash report.Did I anything wrong?Thanks for your help!Happy landing,Dominik

Regards, Dominik Schreier

Sometimes I get the same problem when editing waypoints. And I haven't installed SP1c yet.

Caio Belmock Mascarenhas de Campos

Yeah it still seems that when you play with the FMC to much, that the sim wants to crash sometimes. Especially when you play with the HOLD page, and when entering custom waypoints as you say.

Arjen Vandervelde

That is not good.Changing FMS data (custom waypoints,holds etc.) should not cause a FSX crash.I wonder how many people are having this problem.I have seen reports of this prior with other (e.g. 767) aircraft .. like some people entered a STAR with a specific transition would cause a crash ... but, not all pilots had the problem (if I remember correctly).I am still reading the "excellent", beautifully written PMDGNGX Training flight Tutor #2 manual ... complete with nice references to exact pages in the FCOM docs ,, a real PLUS!When I get to flying I will do a few tests and see what I come up with.

Edited by vonmar

Best Regards,

Vaughan Martell  PP-ASEL KDTW

Did you check your event viewer to try to figure out which module crashed your sim?

Johan Pettersen

  • Author
Did you check your event viewer to try to figure out which module crashed your sim?
As said above, the sim stuck without any report. So I had to quit with the task manager.

Regards, Dominik Schreier

So it doesnt actually crash, it "just" hangs?

Johan Pettersen

  • Author
So it doesnt actually crash, it "just" hangs?
Yes, sorry for my misleading diction.

Regards, Dominik Schreier

As said above, the sim stuck without any report. So I had to quit with the task manager.
Check you Event Viewer anyway.

Best Regards,

Vaughan Martell  PP-ASEL KDTW

I wonder how many people are having this problem.I have seen reports of this prior with other (e.g. 767) aircraft .. like some people entered a STAR with a specific transition would cause a crash ... but, not all pilots had the problem (if I remember correctly).
I just had this occur when entering a appr, procedure (STAR) during flight progress. Ive had it loch the FMC up before,, this time it locked the whole computer. No CTD etc. No error report. This has been happening on and off since the releases of the NGX and I havnt seen a explanation or cause yet. Its not very frequent and has continued threw each release version. Been told to try different things but no avail! Getting very frustrating.

ArDee

ArDee,I am not flying for a few more days yet. I will test when I do.Prior days, I entered the procedure prior to departure and all was ok .. but with the previous SP.It would be helpful if you gave your plan here and which procedure errored when you entered it.I would guess some on-line flights (with SP1C installed) would have already required procedure changes before arrival.Maybe they will report their results here.

Edited by vonmar

Best Regards,

Vaughan Martell  PP-ASEL KDTW

As said above, the sim stuck without any report. So I had to quit with the task manager.
There is a way to see what files was FSX process accessing at the time of hanging. I am not sure if EventViewer is enough for this, but I managed to solve quite a few problems with this approach.

--Peter Fabian 
RTFM.jpg

ArDee,I am not flying for a few more days yet. I will test when I do.Prior days, I entered the procedure prior to departure and all was ok .. but with the previous SP.It would be helpful if you gave your plan here and which procedure errored when you entered it.I would guess some on-line flights (with SP1C installed) would have already required procedure changes before arrival.Maybe they will report their results here
Route when hang occured. SP1c. Nouthing in the event viewer. The computer would stay hung till hell froze over. It occured when approx 200 mi out and choosing Star/Appr procedure. (SIRON) RWY8. . LFPG....LLBGLANVI DEGES UN871 MADEB UN606 SPL UL607 ATV UL995 KEA UL52 RAPOS UL52 MAGIS UN134 SOLIN H2 SIRON

Edited by Barnstormer1

ArDee

I got this today when using the fmc while trying to do the tutorial...#2.. It crashed / stop working and had to close. I'll try again tomorrow. Also I might add that I have never had a system crash like this before with the NGX..I 've had the frozen panel but only with the RTM and not since the Sb1.Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeaf722Exception code: 0xc0000005Fault offset: 0x00009b60Faulting process id: 0xf34Faulting application start time: 0x01ccfafa9e94b9dfFaulting application path: C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator Xfsx.exeFaulting module path: C:Windowssyswow64msvcrt.dllReport Id: c9f67c7a-6703-11e1-a7d9-6cf049753034 fsx.exe 10.0.61472.0 475e17d3 msvcrt.dll 7.0.7601.17744 4eeaf722 c0000005 00009b60 f34 01ccfafa9e94b9df C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator Xfsx.exe C:Windowssyswow64msvcrt.dll c9f67c7a-6703-11e1-a7d9-6cf049753034

Boeing777_Banner_Pilot.jpg

I got this today when using the fmc while trying to do the tutorial...#2.. It crashed / stop working and had to close. I'll try again tomorrow. Also I might add that I have never had a system crash like this before with the NGX..I 've had the frozen panel but only with the RTM and not since the Sb1.Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeaf722Exception code: 0xc0000005Fault offset: 0x00009b60Faulting process id: 0xf34Faulting application start time: 0x01ccfafa9e94b9dfFaulting application path: C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator Xfsx.exeFaulting module path: C:Windowssyswow64msvcrt.dllReport Id: c9f67c7a-6703-11e1-a7d9-6cf049753034 fsx.exe 10.0.61472.0 475e17d3 msvcrt.dll 7.0.7601.17744 4eeaf722 c0000005 00009b60 f34 01ccfafa9e94b9df C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator Xfsx.exe C:Windowssyswow64msvcrt.dll c9f67c7a-6703-11e1-a7d9-6cf049753034
Ok,I will take a look at all this ... BTW, "C:Program Files (x86)Microsoft GamesMicrosoft Flight Simulator Xfsx.exe" is generally a bad place to put FSX....I looked up the module filed (edit) failed module information:Msvcrt.dll is the Microsoft Visual C++ Run-Time for Visual C++ version 4.2 to 6.0. It provides programs compiled with these versions of Visual C++ a typical set of library functions required by C and C++ programs. These include string manipulation, memory allocation, C-style input/output calls, etc.** In tutor 2, what were you doing when it failed .. what step or page etc?

Edited by vonmar

Best Regards,

Vaughan Martell  PP-ASEL KDTW

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.