What's wrong with this???

[Alonso]

I just started FS as I would do any day.. and I got this:




(this means: "The instruction in 0x7c14f0e7 makes reference to the memory in "0x0000001c. The memory can't be read. Click ok to finalize the program")


I have 30gb of free space on FS drive...
And I use to start FS with at least 400mb of free RAM...

I found this:
http://support.microsoft.com/kb/892610

I rebuilt the paginig file but I'm still getting the error message

Do I have to reinstall FS9? Oh lord... :-/

[Fozzer]

I'm afraid the Lord wont be much help, Alonso!......!

LOL...!

How much memory have you got installed?

I have 2.3 GB installed to prevent FS 2004 from spooling off the Hard Drive when running.

Paul...G-BPLF...FS 2004 and Win XP.... 8-)...!

[Alonso]

But my FS was running so softly

It's the first time I recieve this error... Now I will reboot and wait for windows to make a "chkdsk" for "E:"  :-/

[Sean_TK]

Have you added any addons of any type within the last few days?
Also, you indicated that you have enough room on your flightsim drive, but what is the status of your space and memory on your system drive, since FS loads some core files from their as well, such as your FS9.cfg, scenery.cfg, and some other general startup files.

[KC Jones]

Got the same message after......

doing a virus scan or defrag, can't remember.

Get MaxMem to 'flush out' your memory.

or reboot

Nothing serious but can scare the heck outta you.

In other words...no biggy.

KC
ps - if it is indeed a failing memory stick or errors related to memory sticks ...after a reboot don't solve your problem....there is a MS program for 'cleaning' your memory sticks [as I call it - the 'scrubber'] that will run tests on your physical memory sticks and make them all better.

[rpjkw11]

I use Rambooster.  Before firing up FS9, I always do a quick check of available RAM and if it's less than 600mb, I have Rambooster do a quick optimization to around 620-650mb.  Then I'm good to go for almost anything.

Bob

[jrbirdman]

I am having this problem as well and my memory is still running at 50% and I have 3 gigs of ac. I have tried these suggestions and none worked. Any other suggestions would be greatly apprieciated as this is all I have. Without my sim I go crazy.  :'(  :-[

[pepper_airborne]

Sound like a memory error, you could try running a memtest to see if any of your sticks are screwed, not quite sure how to do it, but ive seen people do it before, maby you could ask NickN.

[garryrussell]

I had that a while ago simple because I was busy on projects and ran out of memory when FS tried to power up

Offloading files onto back sorted that out.

Garry

[beaky]

Check your system cache size (virtual RAM)... that's often the source of this particular error message.
I know it refers to cleaning up your disc, but it may not be that.
Re-setting your virtual cache limit may re-allocate a nice clean spot on the HDD for that.

[Alonso]

Had to reinstall FS like a month ago...

Tedious task that was!

[jrbirdman]

A little update for the masses. I uninstalled then reinstalled. Nothing. Then I also ran ramboost. Nothing. I don't know how to do memtest and I really don't know where on my computer, I would find the cache file that I should check?Tomake I long story short, I'm still stuck.  There has to be a solution. I am having a sim fit. (I never thought I would hear myself saying that one.) Would someone be willing to help me by walking me through this or something?

Posted by: rottydaddy Posted on: Yesterday at 15:35:45
Check your system cache size (virtual RAM)... that's often the source of this particular error message.
I know it refers to cleaning up your disc, but it may not be that.
Re-setting your virtual cache limit may re-allocate a nice clean spot on the HDD for that.  

[Daube]

I had this problem about missing memory in the past when I flew FS9.
My virtual memory was set to "let windows handle", something like that, automatic, that is.
What I did:
- disable completely the virtual memory, so that the page file gets completely erased on the next reboot and do not disturb the future defragmentation
- reboot
- disk check
- disk defrag
- set the virtual memory back, but with a fixed size (I had 1Gb of RAM, and I have set my virtual memory to 4096 min and 4096 max)
- reboot.
Never had the message again.