Hello, I'm having this weird FSpassenger problem where whenever a cabin service is performed, FSX will CTD, throwing BEX error according to appcrashview.
Initially I thought it has something to do with the mini panel and the buttons, so I switched to automatic service, and exact same thing happened.
After a minute or so after cabin service, FSX will crash. I have tried a flight without service, and sure enough, it did not crash.

Pretty sure it's not the menu crash, since flying without fsp or service it does not crash, period. and i do have the uiautomation.dll fix applied.

Tried reinstall, nothing. After some searching, found only about 2 other people experiencing this.
I'm running windows 8 pro 64 bit, but that should be irrelevant, as the other 2 ppl reported the issue before win8 came out. And other people managed
to use FSP on windows 8 just fine as far as i can tell...

Oh yes, playing a movie/music on the ground does NOT lead to a crash. Only drinks and food.

specs are relatively new (see sig), so shouldn't be hardware related...as it doesn't crash without performing cabin service:
 

 

(I have posted the same on fspassenger forum, but since that forum is not active at all, going to try my luck here)

The uiautomationcore.dll "fix" only works for stopping FSX Menu crashes.  Repeatedly hitting the menu should cause this crash.  It does not fix any other type of FSX CTD (otherwise you wouldn't be posting here...). 

 

If you are getting a BEX error, what was the faulting module?  BEX means you had a Buffer_Exception_Overrun and most likely something to do with your system memory.  If you have your settings set too high you will get a BEX CTD. 

 

Have you tried uninstalling/reinstalling FSP.  Perhaps it is missing the files. 

 

It could be a sharing problem too. You need to right click the FSP folder and then click on Sharing... or Properties and make sure the folder is shared with everyone.  Same with the main FSX folder and subfolders.  Microsoft wants to protect you from other people looking at your files.  Make sure User Access Controls are disabled too (if Windows 8 has a Search box, you should just type in the box User Access Controls and it will tell you how to enable/disable UAC).

 

Hope this helps.

 

Best regards,

Jim

The uiautomationcore.dll "fix" only works for stopping FSX Menu crashes. Repeatedly hitting the menu should cause this crash. It does not fix any other type of FSX CTD (otherwise you wouldn't be posting here...).

 

If you are getting a BEX error, what was the faulting module? BEX means you had a Buffer_Exception_Overrun and most likely something to do with your system memory. If you have your settings set too high you will get a BEX CTD.

 

Have you tried uninstalling/reinstalling FSP. Perhaps it is missing the files.

 

It could be a sharing problem too. You need to right click the FSP folder and then click on Sharing... or Properties and make sure the folder is shared with everyone. Same with the main FSX folder and subfolders. Microsoft wants to protect you from other people looking at your files. Make sure User Access Controls are disabled too (if Windows 8 has a Search box, you should just type in the box User Access Controls and it will tell you how to enable/disable UAC).

 

Hope this helps.

 

Best regards,

Jim

Thanks for the fast response,

the fault module according to appcrashview is "unknown".

Yes I have tried reinstalling fsp and fsx, no help

UAC is the first thing i disabled once I got windows 8

I didn't install FSX in system partition, and i'm the only user on my computer. Sharing was disabled i just enabled it, I don't think that's the source of the problem tho?

 

My settings are rather high, but i'm checking my resource usage it's using nowhere near the limit. 4.2GB/12GB RAM, and 608MB/2048MB VRAM, with fsx taking up about 1.5G of systam RAM and ~530MB of VRAM. Plus it doesn't crash at all if I do not serve food/drink to passengers. and I never got any OOM errors.

 

I have noticed, however, that it happens 99% the time when I minimize fsx or switch it to background(running browser). If i keep fsx window on top, the crash is a lot less frequent. (Running in windowed mode). But like I said, only happens when serve drink/food, no problem with minimizing or background switching whatsoever if flying with fsp without service, or no fsp at all.

 

Thanks

 

EDIT:

And here is the short version of the detail

 

Version=1

EventType=BEX

EventTime=130173458185654669

ReportType=2

Consent=1

UploadTime=130173458187161415

ReportIdentifier=4c00294d-e405-11e2-bee8-60a44caebced

IntegratorReportIdentifier=4c00294c-e405-11e2-bee8-60a44caebced

WOW64=1

Response.BucketId=b4faac2093055a0f012f07a767b604de

Response.BucketTable=5

Response.LegacyBucketId=50

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=fsx.exe

Sig[1].Name=Application Version

Sig[1].Value=10.0.61472.0

Sig[2].Name=Application Timestamp

Sig[2].Value=475e17d3

Sig[3].Name=Fault Module Name

Sig[3].Value=unknown

Sig[4].Name=Fault Module Version

Sig[4].Value=0.0.0.0

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=00000000

Sig[6].Name=Exception Offset

Sig[6].Value=78f5e06b

Sig[7].Name=Exception Code

Sig[7].Value=c0000005

Sig[8].Name=Exception Data

Sig[8].Value=00000008

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.2.9200.2.0.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=2052

UI[2]=F:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

UI[3]=A fatal error occurred.

UI[4]=Windows can check online for a solution to the problem and try to restart the program.

UI[5]=Check online for a solution and restart the program

UI[6]=Check online for a solution later and close the program

UI[7]=Close the program

 

 

but i'm checking my resource usage it's using nowhere near the limit. 4.2GB/12GB RAM

 

FSX can only use the max of 4GB's of memory.  Anything left over would be used for Windows Apps.  This is a limitation of Windows, not FSX.  If you had a 32 bit OS, FSX would only use the max of 2GB's but more with the /3GB or UserVA switch.  So you have a lot of memory with a 64 bit OS but FSX can only see or use so much.  You need to turn your settings down.  You'll enjoy FS much more.

 

More information here - http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx

 

Best regards,

Jim

FSX can only use the max of 4GB's of memory.  Anything left over would be used for Windows Apps.  This is a limitation of Windows, not FSX.  If you had a 32 bit OS, FSX would only use the max of 2GB's but more with the /3GB or UserVA switch.  So you have a lot of memory with a 64 bit OS but FSX can only see or use so much.  You need to turn your settings down.  You'll enjoy FS much more.

 

More information here - http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx

 

Best regards,

Jim

Yes, but fsx is only using about 1.5G of system RAM and about 530MB of VRAM.(in fact during cruise it only uses about 900M system RAM) So that only adds up to 2GB of the 4GB fsx is capable of using. And i have zero crash or stutters whatsoever (FPS limited to 58 using nvidia inspector) without performing fsp's cabin service. So that's why i assumed it's a compatibility issue with something...based on your experience, what programs/addons are known to cause problems with FS passengers?

Never owned FS Passengers and heard their support is gone.  I never heard of any program that's not compatible with FS Passengers.  In your case, you receive the crash when you play a certain menu item.  I did some further research and FS Passengers says their menu crash can be fixed with the Vista version of the uiautomationcore.dll installed in the main fsx folder.  Make sure you have the proper Vista version.  To be sure, they say the proper version is located here - http://simviation.com//simviation/?type=item&ID=69&page=13.  I have heard of several problems with FS Passenger here but this is the first time I have heard about the FSP menu crash.

 

Best regards,

 

Jim

actually it appears that I have found the problem, it only happens with feelthere's EMB jets addon. Which is probably why I didn't notice it before. But i've flown that aircraft in windows 7 with fsp before and it didn't seems to  give me any issue. So i'm guessing it's a windows 8+aircraft+fsp problem. Something combining all 3 makes fsx crash...I tried other aircrafts, and the crash is gone.

 

Thanks

Strange for sure.  I have had the Embracer jets installed in the past and never received any CTD's (but then I have never owned FSP).  Thanks for providing your solution.  It could be a help to others.

 

Best regards,

Jim