Jump to content

Archived

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

Norwegian

Fsx crashing before startup.

Recommended Posts

Hey,

 

Just got this ctd today after installing 2 carenado aircraft.

Weird thing is that the error said something about an ezdok file. Tried uninstalling the aircraft, didn't work. Then i tried uninstalling ezdok, still didn't work.

Any idea what can be causing this?

 

 

Thanks.
Kim.


Kjevik2_zps5cecrndf.jpg

Share this post


Link to post
Share on other sites

I had the same problem last week.  I use FTX Central so tried reinstalling the latest ORBX!LIBS.  That seemed to work but still had the occasional problem until I used FTX Central to change to a different area. Repeatedly.

 

Eventually the problem went away but I have no idea what really fixed it?  My suspicion is that it has something to do with scenery & FTX?

 

FYI, I had been messing with UTX just prior to the problem, not sure if that is relevant.

 

Rick S.



6dfuecbymy0s0t74g.jpg                                                                                                                                                     

Share this post


Link to post
Share on other sites

Any crash reports?  Anything in the Event Viewer?  See the AVSIM CTD Guide for information about the AppCrashView program and how to check out the Event Viewer.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Mine was not a system crash but a crash to desktop.  FSX failed to load with an error referring to ezdok.  I did remove ezdok from loading and still got a crash to desktop.  Cannot remember that error?

 

I believe this is the last AppCrashView report I got; if you can make any sense out of it?

 

Version=1
EventType=APPCRASH
EventTime=130654755548734019
ReportType=2
Consent=1
UploadTime=130654755549214484
ReportIdentifier=125b44c5-99c2-11e4-87a8-7824af3752c9
IntegratorReportIdentifier=125b44c4-99c2-11e4-87a8-7824af3752c9
WOW64=1
Response.BucketId=5c761b363d56a35d702dd066befbbc30
Response.BucketTable=1
Response.LegacyBucketId=657952111
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=atc.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.61637.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=46fadb59
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00043cb9
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=D:\fsx\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\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\system32\apphelp.dll
LoadedModule[5]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[6]=C:\Windows\SYSTEM32\msvcrt.dll
LoadedModule[7]=C:\Windows\SYSTEM32\USER32.dll
LoadedModule[8]=C:\Windows\SYSTEM32\GDI32.dll
LoadedModule[9]=C:\Windows\SYSTEM32\SHELL32.dll
LoadedModule[10]=C:\Windows\SYSTEM32\SHLWAPI.dll
LoadedModule[11]=C:\Windows\SYSTEM32\OLEAUT32.dll
LoadedModule[12]=C:\Windows\SYSTEM32\MPR.dll
LoadedModule[13]=C:\Windows\SYSTEM32\SETUPAPI.dll
LoadedModule[14]=C:\Windows\SYSTEM32\sfc.dll
LoadedModule[15]=C:\Windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[16]=C:\Windows\SYSTEM32\RPCRT4.dll
LoadedModule[17]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[18]=C:\Windows\SYSTEM32\CFGMGR32.dll
LoadedModule[19]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[20]=C:\Windows\SYSTEM32\sfc_os.DLL
LoadedModule[21]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[22]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[23]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[24]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[25]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17415_none_7c5769eaaa0aa358\COMCTL32.dll
LoadedModule[26]=C:\Windows\SYSTEM32\mscms.dll
LoadedModule[27]=C:\Windows\SYSTEM32\ADVAPI32.dll
LoadedModule[28]=C:\Windows\SYSTEM32\ole32.dll
LoadedModule[29]=C:\Windows\SYSTEM32\WINMM.dll
LoadedModule[30]=C:\Windows\SYSTEM32\DDRAW.dll
LoadedModule[31]=C:\Windows\SYSTEM32\USERENV.dll
LoadedModule[32]=C:\Windows\SYSTEM32\COMDLG32.dll
LoadedModule[33]=C:\Windows\SYSTEM32\IMM32.dll
LoadedModule[34]=C:\Windows\SYSTEM32\WS2_32.dll
LoadedModule[35]=C:\Windows\SYSTEM32\dwmapi.dll
LoadedModule[36]=C:\Windows\SYSTEM32\msi.dll
LoadedModule[37]=C:\Windows\SYSTEM32\WINMMBASE.dll
LoadedModule[38]=C:\Windows\SYSTEM32\DCIMAN32.dll
LoadedModule[39]=C:\Windows\SYSTEM32\profapi.dll
LoadedModule[40]=C:\Windows\SYSTEM32\SHCORE.DLL
LoadedModule[41]=C:\Windows\SYSTEM32\MSCTF.dll
LoadedModule[42]=C:\Windows\SYSTEM32\NSI.dll
LoadedModule[43]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[44]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[45]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll
LoadedModule[46]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[47]=D:\fsx\language.dll
LoadedModule[48]=D:\fsx\API.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCP80.dll
LoadedModule[50]=D:\fsx\ablscpt.dll
LoadedModule[51]=D:\fsx\acontain.dll
LoadedModule[52]=D:\fsx\ai_player.dll
LoadedModule[53]=D:\fsx\atc.dll
LoadedModule[54]=D:\fsx\controls.dll
LoadedModule[55]=D:\fsx\demo.dll
LoadedModule[56]=D:\fsx\facilities.dll
LoadedModule[57]=D:\fsx\fe.dll
LoadedModule[58]=D:\fsx\flight.dll
LoadedModule[59]=D:\fsx\fsui.dll
LoadedModule[60]=D:\fsx\g2d.dll
LoadedModule[61]=D:\fsx\g3d.dll
LoadedModule[62]=D:\fsx\gps.dll
LoadedModule[63]=D:\fsx\livingwater.dll
LoadedModule[64]=D:\fsx\main.dll
LoadedModule[65]=D:\fsx\multiplayer.dll
LoadedModule[66]=D:\fsx\panels.dll
LoadedModule[67]=D:\fsx\sim1.dll
LoadedModule[68]=D:\fsx\simprop.dll
LoadedModule[69]=D:\fsx\simscheduler.dll
LoadedModule[70]=D:\fsx\sound.dll
LoadedModule[71]=D:\fsx\symmap.dll
LoadedModule[72]=D:\fsx\terrain.dll
LoadedModule[73]=D:\fsx\fs-traffic.dll
LoadedModule[74]=D:\fsx\ui.dll
LoadedModule[75]=D:\fsx\util.dll
LoadedModule[76]=D:\fsx\visualfx.dll
LoadedModule[77]=D:\fsx\weather.dll
LoadedModule[78]=D:\fsx\window.dll
LoadedModule[79]=D:\fsx\xuipc.dll
LoadedModule[80]=C:\Windows\SYSTEM32\MSWSOCK.dll
LoadedModule[81]=C:\Windows\SYSTEM32\SHFOLDER.dll
LoadedModule[82]=C:\Windows\SYSTEM32\VERSION.dll
LoadedModule[83]=C:\Windows\SYSTEM32\POWRPROF.dll
LoadedModule[84]=C:\Windows\SYSTEM32\DINPUT8.dll
LoadedModule[85]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17415_none_dad8722c5bcc2d8f\gdiplus.dll
LoadedModule[86]=C:\Windows\SYSTEM32\d3dx9_34.dll
LoadedModule[87]=D:\fsx\d3dx10_34.dll
LoadedModule[88]=C:\Windows\SYSTEM32\d3d9.dll
LoadedModule[89]=C:\Windows\SYSTEM32\DSOUND.dll
LoadedModule[90]=C:\Windows\SYSTEM32\WININET.dll
LoadedModule[91]=C:\Windows\SYSTEM32\MSACM32.dll
LoadedModule[92]=C:\Windows\SYSTEM32\MSIMG32.dll
LoadedModule[93]=C:\Windows\SYSTEM32\MSVCR100.dll
LoadedModule[94]=C:\Windows\SYSTEM32\iertutil.dll
LoadedModule[95]=D:\fsx\reald3dx10_34.DLL
LoadedModule[96]=D:\fsx\dx10fixerlib.DLL
LoadedModule[97]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[98]=C:\Windows\system32\uxtheme.dll
LoadedModule[99]=C:\Program Files\NVIDIA Corporation\Display\NvSmartMax.dll
LoadedModule[100]=C:\Windows\SYSTEM32\WTSAPI32.dll
LoadedModule[101]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[102]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[103]=C:\Windows\system32\rsaenh.dll
LoadedModule[104]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[105]=C:\Windows\SYSTEM32\WINTRUST.dll
LoadedModule[106]=C:\Windows\SYSTEM32\CRYPT32.dll
LoadedModule[107]=C:\Windows\SYSTEM32\MSASN1.dll
LoadedModule[108]=C:\Windows\SYSTEM32\clbcatq.dll
LoadedModule[109]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[110]=C:\Windows\SYSTEM32\wbemcomn.dll
LoadedModule[111]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[112]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[113]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[114]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[115]=C:\Windows\SYSTEM32\dxgi.dll
LoadedModule[116]=C:\Windows\SYSTEM32\d3d10.dll
LoadedModule[117]=C:\Windows\SYSTEM32\d3d10core.dll
LoadedModule[118]=C:\Windows\SYSTEM32\d3d11.dll
LoadedModule[119]=C:\Windows\SYSTEM32\nvd3dum.dll
LoadedModule[120]=C:\Windows\SYSTEM32\PSAPI.DLL
LoadedModule[121]=C:\Windows\SYSTEM32\nvwgf2um.dll
LoadedModule[122]=C:\Windows\SYSTEM32\D3DCompiler_34.dll
LoadedModule[123]=C:\Windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[124]=C:\Windows\SYSTEM32\d3d10_1.dll
LoadedModule[125]=C:\Windows\SYSTEM32\d3d10_1core.dll
LoadedModule[126]=C:\Windows\SYSTEM32\WINSTA.dll
LoadedModule[127]=C:\Windows\SYSTEM32\gameux.dll
LoadedModule[128]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17415_none_a9ed7f470139b3c1\COMCTL32.dll
LoadedModule[129]=C:\Windows\SYSTEM32\XmlLite.dll
LoadedModule[130]=C:\Windows\SYSTEM32\msxml6.dll
LoadedModule[131]=C:\Windows\System32\Wpc.dll
LoadedModule[132]=C:\Windows\System32\NETAPI32.dll
LoadedModule[133]=C:\Windows\SYSTEM32\Normaliz.dll
LoadedModule[134]=C:\Windows\System32\wevtapi.dll
LoadedModule[135]=C:\Windows\System32\netutils.dll
LoadedModule[136]=C:\Windows\System32\srvcli.dll
LoadedModule[137]=C:\Windows\System32\wkscli.dll
LoadedModule[138]=C:\Windows\System32\SAMCLI.DLL
LoadedModule[139]=C:\Windows\System32\Windows.Globalization.dll
LoadedModule[140]=C:\Windows\System32\Bcp47Langs.dll
LoadedModule[141]=C:\Windows\System32\Windows.Web.dll
LoadedModule[142]=D:\fsx\uiautomationcore.dll
LoadedModule[143]=C:\Windows\SYSTEM32\OLEACC.dll
LoadedModule[144]=C:\Windows\System32\MMDevApi.dll
LoadedModule[145]=C:\Windows\SYSTEM32\AUDIOSES.DLL
LoadedModule[146]=C:\Windows\SYSTEM32\RICHED20.DLL
LoadedModule[147]=C:\Windows\SYSTEM32\USP10.dll
LoadedModule[148]=C:\Windows\SYSTEM32\msls31.dll
LoadedModule[149]=C:\Windows\SYSTEM32\HID.DLL
LoadedModule[150]=C:\Windows\SYSTEM32\XInput9_1_0.dll
LoadedModule[151]=C:\Windows\SYSTEM32\wdmaud.drv
LoadedModule[152]=C:\Windows\SYSTEM32\ksuser.dll
LoadedModule[153]=C:\Windows\SYSTEM32\AVRT.dll
LoadedModule[154]=C:\Windows\SYSTEM32\msacm32.drv
LoadedModule[155]=C:\Windows\SYSTEM32\midimap.dll
LoadedModule[156]=C:\Windows\SYSTEM32\dinput.DLL
LoadedModule[157]=C:\Windows\SYSTEM32\XInput1_4.dll
LoadedModule[158]=D:\fsx\ORBX\FTX_NA\FTX_NA_SAK05_SCENERY\scenery\ObjectFlow_SAK.dll
LoadedModule[159]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[160]=D:\fsx\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll
LoadedModule[161]=D:\fsx\Modules\FSUIPC4.dll
LoadedModule[162]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[163]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[164]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[165]=D:\fsx\Modules\A2A_Feel.dll
LoadedModule[166]=C:\WINDOWS\SYSTEM32\XAudio2_6.dll
LoadedModule[167]=D:\fsx\Modules\AccuFeelMenu.dll
LoadedModule[168]=D:\fsx\as_srv\as_btstrp.dll
LoadedModule[169]=C:\Windows\SYSTEM32\mscoree.dll
LoadedModule[170]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[171]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[172]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\5bd3374f05d46ba0563f44d032209f08\mscorlib.ni.dll
LoadedModule[173]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[174]=C:\Windows\SYSTEM32\imagehlp.dll
LoadedModule[175]=C:\Windows\SYSTEM32\ncrypt.dll
LoadedModule[176]=C:\Windows\SYSTEM32\NTASN1.dll
LoadedModule[177]=C:\Windows\SYSTEM32\gpapi.dll
LoadedModule[178]=C:\Windows\SYSTEM32\cryptnet.dll
LoadedModule[179]=C:\Windows\SYSTEM32\WLDAP32.dll
LoadedModule[180]=D:\fsx\as_srv\as_connect.dll
LoadedModule[181]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[182]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\4976746d2f27ea6b60301a84d6c3e4be\System.ni.dll
LoadedModule[183]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\828956d62d94914af63efc7fb36d1120\System.Drawing.ni.dll
LoadedModule[184]=C:\Windows\SYSTEM32\PROPSYS.dll
LoadedModule[185]=C:\Windows\SYSTEM32\Secur32.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=D:\fsx\fsx.exe
ApplicationIdentity=00000000000000000000000000000000

 

Thanks

Rick S.



6dfuecbymy0s0t74g.jpg                                                                                                                                                     

Share this post


Link to post
Share on other sites

I believe this is the last AppCrashView report I got; if you can make any sense out of it?

According to the AVSIM CTD Guide:

 

ATC.dll – Three possible solutions –

• It occurs on a change of frequency (TWR to GND for example) and is associated with other frequencies used in your plan. Try entering removeatc=yes in the General section of FSUIPC.INI.

• There are minor issues where the file atc.dll, responsible for containing the viewing graphics display during game play, encounters errors in displaying multiple image streams, especially when it renders multiple overlays. If you have multiple displays and/or multiple Windows open, there is probably a conflict or problem with the configuration. Troubleshoot.

• Make sure your memory modules in your BIOS are properly configured (i.e., match timings and voltages as some BIOS have been known to not manage these settings properly). See CPU-Z, SPD Tab and make sure settings are the same in the BIOS.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Thanks Jim, just to be clear this only happened when loading FSX, at least for me, not in flight or loading a flight.

 

Rick S.



6dfuecbymy0s0t74g.jpg                                                                                                                                                     

Share this post


Link to post
Share on other sites

Thanks Jim, just to be clear this only happened when loading FSX, at least for me, not in flight or loading a flight.

 

Rick S.

According to your crash report, FSX loaded to the setup screen. If you configure Process Monitor as I suggest in the AVSIM CTD Guide where only FSX and FSX addons are loading, you will be able to see what was loading up to the setup screen. You will need to startup FSX first (even if it shows a crash) and then run Process Monitor and set it up. Then shutdown FSX and then restart.

 

The second suggestion (bad BIOS settings) may be the cause too and the only way to fix that is to go back to Optimized Defaults.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    18%
    $4,525.00 of $25,000.00 Donate Now
×
×
  • Create New...