Fsx often crash with my 777 :(

[koala63 2]

Im totaly agree with Nils_93, when PMDG will do a general update to stop the bugs? And also, when it's not our fault?...

 

Wait... wait and always wait  <_<

[Mike777 163]

I meet a problem since last week, in 5 flights on ivao network i crash 3... all the crash was when i was quietly on my cruize altitude not on the ground or approaching.

 

You might look at this thread:

http://forum.avsim.net/topic/421820-wrong-version-of-uiautomationcoredll/

 

I don't think uninstalling and reinstalling is going to help.  Unfortunately you need to try different things to figure out what the problem is.  If you haven't already, start with most of your display sliders all or most of the way to the left and see if that helps.  Were you able to use the memory monitoring tool PMDG recommends in the 777 Introductory Manual?

 

Also want to mention that the freezing problem reported above is different from your problem.  PMDG says they are working on the freezing and then resuming problem.  Yours appears different to me.

 

I don't see the point of trashing PMDG.  You seem to have a rather unusual problem.  If they cannot reproduce it they cannot fix it.  Most people are not having repeated crashes, especially during cruise.

 

Mike

[koala63 2]

Hello,

 

 

 

Most people are not having repeated crashes, especially during cruise.

 

Yes but how explain... all my plane are working fine without crash problem (MD-11, maddog pro, airbus aerosoft etc...)  

 

For the last time i install the T7, but this time i deleted the logbook.bin, pmdg said me the code of 777 product doesn't affect the logbook.bin... Ok im agree... but at this time i flew five time without crash.I read a lot of things with this logbook file in many forums, this is not an essential file to fsx and he can be corrupt quickly.So i know the code of the 777 not affect this file but maybe FSX affect the T7 with this file and at this time i can fly without bug since i deleted it (im planning a flight to Morocco now).

 

If you don't see me more in this topic... you know what you have to do.

 

Regards

[fredstras 0]

I installed new update FSUIPC and no more crashes at all...

[koala63 2]

Hello it's me another twice...

 

 

Im on flight to KBOS from France on IVAO network, so i got a big freeze (FSX no answer) for three minutes.I just let him (DON T CLOSE THE WINDOWS OR IT WILL REALLY CRASH) then second freeze (but without the fsx windowd no answer) he seem to be in PAUSE mode.i was 178nm of my LAT/LON and when the freeze disepear i jump to 161nm...

 

 

So im very angry with PMDG spending 89 dollars (68 euros for me) and get a product wich is not working well... i enjoy the plane and all his system are good, very good job of the team of PMDG but... when ou spend 68 euros or 89 dollars you MUST have a working product.

 

 

Now im fliyng to KBOS but i always ask me if i will can do all the way... BORING THINKS.

 

 

 

I installed new update FSUIPC and no more crashes at all    

For example when ou install IVAO, the installer update the version of FSUIPC, i don't think the problem is here.

[Jeff H 63]

So im very angry with PMDG spending 89 dollars (68 euros for me) and get a product wich is not working well... i enjoy the plane and all his system are good, very good job of the team of PMDG but... when ou spend 68 euros or 89 dollars you MUST have a working product.

 

Well first off, I think your anger is misplaced.  The 777 is a working product and I think there are a lot of people flying this aircraft without issue or complaint who will back me up on that...including you, as you seem to indicate in an earlier post.

 

And why i don't have problem when im play with my PC sony vaio i5 which is a lower configuration than my home computer?

So it's more likely that your system is the problem and not the program.  My first suggestion is to look at the crash to desktop guide, here:

http://forum.avsim.net/files/file/65-avsim-crash-to-desktop-guide-for-fsx-p3d-fs9/

You should also submit a support ticket at the Precision Manuals website as they will likely be able to assist you with a fix.  

http://support.precisionmanuals.com/Main/Default.aspx

Hope you get it worked out.

Cheers, 

Jeff 

[HiFly 16]

Just a quick question to all who have participated in this thread:  are you sure it is PMDG 777?  How many of you have recently switched to ASN and are now having lockups, CTD's on longer flights?

 

Many of us our experiencing the issue on other aircraft as well.  The common denominator seems to be that for the most part we have switched to ASN and it does not occur on short flights of less than about 1.5 hours inflight duration but on longer flights...the kind you fly with the 777.  Check out the HIFI forum and you will find that it is an issue that is beginning to gather momentum.

 

Now obviously PMDG products are more complex and do demand more memory and horsepower but if you are also using ASN for weather you may want to access their forum and add your experience to the threads.  The more heat we create the more incentive for the developers to come up with a true solution rather than their stock answer of "turn back the sliders on the cloud draw distance", etc.

 

Just a thought.

[rsrandazzo 6,353]

Gents-

 

One of the down sides to having so many product choices to use in the FSX environment is that you wind up getting a broad range of quality control with those products.

 

I strongly discourage the belief that "turning up the heat" is going to accomplish any good.  The guys over at HiFi are a good bunch- and they are proud of their reputation.  If there is a problem it will be obvious to them based on their support activity- so don't jump up and down on them just because that was the last thing you installed...

 

If it matters I have put about 40hrs of flying into the 777 during the past couple of weeks while using ASN and lately also REX 4.  I haven't had any CTDs/OOMs/VAS issues that some others report.

 

That being said:  I am EXTREMELY careful what gets installed into FSX because there are so many ways that developers can accidentally screw things up without realizing it.

 

Some of you may be aware that we gave you a very detailed "How To" guide with the 777 that will make keep you out of trouble with respect to VAS.

 

One of the most important pieces of information included in that guide is to be aware of the dangers of "photoreal" scenery.  As much as I LOVE some of the megascenery products- (Reno Tahoe has my house in it!) the fact is that poor programming within FSX causes the sim to load ALL OF IT into memory even if I am flying in a different part of the world.

 

For that reason, I disable the photoreal scenery when flying either the NGX or the 777.  I did this after months of searching for problems in the 777 during development- and since that time I haven't had a single OOM/VAS issue.

 

THIS IS IMPORTANT:  We **hate** telling a customer to reinstall FSX.  It is generally a bad practice to get into.  However- there are times when a customer has hundreds and hundreds of scenery packages installed that run the range from the highest quality OrbX or FlyTampa down to freeware scenery downloaded from some location you can't even find on google...  If you don't have a good feel for what is installed in FSX and you are having problems with it running- it might be time to cull some of those un-used VA apps and scenery packages that were released as freeware in 1984....

 

We have a ton of options available to us in the simming world- but not all addons are created equally!

<snip>

 

So im very angry with PMDG spending 89 dollars (68 euros for me) and get a product wich is not working well... i enjoy the plane and all his system are good, very good job of the team of PMDG but... when ou spend 68 euros or 89 dollars you MUST have a working product.

 

<snip>

 

Nameless-

 

I certainly appreciate your frustration.  It might surprise you to know that we get equally frustrated when we cannot diagnose and solve a problem that you are having.

 

You are our customer, after all- and we want you to enjoy the product.

 

Unfortunately, in all the communication in this thread I cannot diagnose the problem you are having because I cannot tell if you read/followed any of the advice we give out with our products.  This advice is designed to help you avoid the problems you are having- and to help you resolve them.

 

 I can tell by reading your posts that you have either not read, or chosen to not follow the advice we provide in that guide.  That makes it hard for me to help you solve the problem because I cannot be certain where the base line is- because you don't seem to be trying to help yourself with the help we are already providing!

 

(Example 1:  We make it VERY clear that you should not set up a default flight using our products... but you indicated in your post earlier that you have done precisely that...  It is a guaranteed route to CTDs.  We have been telling our customers this since 2004...

 

Example 2: We require users to sign their posts in this forum.  That is posted at the top of the forum here- and it even says you must read the post before posting here... but you chose not to- or you chose to ignore our requirements...)

 

So, Nameless...  We want to help you.  That is what we do for tens of thousands of customers...   But you have to help us to help you.  That means following our advice and suggestions at the very minimum!

 

You have gotten a ton of advice here- none of it which I think solved your problem- but at least you have had some things to try and that probably eliminated some other issues.

 

We don't know what you have installed with FSX- nor do we know what you are running on your own machine.  It know some folks don't like it when I say this- but after providing support of our products since 1997- we have learned that what you install on your machine matters.  Everything on your machine is related in memory somehow- and you have to keep that in mind when simming with high end addons.

 

If you have the tenacity to be patient and to work with us- I am certain we will be able to figure out the problem that ails you.  When a customer is interested in having us partner with them to solve a problem we almost always do...   And lets just be honest- 90% of our support effort is spent solving problems for which the answers already exist here in this forum.

 

But as I keep saying- we don't mind.  It is what we do- because we want you to enjoy this product.

[777simmer 117]

I have posted suggestions several times of what to do when you have problems with FSX.

 

The problem is that there are quite a few suggestions to make, and each time I forget one or two.

I have not looked at the AVSIM CDT thread.l..but I bet my suggestions are in there as well.

Nothing I invented!

 

But if we would just make a sticky.....then we would not have to keep repeating this.

 

Instead of this being a slow process that takes days (due to everybody being at different time zones).....like this

Are you overclocking?

yes

Ok set that back to default!

next day....

Ok I did, still crashes.

eeem did you start from a saved flight?

yes

Well dont, start fresh

next day.....

ok I did, still crashes :-(

What is your default FSX flight?

The PMDG!

Dont do that, make the default tryke or C172 or so your default flight.

next day....

Ok still crashes

Eeeh you have any other software running with FSX?

Yeah sure, Track IR, a weather programm, my IPAD with such and such app.

Ok, shut all that down and try again!

etc etc etc

 

And this here above is actually a good conversation because it is one with feedback!

Many times I see suggestions being offered that dont get any feedback as to whether or not any of it was even tried!!

 

If we would have a sticky on the top of this 777 forum, then we could simply ask:

"Have you tried all that is suggested in the XXXXXXX sticky?"

 

If the answere to that is yes....then you know we are on the same page and can start trouble shooting for less obvious things.

 

 

My suggestions:

(note: I did not invent this stuff....this is info I gathered by experience and from others (hardware/software specialist) who know what they are talking about......still though some might disagree)

 

-I use DX9. If you use DX10 (of which I know nothing)....then maybe try switching back to DX9 (it might not be the cause....but I say back to basics first!)

 

-check the list of known bugs (they will be fixed in SP1) and make sure you are not causing the CDT due to a known bug.

 

-If you have overclocked you CPU or RAM or GPU, make sure you set your Bios back to default when you have problems.

(just because one airplane has no problems on your current OC does not mean that non will)

Again, back to basics.

 

-I know reinstalling is not the first thing to try.....but if you installed anything (FSX,WIN7 or whatever addon) WHILE being overclocked....then it is very possible your install (FSX, WIN7, etc) is corrupted. NEVER INSTALL SOFTWARE WHILE BEING OVERCLOCKED. (not even when you think you are stable!)

First reset Bios, then instal software.

 

-If you reinstall....then Install all software you thrust (FSX, PMDG) with the antivirust scanner OFF

(the virus scanner can prevent some files from being installed)

 

-Install as administrator.

 

-create a clean FSX.cfg file with only these two very basic additions.

HIGHMEMFIX=1 (required!) and WIDEVIEWASPECT=true (for wide monitors)

 

you can add the rest of your tweaks (one by one!) after the problem has been solved.

 

-If you are using ANY other software alongside FSX, then close all of it.

If the problem stops then start adding them back one at the time.

As said, back to basics.

 

-leave an FSX default FSX aircraft as your default flight.

I just left that Tryke flight FSX ships with as default.

Do not change a PMDG aircraft to be the default flight!

 

-Create a fresh flight and choose the PMDG aircraft from the FSX interface.

choose you weather, location and time and then press fly now.

Do NOT first open a flight with a default FSX aircraft to then change in that opened flight to a PMDG!

After the PMDG has initialized (countdown finished) choose the panael state you want (but dont choose Cold and Dark for now as it has known bugs)

 

-run windows on Highperformance power plan.

Make sure it does not throttle back the CPU or shut down USB devices or harddiscs to save energy!

 

-if you use FSUIPC then update it to the latest version.

 

-did you update a driver recently?

If so, uninstall it and reinstall the previous driver (do not use driver rollback)

Never change a winning team....if all is fine dont update drivers....it will not make things better usually!

Note: Turn windows auto updating off so you can select the updates to install.

This prevents windows from automatically updating drivers without you knowing it.

 

 

Thats all I can think of right now.

Well, there is one more thing....but that might not be possible for everyone.

But I think you should use a dedicated Windows FSX boot with no other software to interveine!

[koala63 2]

Finaly i come back playing with my PC sony vaio... i tried reeinstall win7/64 on my home compter from the CD i have, next updating windows and finaly install fsx without sceneries, REX and other addons only the T7, same result, freeze and finaly crash of fsx.

 

 

@777simmer, im a developer under linux system, i use windows only for FSX and i know before posting i have to check all the settings to see if that fix my problems and if i post it's i tried many things... and for @Rsrandazzo with my job, i don't have many time at this moment to help you for help me  ^_^ maybe it's PMDG product... maybe my system... i don't know but what i know, im not alone to have a freezing problem with crashing system at the end.

 

@777simmer, i already check my FSUIPC version, fsx.cfg, uiaotimaticore.dll, reseting the bios etc... but one things you remember me it's an new update from Nvidia driver for my GTX660Ti.

 

Windows7 is on my Hard drive D:\ (i change that because before he was in C:\ on a Kingston SSD 60Gb, i was thinking maybe the problem is on my SSD with the writing system but no) i have a cool air refresh system with a Z68 Gygabyte and a i5 4470 processor with 8gb, my system isn't overcloacked.

 

 

We have to create an FSX version for all the linux system, because windows is a big s**** 

[koala63 2]

I found a lot of topic in AVSIM with "AppHangB1" error wich always happen to me if i close the windows when i have a freeze but the users seem to be following with his unsolved problem...

[777simmer 117]

Hi Koala,

 

There are quite a few threads about freezing FSX.

Read post #128 in this one, maybe his solution works for you as well

 

http://forum.avsim.net/topic/419895-777-freezing/page-6

[fredstras 0]

For example when ou install IVAO, the installer update the version of FSUIPC, i don't think the problem is here.

 

FSUIPC Last Updated: September 09, 2013, so if you installed IVAO before this date, your FSUIPC is not up to date...

[koala63 2]

Hi 777simmer,

 

 

I saw the post, it seem to be very easy... maybe too easy...  but i will try that because i changed many keys settings.But how i can shut up the warning of the autopilot OFF with the default key in the 777? because in the MD11 you just have to press two times the same key, in the 777 i remember at the begining i use it, the warning sound stay if i try to cancel it with the display button alarm.

 

@fredstras

 

I reeinstall windows and fsx last week, so my FSUIPC can't be the problem.

[Julean 12]

Sorry for now attended this post so late but its because of Christmas and New Year..

 

And Happy New Year to everyone :rolleyes:

 

After the new fsuipc and Active Sky Next, the trible 7 are not ctd. 

I landed in the new Oslo 2.0 and it OOM'ed.

 

 

Starting from VABB to ENGM