Dear All,On Saturday, I was conducting a routine FS9 when the PC came up with a strange error message and I had to shut the program down. I have just repeated the same flight and once again the FS9 shut down at exactly the same point. This time, I wrote down the error message, which wasThe instruction "0x2077660c" referenced memory at "0x09612874" the memory could not be written. Click OK to terminate the program.Any ideas what the problem is?I wasn't flying near any built up areas or where intensive flight activity was happening, as far as I could tell.I would appreciate any help on this as I am truly baffled by it.Best regards,Peter Keenan

Hello,Can you post the first step of the report of error ?Like this:http://www.adventure-unlimited.org/faultfinding.phpUsually it's more easy to give or receive some help from there :)Regards.Gus.

Hello,Can you post the first step of the report of error ?Like this:http://www.adventure-unlimited.org/faultfinding.phpUsually it's more easy to give or receive some help from there :)Regards.Gus.

Thanks for the plug, Gus :o)By the sound of this report it sounds like a Windows hiccup and not an FS problem. Quite frankly, if it has only occurred once I would forget about it.A web search for The instruction referenced memory at the memory could not be written. Click OK to terminate the program.(i.e. leaving out the specific figures) will bring lots of results. Just one I picked out, referring to MS Access actually, read:"This is not an Access [or, program-specific] instruction that the message refers to, this is a low level memory read error from windows. If this is happening predictably it could be: 1. a bad memory module. 2. A conflict with another dll or ocx control trying to compete for the same memory area." "If you have Dr Watson running and trapping errors, you can gain some additional insight into what is happening at the 'moment of impact'"http://www.experts-exchange.com/Databases/...Q_20809500.htmlHope this helps,John

Hi Guys,If I recall, the first message said that I was out of memory and needed to clear some space on my hard drive. Now, as I'm running XPPro 32 bit with a hard drive that has over 500GB free and with 8GB memory, albeit limited by FS9 and being a 32 bit program, I was some what surprised to receive this message.I then had the second message that came up which is that that I referred to in my first post.As I said in my first post, this has occurred two times at exactly the same point in the flight - I'm flying at 39000 ft south of the Chicago area.I have not had any issues flying into any of the Chicago airports, so it can't be that which is the problem.The only thing that I can think of is that it might me a scenery problem at my departure airport KSLC, in combination with the long flight (to Baltimore). However, I haven't found anything in the KSLC scenery that I would identify as being the problem.Best regards,Peter

Well, I will relate my error (first one in 2+ years). I was running an instant replay of landing (2nd time) and so I hit key to change view from cockpit to spot view, followed immediately by hit of 'Esc' to end replay and neither one happened-I got no response. A few seconds later I got the '.. instruction at 0x7c809823 ..ref memory at 0x0e9b70bo ..could not be written' and 'ck ok to terminate..'. So I probably caused this with too rapid a sequence of inputs (keypresses), maybe? There could be other ways to cause this 'error', I guess. But I am not worried and did not change anything and I fly, and do instant replays, all night with no sign of anything being wrong. Of course, in your case, it could be co-incidence? Nah. Too far fetched. It's scenery. And I am not interested in tracking down (or capable of) a solution. Just info, for whatever it's worth.CBNapamule

If I recall, the first message said that I was out of memory and needed to clear some space on my hard drive. Now, as I'm running XPPro 32 bit with a hard drive that has over 500GB free and with 8GB memory, albeit limited by FS9 and being a 32 bit program, I was some what surprised to receive this message.

Aha, the goal posts are on the move. A shame you didn't mention this before. "Windows has run out of available memory" is presumably the message you got, although you seem a little vague about it.An Out of Memory error (often referred to as OOM) is a totally different issue and is a common issue frequently raised in forums. It has nothing to do with your disc size or actual memory levels. Suggest you search the forum, or indeed the entire web, for this.JohnPS - did you look at that link Gus gave you - there is even mention of it on that page!

Dear All,On Saturday, I was conducting a routine FS9 when the PC came up with a strange error message and I had to shut the program down. I have just repeated the same flight and once again the FS9 shut down at exactly the same point. This time, I wrote down the error message, which wasThe instruction "0x2077660c" referenced memory at "0x09612874" the memory could not be written. Click OK to terminate the program.Any ideas what the problem is?I wasn't flying near any built up areas or where intensive flight activity was happening, as far as I could tell.I would appreciate any help on this as I am truly baffled by it.Best regards,Peter Keenan

The fact that your CTD occurred at the same spot,makes me wonder if you have installed the fs9 patch/update (or whatever it was called).AndyAndy

The fact that your CTD occurred at the same spot,makes me wonder if you have installed the fs9 patch/update (or whatever it was called).AndyAndy

Dear All,I'm convinced that it must be a problem with an AI texture or a scenery file at KSLC.I've flown elsewhere in the US and in Europe without any problems.Best regards,Peter

I'm convinced that it must be a problem with an AI texture or a scenery file at KSLC.I wouldn't be so quick to assume that's the problem.I've flown elsewhere in the US and in Europe without any problems.Have you ever flown that route before without getting the error msg? How many times have you flown it since the original error msg? Did you get another error msg? If no, had you rebooted the machine or no?

I'm convinced that it must be a problem with an AI texture or a scenery file at KSLC.

Simple to prove.Turn off AI and test.Disable any addons for KSLC and test.Just don't do both at the same time.regards,Joe