Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Has anyone else received this error after installing FSUIPC4.02? I don't know if FSUIPC is the problem or not but it's was suggested at the FSX forum that I repost here. I have been using FSX for over three weeks and only had this error occur since installing FSUIPC4.

Here's a link to the original thread:

http://forums.simflight.com/viewtopic.php?t=57130

fsx.exe application error

The instruction at "0x7c809783" referenced memory at "0x40872324"

The memory could not be "written"

Click OK to terminate

Dell 8400 640(3.2GHz/800FSB) | 2GB pc2-4200 | 256MB GeForce 7600 GS - 91.47 drivers) | Samsung 204B 20” LCD Monitor | WindowsXP Home (SP2) | DirectX 9.0c

Posted
Has anyone else received this error after installing FSUIPC4.02? I don't know if FSUIPC is the problem or not but it's was suggested at the FSX forum that I repost here.

The address isn't one that I've seen occur at all in any crash yet. But there appear to be a few bugs in SimConnect which we are trying to nail.

Can you tell me more about the circumstances. i.e:

1) when it occurs

2) what else is installed over and above the base FSX

3) whether you've registered FSUIPC

4) show me the FSUIPC4.LOG please

There are some other things tthat may help but they start to get complicated, so let's see those first please.

Regards

Pete

Posted

Can you tell me more about the circumstances. i.e:

1) when it occurs

It has only occured once and that was after about an hour of using FSX.

2) what else is installed over and above the base FSX

PAI & WAI traffic files and ASV6.5 which wastn't connected at that time.

3) whether you've registered FSUIPC

No, I only use it with ASV

4) show me the FSUIPC4.LOG please

Here is the latest log...I had no errors during that time period of use.

********* FSUIPC4, Version 4.02 by Pete Dowson *********

User Name=""

User Addr=""

FSUIPC not user registered

WIDEFS not user registered, or expired

Running inside FSX

Module base=61000000

LogOptions=00000001

DebugStatus=0

250 System time = 16:35:54

250 FLT UNC path = "C:\Documents and Settings\my name\My Documents\Flight Simulator X Files\"

250 FS UNC path = "D:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

1297 SimConnect_Open succeeded: proceeding to initialise interface!

1297 FSUIPC Menu entry added

23563 Running in "Microsoft Flight Simulator X", Version: 10.0.60905.0 (SimConnect: 2.0.60905.0)

23563 c:\documents and settings\my name\my documents\flight simulator x files\Cessna 172 at DAL.FLT

23563 D:\Program Files\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\C172\Cessna172SP.AIR

30063 System time = 16:36:24, FSX time = 16:36:16 (22:36Z)

163953 Advanced Weather Interface Enabled

3318485 System time = 17:31:13, FSX time = 13:45:45 (20:45Z)

3318485 *** FSUIPC log file being closed

Memory managed: 705 Allocs, 705 Freed

********* FSUIPC Log file closed ***********

Posted

It has only occured once and that was after about an hour of using FSX.

Ahin that case it isn't related to the initialisation issues we are investigating. There is a small chance that it could be a Simconnect problem, but I'm afraid the address is actually in a general library routine so it could be due to anything. The only answer is to tell MS I'm afraid. With it not being reproducible its going to be difficult for anyone to pin down in any case, so we just have to hope that they do get sufficient information over a period.

PAI & WAI traffic files and ASV6.5 which wastn't connected at that time.

3) whether you've registered FSUIPC

No, I only use it with ASV

In that case FSUIPC4 isn't actually doing anything except being the recipient of messages from Simconnect, with which FSUIPC simply updates its oinformation in case any application needs it.

If the crash is down to an add-on, then the Traffic changes are more likely. There have been many subtle changes in the AI traffic system and no one is really very sure how compatible it is with files made for previous versions of FS.

However, if you have only had it happen once so far there's not a lot of point, at present, in trying to eliminate anything by uninstalling.

Regards

Pete

Posted

Well, it happened again but this time along with the FSX.exe Application error I also received a "do you want to report this error to MS" message and the error turned out to be caused by Adobe Reader 7.0 trying to update itself even though I had chosen do not check for critical updates in Adobe preferences. Looks like it over road my preference and started checking anyway! I went ahead and updated Adobe then ran msconfig and unchecked any Adobe programs listed in startup so hopefully this won't happen again.

Posted
Well, it happened again but this time along with the FSX.exe Application error I also received a "do you want to report this error to MS" message and the error turned out to be caused by Adobe Reader 7.0 trying to update itself ...

Hmmm. Weird though. Thanks for letting us know.

Regards

Pete

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.