CTD's with EZDok?

[captain420 3,099]

I'm getting random CTD recently as well. But they are BEX errors. Anyone know anything about this? I tried looking this up but still can't find what the main cause of this is. Some say it could be caused by unecessary background services being run while playing the game. 

[lodestar 186]

I'm getting random CTD recently as well. But they are BEX errors. Anyone know anything about this? I tried looking this up but still can't find what the main cause of this is. Some say it could be caused by unecessary background services being run while playing the game. 

 

Just apply all that settings from my first two posts in this thread. And for turning DEP off, don't use that link, you need to disable it completely using command prompt: http://www.door2windows.com/how-to-disable-data-execution-prevention-dep-in-windows-7vista/

 

Servicess are more probably to be the cause for stackhash error, you have link in my second post with services to be disabled

 

Regards

[jasoncardeira 30]

well, i have a problem too with EZDOK, but only ezdok stops working, fsx continues running, but have no cameras, and can't move in the cockpit and in the outside

 

Here's the report:

 

Version=1
EventType=AppHangB1
EventTime=130260093460829089
ReportType=3
Consent=1
ReportIdentifier=a4bdb43f-32d0-11e3-bb84-742f68d4dc87
IntegratorReportIdentifier=a4bdb440-32d0-11e3-bb84-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=36fa
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=36fabb291b4b6b17b2b99afcd418b03f
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=84c6
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=84c6c5cbdeeeba2860cd403e0b8fbfb9
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.17514_none_ec83dffa859149af\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\system32\DInput.dll
LoadedModule[56]=C:\Windows\system32\HID.DLL
LoadedModule[57]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[58]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[59]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[60]=C:\Windows\system32\DSound.dll
LoadedModule[61]=C:\Windows\system32\POWRPROF.dll
LoadedModule[62]=C:\Windows\System32\MMDevApi.dll
LoadedModule[63]=C:\Windows\System32\PROPSYS.dll
LoadedModule[64]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[65]=C:\Windows\system32\RICHED32.DLL
LoadedModule[66]=C:\Windows\system32\RICHED20.dll
LoadedModule[67]=C:\Program Files (x86)\EZCA\dx8vb.dll
LoadedModule[68]=C:\Windows\system32\d3dxof.dll
LoadedModule[69]=C:\Windows\system32\dinput8.dll
LoadedModule[70]=C:\Windows\syswow64\PSAPI.dll
LoadedModule[71]=C:\Windows\system32\mswsock.dll
LoadedModule[72]=C:\Windows\System32\wship6.dll
LoadedModule[73]=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.

 

Hope someone can help me,

 

Thanks

[lodestar 186]

 

 

i have a problem too with EZDOK, but only ezdok stops working, fsx continues running, but have no cameras, and can't move in the cockpit and in the outside

 

I had this once. You can try a couple of things.

 

1.metod:

 

 - With FSX not running, start EZCA Config.exe

 - press "restore" and confirm 

 - when finished, press "Configure FSX"

 - start FSX

 

if still happens after this, metod 2:

 

 - backup your EZDOK profiles 

 - With FSX not running, start EZCA Config.exe

 - press "restore" and confirm 

 - uninstall Ezdok camera completely

 - use CCleaner to clean registry and leftovers

 - install Ezdok again and use EZCA Config.exe to configure FSX

 - put your profiles back

 

After this, Ezdok should work without problems. But there is a one more posibility - Ezdok can have this problems if you have leftovers in DLL.XML and exe.xml.

To clean them, you should enable simconnect log and see if there are some errors, and then search for those entries in XML files... It's not realy complicated if you are familiar with FSX configuration files. Anyway, let me know if first 2 metods fails and if you need help with XML cleaning

[jasoncardeira 30]

I had this once. You can try a couple of things.

 

1.metod:

 

 - With FSX not running, start EZCA Config.exe

 - press "restore" and confirm 

 - when finished, press "Configure FSX"

 - start FSX

 

if still happens after this, metod 2:

 

 - backup your EZDOK profiles 

 - With FSX not running, start EZCA Config.exe

 - press "restore" and confirm 

 - uninstall Ezdok camera completely

 - use CCleaner to clean registry and leftovers

 - install Ezdok again and use EZCA Config.exe to configure FSX

 - put your profiles back

 

After this, Ezdok should work without problems. But there is a one more posibility - Ezdok can have this problems if you have leftovers in DLL.XML and exe.xml.

To clean them, you should enable simconnect log and see if there are some errors, and then search for those entries in XML files... It's not realy complicated if you are familiar with FSX configuration files. Anyway, let me know if first 2 metods fails and if you need help with XML cleaning

 

Thanks!

 

But i've already tried the 2 methods without success..

 

I have UAC disabled, and the fsx and ezca folders in the AVG exceptions, and nothing seems to work.

 

Maybe the problem is XML related. How can i do to clean ?

One more thing that i did: erased the exe.xml i had two programs there, the ezca and the fsdt coutl, and even after the exe.xml is rebuilt, the problems are still remaining

[lodestar 186]

Maybe the problem is XML related. How can i do to clean ?

 

You need to enable simconnect log but backup your simconnect.ini before this, simconnect log is very helpful, but can cause stutters, so you will need to disable it after this. 

here is described how to configure simconnect log: http://forum.simflight.com/topic/45074-fsx-help-logging-simconnect/

 

Then run FSX, load the flight and leave fsx running for at least couple of seconds. Then close FSX, wait for FSX to close completely and then open "SimConnect0.Log" (it can take 10-20seconds sometimes, there are a lot of info). 

 

You will see there(in the upper part, almost on top)columns with info on how EXE files are launched and DLL files are loaded.

If any column starts with "error" instead of  "Exe Launched" or / and "DLL Loaded", you have a leftover entry in DLL.XML or exe.xml. This must be erased. 

 

If you want, you can send me SimConnect0.Log and FSUIPC4.log after you run FSX, and DLL.XML and exe.xml. I can take a look and see if something needs to be deleted, and check that XML is not corrupted(you can check this too http://support.precisionmanuals.com/KB/a92/dllxml-information-and-troubleshooting.aspx). 

 

You can post here ot PM me. If i don't answer immediately, that means i'm out and i will check this tonight, becouse i have something to repair on my car today

[jasoncardeira 30]

Ok many thanks for your help! I'm at work now and i'll do a flight tonight, after 7PM lisbon time. I'll do that and i'll send you the logs later. Let's see what i can do with the simconnect.

[bbilly05 3]

Do you have ENB or SweetFX installed Martin?

Just to echo pinlifter, I have the same problems as you when I use enb and alt+enter my fsx w/ ezdok. If I remove enb, no problems.

 

I'd suggest you look there first.

[jasoncardeira 30]

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

Here's the first lines of the Simconnect.log

 

0.00000 SimConnect version 10.0.61259.0

0.01169 Server: Scope=local, Protocol=Pipe, Name=\\.\pipe\Microsoft Flight Simulator\SimConnect, MaxClients=64
0.01621 Server: Scope=local, Protocol=IPv6, Address=::1, Port=52488, MaxClients=64
0.01940 Server: Scope=local, Protocol=IPv4, Address=127.0.0.1, Port=52489, MaxClients=64

 
0.64635 Exe Launched:  Path="fsdreamteam\couatl\couatl.exe"  CommandLine=""  Version="2.0.0.2354"
0.66800 Exe Launched:  Path="C:\Program Files (x86)\EZCA\EZCA.exe"  CommandLine=""  Version="1.1.6.4"
0.86938 Panels data export found and set to 20AF19E8
3.30171 DLL Loaded:  Path="bglmanx.dll"  Version="2.9.0.8"
3.30970 Panels data export found and set to 20AF19E8
3.54482 DLL Loaded:  Path="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_NA_SAK05_SCENERY\scenery\ObjectFlow_SAK.dll"  Version="1.0.5.3"
3.55042 Panels data export found and set to 20AF19E8
3.78620 DLL Loaded:  Path="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_AU\FTXAA_YBAS\Scenery\ObjectFlow_YBAS.dll"  Version="1.0.0.3"
3.79230 Panels data export found and set to 20AF19E8
4.02731 DLL Loaded:  Path="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dll"  Version="1.0.0.3"
4.03443 DLL Loaded:  Path="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll"  Version="10.0.0.13"
4.03467 File not found: Path="Aerosoft\Flight Recorder\AS-FlightRecorder.dll"

 

Last line: file not found: that's because i've uninstalled the aerosoft airbus x extended, and i don't reinstalled yet. But i don't believe the EZCA apphangB1 is because of this.

I've already downloaded the notepad plus, and i don't have any errors on dll.xml

[lodestar 186]

it can be becouse of that - "4.03467 File not found: Path="Aerosoft\Flight Recorder\AS-FlightRecorder.dll"

 

This entry will cause simconnect to search continuously for RAASPRO.dll and this may cause conflicts with any application that uses simconnect. And EZDOK uses simconnect. I had only one line of error too, after i removed that entry ezdok was ok.

 

You should delete that entry from DLL.XML. I don't have Aerosoft airbus installed, but this is from PMDG 777 RAS. You should delete this lines from DLL.XML:

 

<Launch.Addon>

<Name>RAASPRO</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>.\RAASPRO\RAASPRO.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

 

Make a backup of DLL.XML if you are not 100% sure how to do this. You can send me DLL.XML if you want too. Re-configure EZDOK after that, just in case(run Config utility again).

BTW, if ENB causes any problems, it's not important if ENB is active or not. IMportant is if ENB modules are present in FSX folder or not. This is if you suspect ENB for any instability. I don't use it, it gives me CTD's.

Don't forget to disable simconnect log, it can affect smoothness

[jasoncardeira 30]

I basically since the PMDG 777 was released, i basically only make my flights with this magnific bird. And the RAAS i always deactivate from the PMDG 777 FMC. So i don't use it. But is it secure to remove RASS fom dll.xml ?

 

And i have the 2 ENB config files on fsx folder. d3d9.dll and enbseries.ini -> but this is the normal procedure, right ?

 

Many thanks for your help, i'll backup the dll.xml and erase that lines, and come back later to tell you something

[lodestar 186]

Don't remove RAS that belogs to PMDG 777, it was an example which lines you need to remove(becouse i don't have aerosoft bus installed). 

 

You actualy need to remove aersoft flight recorder entry, where patch is "Aerosoft\Flight Recorder\AS-FlightRecorder.dll".

 

 

I don't have it, but it should look like this:

 

<Launch.Addon>

<Name>Flight Recorder</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
</Launch.Addon>

 

You need to delete all that lines using Notepad++.

 

For ENB is normal to have 2 files. It can give you some freezes and CTD's. I don't know if that can cause problems with ezdok, but i'm sure that DLL.XML leftovers can do that  

[jasoncardeira 30]

Ok, but i don't use the RAAS, can i erase that from DLL.XML ou leave it there ?

 

<Launch.Addon>
    <Name>Flight Recorder</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
  </Launch.Addon>

 

I erased this, and i left RAAS there, and i'll come back and report

 

thanks again for your help and your time.

[lodestar 186]

You can remove it, but just ensure that you have it disabled for all liveries. I'm not sure, but i think this could create some conflicts if you enable it and there is no entry and patch in dll.xml. Better idea is to disable it in DLL.XML, just change "False" to "True" like here, text in red:

<Launch.Addon>

<Name>RAASPRO</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>.\RAASPRO\RAASPRO.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

 

This way module will not be started at all, just like you delete or uninstall RAS. But this way you can enable it(changing "True" to "False")when you want. I have all unused modules disabled, actualy before each flight i enable only only modules that i need for my next flight, like sceneries. This gives me realy smooth FSX

[jasoncardeira 30]

Yep, i do the same but not in the DLL.xml, only in the addon sceneries, i only enable the departure scenery and the arrive scenery. Ok, but now i left the RAAS like it were before, and simply remove the asrecorder, and see what it comes.

 

Thanks again.