red fred

Strange issue with the 777 fmc after reinstall

Recommended Posts

Yesterday I uninstalled and reinstalled both my PMDG B747 QOTS II and my PMDG 777LR/F to the latest installer, as adviced.

Everything went really smooth.

Today I wanted to testfly the 777 so I prepared a short flight from VHHH to ZSPD.

I did my preflight, inserted the appropriate runway and route.

When I wanted to check te route on the legs page, a CTD occured.

I restarted, went through the same steps with again the same result. I reinstalled my navdata and tried again. Same result; CTD.

So every time I try to enter the legs page with an active flight I get a CTD. Just after startup with no flightdata in the FMC, I can enter the legs page without a problem.

But when I tried to enter my flightplan with direct waypoints into the legs page it also crashed.

In all these events my ADIRU/IRS was still alligning.

I found out that once the ADIRU is online, I can enter waypoints, flightplans, an I can approach the legs page without a problem.

This phenomenon never occured before yesterdays update.

Is this something PMDG changed in this update and is this way of inserting flightplans as it should be, or is this some kind of bug.

 

Love to hear from you guys.

Greetings

Fred Schellens

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I did a quick test, not sure if it's following the procedures you did.

777 was uninstalled and re-installed yesterday

Nav data up to date

Cold and Dark start

Battery on

Connect ground power

Ground power switches on

All lights on (this was just me checking the outside view - it was dark when I tested)

Wait for annoying noises

VHHH in airport and dep airport

ZSPD in arrival airport

ADIRU on

Go to LEGS page

These are the only procedures I followed, I didn't get a CTD when I did it. The route wasn't loaded (either from externally or manually) as I haven't got one to hand. Happy to set one up in PFPX, or if you've got yours I can try with that.

 

 

Edited by Harma43
Added a couple of procedures I'd done

Share this post


Link to post
Share on other sites

I tried with both long and short cockpit setups, but not with a cold and dark.

Tried that just now, and I got another CTD.

Must be something wrong with my configuration.

Share this post


Link to post
Share on other sites
38 minutes ago, shortspecialbus said:

Have you tried the obvious uninstall/reinstall?  

-stefan strandberg

The obvious uninstall and reinstall that PMDG specifically recommend NOT doing?

Share this post


Link to post
Share on other sites
26 minutes ago, PMDG777 said:

The obvious uninstall and reinstall that PMDG specifically recommend NOT doing?

Where did they state that?  The Jul 01 post states to completely uninstall before installing.  If they said otherwise, they certainly didn't do it in a prominent place.

 

-stefan strandberg

Edit:

A few key notes on these new installers, if you elect to install them now:

Completely remove the 747 and 777 you have already installed.  Do this for all of our sanity...

Share this post


Link to post
Share on other sites
21 minutes ago, shortspecialbus said:

Where did they state that?  The Jul 01 post states to completely uninstall before installing.  If they said otherwise, they certainly didn't do it in a prominent place.

That's for updating the software, not troubleshooting.

Share this post


Link to post
Share on other sites
5 minutes ago, PMDG777 said:

That's for updating the software, not troubleshooting.

Where have they said don't try uninstalling and re-installing?  I'm not seeing that in any of the stickies or any other prominent place either.  I'm not saying they haven't said that, I'm just curious where they've specifically recommended NOT doing.  If that's the case, they should really make it more prominent, since it's the obvious first step for all sorts of software problems.  Please don't think I'm calling you a liar or anything like that, I'm certainly not, it's just not something I've seen anywhere before.  I don't spend a lot of time on this forum, I'll admit.

-stefan strandberg

Share this post


Link to post
Share on other sites
21 minutes ago, shortspecialbus said:

Where have they said don't try uninstalling and re-installing?  I'm not seeing that in any of the stickies or any other prominent place either.  I'm not saying they haven't said that, I'm just curious where they've specifically recommended NOT doing.  If that's the case, they should really make it more prominent, since it's the obvious first step for all sorts of software problems.  Please don't think I'm calling you a liar or anything like that, I'm certainly not, it's just not something I've seen anywhere before.  I don't spend a lot of time on this forum, I'll admit.

-stefan strandberg

It's not pinned, but Kyle is always going on to people about uninstalling and reinstalling to try and fix issues. It normally just creates more problems. Generally with P3D, most issues are caused by some conflicting addon somewhere, so an uninstall and reinstall isn't going to fix that issue, you need to find what the problematic addon is.

Share this post


Link to post
Share on other sites

Well, hopefully their new installer has eliminated any bizarre problems that you can get from uninstalling and reinstalling.  Normally with addons that's a perfectly reasonable first step as it lets you quickly eliminate a problem with the install.  I've fixed countless addon issues over the years by reinstalling, and then I can forgo a ticket to support or a forum post or whatever.  If that's something that PMDG doesn't want people doing, they might want to sticky that as it's a very common first step with software troubleshooting.  But I digress.  I'll end the derail, since it's not very nice to OP to hijack his or her thread for it - sorry!

-stefan strandberg

Share this post


Link to post
Share on other sites
6 minutes ago, shortspecialbus said:

they might want to sticky that as it's a very common first step with software troubleshooting.

I definitely agree with you here. A pinned troubleshooting steps post would definitely go a long way in helping people get started.

  • Upvote 1

Share this post


Link to post
Share on other sites
1 hour ago, shortspecialbus said:

Where have they said don't try uninstalling and re-installing?  I'm not seeing that in any of the stickies or any other prominent place either.  I'm not saying they haven't said that, I'm just curious where they've specifically recommended NOT doing.  If that's the case, they should really make it more prominent, since it's the obvious first step for all sorts of software problems.  Please don't think I'm calling you a liar or anything like that, I'm certainly not, it's just not something I've seen anywhere before.  I don't spend a lot of time on this forum, I'll admit.

I don't know that they've ever specifically had a sticky post that said this, but any time somebody has tried to un-install and re-install, Kyle always points out that that's the last thing they should be doing unless specifically instructed, as that can introduce more problems than they can solve. So Chris isn't seeing things.

Share this post


Link to post
Share on other sites

If using the provided uninstaller and then reinstalling with the provided installer created problems, I am very happy that they took the time to create new installers.  That should never create more problems.  Here's to hoping that they've solved that problem, as that particular concern is almost always one of the first things done for troubleshooting by end users.  Or at least they should sticky it, or have the uninstaller tell them to stop doing it until they've been told to by support, even, since it's so counterintuitive.  Reinstalling is just behind rebooting for windows tech support "try that and see if it fixes it."  Just my $0.02.  I'm a Linux admin so I'll admit my windows desktop support knowledge is probably pretty outdated.

Really though, I'm ending my derail!  Sorry for the bad advice!

-stefan strandberg

Share this post


Link to post
Share on other sites

Hello,

Did you check the windows event viewer? Maybe it'll show you the file that causes the CTD. 

My last CTD was caused by a dll file from ultimate traffic live, which I did reinstall afterwards. No new CTD yet.

Cheers

Ben

Share this post


Link to post
Share on other sites
13 hours ago, red fred said:

Yesterday I uninstalled and reinstalled both my PMDG B747 QOTS II and my PMDG 777LR/F to the latest installer, as adviced.

Everything went really smooth.

Today I wanted to testfly the 777 so I prepared a short flight from VHHH to ZSPD.

I did my preflight, inserted the appropriate runway and route.

When I wanted to check te route on the legs page, a CTD occured.

I restarted, went through the same steps with again the same result. I reinstalled my navdata and tried again. Same result; CTD.

So every time I try to enter the legs page with an active flight I get a CTD. Just after startup with no flightdata in the FMC, I can enter the legs page without a problem.

But when I tried to enter my flightplan with direct waypoints into the legs page it also crashed.

In all these events my ADIRU/IRS was still alligning.

I found out that once the ADIRU is online, I can enter waypoints, flightplans, an I can approach the legs page without a problem.

This phenomenon never occured before yesterdays update.

Is this something PMDG changed in this update and is this way of inserting flightplans as it should be, or is this some kind of bug.

Hi Fred,

I am running FSX Steam.  Just want to note that with the newest version of the 777-200LR, I had a problem that appears to be fixed by using a fresh panel state and newly entered flight plan

.  I loaded a ready for takeoff situation using an existing panel state, including flight plan.  After take off I simulated an engine failure.  In trying to return to the airport, upon choosing an approach from the list of approaches for the departure airport, FSX crashed.  This happened twice.

I then set up a similar situation, but using the default, engines-on panel state, creating a new flight plan using the CDU to enter it, and no more crash.

So my point  is, if you are using an old situation/flightplan/whatever, maybe that is the source of your problem.

Mike

 

Share this post


Link to post
Share on other sites
14 minutes ago, Mike777 said:

Hi Fred,

I am running FSX Steam.  Just want to note that with the newest version of the 777-200LR, I had a problem that appears to be fixed by using a fresh panel state and newly entered flight plan

.  I loaded a ready for takeoff situation using an existing panel state, including flight plan.  After take off I simulated an engine failure.  In trying to return to the airport, upon choosing an approach from the list of approaches for the departure airport, FSX crashed.  This happened twice.

I then set up a similar situation, but using the default, engines-on panel state, creating a new flight plan using the CDU to enter it, and no more crash.

So my point  is, if you are using an old situation/flightplan/whatever, maybe that is the source of your problem.

Mike

 

Thanks MIke,

I'm running FSX. Sorry I didn't mention that before.

The only time I get this problem is when my ADIRU is not alligned.

Once it is alligned I can do whatever I want, with flightplans or whatever I want do do or change.

I doubt if it has something tot do with addons, because my config hasn't changed lately, and my 777 used to run like clockwork.

Fred

Share this post


Link to post
Share on other sites
8 minutes ago, red fred said:

The only time I get this problem is when my ADIRU is not alligned.

Once it is alligned I can do whatever I want, with flightplans or whatever I want do do or change.

Hi Fred,

Is it possible you are using an old panel state (created before the current 777 version), or one derived from an old panel state?   It looks like PMDG has NOT updated its supplied startup panel states, but sometimes saving, reloading, saving, reloading can produce issues.  Or just one panel state can develop strange glitches.

When I get a chance I will double check if an unaligned ADIRU situation causes flight plan issues. 

Mike

 

 

Share this post


Link to post
Share on other sites

Gents,

Wow- you guys WILL argue about nearly anything, sometimes.  :laugh:

 

Fred,

We haven't heard any reports of this from any other corners- but I am unable to try it myself at the moment to see if I can reproduce it, as I'm not in the office.  Normally something like what you are seeing would create a pretty significant amount of traffic at support- which has me leaning in the direction of "something is getting vacuumed up in your location installation that is creating this CTD event."

Things to try:

1) Go into the <FSX ROOT>/PMDG/PMDG 777X directory and delete the 777X_Options.ini file, then try again.

2) Delete if you are using a panel-state (even if it is one we gave to you) try deleting it and recreating it using your currently installed 777.  (tedious, i know- but it will be faster than waiting for me to get to the office to test for you...)  Once you have that saved- try loading it and starting your process again....

Let us know?  I'm sure we are going to find some setting in one of those two files is setting this up- and if that is the case we will want copies of those files so we can try to duplicate it in-house and prevent it... 

Thanks, Fred- sorry for the hassle.

 

Share this post


Link to post
Share on other sites
6 minutes ago, rsrandazzo said:

Gents,

Wow- you guys WILL argue about nearly anything, sometimes.  :laugh:

 

Fred,

We haven't heard any reports of this from any other corners- but I am unable to try it myself at the moment to see if I can reproduce it, as I'm not in the office.  Normally something like what you are seeing would create a pretty significant amount of traffic at support- which has me leaning in the direction of "something is getting vacuumed up in your location installation that is creating this CTD event."

Things to try:

1) Go into the <FSX ROOT>/PMDG/PMDG 777X directory and delete the 777X_Options.ini file, then try again.

2) Delete if you are using a panel-state (even if it is one we gave to you) try deleting it and recreating it using your currently installed 777.  (tedious, i know- but it will be faster than waiting for me to get to the office to test for you...)  Once you have that saved- try loading it and starting your process again....

Let us know?  I'm sure we are going to find some setting in one of those two files is setting this up- and if that is the case we will want copies of those files so we can try to duplicate it in-house and prevent it... 

Thanks, Fred- sorry for the hassle.

 

Thanks Robert. I will try your options later today or tomorrow morning. I will let you know the results.

Thank you for your quick respons.

Fred

Share this post


Link to post
Share on other sites

I set up a flight last night, including flight plan, with the ADIRU off, and had no problem with the legs page or anything else.  I then turned on the ADIRU and while it was aligning I could look at the flight plan with no issues.   Used latest version of 777-200LR in FSX-SE, latest version of -300ER (downloaded last night) also installed.

Mike

Share this post


Link to post
Share on other sites
14 hours ago, rsrandazzo said:

Gents,

Wow- you guys WILL argue about nearly anything, sometimes.  :laugh:

 

Fred,

We haven't heard any reports of this from any other corners- but I am unable to try it myself at the moment to see if I can reproduce it, as I'm not in the office.  Normally something like what you are seeing would create a pretty significant amount of traffic at support- which has me leaning in the direction of "something is getting vacuumed up in your location installation that is creating this CTD event."

Things to try:

1) Go into the <FSX ROOT>/PMDG/PMDG 777X directory and delete the 777X_Options.ini file, then try again.

2) Delete if you are using a panel-state (even if it is one we gave to you) try deleting it and recreating it using your currently installed 777.  (tedious, i know- but it will be faster than waiting for me to get to the office to test for you...)  Once you have that saved- try loading it and starting your process again....

Let us know?  I'm sure we are going to find some setting in one of those two files is setting this up- and if that is the case we will want copies of those files so we can try to duplicate it in-house and prevent it... 

Thanks, Fred- sorry for the hassle.

 

Hi Robert,

I tried both your suggestions, but they unfortunately didn't work. Do you have any other suggestions that I could try?

Fred

Share this post


Link to post
Share on other sites
6 minutes ago, red fred said:

I tried both your suggestions, but they unfortunately didn't work. Do you have any other suggestions that I could try?

Hi Fred,

How did you load the flight plan?  If it was created by an external program, or if it s one you saved using a previous version of the 777, what happens if you create the same flight plan from scratch by manually entering all the waypoints, departure, approach, using the CDU screen?

Mike

Share this post


Link to post
Share on other sites
11 hours ago, Mike777 said:

Hi Fred,

How did you load the flight plan?  If it was created by an external program, or if it s one you saved using a previous version of the 777, what happens if you create the same flight plan from scratch by manually entering all the waypoints, departure, approach, using the CDU screen?

Mike

Hi Mike,

I always insert a flightplan manualy. I generate a flightplan with simbrief.com and I build it in the FMC by hand.

I know I could load is, but it's my own choice not to do that.

I just tried to enter a complete flightplan from one of the previous flightplans I saved.

It seemed to work at first. I could enter the legs page. But 5 tot 10 seconds later it crashes again.

So it comes down to this: As long as my ADIRU is not online or aligning, I can enter flightplans through the route page, but I cannot in any way enter the legs page.

Once my ADIRU is alligned I can do everything on any page.

It is nog a very big issue but I would to get it back to the state it was before the update.

 

Fred

Share this post


Link to post
Share on other sites

Try a brand-new flightplan. I had a CTD using an exising flightplan, but a new one seems to work (so far)!

Error was

Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: ucrtbase.dll, version: 10.0.15063.413, time stamp: 0x5ba8b66e
Exception code: 0xc0000409

 

Share this post


Link to post
Share on other sites

Hey Robert,

Problem is not solved with the july 12 installer.

Thanks for your support!!

 

Fred

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now