Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Can't fly in the usa anymore

Featured Replies

Hey!

My first question is... How do I allocate more memory to FS9?

I recently doubled my RAM from 4Gig to 8Gig... Is'nt that good enough?

 

Furthermore I'm flying in FS9, nothing to do with FSX....

 

And more.... I don't know StackHash error, my memory would not be properly configured.... What can I do, as a flightsimmer, and not being a computer specialist, in order to solve that? I'm affraid I cannot. And above that, the explanation on that error is complete like Chinese to me...

Sorry! But according to your last words, Jim, I will even not be able to solve that StackHash error?...

 

A crorrupt texture in the scenery\world\texture folder... I did already before replace all the textures in that folder, and I did it now again, but no solution.

 

So I tried anything possible what has been told here, up to now nothing helps. About the memory not properly configured, or not enough allocated to FS9, maybe some solution could be in there, because I did not yet do something in that respect, because I'm possibly not a computer specialist...

If somebody could explain me how to do both of thesethings, maybe I could find solution?

 

Greetz

Jive1

 

Where are you geing your replacment texture set from, disc 4? If you're able to fly everyplace else without issue and only crash entering a certain location it's not a memort issue. FS9 runs perfectly well on 1 gig of memory.

 

1. I would uncheck all addons in scenery file

2. Backup and delete fs9 cfg file

3. replace texture set in world texture from fs9 disc 4

4. if problem disappears shut down fs9 and check the box of 1 addon at a time and retest. To duplicate crash.

 

Try again again report back

Bill McIntyre

Asus StrixB650E-F Gamer, AMD Ryzen 9 7900X3D, Corsair Titanium DDR5 64GB, Samsung 990 PRO-4TB M.2, (4) 2TB SSD's, Corsair H1150i liquid cooler, RTX 2080TI Founders Edition, (2) LG 34" HD Curved Monitor, Sound Blaster Audigy X, 1Kw PC Power & Cooling Power Supply, Corsair Obsidian Full tower Case. MSFS 2024, WIN11 Pro x64                                                                                                                                             

  • Replies 37
  • Views 7.5k
  • Created
  • Last Reply

Top Posters In This Topic

  • Author

Hey!

Intermediate reporting....

Very strage!...

New test...

I disable the whole set of addon sceneries and start FS9. And the same crash happens, already now even withoout having chosen any departure airport, it happened before the choosing!.

Usually, up to this test, I only got the crash error when I start FS9 and first chose a departure airport somewhere in the USA by daytime, any season. So the crash always happened after choosing the departure airport. And also... When I do the same, but choosing my personal default departure airport EBAW in Belgium also by daytime there is never the crash error

So I wondered now why in this test the crash happened even without any addon scenery disabled?....

Interesting also... I noticed that the crash error always shows at exactky 56% of the scenery loading, you know, that indicator that shows a percentage of loading time, always at the same moment of loading up.... And!... So also with this test that I made without any addon scenery enabled!

And that looks very strange to me... Why is it always at exactly 56% of the scenery loading ?...

 

So far the intermediate reporting. I'm going to make further tests...

I'll be back!

Greetz

Jive1

Hey!

Intermediate reporting....

Very strage!...

New test...

I disable the whole set of addon sceneries and start FS9. And the same crash happens, already now even withoout having chosen any departure airport, it happened before the choosing!.

Usually, up to this test, I only got the crash error when I start FS9 and first chose a departure airport somewhere in the USA by daytime, any season. So the crash always happened after choosing the departure airport. And also... When I do the same, but choosing my personal default departure airport EBAW in Belgium also by daytime there is never the crash error

So I wondered now why in this test the crash happened even without any addon scenery disabled?....

Interesting also... I noticed that the crash error always shows at exactky 56% of the scenery loading, you know, that indicator that shows a percentage of loading time, always at the same moment of loading up.... And!... So also with this test that I made without any addon scenery enabled!

And that looks very strange to me... Why is it always at exactly 56% of the scenery loading ?...

 

So far the intermediate reporting. I'm going to make further tests...

I'll be back!

Greetz

Jive1

 

If you're crashing at 56% loading, you have corrupt textures in you,re world texture folder. Again replace the whole sceney\world\texture folder from oringinal from FS9 CD

Bill McIntyre

Asus StrixB650E-F Gamer, AMD Ryzen 9 7900X3D, Corsair Titanium DDR5 64GB, Samsung 990 PRO-4TB M.2, (4) 2TB SSD's, Corsair H1150i liquid cooler, RTX 2080TI Founders Edition, (2) LG 34" HD Curved Monitor, Sound Blaster Audigy X, 1Kw PC Power & Cooling Power Supply, Corsair Obsidian Full tower Case. MSFS 2024, WIN11 Pro x64                                                                                                                                             

  • Author

Hey!

Thank you all my friends!

Indeed!.. I checked the textures of scenery/world/texture...

On september 27 I replaced 11 water-textures by a set of so called better water textures. I don't know how it happened, but three of these textures were in my FS9 set of a very small size as compared to the eight other ones, so I replaced them again with the same textures from the original addon set, where all texturesindeed had the same size of 171kB.

How it happened that three of them were smaller in my FS9 set, I don't know, and I cannot trace that anymore.

Anyhow, by re-replacing these 11 water textures now, everything is now working fine, thanks to your help! For which I thank you very much indeed!

So I think that the first time that the error accured, and I told you a few days ago, that it happened in august, well, that must certainly have been for an other reason then....

 

Ones again, thank you all for the great help!

 

Greetz

Jive1

Glad you got it figured out. Enjoy flying

Bill McIntyre

Asus StrixB650E-F Gamer, AMD Ryzen 9 7900X3D, Corsair Titanium DDR5 64GB, Samsung 990 PRO-4TB M.2, (4) 2TB SSD's, Corsair H1150i liquid cooler, RTX 2080TI Founders Edition, (2) LG 34" HD Curved Monitor, Sound Blaster Audigy X, 1Kw PC Power & Cooling Power Supply, Corsair Obsidian Full tower Case. MSFS 2024, WIN11 Pro x64                                                                                                                                             

Hey!

My first question is... How do I allocate more memory to FS9?

I recently doubled my RAM from 4Gig to 8Gig... Is'nt that good enough?

 

Just for the record, Windows 32-bit hates to run on 8GB of RAM. Actually, when you reach 8GB, Windows 64-bit is pretty much required.

Apparently, things are really hot when fresh from the oven, or so I hear. I think we need to test this theory.

Hey!

My first question is... How do I allocate more memory to FS9?

I recently doubled my RAM from 4Gig to 8Gig... Is'nt that good enough?

 

Just for the record, Windows 32-bit hates to run on 8GB of RAM. Actually, when you reach 8GB, Windows 64-bit is pretty much required.

 

 

It’s not that Windows x86 (32 bit) hates to run on 8 or more GB or RAM.

 

The problem or I should say limitation is that Windows x86 cannot address memory beyond 4 GB. As a matter of fact Virtual Memory Address Space for 32 bit processes is 2 GB, unless coded and linked with /LARGEADDRESSAWARE flag or PAE extensions, but then the processor also must be capable of doing just that.

 

I could be wrong, but as far as I know FS9 is not linked with the /LARGEADDRESSAWARE option.

 

The /3GB switch as stated in a previous post allows Windows x86 to allocate up to 3GB of VAS to programs.

 

/userva

Use this switch to customize the amount of memory that is allocated to processes when you use the /3GB switch. This switch permits more page table entry (PTE) kernel memory but still maintains almost 3 GB of process memory space.

 

Note Microsoft Product Support Services strongly recommends using a range of memory for the /USERVA switch that lies within the range of 2900-3030. This range is wide enough to provide a large enough pool of system page table entries for all currently observed issues. Usually a setting of /userva=2900 will provide close to the maximum available number of system page table entries possible.

 

It does not matter if you install 8 or 16 GB or RAM, It won’t be available to Windows x86 nor to FS9

 

If you want to take advantage of your installed RAM, you only have one option. Windows x64.

 

Some useful links:

 

How to use the /userva switch with the /3GB switch to tune the User-mode space to a value between 2 GB and 3 GB

 

Memory Management - Demystifying /3GB

 

Memory Management - x86 Virtual Address Space

 

Memory Limits for Windows Releases

 

Handle Large Addresses

 

Cheers.

Ramón.
Time, is the one thing no one can buy.
ovbe94a9nab0bbc6g.jpg

 

  • Author

Hey!

Thanks for the information!

I have Windows7 Home Premium 64-Bit SP1, so I think that will do?

All the other information I will certainly study what is in htere....

Thanks again and

Greetz

Jive1

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.