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....Why is this?I looked up the module filed module: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.

What does this mean? Does this have something to do with the SP1c?

Edited March 6, 201214 yr by readyfortakeoff

Might be, SP1c changed VS2008 to 2010. Make sure you install all the runtime libraries from Microsoft pages

Do you mean re install?... I thought I needed/had all of these in order to run this simI just checked ..I do have the C++ 2010 x86 Ver.10.0.40219 installed today that came with the SP1c

Edited March 6, 201214 yr by readyfortakeoff

reinstall. And if you have 64bit system, try installing 64bit version as well, just to be safe.Also, install 2008 version if you dont have it, 2010 does not install over, but next to 2008, AFAIK.

Rick,Just for info:** In tutor 2, what were you doing when it failed .. what step or page etc?Were you at the departure gate, enroute or what?

Same problem here after SP1c. Missed approach LOWI runway 08 climbing to 9500. Input a new STAR into the CDU and just as I cleared the first discontinuity FSX froze. The strange thing is that I did the exact same route and missed approach procedure the day before without any issues. I have noticed a frame hit in this area probably due to all the terrain the computer must render. Not sure if memory or computer performance might be the culprit.

Same problem here after SP1c. Missed approach LOWI runway 08 climbing to 9500. Input a new STAR into the CDU and just as I cleared the first discontinuity FSX froze. The strange thing is that I did the exact same route and missed approach procedure the day before without any issues. I have noticed a frame hit in this area probably due to all the terrain the computer must render. Not sure if memory or computer performance might be the culprit.

Need to sort this out.What are your PC specs?Why are you entering a STAR after a missed approach?What scenery are you using?What was in your Event Viewer

Its the entering of the STAR that is activating the problem. I entered upon arrival and had the hang.Computer spec: Typ SB setup.

Need to sort this out.What are your PC specs?Why are you entering a STAR after a missed approach?What scenery are you using?What was in your Event Viewer

Just tried another few flights form KIAH to KGPT and back. touch and go a few time in KGPT and selecting new arrival runways which adds new waypoints to the plan without any problems. The only time I have encountered the freeze was at LOWI. There seems to be another topic about a member having issues with selecting DEP/ARR while in flight. This person was asked by Ryan at PMDG to save a flight to test it so maybe they can figure it out -- if indeed we are taking about the same issue... sounds like it.My PC specs: WIN XP professional / ATI Radeon HD 4670 graphics processor with 256MB / 3.33GHz Intel Core 2 Duo processor / 4 GB Ram I was entering a STAR after missed approach just to practice the LOWI approach over again. I use the default Scenery. no weather. no traffic. not a whole lot of anything ;-) my computer seems to just be able to handle the NGX and blue skies which is fine by me.Event viewer? didn't look. Thank you.

Just tried another few flights form KIAH to KGPT and back. touch and go a few time in KGPT and selecting new arrival runways which adds new waypoints to the plan without any problems. The only time I have encountered the freeze was at LOWI. There seems to be another topic about a member having issues with selecting DEP/ARR while in flight. This person was asked by Ryan at PMDG to save a flight to test it so maybe they can figure it out -- if indeed we are taking about the same issue... sounds like it.My PC specs: WIN XP professional / ATI Radeon HD 4670 graphics processor with 256MB / 3.33GHz Intel Core 2 Duo processor / 4 GB RamI was entering a STAR after missed approach just to practice the LOWI approach over again.I use the default Scenery. no weather. no traffic. not a whole lot of anything ;-) my computer seems to just be able to handle the NGX and blue skies which is fine by me.Event viewer? didn't look. Thank you.

What happens if you do the missed approach procedure .. then just load the approach you want to do next?

Can you be specific on how you guys are selecting the arrival into the airport? The issue I am having is when selecting an arrival back into the airport listed as departure in the route page.So, for example, say my route page is departure from PAWG to destination airport PAKT. After takeoff, while flying the SID, I decide to return to PAWG. I select the DEP/ARR page and try to select an arrival procedure. As soon as I press the LSK to select a procedure back into PAWG, the sim freezes and I have to close it via task manager.The only way around this for me is to change the destination airport in the route page and then use the destination LSK in the DEP/ARR page. By doing this method, I can fly multiple departures and approaches all day long without a single hitch. I've had sessions in the NGX where I am flying 8 to 10 approaches and missed approaches without a single crash or freeze.

Mariano,As soon as you know you need to divert to any airport you go to the RTE 1 page and enter the new DEST ICAO. Now you can enter your waypoint(s) and select the APPR for the destination airport.As for the sim freeze ... that is bad.I will have to do a test on a test flight.Ok, I did a quick test without actually departing and the departure airport procedures for its departure and arrival are all working (selectable) without a crash/freeze.So, as long as they are available for selection they should work. Are you using Navigraph current cycle NavData .. just for info here.Try it at the departure gate and see if you get the freeze ..

As soon as you know you need to divert to any airport you go to the RTE 1 page and enter the new DEST ICAO. Now you can enter your waypoint(s) and select the APPR for the destination airport.

Yeah, I know. But mister Boeing decided to include a button to select an approach back into the departure airport to save the user a few key strokes in the FMC when things are going pear-shaped. I mentioned that I needed to change the destination as a way around the problem. Anyways, will do more testing and report back. I did some flights today where it worked, so there is something else to it. Maybe as you say, it was a corrupt Navigraph file. I'm running the latest Airac (13? I think). Haven't tried at the gate, my crashes were airborne once I am actually flying the programmed route.