Ok I just had a chance to run test. Its still freezing around the IAD area. I went back to default for IAD and checked the airport around it with scanafc and didn't find any double AFCADS. I disabled UT and that wasn't it. I also disabled my DC JFK BWI and still got the freeze.

And the offending DLL is . . . ?

 

John

Just run the F!#%ing patch!!......if it doesn't help your problem then you can revert back to the original exe (which the program will create a backup of) at which point everyone can say "I told you so" and you can continue to chase your tail.....it is an exercise that will take 5 minutes of your time........and it will finally put me in my place  (for better or for worse) :rolleyes:

Ok this is what I did JS I unchecked everything restarted FS rebuilt the scenery. Rechecked everything back restarted FS rebuilt scenery and all went well that time no freezes

Wow, a bad scenery file!

 

Now, it doesn't even need to be a scenery in the area. So now your task needs to be to enable one of your sceneries at a time until you get the freeze again. Start with your UT scenery and make sure they are all up to date as well. I do recall an early version had an issue with winter textures.

Well .......perhaps Jim and Bill are right, perhaps your problems are not related to only using 2 gigs of ram to run your FS ????

Anyways, there is a bucket of water......it's up to you if you wanna have a drink.

I will keep an eye on this thread......but I will now shut up

Good luck either way

Cheers

Romflyer

 

No offense but perhaps you should follow your own advice here. He's troubleshooting now in the right direction with Jim. Please take a chill pill. And let them figure things out.... B) B) B)

No offense but perhaps you should follow your own advice here. He's troubleshooting now in the right direction with Jim. Please take a chill pill. And let them figure things out.... B) B) B)

Hey Bill.....no offence taken.

My last post was said, and intended, in a light hearted manor  :wink: ......Hopefully he and Jim can figure it out.

If they come to a dead end (as I expect) then I hope the OP will take the time to go back and take my advise seriously......despite the rush to disregard my suggestions. ......the goal here is to help out a fellow simmer to get to the bottom of a problem.

Cheers

Ok I did a flight from CYUL to KCLE. When I got to about Dansville NY it froze. Now I did a flight from KBOS to KCLE and it took me to SYR VOR then down toward Dansville. I went thru there that time no problem. So what was the difference between the two flights except one was from the North the other from the East. Jim any thoughts on this?

There seems to be a little confusion here about the whole 3GB patch, 4GB patch, however you want to refer to it.   Let's first clear something up.  OOM errors, more often than not, have absolutely nothing to do with how much RAM you have in your system, nor does it have anything to do with how much virtual memory is being used.  FS9 is a 32 bit application and is restricted to 2GB of addressable memory, as are all 32 bit apps.  OOM's often occur when something in the sim, a specific scenery for example, tries to access a memory address that isn't available to it within the program's allocated 2 GB of memory.  The result is a CTD, sometimes with an OOM error message, sometimes not.  And it may not always happen.  A short flight to an airport may go just fine, whereas a long flight to the very same airport will CTD with an OOM error. 
Now, as for the 3 GB patch; there are two components to this.  The first involves editing your boot.ini, and this is only applicable to a 32 bit OS.  If you are running a 64 bit operating system, then you don't have to worry about this part.  The second part of this is making the FS9 executable able to take advantage of additional memory address space.  This is done by setting a flag in the executable to make it large address aware.  This is done with a program called CFF explorer.  It's easy to do and is non destructive.  I have this flag set myself, and I have never experienced an OOM error since I set it up.  Now that said, this may be the problem and solution for the OP, it may not.  Going through a systematic troubleshooting process is just sound practice.  Either way, let's all try to take a breath and focus a little more on resolving the problem and a little less on who's right and who's wrong, yes??

Cheers!!   :smile:

 

Edit:  My apologies.  It seems everyone did take a breath.  I failed to look at the post dates.  My bad.  
To the OP, what exactly is happening now?  Are you just freezing up or crashing to the desktop?   
 

OP,

 

All with default scenery and zero AI traffic?

 

By freeze do you mean that FS is showing on the screen but nothing is happening and you can't access any part of the program?

Jim - the problem is that you can disable all add-on scenery directories but that doesn't actually disable all files as many add-ons place extra files into default directories etc. The only way to be 100% certain all addons are removed is to work from a squeaky-clean fresh installation and we know that would work perfectly so there is probably little point in going there.

 

I appreciate that if FS completely "freezes" no error message may be given* but I am surprised at the OPs reluctance throughout this discussion to follow my requests concerning error messages when FS crashes. As such I cannot really contribute further with suggestions.

 

John

 

* - even then, usually FS does fail with an error message.

I am beginning to suspect that the problem may be an AI issue - thus, if the issue is not a CTD, it may be conditional on the time of day - whether or not a particular AI aircraft with a corrupt texture is at that airport. Again, though, the situation is as John Hinson has noted - the OP has not taken any steps to troubleshoot his problem and appears to be relying wholly on us. As such, we cannot reasonably expect to find a solution.

Another link http://forum.avsim.net/topic/429619-fs9-crashes-right-before-a-landing/

Similar problem...... With a positive ending.....???

"Except this time, it said I ran out of memory again."

 

Big difference than in this thread.

...if the issue is not a CTD...

...OOM, I meant OOM...

Jim, If you go back and re-read that thread http://forum.avsim.net/topic/429619-fs9-crashes-right-before-a-landing/  the OP says that originally he got an OOM message but later his sim was just crashing/CTDing/freezing without that specific message......this fits with my experiences, it fits with Jeff's earlier remarks, and even though you don't like it...it fits with the problems of the OP in this thread.