Page 1 of 1

Memory could not be 'read' error in FSX

PostPosted: Mon Apr 23, 2007 12:03 pm
by TheConfused
Hi everyone
I have the following problem. I am running Win XP Pro and on that have FSX. They are both installed onto a clean new drive. I have  had the same error on another installation on the same computer (I have dual boot). When either FSX is loading after choosing aircraft type/location/weather etc.. and it's loading scenery files or what ever I have an error message come up saying' memory referanced at 0x0b72c739b at 0x2c9b72b memory could not be 'read'   This is roughly what the message was as I did not write it down. It also happens when flying the aircraft and could be at anytime. I have tested my memory (3GB) using Memtest 86 and it ran for 18hours and found no problems. I was wondering if it maybe GFX memory, but I dont know of a way of testing that. The PC works fine apart from that, but the only other issue I had was installing Vista Business, where it would just crash all the time..could that be part of the same problem??

I thank you in advance for any help..

Mart

Re: Memory could not be 'read' error in FSX

PostPosted: Mon Apr 23, 2007 12:12 pm
by Nick N
that has been known to be caused by several things.. defective memory,  add-on scenery or a page file issue in Windows

The easiest thing to change is the page file. Increase it. Set it to a static size of 3070-3070 on the C drive, reboot and see if that cures it

Re: Memory could not be 'read' error in FSX

PostPosted: Mon Apr 23, 2007 12:28 pm
by TheConfused
Thanks Nick, I have just changed it and will test . Incidently, I have no add on scenery files installed (yet)

Mart

Re: Memory could not be 'read' error in FSX

PostPosted: Mon Apr 23, 2007 12:38 pm
by Nick N
Thanks Nick, I have just changed it and will test . Incidently, I have no add on scenery files installed (yet)

Mart



I have usually seen that associated with bad BGL's and landclass files.. and an entire list of badly made scenery addons... I have also seen it associated with the FS9.1 update

I assume you installed the 9.1 update?

If so, when you did the update... did you put the updater INSIDE the Flight Simulator 9 folder BEFORE you ran it?

If not, you most likely corrupted your modules. You will need to uninstall the FS9.1 update, delete the BACKUP folder it created in the FS9 directory and then reboot, reinstall the update by running in from INSIDE the Flight Simulator 9 folder

Re: Memory could not be 'read' error in FSX

PostPosted: Mon Apr 23, 2007 2:24 pm
by TheConfused
Hi Nick. I have not installed FS 9 on that part of the system yet. I hopefully now have a screen grab of the exact message I get when running FSX. I dont think the numbers are the same everytime though.



All right, how do you add images to this message? The button does nothing.

Re: Memory could not be 'read' error in FSX

PostPosted: Mon Apr 23, 2007 3:07 pm
by Nick N
Hi Nick. I have not installed FS 9 on that part of the system yet. I hopefully now have a screen grab of the exact message I get when running FSX. I dont think the numbers are the same everytime though.



All right, how do you add images to this message? The button does nothing.



You must click UPLOAD IMAGE at the top and a new window will open. The image must be 800x600 or less and 100k or less in size. Use the address it provides for the post.


The error message probably wont tell me much but post it.. It sounds like something is corrupted. I would install the 9.1 update as specified and see if the problem persists because 9.1 and XP SP2 are very important to FS9

I would try changing the setting "render to texture' from what you are running now and see if it ceases... if it does, there is probably a driver or corrupt texture issue involved. The correct setting for that is ENABLED or checked. If it is currently enabled, disable it and see what it does and visa versa

If the problem still comes up, my next advice would be to pull a stick of memory, leaving the page file as is and running 2gigs on the Dual Channel (matched color) sockets of the motherboard.

If it still comes up, I would try a driver upgrade or downgrade and if it still pops up... hmmmm