Out of memory error (WinXP)

[Hansie]

Hi All,

I've got the out-of-memory error and I like to explore every possible option before I go and uninstall/reinstall FSX completely. Who knows what to do?

My specs: SW: WinXP Pro SP2; HW: Dell XPS700, Core2 6400, 2 Gigs RAM, Geforce 7950 GTX, TrackIR 4.

I bought FSX Deluxe on day 1 and although lower in FPS then expected, I liked it anyway. I've done a lot of scenery creation, hence my reluctance to reinstall. Then I installed the highly anticipated SP1. And yes! it made things better: less stutter and around 30-40% better FPS.

Then things took a wrong turn. I started messing with the grahics drivers because I really wanted that nvidia stereo anaglyph effect back in FSX. It wouldn't work. Then I found newer versions of the graphics card and installed them; replaced v84.21 with 93.13. Still stereo didn't work. All this took me through a lot of BOD's (blue-screens of death) and now I'm stuck with this:

When I start flying (with ultralight) from Boulder City Mun [61B] northbound, I never make it past the tree patch at the end of the runway.

- I did slide down the settings as the error message suggests even up to a point well below what I used before SP1,
- I uninstalled the stereodrivers,
- I tried v94.24
- I reverted back to v84.21 (all driver were installed from Windows Safe Mode)
- Yes it works with every setting on minimal, but that's just plain silly.
- I managed to sort out that the first setting with trees, gets FSX to produce the error.

This happens too on other locations, but Boulder City Mun has become a nice bench-marking one. Although it

[TheConfused]

I wish I could help, but it's nice to know that I am not the only one to get the "Memory could not be read" message. So far I have installed SP1 and now turned off the overclocking on my system to see if that cures that issue..

Good luck

Mart

[SubZer0]

Well I'm not too advanced in hardware, but I'll give it a shot. How much hard drive space do you have left? And maybe your RAM is faulty or maybe you should just try taking it out and putting it back in to see if that does anything. I probably wasn't of much help, but I wish you good luck figuring this one out.

SubZ

[macca22au]

Apparently FSX only allocates 2gig of VRAM or paging file, regardless of how much installed RAM or how much space you have allocated for VRAM.  However with XP there is a fix that will allow 3gig to be allocated.  I am sorry that I cannot recall where it can be found, but it is on the main sites.  Meanwhile pull some of your sliders back to stop loading choking your available virtual memory.  Max back to Very Dense etc.

[chiptas]

Well I'm not too advanced in hardware, but I'll give it a shot. How much hard drive space do you have left? And maybe your RAM is faulty or maybe you should just try taking it out and putting it back in to see if that does anything. I probably wasn't of much help, but I wish you good luck figuring this one out.

SubZ

Cool ill have too try getting in and out of my car next time it breaks down lol

[reider]

Well I'm not too advanced in hardware, but I'll give it a shot. How much hard drive space do you have left? And maybe your RAM is faulty or maybe you should just try taking it out and putting it back in to see if that does anything. I probably wasn't of much help, but I wish you good luck figuring this one out.

SubZ

Cool ill have too try getting in and out of my car next time it breaks down lol

He was talking about taking the memory chip/s out and reseating them, a valid idea.  This would be like taking a part of the car engine out and placing it back to make sure its seated properly, not just simply getting out of the car and back in again.......

Reider

[chiptas]

Well I'm not too advanced in hardware, but I'll give it a shot. How much hard drive space do you have left? And maybe your RAM is faulty or maybe you should just try taking it out and putting it back in to see if that does anything. I probably wasn't of much help, but I wish you good luck figuring this one out.

SubZ

Cool ill have too try getting in and out of my car next time it breaks down lol

He was talking about taking the memory chip/s out and reseating them, a valid idea.

[Hansie]

Hi,

Thanks all for replying! I will give that refitting thing a chance. That sort of stuff did help me in the past, so maybe...

@macca22au, I have initial size, as well as maximum size VRAM on 4092 Mb. I googled for some fix that should work in this area, but came up empty so far. I'll keep looking though. Let me know if you find something.

@SubZer0: 153 Gb free. So... no problem there, I guess.

Funny stuff with stepping in and out of your car!

Hans

[Hansie]

These are the next actions I took:

• A collaegue of mine suggested to disable the GC in the hardware section of system in the control panel, that way triggering the pc to come up with 'Found new hardware', but sadly that didn't do it.

• Then I did the RAM removing and refitting stuff, but to no avail either.

• I searched some more for a tool that let programs use 3 gb, but the closest thing I found was for Linux machines, better not try that then.

Well... one of these days I go and uninstall FSX. I won't do it right away, so please feel free to make another suggestion. Everything will be greatly appreciated!

Hans

[Nick N]

From what I understand, Nvidia released a beta video driver that is suppose to address this issue to a certain extent. I do not know if it is posted in the open yet yet or not but I have heard a few people testing it, the memory issue is gone.

[Hansie]

OK Nick, I investigated that idea too, but what I noticed is that of all the OOM discussions on the web, some 90% are related to Windows Vista, but indeed there is mention of a new beta version that does seem to work there.

I found this list of drivers: http://www.nzone.com/object/nzone_downl ... river.html and there you have 93.81. As said I tried 84.21 and 94.24 and now I will add yet another one to my collection. Mind you I'm starting to loose my confidence a little with these sort of actions.

But of course, if what you read was in relation with XP, then by all means try to find out what version it was and I'll be one mighty happy guy. nVidia is releasing beta versions like there's no tomorrow which tends to make things somewhat complicated.

[Nick N]

OK Nick, I investigated that idea too, but what I noticed is that of all the OOM discussions on the web, some 90% are related to Windows Vista, but indeed there is mention of a new beta version that does seem to work there.

I found this list of drivers: http://www.nzone.com/object/nzone_downl ... river.html and there you have 93.81. As said I tried 84.21 and 94.24 and now I will add yet another one to my collection. Mind you I'm starting to loose my confidence a little with these sort of actions.

But of course, if what you read was in relation with XP, then by all means try to find out what version it was and I'll be one mighty happy guy. nVidia is releasing beta versions like there's no tomorrow which tends to make things somewhat complicated.

I hear you and yes, I do believe the driver is for Vista. You can expect little support for anything under 8800 cards in XP pro because MS has a knife to the vendors throats to force a move from XP to Vista.

I use x64 for Vista and XP so I will most likely never see the problem. x64 does not have memory limits

Try this...


Browse to
CONTROL PANEL - SYSTEM - ADVANCED TAB - PERFORMANCE BUTTON - ADVANCED TAB - VIRTUAL MEMORY

[Hansie]

Well, I tried the page file thingy too, but sadly...

[Ivan]

pagefile fixed @ 2x memory

And check all the numbering in the cfg files...
out of memory usually has to do with scenery.cfg numbering errors

[Nick N]

[quote]Well, I tried the page file thingy too, but sadly...