I use ENB, but it happens with ENB disabled and ENB enabled, is the same thing

 

I'd suggest you remove both of those enb files from your fsx folder and see what happens. The DLL will still be resident in memory even when it is disabled (assuming you are using shift+F12 to toggle)

 

Sent from my Galaxy Nexus using Tapatalk

 

 

If i remove, how do i switch to ENB mod ?

oh no, it happened again.. don't know really what can i do more.. It's happen with more frequency when i switch to 16x or 8x and turn to normal time. When back to normal time, ezdok freezes, but the sim continues runnning..

Here's the report:

 

Version=1
EventType=AppHangB1
EventTime=130262550883080373
ReportType=3
Consent=1
ReportIdentifier=ce86fff3-350c-11e3-a693-742f68d4dc87
IntegratorReportIdentifier=ce86fff4-350c-11e3-a693-742f68d4dc87
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=EZCA.exe
Sig[1].Name=Application Version
Sig[1].Value=1.1.6.4
Sig[2].Name=Application Timestamp
Sig[2].Value=2a425e19
Sig[3].Name=Hang Signature
Sig[3].Value=a0b5
Sig[4].Name=Hang Type
Sig[4].Value=1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2070
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=a0b5c91776a4c5c3cb23a5e0f3b252d4
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=c6f7
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=c6f74e639a40df75acb179229d002a00
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=a0b5
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=a0b5c91776a4c5c3cb23a5e0f3b252d4
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=c6f7
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=c6f74e639a40df75acb179229d002a00
UI[3]=EZCA for FSX is not responding
UI[4]=Windows can check online for a solution. If you close the program, you might lose information.
UI[5]=Check for a solution and close the program
UI[6]=Check for a solution and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files (x86)\EZCA\EZCA.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.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\comctl32.dll
LoadedModule[5]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[8]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[9]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[10]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[11]=C:\Windows\syswow64\GDI32.dll
LoadedModule[12]=C:\Windows\syswow64\USER32.dll
LoadedModule[13]=C:\Windows\syswow64\LPK.dll
LoadedModule[14]=C:\Windows\syswow64\USP10.dll
LoadedModule[15]=C:\Windows\system32\apphelp.dll
LoadedModule[16]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[17]=C:\Windows\syswow64\SHLWAPI.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\syswow64\ole32.dll
LoadedModule[22]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[23]=C:\Windows\system32\MSACM32.dll
LoadedModule[24]=C:\Windows\system32\VERSION.dll
LoadedModule[25]=C:\Windows\syswow64\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\syswow64\SETUPAPI.dll
LoadedModule[32]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[33]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[34]=C:\Windows\syswow64\urlmon.dll
LoadedModule[35]=C:\Windows\syswow64\iertutil.dll
LoadedModule[36]=C:\Windows\syswow64\WININET.dll
LoadedModule[37]=C:\Windows\syswow64\Normaliz.dll
LoadedModule[38]=C:\Windows\system32\MPR.dll
LoadedModule[39]=C:\Windows\system32\IMM32.DLL
LoadedModule[40]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[41]=C:\Program Files (x86)\EZCA\borlndmm.dll
LoadedModule[42]=C:\Windows\system32\olepro32.dll
LoadedModule[43]=C:\Windows\system32\winspool.drv
LoadedModule[44]=C:\Windows\syswow64\comdlg32.dll
LoadedModule[45]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[46]=C:\Program Files (x86)\EZCA\Control.dll
LoadedModule[47]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[48]=C:\Windows\SysWow64\EZCACO~1.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SIMCONNECT.DLL
LoadedModule[50]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCR80.dll
LoadedModule[51]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc\MSVCP80.dll
LoadedModule[52]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[53]=C:\Windows\syswow64\NSI.dll
LoadedModule[54]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[55]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.DLL
LoadedModule[56]=C:\Windows\system32\DInput.dll
LoadedModule[57]=C:\Windows\system32\HID.DLL
LoadedModule[58]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[59]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[60]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[61]=C:\Windows\system32\DSound.dll
LoadedModule[62]=C:\Windows\system32\POWRPROF.dll
LoadedModule[63]=C:\Windows\System32\MMDevApi.dll
LoadedModule[64]=C:\Windows\System32\PROPSYS.dll
LoadedModule[65]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[66]=C:\Windows\system32\RICHED32.DLL
LoadedModule[67]=C:\Windows\system32\RICHED20.dll
LoadedModule[68]=C:\Program Files (x86)\EZCA\dx8vb.dll
LoadedModule[69]=C:\Windows\system32\d3dxof.dll
LoadedModule[70]=C:\Windows\system32\dinput8.dll
LoadedModule[71]=C:\Windows\syswow64\PSAPI.dll
LoadedModule[72]=C:\Windows\system32\mswsock.dll
LoadedModule[73]=C:\Windows\System32\wship6.dll
LoadedModule[74]=C:\Windows\system32\avrt.dll
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=EZCA for FSX
AppPath=C:\Program Files (x86)\EZCA\EZCA.exe
ReportDescription=A problem caused this program to stop interacting with Windows.

Maybe you should try to remove ENB files and see if still happens. ENB and SweetFx just don't work well on some systems. On my old system ENB was ok, and on this new system i get hanging and CTD's, so i just stoped using ENB.

 

Just to check something else, have you updated your SDK during FSX installation? http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_(FSX)#Versions

Which version of EZDOK you have?

yup, i have SP2 installed. I never had problems with ENB, the problems started with PMDG 777

But i don't have the SDK installed, only the SP1 and SP2, do i have to install the SDK ?

That was important for proper functioning of simconnect. But this should be installed during FSX installation. If you have FSX SP2, you should install first SDK version from FSX Disk, then SDK SP1a, and then SDK SP2. The first one is on the FSX installation Disk 1, the other two can be downloaded in the link i sent you in above post.

 

But ask first in simconnect forum(here on Avsim or FSDevelopers forums)if you can install them now, after you have FSX SP2 installed. I'm not sure if that is posible becouse first version is for FSX without service packs and second only for FSX SP1. It should be installed during FSX installation. Just check before you do something.

There are some rules on how to install FSX, service packs and SDK, with loading free flight between them and restarting PC... Also, you should not install FSX in default location on C, this can be a problem too. It should be installed on separate Disk or at least separate partition, not on the same partition with Windows. 

 

But anyway, try to run it without ENB files in FSX folder and see if you still have problems. Just move ENB files somewhere and test it, you can put them back after that if you see they are not the reason for hanging.

thanks for your answer! but if i put ENB outside fsx folder, how can i use the effect inside the sim ?

You can't. Some of us just can't use it without FSX crashing. I stoped using ENB and SweetFx long time ago becouse they can induce instability

It's strange, since i never had any problems using ENB, and i'm using ENB since mid 2012, the problems only started with the 777. bad config or something. got to take a look again. if it persists i'll do a clean reinstall

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

So, the correct install is: FSX / sdk /sdk sp1a /sdk sp2 / sp1 /sp2. is this right ?

No.  FSX first.  Then run it at least once to generate a Fsx.cfg or other files.  I would also recommend making some minor changes like changing the resolution, maybe moving a couple of sliders and then running FSX again.  Make sure it is running properly.  If you are not installing Acceleration, then, install SP1.  Run fsx at least once.  No problems?  Then continue with installing SP2.  Run that at least once.  Now you can install the SDK - http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_%28FSX%29.

 

I like this guide for uninstalling/installing FSX - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.  Only additional thing I would recommend is running a registry cleaner like CCleaner before reinstalling.

 

Best regards,

Jim

Jim,

 

Thank you very much for your reply!

 

I have installed fsx + sp2, and i have installed yesterday the SDK. i think i'm in trouble.. but fsx is running well, but i didn't do yet a flight to test the ezdok camera. The camera only stops when i increse the sim rate to 8x ou 16x (when back to normal rate), the camera doesn't respond.

 

I'll do a flight today to make the tests. (i reinstalled SP2 too before the sdk)