Hi,
Some users have reported that OCP4NGX.exe ( version 2.4.0.0 with the latest OC4BA v2_5814 package) crashes now and then.
The module that crashes is actully not OCP4NGX.exe , but the MSVCR100.dll that OCP4NGX.exe and other C++ program uses.
The version of the msvcr100.dll that crashed belongs to Microsoft Visual C++ 2010, SP1 .
AS I have not been able to reproduce the crash on my PC's and the info I have received so far do not help me to trace down the problem I need some more info.
If you have any of these crashes on your system, please report them here at this thread + info as below.
Info needed
0. Opencockpits modules in use when crash occur
1. FSX version ( Accelleration or standard + SP2)
2. FSX Addons installed
3. Installed OS version
4. MS redistributables versions installed
5. Overclocking CPU (Yes, No)
6. Type of GPU
7. Type of CPU
8. Crash info from MS Event Viewer
9. Are you running ENB or any other Shader addon with FSX?
I can send out some modified/test OCP4NGX.exe files for those that are interessed to help me track down this issue.
/Roar
/Roar
OC4BA v2 Crash Info needed
Re: OC4BA v2 Crash Info needed
HI Roar,
My old version of OC4BA had been working fine. The new version V2.8 did work once with one time communication failure between FSX (PMDG NGX) and OC modules during flight, but was able to re-connect during the ongoing flight.
It has not worked second time, since. It seems to communicate but there seems to be something not making full connection.
All my NGX o'head switches are turned off after establishing communication with OC modules. Module's windows remain blank and no digits show.
I have bought OC4BA but not tried the 777, since the 737 is not working yet. Please help and advise.
Here is the info as far as I know:
FSX SP2. No acceleration pack.
OC Modules: EFIS, MCP v2 and multi radio.
FSUIP registered.
EZDOK.
Active Sky Next
GSX
PMDG NGX, 777 ER
NVIDIA 8800 GTX, not o'clocked.
Intel i7
MS C++ 2012
Thank you,
Syed Ali
My old version of OC4BA had been working fine. The new version V2.8 did work once with one time communication failure between FSX (PMDG NGX) and OC modules during flight, but was able to re-connect during the ongoing flight.
It has not worked second time, since. It seems to communicate but there seems to be something not making full connection.
All my NGX o'head switches are turned off after establishing communication with OC modules. Module's windows remain blank and no digits show.
I have bought OC4BA but not tried the 777, since the 737 is not working yet. Please help and advise.
Here is the info as far as I know:
FSX SP2. No acceleration pack.
OC Modules: EFIS, MCP v2 and multi radio.
FSUIP registered.
EZDOK.
Active Sky Next
GSX
PMDG NGX, 777 ER
NVIDIA 8800 GTX, not o'clocked.
Intel i7
MS C++ 2012
Thank you,
Syed Ali
Re: OC4BA v2 Crash Info needed
waris600 wrote:HI Roar,
My old version of OC4BA had been working fine. The new version V2.8 did work once with one time communication failure between FSX (PMDG NGX) and OC modules during flight, but was able to re-connect during the ongoing flight.
It has not worked second time, since. It seems to communicate but there seems to be something not making full connection.
All my NGX o'head switches are turned off after establishing communication with OC modules. Module's windows remain blank and no digits show.
I have bought OC4BA but not tried the 777, since the 737 is not working yet. Please help and advise.
Here is the info as far as I know:
FSX SP2. No acceleration pack.
OC Modules: EFIS, MCP v2 and multi radio.
FSUIP registered.
EZDOK.
Active Sky Next
GSX
PMDG NGX, 777 ER
NVIDIA 8800 GTX, not o'clocked.
Intel i7
MS C++ 2012
Thank you,
Syed Ali
Hi
There is now a new OPC4NGX_PP_V1.0.ssi script in the Download page. This one will not mess up your OVH
Re: OC4BA v2 Crash Info needed
Hi Roar,
Had a crash tonight but this time it wasn't the msvcr100.dll
This is my data:
0. Opencockpits modules in use when crash occur
MCP, EFIS, COM, NAV, ADF, ATC
1. FSX version ( Accelleration or standard + SP2)
Microsoft Flight Simulator X Service Pack 2 10.0.61472.0
2. FSX Addons installed
EZdok Camera for Microsoft Flight Simulator X 1.17
FSiPanel 1.0.0.52
NaturalPoint USB Drivers x64 (TRACK-IR)
Navigraph FMS Data Manager 1.0.11.0603
NL2000V4_Installer 4.0.58
NL2000V4 latest scenery
NVIDIA Grafisch stuurprogramma 340.52
NVIDIA PhysX systeemsoftware 9.13.1220
OC4BA v2 version 2.0
Opencockpits SIOC software ver 5.0
PMDG 737 8900 NGX 1.00.3219
RAAS Professional by FS2Crew (UNLOCKED)
REX Essential Plus Overdrive (Upgrade) 3.7.2013.0715 (only used for graphics)
SceneryConfig Editor v1.1.2
TrackIR 5.2.0200
Ultimate Terrain X - Europe
VrInsight VRiSim version Rel.2014-07-17
VrInsight VRiSim/CDU-II version 1.0
VOXATC 6.20
Voices used with VOXATC
- Cepstral Callie 5.1.0
- Cepstral David 5.1.0
- Cepstral Diane 5.1.0
- Cepstral William 5.1.0
3. Installed OS version
WIN7 64bit (with the latest updates as of today's date).
4. MS redistributables versions installed
Microsoft Visual C++ 2005 Redistributable 8.0.61001
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
5. Overclocking CPU (Yes, No)
Yes, 3,40GHz to 4,2OGHz
6. Type of GPU
NVIDIA Geforce GTX650 Ti BOOST
NVIDIA Geforce GT520
7. Type of CPU
INTEL I7-2600K, 3.40GHz, 8Mb Cache, LGA1155, 95W
8. Crash info from MS Event Viewer
See the three info files after question 10
9. Are you running ENB or any other Shader addon with FSX?
No
------------------------------------------------------------------------------------------------
Addition
10. Using an Anti Virus scanner
Not using a virusscanner on my flightsim PC
1. Event viewer Error
Faulting application name: OCP4NGX.exe, version: 0.0.0.0, time stamp: 0x53de8886
Faulting module name: OCP4NGX.exe, version: 0.0.0.0, time stamp: 0x53de8886
Exception code: 0xc0000417
Fault offset: 0x00013da6
Faulting process id: 0x968
Faulting application start time: 0x01cfc2222591db92
Faulting application path: C:\SIOC\OCP4NGX.exe
Faulting module path: C:\SIOC\OCP4NGX.exe
Report Id: 939f416b-2e19-11e4-936f-8c89a564afab
2. Event viewer information
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: OCP4NGX.exe
P2: 0.0.0.0
P3: 53de8886
P4: OCP4NGX.exe
P5: 0.0.0.0
P6: 53de8886
P7: 00013da6
P8: c0000417
P9: 00000000
P10:
Attached files:
These files may be available here:
C:\Users\lnxfsp\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_OCP4NGX.exe_588588f5ae40c4228917122fa6d331b335abf6b_0dce5512
Analysis symbol:
Rechecking for solution: 0
Report Id: 939f416b-2e19-11e4-936f-8c89a564afab
Report Status: 4
3. AppCrash_OCP4NGX.exe_588588f5ae40c4228917122fa6d331b335abf6b_0dce5512
Version=1
EventType=BEX
EventTime=130536384125605432
ReportType=2
Consent=1
ReportIdentifier=939f416c-2e19-11e4-936f-8c89a564afab
IntegratorReportIdentifier=939f416b-2e19-11e4-936f-8c89a564afab
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=OCP4NGX.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=53de8886
Sig[3].Name=Fault Module Name
Sig[3].Value=OCP4NGX.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=53de8886
Sig[6].Name=Exception Offset
Sig[6].Value=00013da6
Sig[7].Name=Exception Code
Sig[7].Value=c0000417
Sig[8].Name=Exception Data
Sig[8].Value=00000000
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1043
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=f16d
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=f16d3ba2d05eee5c0e7bf740bf8bac45
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=8e9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=8e9eb445ede580c6ba9d3a73836ca82a
UI[2]=C:\SIOC\OCP4NGX.exe
UI[3]=OCP4NGX Driver has stopped working
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]=C:\SIOC\OCP4NGX.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\syswow64\USER32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.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\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[15]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[16]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[17]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[18]=C:\Windows\syswow64\NSI.dll
LoadedModule[19]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[20]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[21]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[22]=C:\Windows\system32\WSOCK32.dll
LoadedModule[23]=C:\Windows\system32\IMM32.DLL
LoadedModule[24]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[25]=C:\Windows\system32\uxtheme.dll
LoadedModule[26]=C:\Windows\system32\dwmapi.dll
LoadedModule[27]=C:\Windows\system32\ole32.dll
LoadedModule[28]=C:\Windows\system32\mswsock.dll
LoadedModule[29]=C:\Windows\System32\wshtcpip.dll
LoadedModule[30]=C:\Windows\syswow64\OLEAUT32.DLL
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=OCP4NGX Driver
AppPath=C:\SIOC\OCP4NGX.exe
--------------------------------------------
Regards
Rene
(Netherlands)
Had a crash tonight but this time it wasn't the msvcr100.dll
This is my data:
0. Opencockpits modules in use when crash occur
MCP, EFIS, COM, NAV, ADF, ATC
1. FSX version ( Accelleration or standard + SP2)
Microsoft Flight Simulator X Service Pack 2 10.0.61472.0
2. FSX Addons installed
EZdok Camera for Microsoft Flight Simulator X 1.17
FSiPanel 1.0.0.52
NaturalPoint USB Drivers x64 (TRACK-IR)
Navigraph FMS Data Manager 1.0.11.0603
NL2000V4_Installer 4.0.58
NL2000V4 latest scenery
NVIDIA Grafisch stuurprogramma 340.52
NVIDIA PhysX systeemsoftware 9.13.1220
OC4BA v2 version 2.0
Opencockpits SIOC software ver 5.0
PMDG 737 8900 NGX 1.00.3219
RAAS Professional by FS2Crew (UNLOCKED)
REX Essential Plus Overdrive (Upgrade) 3.7.2013.0715 (only used for graphics)
SceneryConfig Editor v1.1.2
TrackIR 5.2.0200
Ultimate Terrain X - Europe
VrInsight VRiSim version Rel.2014-07-17
VrInsight VRiSim/CDU-II version 1.0
VOXATC 6.20
Voices used with VOXATC
- Cepstral Callie 5.1.0
- Cepstral David 5.1.0
- Cepstral Diane 5.1.0
- Cepstral William 5.1.0
3. Installed OS version
WIN7 64bit (with the latest updates as of today's date).
4. MS redistributables versions installed
Microsoft Visual C++ 2005 Redistributable 8.0.61001
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.4148
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
5. Overclocking CPU (Yes, No)
Yes, 3,40GHz to 4,2OGHz
6. Type of GPU
NVIDIA Geforce GTX650 Ti BOOST
NVIDIA Geforce GT520
7. Type of CPU
INTEL I7-2600K, 3.40GHz, 8Mb Cache, LGA1155, 95W
8. Crash info from MS Event Viewer
See the three info files after question 10
9. Are you running ENB or any other Shader addon with FSX?
No
------------------------------------------------------------------------------------------------
Addition
10. Using an Anti Virus scanner
Not using a virusscanner on my flightsim PC
1. Event viewer Error
Faulting application name: OCP4NGX.exe, version: 0.0.0.0, time stamp: 0x53de8886
Faulting module name: OCP4NGX.exe, version: 0.0.0.0, time stamp: 0x53de8886
Exception code: 0xc0000417
Fault offset: 0x00013da6
Faulting process id: 0x968
Faulting application start time: 0x01cfc2222591db92
Faulting application path: C:\SIOC\OCP4NGX.exe
Faulting module path: C:\SIOC\OCP4NGX.exe
Report Id: 939f416b-2e19-11e4-936f-8c89a564afab
2. Event viewer information
Fault bucket , type 0
Event Name: BEX
Response: Not available
Cab Id: 0
Problem signature:
P1: OCP4NGX.exe
P2: 0.0.0.0
P3: 53de8886
P4: OCP4NGX.exe
P5: 0.0.0.0
P6: 53de8886
P7: 00013da6
P8: c0000417
P9: 00000000
P10:
Attached files:
These files may be available here:
C:\Users\lnxfsp\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_OCP4NGX.exe_588588f5ae40c4228917122fa6d331b335abf6b_0dce5512
Analysis symbol:
Rechecking for solution: 0
Report Id: 939f416b-2e19-11e4-936f-8c89a564afab
Report Status: 4
3. AppCrash_OCP4NGX.exe_588588f5ae40c4228917122fa6d331b335abf6b_0dce5512
Version=1
EventType=BEX
EventTime=130536384125605432
ReportType=2
Consent=1
ReportIdentifier=939f416c-2e19-11e4-936f-8c89a564afab
IntegratorReportIdentifier=939f416b-2e19-11e4-936f-8c89a564afab
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=OCP4NGX.exe
Sig[1].Name=Application Version
Sig[1].Value=0.0.0.0
Sig[2].Name=Application Timestamp
Sig[2].Value=53de8886
Sig[3].Name=Fault Module Name
Sig[3].Value=OCP4NGX.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=53de8886
Sig[6].Name=Exception Offset
Sig[6].Value=00013da6
Sig[7].Name=Exception Code
Sig[7].Value=c0000417
Sig[8].Name=Exception Data
Sig[8].Value=00000000
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1043
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=f16d
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=f16d3ba2d05eee5c0e7bf740bf8bac45
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=8e9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=8e9eb445ede580c6ba9d3a73836ca82a
UI[2]=C:\SIOC\OCP4NGX.exe
UI[3]=OCP4NGX Driver has stopped working
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]=C:\SIOC\OCP4NGX.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\syswow64\USER32.dll
LoadedModule[5]=C:\Windows\syswow64\GDI32.dll
LoadedModule[6]=C:\Windows\syswow64\LPK.dll
LoadedModule[7]=C:\Windows\syswow64\USP10.dll
LoadedModule[8]=C:\Windows\syswow64\msvcrt.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\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[15]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[16]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[17]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[18]=C:\Windows\syswow64\NSI.dll
LoadedModule[19]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[20]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[21]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[22]=C:\Windows\system32\WSOCK32.dll
LoadedModule[23]=C:\Windows\system32\IMM32.DLL
LoadedModule[24]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[25]=C:\Windows\system32\uxtheme.dll
LoadedModule[26]=C:\Windows\system32\dwmapi.dll
LoadedModule[27]=C:\Windows\system32\ole32.dll
LoadedModule[28]=C:\Windows\system32\mswsock.dll
LoadedModule[29]=C:\Windows\System32\wshtcpip.dll
LoadedModule[30]=C:\Windows\syswow64\OLEAUT32.DLL
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=OCP4NGX Driver
AppPath=C:\SIOC\OCP4NGX.exe
--------------------------------------------
Regards
Rene
(Netherlands)
Re: OC4BA v2 Crash Info needed
Hi Roar,
New script, OPC4NGX_PP_V1.0.ssi seems to connect, however, only switches on EFIS and MCP work with NGX. Knobs are not responding and and MCP windows are off.
Regards,
syed
New script, OPC4NGX_PP_V1.0.ssi seems to connect, however, only switches on EFIS and MCP work with NGX. Knobs are not responding and and MCP windows are off.
Regards,
syed
- Attachments
-
- with
- oc4bappv1.JPG (177.8 KiB) Viewed 3591 times
Re: OC4BA v2 Crash Info needed
Did you push In the CO on MCP to turn on data transmission from OCP4NGX?Hi Roar,
New script, OPC4NGX_PP_V1.0.ssi seems to connect, however, only switches on EFIS and MCP work with NGX. Knobs are not responding and and MCP windows are off.