Sign in to follow this  
Supermalc

FSX will not start even though I have reinstalled - HELP

Recommended Posts

Hello gurus, I have a very knotty problem.  

 

But first some background, I installed FSX and Acceleration on a separate SSD drive in April along with a whole host of add-ons and it was running acceptably on my i7-2700 @ 3.5 Ghz machine with 8 GB of ram and Windows 7 64bit Pro.  But a few days ago when I changed two things in parallel it all went wrong, I know it was stupid but I am where I am.  

 

Firstly I decided I was fed up with the way FSX handles time and downloaded FSRealTime, some how I got hold of a really old copy, it worked fine but the reg key wouldn't work.  So I downloaded an up to date copy and got it registered and thats when my problems started.  It may well be a coincidence but thats when it happened.  In parallel with this I decided to get a better USB hub (D-Link) to tidy up the multitude of cables, the hub took a while to settle down, lots of bongs, may have been fixed by downloading Windows updates.  Anyhow both of these issues were in progress when FSX stopped working by crashing to desktop with “A fatal error occurred” while the startup screen was displaying.

 

So I looked at some forums and couldn't see any obvious fixes so I did a re-install in the approved manner after uninstalling all add-ons and then FSX itself.  After the reinstall the same problem occurred.  I then did the reinstall again being far more careful about the uninstalls, using Revo Uninstaller and CClean to check the registry, and the same problem is there. I have also updated the video card drivers thinking they may be out of sync with Windows.


Dont really know how to read the AppCrashView report but do notice that it stopped at “d3d10_1core.dll” and this was updated when I did the Windows updates.


I cannot see a way out of this short of rebuilding the machine which I am obviously reluctant to do but need some help with an alternative solution, (my wife suggested i should buy a new machine , but that seems a bit too drastic).

 

By the way FSX is the only programme that is impacted, Chrome, Photoshop for example are fine.


Here is the output from AppCrashView

Version=1

EventType=BEX

EventTime=130576041784414780

ReportType=2

Consent=1

UploadTime=130576041784852286

ReportIdentifier=186596c3-522b-11e4-b2fb-5404a646ed2c

IntegratorReportIdentifier=186596c2-522b-11e4-b2fb-5404a646ed2c

WOW64=1

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=04caf8bc

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.7601.2.1.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=2057

UI[2]=F:\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]=F:\FSX\fsx.exe

LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll

LoadedModule[2]=C:\Windows\syswow64\kernel32.dll

LoadedModule[3]=C:\Windows\syswow64\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\syswow64\msvcrt.dll

LoadedModule[7]=C:\Windows\syswow64\GDI32.dll

LoadedModule[8]=C:\Windows\syswow64\USER32.dll

LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll

LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll

LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll

LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll

LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll

LoadedModule[14]=C:\Windows\syswow64\LPK.dll

LoadedModule[15]=C:\Windows\syswow64\USP10.dll

LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll

LoadedModule[17]=C:\Windows\syswow64\ole32.dll

LoadedModule[18]=C:\Windows\system32\apphelp.dll

LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL

LoadedModule[20]=C:\Windows\system32\UxTheme.dll

LoadedModule[21]=C:\Windows\system32\WINMM.dll

LoadedModule[22]=C:\Windows\system32\samcli.dll

LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll

LoadedModule[24]=C:\Windows\system32\MSACM32.dll

LoadedModule[25]=C:\Windows\system32\VERSION.dll

LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll

LoadedModule[27]=C:\Windows\system32\sfc.dll

LoadedModule[28]=C:\Windows\system32\sfc_os.DLL

LoadedModule[29]=C:\Windows\syswow64\USERENV.dll

LoadedModule[30]=C:\Windows\syswow64\profapi.dll

LoadedModule[31]=C:\Windows\system32\dwmapi.dll

LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll

LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll

LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll

LoadedModule[35]=C:\Windows\syswow64\urlmon.dll

LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll

LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll

LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll

LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll

LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll

LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll

LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL

LoadedModule[43]=C:\Windows\syswow64\iertutil.dll

LoadedModule[44]=C:\Windows\syswow64\WININET.dll

LoadedModule[45]=C:\Windows\system32\MPR.dll

LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL

LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV

LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL

LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll

LoadedModule[50]=C:\Windows\system32\mscms.dll

LoadedModule[51]=C:\Windows\system32\DDRAW.dll

LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll

LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll

LoadedModule[54]=C:\Windows\syswow64\IMM32.dll

LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll

LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll

LoadedModule[57]=C:\Windows\syswow64\NSI.dll

LoadedModule[58]=C:\Windows\system32\msi.dll

LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL

LoadedModule[60]=F:\FSX\language.dll

LoadedModule[61]=F:\FSX\API.DLL

LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll

LoadedModule[63]=F:\FSX\ablscpt.dll

LoadedModule[64]=F:\FSX\flight.dll

LoadedModule[65]=F:\FSX\ai_player.dll

LoadedModule[66]=F:\FSX\acontain.dll

LoadedModule[67]=F:\FSX\controls.dll

LoadedModule[68]=C:\Windows\system32\DINPUT8.dll

LoadedModule[69]=F:\FSX\fsui.dll

LoadedModule[70]=F:\FSX\atc.dll

LoadedModule[71]=F:\FSX\facilities.dll

LoadedModule[72]=F:\FSX\demo.dll

LoadedModule[73]=F:\FSX\main.dll

LoadedModule[74]=F:\FSX\fe.dll

LoadedModule[75]=F:\FSX\util.dll

LoadedModule[76]=F:\FSX\simprop.dll

LoadedModule[77]=F:\FSX\g2d.dll

LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll

LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll

LoadedModule[80]=C:\Windows\system32\d3d9.dll

LoadedModule[81]=C:\Windows\system32\d3d8thk.dll

LoadedModule[82]=F:\FSX\g3d.dll

LoadedModule[83]=F:\FSX\panels.dll

LoadedModule[84]=F:\FSX\multiplayer.dll

LoadedModule[85]=F:\FSX\ui.dll

LoadedModule[86]=F:\FSX\sound.dll

LoadedModule[87]=F:\FSX\sim1.dll

LoadedModule[88]=F:\FSX\simscheduler.dll

LoadedModule[89]=F:\FSX\visualfx.dll

LoadedModule[90]=F:\FSX\window.dll

LoadedModule[91]=F:\FSX\terrain.dll

LoadedModule[92]=F:\FSX\weather.dll

LoadedModule[93]=C:\Windows\system32\DSOUND.dll

LoadedModule[94]=C:\Windows\system32\POWRPROF.dll

LoadedModule[95]=F:\FSX\symmap.dll

LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll

LoadedModule[97]=C:\Windows\system32\MSIMG32.dll

LoadedModule[98]=F:\FSX\xuipc.dll

LoadedModule[99]=F:\FSX\livingwater.dll

LoadedModule[100]=F:\FSX\fs-traffic.dll

LoadedModule[101]=F:\FSX\gps.dll

LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll

LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll

LoadedModule[104]=C:\Program Files (x86)\ATI Technologies\HydraVision\HydraDMH.dll

LoadedModule[105]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll

LoadedModule[106]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[107]=C:\Program Files\UPDD\tbhook.dll

LoadedModule[108]=C:\Windows\system32\rsaenh.dll

LoadedModule[109]=C:\Windows\syswow64\WINTRUST.dll

LoadedModule[110]=C:\Windows\syswow64\CRYPT32.dll

LoadedModule[111]=C:\Windows\syswow64\MSASN1.dll

LoadedModule[112]=C:\Windows\syswow64\CLBCatQ.DLL

LoadedModule[113]=C:\Windows\system32\wbem\wbemprox.dll

LoadedModule[114]=C:\Windows\system32\wbemcomn.dll

LoadedModule[115]=C:\Windows\system32\RpcRtRemote.dll

LoadedModule[116]=C:\Windows\system32\wbem\wbemsvc.dll

LoadedModule[117]=C:\Windows\system32\wbem\fastprox.dll

LoadedModule[118]=C:\Windows\system32\NTDSAPI.dll

LoadedModule[119]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL

LoadedModule[120]=C:\Windows\system32\dxgi.dll

LoadedModule[121]=C:\Windows\system32\d3d10.dll

LoadedModule[122]=C:\Windows\system32\d3d10core.dll

LoadedModule[123]=C:\Windows\system32\d3d11.dll

LoadedModule[124]=C:\Windows\system32\atklumdisp.dll

LoadedModule[125]=C:\Windows\system32\aticfx32.dll

LoadedModule[126]=C:\Windows\system32\atiu9pag.dll

LoadedModule[127]=C:\Windows\system32\atiumdag.dll

LoadedModule[128]=C:\Windows\system32\atiumdva.dll

LoadedModule[129]=C:\Windows\system32\atkdx11disp.dll

LoadedModule[130]=C:\Windows\system32\atiuxpag.dll

LoadedModule[131]=C:\Windows\system32\atidxx32.dll

LoadedModule[132]=C:\Windows\system32\D3DCompiler_34.dll

LoadedModule[133]=C:\Windows\system32\WindowsCodecs.dll

LoadedModule[134]=C:\Windows\system32\d3d10_1.dll

LoadedModule[135]=C:\Windows\system32\d3d10_1core.dll

Sec[0].Key=LCID

Sec[0].Value=2057

FriendlyEventName=Stopped working

ConsentKey=BEX

AppName=Microsoft® Flight Simulator X

AppPath=F:\FSX\fsx.exe

 

 

So I looked at some forums and couldn't see any obvious fixes so I did a reinstall in the approved manner after uninstalling all add-ons and then FSX itself.  After the reinstall the same problem occurred.  I then did the reinstall again being far more careful about the uninstalls, using Revo Uninstaller and CClean to check the registry, and the same problem is there. I have also updated the video card drivers too.

 

Dont really know how to read the AppCrashView report but do notice that it stopped at “d3d10_1core.dll” and this was updated when I did the Windows updates

 

I cannot see a way out of this short of rebuilding the machine which I am obviously reluctant to do but need some help with an alternative solution, (my wife suggested i should buy a new machine , but that seems a bit too drastic).

 

Here is the output from AppCrashView

Version=1

EventType=BEX

EventTime=130576041784414780

ReportType=2

Consent=1

UploadTime=130576041784852286

ReportIdentifier=186596c3-522b-11e4-b2fb-5404a646ed2c

IntegratorReportIdentifier=186596c2-522b-11e4-b2fb-5404a646ed2c

WOW64=1

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=04caf8bc

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.7601.2.1.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=2057

UI[2]=F:\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]=F:\FSX\fsx.exe

LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll

LoadedModule[2]=C:\Windows\syswow64\kernel32.dll

LoadedModule[3]=C:\Windows\syswow64\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\syswow64\msvcrt.dll

LoadedModule[7]=C:\Windows\syswow64\GDI32.dll

LoadedModule[8]=C:\Windows\syswow64\USER32.dll

LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll

LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll

LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll

LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll

LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll

LoadedModule[14]=C:\Windows\syswow64\LPK.dll

LoadedModule[15]=C:\Windows\syswow64\USP10.dll

LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll

LoadedModule[17]=C:\Windows\syswow64\ole32.dll

LoadedModule[18]=C:\Windows\system32\apphelp.dll

LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL

LoadedModule[20]=C:\Windows\system32\UxTheme.dll

LoadedModule[21]=C:\Windows\system32\WINMM.dll

LoadedModule[22]=C:\Windows\system32\samcli.dll

LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll

LoadedModule[24]=C:\Windows\system32\MSACM32.dll

LoadedModule[25]=C:\Windows\system32\VERSION.dll

LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll

LoadedModule[27]=C:\Windows\system32\sfc.dll

LoadedModule[28]=C:\Windows\system32\sfc_os.DLL

LoadedModule[29]=C:\Windows\syswow64\USERENV.dll

LoadedModule[30]=C:\Windows\syswow64\profapi.dll

LoadedModule[31]=C:\Windows\system32\dwmapi.dll

LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll

LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll

LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll

LoadedModule[35]=C:\Windows\syswow64\urlmon.dll

LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll

LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll

LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll

LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll

LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll

LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll

LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL

LoadedModule[43]=C:\Windows\syswow64\iertutil.dll

LoadedModule[44]=C:\Windows\syswow64\WININET.dll

LoadedModule[45]=C:\Windows\system32\MPR.dll

LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL

LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV

LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL

LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll

LoadedModule[50]=C:\Windows\system32\mscms.dll

LoadedModule[51]=C:\Windows\system32\DDRAW.dll

LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll

LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll

LoadedModule[54]=C:\Windows\syswow64\IMM32.dll

LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll

LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll

LoadedModule[57]=C:\Windows\syswow64\NSI.dll

LoadedModule[58]=C:\Windows\system32\msi.dll

LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL

LoadedModule[60]=F:\FSX\language.dll

LoadedModule[61]=F:\FSX\API.DLL

LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll

LoadedModule[63]=F:\FSX\ablscpt.dll

LoadedModule[64]=F:\FSX\flight.dll

LoadedModule[65]=F:\FSX\ai_player.dll

LoadedModule[66]=F:\FSX\acontain.dll

LoadedModule[67]=F:\FSX\controls.dll

LoadedModule[68]=C:\Windows\system32\DINPUT8.dll

LoadedModule[69]=F:\FSX\fsui.dll

LoadedModule[70]=F:\FSX\atc.dll

LoadedModule[71]=F:\FSX\facilities.dll

LoadedModule[72]=F:\FSX\demo.dll

LoadedModule[73]=F:\FSX\main.dll

LoadedModule[74]=F:\FSX\fe.dll

LoadedModule[75]=F:\FSX\util.dll

LoadedModule[76]=F:\FSX\simprop.dll

LoadedModule[77]=F:\FSX\g2d.dll

LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll

LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll

LoadedModule[80]=C:\Windows\system32\d3d9.dll

LoadedModule[81]=C:\Windows\system32\d3d8thk.dll

LoadedModule[82]=F:\FSX\g3d.dll

LoadedModule[83]=F:\FSX\panels.dll

LoadedModule[84]=F:\FSX\multiplayer.dll

LoadedModule[85]=F:\FSX\ui.dll

LoadedModule[86]=F:\FSX\sound.dll

LoadedModule[87]=F:\FSX\sim1.dll

LoadedModule[88]=F:\FSX\simscheduler.dll

LoadedModule[89]=F:\FSX\visualfx.dll

LoadedModule[90]=F:\FSX\window.dll

LoadedModule[91]=F:\FSX\terrain.dll

LoadedModule[92]=F:\FSX\weather.dll

LoadedModule[93]=C:\Windows\system32\DSOUND.dll

LoadedModule[94]=C:\Windows\system32\POWRPROF.dll

LoadedModule[95]=F:\FSX\symmap.dll

LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll

LoadedModule[97]=C:\Windows\system32\MSIMG32.dll

LoadedModule[98]=F:\FSX\xuipc.dll

LoadedModule[99]=F:\FSX\livingwater.dll

LoadedModule[100]=F:\FSX\fs-traffic.dll

LoadedModule[101]=F:\FSX\gps.dll

LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll

LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll

LoadedModule[104]=C:\Program Files (x86)\ATI Technologies\HydraVision\HydraDMH.dll

LoadedModule[105]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll

LoadedModule[106]=C:\Windows\system32\CRYPTSP.dll

LoadedModule[107]=C:\Program Files\UPDD\tbhook.dll

LoadedModule[108]=C:\Windows\system32\rsaenh.dll

LoadedModule[109]=C:\Windows\syswow64\WINTRUST.dll

LoadedModule[110]=C:\Windows\syswow64\CRYPT32.dll

LoadedModule[111]=C:\Windows\syswow64\MSASN1.dll

LoadedModule[112]=C:\Windows\syswow64\CLBCatQ.DLL

LoadedModule[113]=C:\Windows\system32\wbem\wbemprox.dll

LoadedModule[114]=C:\Windows\system32\wbemcomn.dll

LoadedModule[115]=C:\Windows\system32\RpcRtRemote.dll

LoadedModule[116]=C:\Windows\system32\wbem\wbemsvc.dll

LoadedModule[117]=C:\Windows\system32\wbem\fastprox.dll

LoadedModule[118]=C:\Windows\system32\NTDSAPI.dll

LoadedModule[119]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL

LoadedModule[120]=C:\Windows\system32\dxgi.dll

LoadedModule[121]=C:\Windows\system32\d3d10.dll

LoadedModule[122]=C:\Windows\system32\d3d10core.dll

LoadedModule[123]=C:\Windows\system32\d3d11.dll

LoadedModule[124]=C:\Windows\system32\atklumdisp.dll

LoadedModule[125]=C:\Windows\system32\aticfx32.dll

LoadedModule[126]=C:\Windows\system32\atiu9pag.dll

LoadedModule[127]=C:\Windows\system32\atiumdag.dll

LoadedModule[128]=C:\Windows\system32\atiumdva.dll

LoadedModule[129]=C:\Windows\system32\atkdx11disp.dll

LoadedModule[130]=C:\Windows\system32\atiuxpag.dll

LoadedModule[131]=C:\Windows\system32\atidxx32.dll

LoadedModule[132]=C:\Windows\system32\D3DCompiler_34.dll

LoadedModule[133]=C:\Windows\system32\WindowsCodecs.dll

LoadedModule[134]=C:\Windows\system32\d3d10_1.dll

LoadedModule[135]=C:\Windows\system32\d3d10_1core.dll

Sec[0].Key=LCID

Sec[0].Value=2057

FriendlyEventName=Stopped working

ConsentKey=BEX

AppName=Microsoft® Flight Simulator X

AppPath=F:\FSX\fsx.exe

 

Share this post


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

Dont really know how to read the AppCrashView report but do notice that it stopped at “d3d10_1core.dll” and this was updated when I did the Windows updates

This means nothing. The module successfully loaded and is not your problem. You had a BEX or Buffer_Exception_Overrun or Buffer_Overrun. The explanation of this crash can be found at the following link - http://en.wikipedia.org/wiki/Buffer_overflow. Most likely your settings are too high or you have the BufferPool tweak in your fsx.cfg. The faulting module is unknown but it means it is getting close to a StackHash. There is no known solution, except one, for BEX/StackHashes. The one known solution involves MyTrafficX 5.4c as this program causes this crash when an AI Schedule cannot find a flightplan or aircraft and something goes wrong. Reinstalling MyTrafficX and using the default schedule (not the 2012/2013 schedules works for most). An ntdll.dll could also pop up occasionally as the faulting module and the same thing applies as with a StackHash. High settings, BufferPool tweak. Bad.

 

Best regards,

Share this post


Link to post
Share on other sites

Hi Jim

 

Thank for the response, unfortunately I have not managed to load the sim since the reinstall and therefore not changed any settings and the fsx.cfg is as installed by Microsoft, I have not reinstalled any addons, so FSX is completely clean.

 

Not sure where to go from here, I have loaded native FSX on a clean system and it will not run past the initial screen. Do you have any other suggestions?

 

Malcolm

Share this post


Link to post
Share on other sites

 


 

downloaded FSRealTime, some how I got hold of a really old copy, it worked fine but the reg key wouldn't work.

 

:Thinking:

Share this post


Link to post
Share on other sites

I have not reinstalled any addons, so FSX is completely clean.

If FSX will not start up, it could be that you do not have Microsoft Visual C++ Redistributable 2005 w/SP1. That is required for FSX to start up. A lot of people try to take shortcuts and move their previous install to a new system or HDD w/o fully reinstalling and the Microsoft Visuals required to run FSX are not installed. If it is not loading after the setup screen (after you hit Fly Now), then where is it getting hung up? While loading terrain?

 

Uninstall FSRealTime and see if that fixes the problem. I heard FSRealTime does not really work anyway. That program is probably not loading properly if you do not have a valid registration.

 

Best regards,

Share this post


Link to post
Share on other sites

How can I check what Visual C++ redistribute I have, is it the list in control panel/programs? How do I check what I need, is the list in the CTD document accurate?

 

The second reinstallation was completely clean, no trace of fsx or any fsx related software on the machine.

 

It crashes before the user interface is displayed so no opportunity to hit any buttons.

 

FS RealTime is long gone.

Share this post


Link to post
Share on other sites

How can I check what Visual C++ redistribute I have, is it the list in control panel/programs?

If you look in the AVSIM CTD Guide located at the right of this forum under hot spots, there's a section there on page 2 or 3 about all of the required Microsoft Visuals and where to find them on your computer. The list should be shown in your Add/Remove Programs. There's also a requirement for certain Microsoft.net framework programs. If they are not installed properly, then fsx will not work properly. You can see the details in the AVSIM CTD Guide.

 

Best regards,

Share this post


Link to post
Share on other sites

Hi Jim

I found the on the fabulous CTD Guide and have checked/installed them all as the guide, DotNet stuff too, with the exception of a couple go the 2012 Visual C programmes where I only seemed to be able to get more up to date versions.

 

No joy with these moods, doing a reboot each time just in case the registry needs to update its self. The error remains the same.

 

I am thinking the only way to fix it is to reinstall windows 7 with a disk reformat after reform formatting my FSX SSD. I am assuming that will have the effect of reseting the machine to "factory settings" which should cleanup whatever mess I have made. There was no problem installing FSX when the machine was new. There is do little software on the machine now it's not that much extra work to do windows. Can in be certain this would work?

 

Malcolm

Hi Jim

I found the on the fabulous CTD Guide and have checked/installed them all as the guide, DotNet stuff too, with the exception of a couple go the 2012 Visual C programmes where I only seemed to be able to get more up to date versions.

 

No joy with these moods, doing a reboot each time just in case the registry needs to update its self. The error remains the same.

 

I am thinking the only way to fix it is to reinstall windows 7 with a disk reformat after reform formatting my FSX SSD. I am assuming that will have the effect of reseting the machine to "factory settings" which should cleanup whatever mess I have made. There was no problem installing FSX when the machine was new. There is do little software on the machine now it's not that much extra work to do windows. Can in be certain this would work?

 

Malcolm

Don't know what happened there my post seems to have got duplicated, won't make it twice as good.

Share this post


Link to post
Share on other sites

No joy with these moods, doing a reboot each time just in case the registry needs to update its self. The error remains the same.

Your issue was that FSX would not start up (post#3). I wanted to make sure you have the Microsoft Visuals and Microsoft.net's installed as they can prevent a startup.

 

In your OP you stated you reinstalled FSX/Acceleration and the fsx will not load up. I do not know how you can have a failed start up and you get everything that was loaded in the OP!!

 

In post #2, I talked about the error you are getting - BEX or Buffer Exception Overrun or Buffer Overrun. I provided a link to an explanation of this. You have a serious problem with Microsoft Windows AND the installation of FSX/Acceleration. I cannot continue to go through the AVSIM CTD Guide and provide you a possible solution and you try the solution one by one until all the solutions run out. There is no known solution for BEX errors.

 

I will politely bow out of this thread as I have run out of ideas. Perhaps another member can provide you with more guidance.

 

Best regards,

Share this post


Link to post
Share on other sites

Malcolm,

 

Before reinstalling Windows, one thing you could do is check the following folders have been deleted as part of the FSX uninstall process:

 

C:\Users\YourUserName\Documents\Flight Simulator X Files

C:\Users\YourUserName\AppData\Roaming\Microsoft\FSX

C:\Users\YourUserName\AppData\Local\Microsoft\FSX

 

You'll need to select 'show hidden files and folders' in the control panel to access the latter two locations. I recall being unable to start FSX in the past because the Logbook.BIN had become corrupted.

 

Failing that, a reformat and reinstall from the Windows disk should fix any software issues including registry probs.

 

Cheers,

Nick

Share this post


Link to post
Share on other sites

 

 

I will politely bow out of this thread as I have run out of ideas. Perhaps another member can provide you with more guidanc

Thanks for you help Jim, it does seem my system is beyond repair.

The lesson learned is never to change more than one thing at a time, you never know when it's all going to blow up in your face.

I wouldn't have done it at work so don't know why I didn't take the same level of care with what is an inherently unstable bit of software.

Thanks Nick

 

I have checked the first three and they were removed by the uninstall, not sure about the last one.

 

One thing I do have to try is installing fsx without acceleration as it was working ok at that stage. Not sure what I lose with fsx plus sp1 & 2 compared with acceleration. I only fly PMDG & majestic really.

Share this post


Link to post
Share on other sites

Here's an interesting thing.

After re-installing FSX Deluxe the sim worked fine.

After installing SP1 the sim worked fine.

After installing SP2 I get the fatal error during start up.

 

Not that its much help as I still don't have a sim that works but it does narrow the problem down a bit for those who know about these things.

 

So here I go with re-installing Win 7 and reformatting the C: drive

Here's the plan

Reformat the FSX drive

Pull the plugs from the FSX drive and the Data drive (Photos, Software Backups), belt and braces to ensure they are not impacted by the Win 7 re-install.

Re-install Win 7 on the C: drive with the reformat option

Install all Win 7 updates

Plug the FSX and Data drives back in

Install FSX Deluxe

Install Acceleration

 

Share this post


Link to post
Share on other sites

Here's an interesting thing.

After re-installing FSX Deluxe the sim worked fine.

After installing SP1 the sim worked fine.

After installing SP2 I get the fatal error during start up.

SP2 is about the same as Acceleration. The same exact thing as Acceleration except that Acceleration is payware and contains several payware products, like new aircraft and scenery, and SP2 is freeware because it does not contain the payware stuff in Acceleration. They released SP2 long after releasing the payware Acceleration thinking they could make millions, maybe billions, by holding off on the freeware version. For $20 (the cost of Acceleration back then) you could have SP2 right now, immediately! $20. The only difference between SP2 and Acceleration is that they coded SP2 so that it would be impossible to use any of the payware aircraft and scenery that's in Acceleration. It will probably cause crashes or simply will not start up. It's something I have never tested so can't say for sure. But, if you had Acceleration installed once, it is possible the registry thinks Acceleration is still installed and crashing SP2 as the two are just not compatible.

 

Best regards,

Share this post


Link to post
Share on other sites

Well guys reinstallation of Win 7, fully updated and updating the bios and the graphics card seem to have done the trick, i have got FSX back again.  Now just got to reconfigure FXS, reinstall all the addons, peripherals and other software to complete the rebuild.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this