Hmm, okay, what settings did you pass IBT with?

 

Were your results (time per pass) mostly the same, along with GFlops?

Guys, as far as I know, you cant just copy someone elses .cfg and paste into your install.

Different GPUs require different .cfg files!

 

Here are my suggestions:(I have this text saved so I just copy/paste it here. might be that some things have already been offered)

 

(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! 

Are you getting blue screens or just an FSX crash?

 

I am curious about a couple of things:

 

1. Do you know how to over clock and how to test stability?

 

2. How many passes did you do in intel burn test? I would set it on the hardest test for your system, and do at least 10 passes.

 

3. Which OS do you have? (32 or 64bit?)

What I mainly see is your screen resolution. Are you on a laptop? Despite it being Nvidia, laptops are very aggressive about reducing power on the machine on various components, much of the tech invented post-FSX final version. So that could be a factor.

 

Try backing up your FSX.cfg, then deleting it and letting FSX create a new one. Don't tweak, except to add HIMEMFIX=1. Change no other settings. See what happens.

 

The simple thing I've seen with 777 CTD is just memory overload. Start with identifying that. Run FSX in a window, not full-screen, and have says internals.com Process Explorer installed and running alongside it. Turn on the Virtual Size column in PE. Report back how much VAS is being eaten by FSX, just on start screen, then at an airport running in the 3d engine.

 

 

Sent from my iPad using Tapatalk

hi Fleeting Thought

 

not a laptop no my pc specs are attached above in previous post because I cant past them for some reason.is win7 64

 

 

 

 

cheers

kav

My process explorer data as follows

 

 

virtual size for fsx

 

start screen is 3556000

 

and at omdb  fly tampa is 3700000

 

 so based on these figures I am guessing that due to the 3 gig memory limit of fsx I am already pushing over the limits right?

 

once in cruise the vas stabilizes to just over 3g but the ctds tend to be happening in cruise , minimal weather or clouds and no  traffic to been seen. ctds are basically just fsx quitting instantly to desk top , no blue screens just a message from windows saying fatal error encountered and fsx is gone

 

edit:  ok so as I was typing a got that fatal error fsx needs to close message. vas was just over 3g when the ctd occurred and less than it had been at the airport. so why doesn't fsx crash at the airport and not later because the vas usage was higher at the airport?

 

kav

I know you said your not running Enb Series mod but that was a cause of a ton of my FSX CTD's. I would double check for the two EMB files just to make sure and install the latest freeware FSUICP...

 

Last night however my T7 turned completely invisible in external view on the runway and I had to restart FSX to get it back... very strange!

I have never even purchased emb but where would I find these files anyway

 

I have the latest fsuipc yes

 

 

regarding your invisible plane I would think that is a graphics card issue probably

 

 

kav

hi Fleeting Thought

 

not a laptop no my pc specs are attached above in previous post because I cant past them for some reason.is win7 64

 

 

 

 

cheers

kav

My process explorer data as follows

 

 

virtual size for fsx

 

start screen is 3556000

 

and at omdb  fly tampa is 3700000

 

 so based on these figures I am guessing that due to the 3 gig memory limit of fsx I am already pushing over the limits right?

 

once in cruise the vas stabilizes to just over 3g but the ctds tend to be happening in cruise , minimal weather or clouds and no  traffic to been seen. ctds are basically just fsx quitting instantly to desk top , no blue screens just a message from windows saying fatal error encountered and fsx is gone

 

edit:  ok so as I was typing a got that fatal error fsx needs to close message. vas was just over 3g when the ctd occurred and less than it had been at the airport. so why doesn't fsx crash at the airport and not later because the vas usage was higher at the airport?

 

kav

 

I had trouble with the NGX because of the 64 bit Windows problem.  The folks at PMDG support sent me a program to install into FSX that solved it.  

 

Colin Ware

Seattle

One thing is that the longer you fly, the more terrain (and cloud, water, other aircraft, traffic, ships, boats, etc.) data gets streamed into memory; and FSX is kinda laggard about dropping it back out.

 

So, even if you're just under full VAS load at start, if you're close to the edge, and flying over any areas that feature more content in any of the categories above, you're going to fill up rapidly.

 

The simplest solution is to think about your flight path (I use flight planning software in part for this) and think about whether your flight is hitting any "heavy" areas along the way.  Save a config that has the right things turned down and it should help.

 

That's about all I can say from my own research so far.

If you are having a startup VAS of 3.5 or even 3.7 GB, something is seriously wrong, but as you state you are crashing at 3GB, the VAS seems not to be the issue.

 

Though, I have a high end system with a huge load of add ons, and I am nowhere near those figures at the start of FSX. 

 

I would start with this:

 

0. Don't worry about ENB as the user above suggested. If you don't know what that is, you will not have it on your system at all.

 

1. Delete your FSX.CFG file. (just add ".old" to the end of the file, so you keep it as a backup.) then restart FSX so it creates a new one. After restart you have to reconfigure your settings. 

 

2. Update Nvidia drivers to the latest from their website and ditto for inspector.

 

3. Reset your settings in your BIOS. If you don't know how to over clock, don't(!), because you will very likely create an unstable system. (just select reset to defaults in you bios!)

 

4. Run FSX in lower than your current settings, monitor your hardware and see how it goes. try to do a short flight.

 

5. Make sure to run FSX as admin.

 

6. If you know how to, do a BIOS upgrade if there is one available for your mono. This might help if there is some kind of conflict with your video card. 

 

Keep in mind that you will get very very limited performance from that processor! the 777 will almost kill your core_0 if you don't keep your settings low!

 

I suspect your BIOS settings are unstable as you seem to be a bit confused about over clocking and you are crashing with 3gb VAS usage. 

Hi outofphaze

 

thanks for your advice here I will try your suggestions again although I have pretty much done all of that already at one stage or other.

 

one thing though you suggest my processor will give very limited performance which I am suprized to hear do you really think  an Intel core I 7 980 is a slow processor? I know its a few years old but I wouldn't think of it as slow really?

 

 

kav

Hi Kav.

 

Sorry about that.

 

I read somewhere in the post you had a core2duo, but I guess that was someone else!

 

You have a very nice processor. Are you using an affinity mask setting in your fsx.cfg file?

 

It would increase performance in fsx if you turn off hyper threating in your bios, and then use affinity mask setting of 62. (Remember, this is only the correct setting if hyper threat is off!)

Go into the scenery window and uncheck everything that is not stock scenery. Set up the dll.xml with only the PMDG777 items. Use a default fsx.cfg, restart FSX and set LOD radius and Autogen to the middle, set Ai objects off. Now try out a flight in the 777. :biggrin:

no probs yeah definitely not a core2duo : )

 

stock fsx cfg except for highmemfix tweak so no affinity mask tweak no. will try turning hyperthreading off in the bios.

 

 

 

Steve

 

thanks for your suggestions too could you explain what you mean by set up the dll.xml with only the pmdg items? and how to do that

 

 

tks

 

kav

here are my pc specs attached again sorry I cant paste them in to post I have some issue with the forum site and it wont allow it for some reason

 

 

cheers

 

kav

MY PC SPECS.txt

Make a backup of your current dll.xml file, and then edit the dll.xml file with, say, Notepad++ (downloadable freeware), to avoid introducing spurious formatting characters into the XML file, and only allow the PMDG XML entry to be enabled. There is detailed advice available on this here and in the Internet if you are unfamiliar with XML (it is merely a text-based scripting language, eXtended Markup Language, as opposed to HTML, Hypertext Markup Language, both derivatives of SGML, if memory serves).