Today after i finish a flight i got a CTD that i haven't had in a long time. I completed my flight with out no stutter or anything , then when i click on full sceen to get it to window mode . I got this crash to the desktop . Also ENB Series plugin was disable at the time i minimize the screen.

 

 

Here is the log file from the EVENT VIEWER

 

 

Log Name: Application

Source: Windows Error Reporting

Date: 2/14/2013 5:52:39 PM

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: Admin-PC

Description:

Fault bucket 568148798, type 5

Event Name: BEX

Response: Not available

Cab Id: 0

 

Problem signature:

P1: fsx.exe

P2: 10.0.61472.0

P3: 475e17d3

P4: unknown

P5: 0.0.0.0

P6: 00000000

P7: 2b2b2b2b

P8: c0000005

P9: 00000008

P10:

 

Attached files:

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\dxdiag.txt

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\scenery.cfg

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\fdr.dat

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\dll.xml

C:\Users\Admin\AppData\Local\Temp\WER4D78.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\Users\Admin\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_e8b2b51d3f38e6ed83b87dcf7e1b6f87dc478e5_185e69fd

 

Analysis symbol:

Rechecking for solution: 0

Report Id: 5be736c0-7712-11e2-820b-8c89a564bab2

Report Status: 0

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Windows Error Reporting" />

<EventID Qualifiers="0">1001</EventID>

<Level>4</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2013-02-15T01:52:39.000000000Z" />

<EventRecordID>14683</EventRecordID>

<Channel>Application</Channel>

<Computer>Admin-PC</Computer>

<Security />

</System>

<EventData>

<Data>568148798</Data>

<Data>5</Data>

<Data>BEX</Data>

<Data>Not available</Data>

<Data>0</Data>

<Data>fsx.exe</Data>

<Data>10.0.61472.0</Data>

<Data>475e17d3</Data>

<Data>unknown</Data>

<Data>0.0.0.0</Data>

<Data>00000000</Data>

<Data>2b2b2b2b</Data>

<Data>c0000005</Data>

<Data>00000008</Data>

<Data>

</Data>

<Data>

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\dxdiag.txt

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\scenery.cfg

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\fdr.dat

C:\Users\Admin\AppData\Roaming\Microsoft\FSX\dll.xml

C:\Users\Admin\AppData\Local\Temp\WER4D78.tmp.WERInternalMetadata.xml</Data>

<Data>C:\Users\Admin\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_e8b2b51d3f38e6ed83b87dcf7e1b6f87dc478e5_185e69fd</Data>

<Data>

</Data>

<Data>0</Data>

<Data>5be736c0-7712-11e2-820b-8c89a564bab2</Data>

<Data>0</Data>

</EventData>

</Event>

Sounds like you need to place the Vista version of the uiautomationcore.dll into your main FSX folder. This has fixed crashes when hitting the FSX menu. I see you have SP2 installed. Some have fixed their problem by uninstalling SP2, running FSX once, closing, then reinstalling SP2. You had a Buffer Overflow Exception (BEX) which is common with FSX. Not known what the solution is though. Most likely, any further crashes will result in a StackHash as the faulting module. I had a similar problem with two monitors. I would get a BEX/StackHash error when closing FSX in full screen. Then when I restarted, FSX would load up on my secondary monitor in windowed mode. I would have to pull FSX over to the main monitor. When finished with FSX, I had to remember to go from Full Screen to Windowed mode and there would be no crash report. That was my solution. But recently I reinstalled Windows 7 and FSX and that issue has gone completely away. I suspect the information that was being held in memory buffer was released when I reinstalled Windows 7.

 

It would be better if you could download App Crash View - http://www.nirsoft.net/utils/app_crash_view.html and copy and paste the latest crash here for analysis. This program provides all the information in the Microsoft Crash report (.wer).

 

Best regards,

Jim

Thanks Jim , you are one of my best friend here AVSIM always there to help in what you can am so glad people like you exist now days . I will do this when i get home from work thanks a lot . An yes am not running a uiautomationcore.dll from vista it is from window 7 itself . I don't know if any of the other suggestion can go with it but am willing to try . I will post what is needed when i get home . Thanks a million glad to have you helping me with my first CTD crash in a long time.

Jim i download the app you told me , an when i check for error reports it is not updated error reports it only shows on feb 8 when i had the blue screen error but i fix that problem . I doesn't show any recent fsx crashes . Only on the even viewer i was able to see my fsx recent crash, which is the one i posted there.

Again i had next crash . This time uninstall FSX SP2 run fsx with out it then install it . I also went ahead an downloaded vista version 32 bit of uiautomationcore.dll an drag it to my fsx directory . After a flight when i went to minimize the window i got a crash to the desktop an fsx was restarting, this time this message came up saying you need assembly for this to work . This is my event viewer report.

 

 

Log Name: Application

Source: Application Error

Date: 2/16/2013 7:49:47 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Admin-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x2b2b2b2b

Faulting process id: 0x3b0

Faulting application start time: 0x01ce0cb760933467

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: unknown

Report Id: 1211d17a-78b5-11e2-a45d-8c89a564bab2

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name="Application Error" />

<EventID Qualifiers="0">1000</EventID>

<Level>2</Level>

<Task>100</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2013-02-17T03:49:47.000000000Z" />

<EventRecordID>14793</EventRecordID>

<Channel>Application</Channel>

<Computer>Admin-PC</Computer>

<Security />

</System>

<EventData>

<Data>fsx.exe</Data>

<Data>10.0.61472.0</Data>

<Data>475e17d3</Data>

<Data>unknown</Data>

<Data>0.0.0.0</Data>

<Data>00000000</Data>

<Data>c0000005</Data>

<Data>2b2b2b2b</Data>

<Data>3b0</Data>

<Data>01ce0cb760933467</Data>

<Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data>

<Data>unknown</Data>

<Data>1211d17a-78b5-11e2-a45d-8c89a564bab2</Data>

</EventData>

</Event>

I'm afraid there is nothing I can do to help you. There is no indication of what caused your error (a faulting module). The information I posted in #2 above is all I can provide right now until you receive a CTD and the AppCrashView report shows me more info. A BEX error is almost impossible to find a cause for the error. My only recommendation now is to do what I did when I got this error and reinstall Windows 7 and then FSX w/SP2. You have to somehow free up that stuck memory buffer that is causing the errors and the only way is to reinstall Windows.

 

One more thing though and that's your statement about the ENB series module. That module is known to not be compatible with FSX. You stated it was disabled when you minimized the screen. Since the module takes one of your DirectX display drivers and modifies it so that it does things to FSX, I suspect this might be the culprit. I know of no way to disable the ENB module other than rename the d3d9.dll or remove the enb.ini out of your FSX directory. So I would pull the d3d9.dll and the enb.ini and move those files to a temp directory then run FSX and see if the problem still occurs. If the d3d9.dll was in your main FSX directory when you were running FSX and, say, your enb.ini was not in there, the d3d9.dll will still run and load up in FSX. There's no way to stop it from loading unless you completely remove it from your FSX directory. You have to remember that everything in your FSX directory will be ran and loaded no matter what. Hope this works. If not, you'll have to reinstall Windows7 (you won't have to uninstall anything as the new installation will overwrite everything).

 

Best regards,

Jim

thanks Jim ,i will try it with enb completely off my fsx director

Jim i remove the ENB series plugin from my fsx directory an what do you know it work .No more crashes i can now click on any menu item with out no crash . I even actually put music in the background when i minimize the screen just to see if it will cause any effect to fsx an nop not even one. So yet again ENB seems to be nice for VFR but also causes lots of problem . When will it ever be fix , the fix i was able to come across was no permanent fix . I hope someone in the near future comes up with a fix for ENB or create something even better an compatible with fsx. Thanks again Jim now i can fly free even dow with out the effect of ENB , is just that i got so used to it that i forgot about how fsx looks like with out it . I do have shade but i don't know how to use it very well . I just load the default setting shades comes with .

i remove the ENB series plugin from my fsx directory an what do you know it work .No more crashes i can now click on any menu item with out no crash .

 

Glad you were able to fix the problem with the removal of the ENB module. There are just a very small minority here at FSX who have been successful with this mod and have had no problems. I suspect they are also computer experts..... In the FSX forum, you can try doing an ENB search and maybe you'll find a post from one of the successful users (look at the top of the forum on the right and type ENB in the search box. You should only get posts from the FSX forum). Modifying a system file is dangerous in my opinion and this is a DirectX file too. I had it working for a couple of weeks and enjoyed it but then I started seeing some anomalies and textures became blocks and with weird colors; then the crashes started. Like you I had no idea what it was. My video card, FSX, or maybe my computer was burning up. I removed the ENB files and all was well again.

 

You might want to start a new post in the FSX forum too asking anyone if they know of a working ENB series mod for FSX.

 

I'm with you regarding Shade and have some problems too but the default is nice too. The ENB mod really does much more than Shade (I've been told thousands of times so far) so it's not a substitute. Still, it is nice to see the shadows on one side of the mountain and not all around the mountain and I think Shade is great.

 

Best regards,

Jim

I will thanks Jim , i got so use to it that it is kind of strange flying with out it . The strange thing is i never had any lost FPS when using enb only those menu crashes. I can really say now that ENB causes almost all those crashes . But i will start my search to see which one works the best. One thing i notice also that for some user who use ENB they normally fly VFR i won't get no crashes unless i mess with the menu options.