Archived

This topic is now archived and is closed to further replies.

Recommended Posts

Hello!

 

I have been having the same problem forever!

 

Log Name: Application

Source: Windows Error Reporting

Date: 6/27/2012 17:17:02

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: Spitfire

Description:

Fault bucket , type 0

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: 0000ffff

P8: c0000005

P9: 00000008

P10:

 

Attached files:

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

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

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

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

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

C:\Users\Matthew\AppData\Local\Temp\WERDA67.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\Users\Matthew\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_bced56bb1859e56a135b39dcfecf9b6995093b4_0e6c3bf7

 

Analysis symbol:

Rechecking for solution: 0

Report Id: 60671a8f-c09d-11e1-9b13-001fd0d574fa

Report Status: 1

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="2012-06-27T21:17:02.000000000Z" />

<EventRecordID>43216</EventRecordID>

<Channel>Application</Channel>

<Computer>Spitfire</Computer>

<Security />

</System>

<EventData>

<Data>

</Data>

<Data>0</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>0000ffff</Data>

<Data>c0000005</Data>

<Data>00000008</Data>

<Data>

</Data>

<Data>

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

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

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

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

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

C:\Users\Matthew\AppData\Local\Temp\WERDA67.tmp.WERInternalMetadata.xml</Data>

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

<Data>

</Data>

<Data>0</Data>

<Data>60671a8f-c09d-11e1-9b13-001fd0d574fa</Data>

<Data>1</Data>

</EventData>

</Event>

 

 

I have tried everything on all of the forums to attempt to fix this but still no luck! I am getting very frustrated about this. The crash always occurs when I am switching views or using the menus! Any help would be great.

 

Thanks !

Matthew

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Go to Start / All Programs / Accessories / Command prompt and right click on command prompt and click run as Administrator. Once open, type sfc /scannow and enter and let it run. It will scan and try to fix some of your system files. If errors are found Windows will fix the files for you. If not, well, that's good too. You do not have Acceleration installed so, do you have SP1 and SP2 installed? A lot of FSX addons require SP2 or Acceleration installed. Make sure you Microsoft Visuals C++ are installed. You need 2005, 2008, and 2010 installed. Normally these programs are installed when you install new software and the program cannot find them installed on your harddrive.

 

Crashes involving the menu have been fixed by placing the Vista version of uiautomationcore.dll in your main FSX directory. The uiautomationcore.dll belongs to the Microsoft.net framework program which FSX programmers used to make their addon run without a problem. It also manages memory for that program. Windows 7 comes with Version 4. The developers did not use Version 4 to develop their addon for FSX. They probably used Version 1.1 or 2.0. These files are located in separate directories so that your software program can find the files faster. When it cannot find the proper file, your program crashes. You need Versions 1.1 thru 4.0 installed in the C:\Windows\Microsoft.net\Framework\(then the appropriate versions). FSX is a very old program and used Version 1 and Version 2 for FSX and SP2/Acceleration. These versions are not backward compatible. So you need to check and make sure you have all of these files installed. FYI, many of your software programs will install this software on your harddrive if it does not find it during the installation process. Hope this helps.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Hey Jim,

 

Thank so much for the help I have SP2 installed. I will go try that out and get back to you on how it turns out.

Share this post


Link to post
Share on other sites

Hey Jim,

 

I still had no luck. I followed all of the steps that you suggested. This time it was a different crash. Here is what came up.

Log Name: Application

Source: Windows Error Reporting

Date: 6/27/2012 20:58:31

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: Spitfire

Description:

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

 

Problem signature:

P1: fsx.exe

P2: 10.0.61472.0

P3: 475e17d3

P4: uiautomationcore.dll

P5: 7.0.0.0

P6: 4a5bdb1d

P7: c0000005

P8: 0000e527

P9:

P10:

 

Attached files:

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

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

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

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

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

C:\Users\Matthew\AppData\Local\Temp\WERAC9.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\Users\Matthew\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_f2c25dbaf2d8375f6a7926cea62e191cec362c_118517a5

 

Analysis symbol:

Rechecking for solution: 0

Report Id: 5e8befaf-c0bc-11e1-9d92-001fd0d574fa

Report Status: 1

 

And the Details:

 

Log Name: Application

Source: Application Error

Date: 6/27/2012 20:58:28

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: Spitfire

Description:

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

Faulting module name: uiautomationcore.dll, version: 7.0.0.0, time stamp: 0x4a5bdb1d

Exception code: 0xc0000005

Fault offset: 0x0000e527

Faulting process id: 0x16a0

Faulting application start time: 0x01cd54c8917a9172

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

Faulting module path: C:\Windows\system32\uiautomationcore.dll

Report Id: 5e8befaf-c0bc-11e1-9d92-001fd0d574fa

Share this post


Link to post
Share on other sites

You have the proper version of uiautomationcore.dll installed. You are running FSX in a 32 bit environment. It should work. At least you got rid of the BEX Event!! And, in the previous error, the faulting module was unknown. Now it's displaying uiautomationcore.dll as the faulting module. Wonder if you experienced another crash whether the uiautomationcore.dll would still be the faulting module or, was this the module being called by FSX to perform and couldn't because of a lack of resources to enable the program? You are still getting the Memory_Access_Violation (Exception code 0xc0000005). You may need to lower some settings. You should also check your virtual memory (page file) and make sure the setting is set to 'System Managed Size'.

 

Some people have found success by place the Vista version of uiautomationcore.dll in their main fsx directory. It does not work for everyone though and not considered by me as a viable fix but you might want to try it. Here is the link to the Vista version - http://www.search-dll.com/dll-files/download/uiautomationcore.dll.html. Download and place in your FSX main directory. If it doesn't work, I would delete it as this is an old version. FSX reads everything in the main FSX directory first. In addition, are you right clicking the FSX icon and running it as Administrator? That might help. I assume you have UAC disabled and any anti-virus program disabled when installing new software.

 

So try to use the above suggestions for a solution and we'll go from there.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

I do always run it in Admin Mode. And I did not deactivate my anti virus while installing. So this time i will try with the new .dll then if that doesnt work re install with my antivirus disable.T

 

Thanks!

Matt

Share this post


Link to post
Share on other sites

Well the new .dll didnt work. So I will eventually get around to uninstalling and re installing. What really amazes me is i have FS9 and it is 9 years old and it still works perfectly fine. I have never had any problems with it but then there is FSX whos problems are endless.

Share this post


Link to post
Share on other sites

Hey Jim,

 

I have done everything you have recommended and just finished installing with anti-virus disabled. Still no luck i am still getting the same error:

 

Log Name: Application

Source: Windows Error Reporting

Date: 7/10/2012 16:34:30

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: Spitfire

Description:

Fault bucket , type 0

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: e544eed0

P8: c0000005

P9: 00000008

P10:

 

Attached files:

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

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

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

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

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

C:\Users\Matthew\AppData\Local\Temp\WER7E34.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\Users\Matthew\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_59d89b20d7cc3e7997a2c3c2937614b7ece376e_15819685

 

Analysis symbol:

Rechecking for solution: 0

Report Id: a1f5a0ff-cace-11e1-9f09-001fd0d574fa

Report Status: 1

Share this post


Link to post
Share on other sites

Well you are back to an 'unknown' faulting module but you still have the Memory_Access_Violation exception code c0000005 (which could be anything).

 

Event type BEX indicates a buffer overflow or DEP exception:

 

The primary benefit of DEP is that it helps to prevent code execution from data pages such as the default heap, various stacks, and memory pools. In normal operations of the system, code is not typically executed from the default heap and stack. Hardware-enforced DEP detects code that is running from these locations and raises an exception when execution occurs. If the exception is unhandled, the process will be terminated. Execution of code from protected memory in kernel mode results in an error.

 

Although terminating a process or causing the system to fail with an error do not appear to be ideal experiences, this helps prevent malicious code from executing. Preventing malicious code from executing on the system may prevent damage to the system or propagation of malicious code whose harmful effects could easily exceed those of a terminated process or system error.

 

DEP can help prevent some exploits in which a virus or other attack has injected a process with executable code and then attempts to execute the injected code. On a system with DEP, execution of the injected code should result in an exception. Software-enforced DEP can help mitigate exploits of exception handling mechanisms within Windows.

 

So, what did you install in FSX that came from earlier versions of FS. An aircraft from FS9? Scenery from FS9? FSInn? FS Co-pilot? If you have anything installed in FSX that was not made specifically for FSX OR Windows 7 64 bit, then you need to disable the program or uninstall it to see if that is causing the problem. For scenery, just start up FSX and go to the Scenery Library and find the problem scenery and uncheck the box next to it. This will disable the scenery. Run FSX and see if the problem still exists.

 

Since you have SP2 installed, make sure any addon you installed was compatible to SP2. Developers will post compatibility information for their commercial programs.

 

Run your anti-virus program and make sure you have no viruses installed. If you have a program that looks for Malware, run Windows Defender to see if any spyware and other unwanted software protection is installed. Microsoft Essentials (free) can also do this.

 

Make sure your virtual memory (page file) is set to System Managed Size. Click on the Start button and in the search box, type Virtual, then look up and click on how to change virtual memory. Follow the steps but don't manually set a size. Instead, at the Virtual Memory page, click on System Managed Size.

 

Turn off your User Access Controls (UAC). Click on the Start button and type UAC in the search box, then look up and click on Change User Account Settings. Pull the slider all the way down and click okay. With this turned on too high, Microsoft security may prevent certain programs to open up thus causing the crash.

 

Hopefully this will help you resolve your problem.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Hey Jim.

 

I have no addons installed other than the PMDG 737 NGX. Also i tryed to disable DEP for FSX, did not work, and i changes the virtual memory to system managed we will have to see if that works. And i already have UAC disabled.

 

Thanks,

Matt

Share this post


Link to post
Share on other sites

Hey Jim.

 

I have no addons installed other than the PMDG 737 NGX. Also i tryed to disable DEP for FSX, did not work, and i changes the virtual memory to system managed we will have to see if that works. And i already have UAC disabled.

 

Thanks,

Matt

 

I knew you couldn't disable DEP for FSX and you shouldn't. I just wanted to emphasize that you have something installed that FSX does not like. Some people install stuff from FS9 and before that is barely compatible or probably not compatible and they create problems with FSX and a 64 bit Windows 7. Hopefully you have all the updates to PMDG's 737 installed. This should cause the problem but I read a lot of people had issues soon after installing just the first version of the 737NGX and PMDG issued fixes. Computers are strange and sometimes not very friendly huh?

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

They are not even close to being friendly! I have the SP1C for the NGX installed which is the newest one, but the problem is still there it crashed again on my today with the same BEX error as before.

 

Matt

Share this post


Link to post
Share on other sites

They are not even close to being friendly! I have the SP1C for the NGX installed which is the newest one, but the problem is still there it crashed again on my today with the same BEX error as before.

 

Matt

 

Matt,

Again, the codes for your error reports show that you have something installed that is not compatible to FSX. It could be an old piece of software or it could be a corrupted driver. I would completely uninstalled FSX using this Uninstaller - http://www.iobit.com/advanceduninstaller.html. The Power Scan should remove any leftover folders and any leftover registry items. Before you uninstall FSX, use the Uninstaller to uninstall the PMDG 737NGX and any other addon. Reinstall FSX. Run FSX and setup your FSX settings. Do one Fly Now flights. Do you still have the problem? If not, install SP1 then run FSX. Do one Fly Now flights. Do you have the problem? If not, install SP2. Run FSX and see if the problem exists. If not, install your addons one by one and before installing another addon, run FSX. Make sure you select Yes when asked if you trust something. They are all safe. I'm sorry you have to go this route but I see no other solution to this problem.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks for the help Jim it has been alot better than anything else i can find. Today I am not able to reinstall or tomorow and i will get around to it and let you know.

Share this post


Link to post
Share on other sites

Hei Jim,

 

I'm Sidharta, from Indonesia

i got the same problem like matt10pilot
 

Version=1
EventType=BEX
EventTime=130415045677819803
ReportType=2
Consent=1
ReportIdentifier=44a67c55-bfbe-11e3-9216-902b341517f1
IntegratorReportIdentifier=44a67c54-bfbe-11e3-9216-902b341517f1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
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=5c5c5f60
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.1.7600.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=E:\GAMES\FSX\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
LoadedModule[0]=E:\GAMES\FSX\fsx.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\system32\msvcrt.dll
LoadedModule[7]=C:\Windows\system32\GDI32.dll
LoadedModule[8]=C:\Windows\system32\USER32.dll
LoadedModule[9]=C:\Windows\system32\LPK.dll
LoadedModule[10]=C:\Windows\system32\USP10.dll
LoadedModule[11]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[12]=C:\Windows\system32\ole32.dll
LoadedModule[13]=C:\Windows\system32\RPCRT4.dll
LoadedModule[14]=C:\Windows\system32\apphelp.dll
LoadedModule[15]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[16]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[17]=C:\Windows\system32\SspiCli.dll
LoadedModule[18]=C:\Windows\system32\UxTheme.dll
LoadedModule[19]=C:\Windows\system32\WINMM.dll
LoadedModule[20]=C:\Windows\system32\samcli.dll
LoadedModule[21]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[22]=C:\Windows\system32\MSACM32.dll
LoadedModule[23]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[24]=C:\Windows\system32\VERSION.dll
LoadedModule[25]=C:\Windows\system32\SHELL32.dll
LoadedModule[26]=C:\Windows\system32\sfc.dll
LoadedModule[27]=C:\Windows\system32\sfc_os.DLL
LoadedModule[28]=C:\Windows\system32\USERENV.dll
LoadedModule[29]=C:\Windows\system32\profapi.dll
LoadedModule[30]=C:\Windows\system32\dwmapi.dll
LoadedModule[31]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[32]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[33]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[34]=C:\Windows\system32\urlmon.dll
LoadedModule[35]=C:\Windows\system32\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[36]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[37]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[38]=C:\Windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[39]=C:\Windows\system32\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[40]=C:\Windows\system32\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[41]=C:\Windows\system32\normaliz.DLL
LoadedModule[42]=C:\Windows\system32\iertutil.dll
LoadedModule[43]=C:\Windows\system32\WININET.dll
LoadedModule[44]=C:\Windows\system32\MPR.dll
LoadedModule[45]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[46]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[47]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[48]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll
LoadedModule[49]=C:\Windows\system32\mscms.dll
LoadedModule[50]=C:\Windows\system32\DDRAW.dll
LoadedModule[51]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[52]=C:\Windows\system32\COMDLG32.dll
LoadedModule[53]=C:\Windows\system32\IMM32.dll
LoadedModule[54]=C:\Windows\system32\MSCTF.dll
LoadedModule[55]=C:\Windows\system32\WS2_32.dll
LoadedModule[56]=C:\Windows\system32\NSI.dll
LoadedModule[57]=C:\Windows\system32\msi.dll
LoadedModule[58]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[59]=E:\GAMES\FSX\language.dll
LoadedModule[60]=E:\GAMES\FSX\API.DLL
LoadedModule[61]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[62]=E:\GAMES\FSX\ablscpt.dll
LoadedModule[63]=E:\GAMES\FSX\flight.dll
LoadedModule[64]=E:\GAMES\FSX\ai_player.dll
LoadedModule[65]=E:\GAMES\FSX\acontain.dll
LoadedModule[66]=E:\GAMES\FSX\controls.dll
LoadedModule[67]=C:\Windows\system32\DINPUT8.dll
LoadedModule[68]=E:\GAMES\FSX\fsui.dll
LoadedModule[69]=E:\GAMES\FSX\atc.dll
LoadedModule[70]=E:\GAMES\FSX\facilities.dll
LoadedModule[71]=E:\GAMES\FSX\demo.dll
LoadedModule[72]=E:\GAMES\FSX\main.dll
LoadedModule[73]=E:\GAMES\FSX\fe.dll
LoadedModule[74]=E:\GAMES\FSX\util.dll
LoadedModule[75]=E:\GAMES\FSX\simprop.dll
LoadedModule[76]=E:\GAMES\FSX\g2d.dll
LoadedModule[77]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[78]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[79]=E:\GAMES\FSX\d3d9.dll
LoadedModule[80]=C:\Windows\system32\d3dx9_26.dll
LoadedModule[81]=E:\GAMES\FSX\g3d.dll
LoadedModule[82]=E:\GAMES\FSX\panels.dll
LoadedModule[83]=E:\GAMES\FSX\multiplayer.dll
LoadedModule[84]=E:\GAMES\FSX\ui.dll
LoadedModule[85]=E:\GAMES\FSX\sound.dll
LoadedModule[86]=E:\GAMES\FSX\sim1.dll
LoadedModule[87]=E:\GAMES\FSX\simscheduler.dll
LoadedModule[88]=E:\GAMES\FSX\visualfx.dll
LoadedModule[89]=E:\GAMES\FSX\window.dll
LoadedModule[90]=E:\GAMES\FSX\terrain.dll
LoadedModule[91]=E:\GAMES\FSX\weather.dll
LoadedModule[92]=C:\Windows\system32\DSOUND.dll
LoadedModule[93]=C:\Windows\system32\POWRPROF.dll
LoadedModule[94]=E:\GAMES\FSX\symmap.dll
LoadedModule[95]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[96]=C:\Windows\system32\MSIMG32.dll
LoadedModule[97]=E:\GAMES\FSX\xuipc.dll
LoadedModule[98]=E:\GAMES\FSX\livingwater.dll
LoadedModule[99]=E:\GAMES\FSX\fs-traffic.dll
LoadedModule[100]=E:\GAMES\FSX\gps.dll
LoadedModule[101]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[102]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[103]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[105]=C:\Windows\system32\rsaenh.dll
LoadedModule[106]=C:\Windows\system32\WINTRUST.dll
LoadedModule[107]=C:\Windows\system32\CRYPT32.dll
LoadedModule[108]=C:\Windows\system32\MSASN1.dll
LoadedModule[109]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[111]=C:\Windows\system32\wbemcomn.dll
LoadedModule[112]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[114]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[115]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[117]=C:\Windows\system32\dxgi.dll
LoadedModule[118]=C:\Windows\system32\d3d11.dll
LoadedModule[119]=C:\Windows\system32\d3d9.dll
LoadedModule[120]=C:\Windows\system32\d3d8thk.dll
LoadedModule[121]=C:\Windows\system32\nvd3dum.dll
LoadedModule[122]=C:\Windows\system32\PSAPI.DLL
LoadedModule[123]=C:\Windows\system32\nvspcap.dll
LoadedModule[124]=C:\Windows\system32\nvapi.dll
LoadedModule[125]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[126]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[127]=C:\Windows\system32\d3d10_1.dll
LoadedModule[128]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[129]=C:\Program Files\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[130]=C:\Windows\system32\dxdiagn.dll
LoadedModule[131]=C:\Windows\system32\d3d10.dll
LoadedModule[132]=C:\Windows\system32\d3d10core.dll
LoadedModule[133]=C:\Windows\system32\winbrand.dll
LoadedModule[134]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[135]=C:\Windows\system32\WINSTA.dll
LoadedModule[136]=C:\Windows\System32\gameux.dll
LoadedModule[137]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[138]=C:\Windows\System32\XmlLite.dll
LoadedModule[139]=C:\Windows\System32\wer.dll
LoadedModule[140]=C:\Windows\System32\Wpc.dll
LoadedModule[141]=C:\Windows\System32\wevtapi.dll
LoadedModule[142]=C:\Windows\System32\msxml6.dll
LoadedModule[143]=C:\Windows\system32\SAMLIB.dll
LoadedModule[144]=C:\Windows\system32\netutils.dll
LoadedModule[145]=C:\Windows\system32\uiautomationcore.dll
LoadedModule[146]=C:\Windows\system32\OLEACC.dll
LoadedModule[147]=C:\Windows\System32\MMDevApi.dll
LoadedModule[148]=C:\Windows\System32\PROPSYS.dll
LoadedModule[149]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[150]=C:\Windows\system32\RICHED20.DLL
LoadedModule[151]=C:\Windows\system32\HID.DLL
LoadedModule[152]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[153]=C:\Windows\system32\wdmaud.drv
LoadedModule[154]=C:\Windows\system32\ksuser.dll
LoadedModule[155]=C:\Windows\system32\AVRT.dll
LoadedModule[156]=C:\Windows\system32\msacm32.drv
LoadedModule[157]=C:\Windows\system32\midimap.dll
LoadedModule[158]=C:\Windows\system32\dinput.DLL
LoadedModule[159]=C:\Windows\System32\wship6.dll
LoadedModule[160]=C:\Windows\System32\wshtcpip.dll
LoadedModule[161]=E:\GAMES\FSX\bglmanx.dll
LoadedModule[162]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[163]=C:\Windows\system32\inetmib1.dll
LoadedModule[164]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[165]=C:\Windows\system32\WINNSI.DLL
LoadedModule[166]=C:\Windows\system32\snmpapi.dll
LoadedModule[167]=E:\GAMES\FSX\FsPassengers\bin\fspassengersx.dll
LoadedModule[168]=E:\GAMES\FSX\Modules\iFly737NG.dll
LoadedModule[169]=C:\Program Files\FS Recorder for FSX\FSRecorder_FSX.dll
LoadedModule[170]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[171]=C:\Windows\System32\ieframe.dll
LoadedModule[172]=C:\Windows\System32\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[173]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[174]=C:\Windows\system32\Secur32.dll
LoadedModule[175]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[176]=C:\Windows\System32\mshtml.dll
LoadedModule[177]=C:\Windows\system32\msimtf.dll
LoadedModule[178]=C:\Windows\system32\msls31.dll
LoadedModule[179]=C:\Windows\system32\d2d1.dll
LoadedModule[180]=C:\Windows\system32\DWrite.dll
LoadedModule[181]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[182]=C:\Windows\system32\MLANG.dll
LoadedModule[183]=C:\Windows\system32\ntmarta.dll
LoadedModule[184]=C:\Windows\system32\WLDAP32.dll
LoadedModule[185]=C:\Windows\system32\msadp32.acm
LoadedModule[186]=C:\Windows\system32\asycfilt.dll
LoadedModule[187]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[188]=C:\Windows\system32\explorerframe.dll
LoadedModule[189]=C:\Windows\system32\DUser.dll
LoadedModule[190]=C:\Windows\system32\DUI70.dll
LoadedModule[191]=C:\Program Files\AVAST Software\Avast\ashShell.dll
LoadedModule[192]=C:\Windows\system32\EhStorShell.dll
LoadedModule[193]=C:\Windows\System32\cscui.dll
LoadedModule[194]=C:\Windows\System32\CSCDLL.dll
LoadedModule[195]=C:\Windows\system32\CSCAPI.dll
LoadedModule[196]=C:\Windows\system32\ntshrui.dll
LoadedModule[197]=C:\Windows\system32\srvcli.dll
LoadedModule[198]=C:\Windows\system32\slc.dll
LoadedModule[199]=C:\Windows\system32\IconCodecService.dll
LoadedModule[200]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[201]=C:\Windows\system32\actxprxy.dll
LoadedModule[202]=C:\Program Files\Internet Explorer\ieproxy.dll
LoadedModule[203]=C:\Windows\system32\thumbcache.dll
LoadedModule[204]=C:\Windows\system32\SearchFolder.dll
LoadedModule[205]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[206]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[207]=C:\Windows\system32\LINKINFO.dll
LoadedModule[208]=C:\Windows\System32\drprov.dll
LoadedModule[209]=C:\Windows\System32\ntlanman.dll
LoadedModule[210]=C:\Windows\System32\davclnt.dll
LoadedModule[211]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[212]=C:\Windows\system32\wkscli.dll
LoadedModule[213]=C:\Windows\system32\PortableDeviceApi.dll
LoadedModule[214]=C:\Windows\system32\EhStorAPI.dll
LoadedModule[215]=C:\Windows\system32\RICHED32.DLL
LoadedModule[216]=C:\Windows\system32\windowscodecsext.dll
LoadedModule[217]=C:\Windows\System32\jscript9.dll
LoadedModule[218]=C:\Windows\system32\imagehlp.dll
LoadedModule[219]=C:\Windows\system32\ncrypt.dll
LoadedModule[220]=C:\Windows\system32\bcrypt.dll
LoadedModule[221]=C:\Windows\system32\bcryptprimitives.dll
LoadedModule[222]=C:\Windows\system32\GPAPI.dll
LoadedModule[223]=C:\Windows\system32\cryptnet.dll
LoadedModule[224]=C:\Windows\system32\SensApi.dll
LoadedModule[225]=C:\Windows\System32\l3codeca.acm
LoadedModule[226]=C:\Windows\system32\d3dx9_31.dll
Sec[0].Key=LCID
Sec[0].Value=1033
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Microsoft® Flight Simulator X
AppPath=E:\GAMES\FSX\fsx.exe
 
i dont know what's the problem is... can you help me
thanks before

Share this post


Link to post
Share on other sites

 

 


i dont know what's the problem is... can you help me
thanks before

 

There is no faulting module but you did have a BEX (Buffer_Exception_Overrun) CTD.  Those are difficult to diagnose.  Usually a BEX CTD is accompanied with a StackHash or ntdll.dll faulting module.  These all indicate high fsx settings and/or bad tweaks in your Fsx.cfg.  Renaming your Fsx.cfg to fsx.orig and restarting FSX so the config can be rebuilt fixes many of these problems. 

 

We now have an AVSIM CTD Guide located to the right of this forum under Hot Spots and that guide provides guidance for investigating your crash and trying to find the cause.  Renaming your Fsx.cfg is just one.  Disabling your addons in your Scenery Library is another.  Disabling modules in your dll.xml is another until the CTD's stop.  If none of those suggestions work, then you will have to reinstall Windows/FSX/FSX addons (ugh!).

 

Best regards,

Share this post


Link to post
Share on other sites