BEX Error

[Paul Williams 1]

Hi Folks. I wasn't going to start another thread related to crashes but can anyone make sense of this? It was working fine then all of a sudden I started getting this error. Nothing has changed on the puter as in installing anything.Thanks in advance,

 

Problem signature:
  Problem Event Name: BEX
  Application Name: fsx.exe
  Application Version: 10.0.61472.0
  Application Timestamp: 475e17d3
  Fault Module Name: unknown
  Fault Module Version: 0.0.0.0
  Fault Module Timestamp: 00000000
  Exception Offset: 00000000
  Exception Code: c0000005
  Exception Data: 00000008
  OS Version: 6.1.7601.2.1.0.768.3
  Locale ID: 1033

Additional information about the problem:
  LCID: 1033

[Jim Young 2,356]

 

 

I wasn't going to start another thread related to crashes

 

You should post your FSX crashes, freezes, stopped responding, etc., reports in the AVSIM CTD Forum.  Your crash report says little but indicates you have a Buffer Exception Overrun (BEX).  Please check out the AVSIM CTD Guide, located under Hot Spots to the right of this forum, for details on investigating your crash(es).  Most likely you have settings too high.

 

Since you are hijacking someone else's topic, I will attempt to split your post to the CTD Forum.  Look for it there.

 

Best regards,

[N400QW 205]

Problem signature:

  Problem Event Name: BEX
  Application Name: fsx.exe
  Application Version: 10.0.61637.0
  Application Timestamp: 46fadb14
  Fault Module Name: unknown
  Fault Module Version: 0.0.0.0
  Fault Module Timestamp: 00000000
  Exception Offset: 00000000
  Exception Code: c0000005
  Exception Data: 00000008
  OS Version: 6.1.7601.2.1.0.768.3
  Locale ID: 1033

 

Same here, just showed up out of nowhere???

[Jim Young 2,356]

Same here, just showed up out of nowhere???

 

Hi Ron,

 

These are quite common in FSX and indicates a high setting somewhere.  It is usually following sometime later with a BEX/StackHash error.  StackHash modules are very hard to diagnose.  Only thing I can recommend is to rename the fsx.cfg, restart fsx and let the config rebuild.  Make slight adjustments to your config such as resolution, AA/AF settings but leave the sliders in the scenery, weather and AI sections alone.  If you don't see the crash, it was likely caused by a bad tweak or fsx setting.  They are very frustrating to diagnose, especially the ones where the faulting module is unknown. 

 

Another thing you can try in addition to the above is to delete your facilities/scenery indexes and shader folders:

 

(From the CTD Guide - Periodically delete your Facilities/Scenery Indexes located in Program Data/Microsoft/FSX.  Delete the Facilities and Scenery folders.  Delete the Shader folders located in AppData/ (your user name)/Local/Microsoft/FSX/Shader10 and Shader folders. When you restart FSX, these folders will be rebuilt.  It has been known to fix some CTD’s.)

 

Hope this helps.

 

Best regards,

[N400QW 205]

Sheesh, read and did everything you and others have posted to no avail. Looing like a fresh FSX Gold install... B)

[GCBraun 2,392]

Sorry for the above. Since I bought my new system with Windows 8.1, I´ve got lots and lots of crashes, including BEX errors. From what I´ve seen, after disabling UT2, I´m still getting APPCRASHes, but no more BEX errors. Hopefully that will be of some help to you.