Jump to content
Sign in to follow this  
CathayA340

P3D v2.5 Fatal Error

Recommended Posts

Hi, 

I recently just switched from FSX to P3D v2.5 and i have gotten some fatal errors.

There is no faulting module and it is unknown, it just says the applicatin- here is the AppCrahhView report:

Version=1

EventType=APPCRASH

EventTime=130692218838866769

ReportType=2

Consent=1

ReportIdentifier=ac6fcdf9-bbd4-11e4-a658-448a5b876aaf

IntegratorReportIdentifier=ac6fcdf8-bbd4-11e4-a658-448a5b876aaf

WOW64=1

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=Prepar3D.exe

Sig[1].Name=Application Version

Sig[1].Value=2.5.12942.0

Sig[2].Name=Application Timestamp

Sig[2].Value=54d24d6d

Sig[3].Name=Fault Module Name

Sig[3].Value=StackHash_0a9e

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 Code

Sig[6].Value=c0000005

Sig[7].Name=Exception Offset

Sig[7].Value=ffb30016

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.1

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Name=Additional Information 1

DynamicSig[22].Value=0a9e

DynamicSig[23].Name=Additional Information 2

DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789

DynamicSig[24].Name=Additional Information 3

DynamicSig[24].Value=0a9e

DynamicSig[25].Name=Additional Information 4

DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789

UI[2]=D:\Prepar3D v2\Prepar3D.exe

UI[3]=Prepar3D exe 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]=D:\Prepar3D v2\Prepar3D.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\syswow64\ole32.dll

LoadedModule[15]=D:\Prepar3D v2\api.dll

LoadedModule[16]=C:\Windows\system32\Cabinet.dll

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

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

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

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

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

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

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

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

LoadedModule[25]=D:\Prepar3D v2\IP2Lib32.DLL

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

LoadedModule[27]=C:\Windows\syswow64\comdlg32.dll

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

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

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

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

LoadedModule[32]=C:\Windows\system32\oledlg.dll

LoadedModule[33]=C:\Windows\system32\WSOCK32.dll

LoadedModule[34]=D:\Prepar3D v2\acontain.dll

LoadedModule[35]=D:\Prepar3D v2\ai_player.dll

LoadedModule[36]=D:\Prepar3D v2\atc.dll

LoadedModule[37]=D:\Prepar3D v2\demo.dll

LoadedModule[38]=D:\Prepar3D v2\controls.dll

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

LoadedModule[40]=D:\Prepar3D v2\flight.dll

LoadedModule[41]=D:\Prepar3D v2\facilities.dll

LoadedModule[42]=D:\Prepar3D v2\fe.dll

LoadedModule[43]=C:\Windows\system32\USERENV.dll

LoadedModule[44]=C:\Windows\system32\profapi.dll

LoadedModule[45]=D:\Prepar3D v2\main.dll

LoadedModule[46]=D:\Prepar3D v2\fs-traffic.dll

LoadedModule[47]=D:\Prepar3D v2\g3d.dll

LoadedModule[48]=C:\Windows\system32\d3dx9_43.dll

LoadedModule[49]=D:\Prepar3D v2\g2d.dll

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

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

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

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

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

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

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

LoadedModule[57]=C:\Windows\system32\OPENGL32.dll

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

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

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

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

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

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

LoadedModule[64]=D:\Prepar3D v2\PDK.dll

LoadedModule[65]=C:\Windows\system32\MSVCR100.dll

LoadedModule[66]=C:\Windows\system32\MSVCP100.dll

LoadedModule[67]=D:\Prepar3D v2\simscheduler.dll

LoadedModule[68]=D:\Prepar3D v2\simprop.dll

LoadedModule[69]=D:\Prepar3D v2\util.dll

LoadedModule[70]=C:\Windows\system32\d3dx10_43.dll

LoadedModule[71]=D:\Prepar3D v2\weather.dll

LoadedModule[72]=D:\Prepar3D v2\sim1.dll

LoadedModule[73]=D:\Prepar3D v2\multiplayer.dll

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

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

LoadedModule[76]=D:\Prepar3D v2\panels.dll

LoadedModule[77]=D:\Prepar3D v2\sound.dll

LoadedModule[78]=D:\Prepar3D v2\window.dll

LoadedModule[79]=D:\Prepar3D v2\terrain.dll

LoadedModule[80]=D:\Prepar3D v2\visualfx.dll

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

LoadedModule[82]=D:\Prepar3D v2\livingwater.dll

LoadedModule[83]=D:\Prepar3D v2\gps.dll

LoadedModule[84]=D:\Prepar3D v2\symmap.dll

LoadedModule[85]=D:\Prepar3D v2\menus.dll

LoadedModule[86]=D:\Prepar3D v2\language.dll

LoadedModule[87]=C:\Windows\system32\uxtheme.dll

LoadedModule[88]=C:\Program Files (x86)\TeamViewer\tv_w32.dll

LoadedModule[89]=D:\Prepar3D v2\uiInterface.dll

LoadedModule[90]=C:\Windows\SYSTEM32\MSCOREE.DLL

LoadedModule[91]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll

LoadedModule[92]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll

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

LoadedModule[94]=C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\ce5f61c5754789df97be8dc991c47d07\mscorlib.ni.dll

LoadedModule[95]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll

LoadedModule[96]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System\17a393b77ae757f0768501fb95ff5af6\System.ni.dll

LoadedModule[97]=C:\Windows\assembly\NativeImages_v4.0.30319_32\WindowsBase\94bbd298ec8575f3c6151a59538a109c\WindowsBase.ni.dll

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

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

LoadedModule[100]=C:\Windows\assembly\NativeImages_v4.0.30319_32\PresentationCore\006d28e7c86f3e70db90ce06ea2f33fb\PresentationCore.ni.dll

LoadedModule[101]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\3646375313dd2b8e3afecbf945960336\PresentationFramework.ni.dll

LoadedModule[102]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xaml\8b133e0d94535a7534719f70873ca7fe\System.Xaml.ni.dll

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

LoadedModule[104]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll

LoadedModule[105]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll

LoadedModule[106]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll

LoadedModule[107]=C:\Windows\system32\PROPSYS.dll

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

LoadedModule[109]=C:\Windows\system32\MSXML6.DLL

LoadedModule[110]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Core\691c1ad89d16f49d80e84fa06a79089a\System.Core.ni.dll

LoadedModule[111]=C:\Windows\assembly\NativeImages_v4.0.30319_32\Presentatio1c9175f8#\7971f3a1c08c4043cf981f457855b4d4\PresentationFramework.Aero.ni.dll

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

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

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

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

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

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

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

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

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

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

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

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

LoadedModule[124]=C:\Windows\syswow64\PSAPI.DLL

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

LoadedModule[126]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Drawing\b4c08872c259018b17b2801da33ac80f\System.Drawing.ni.dll

LoadedModule[127]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\db563d596d76daed04e9b5d25b2f4cb9\System.Windows.Forms.ni.dll

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

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

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

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

LoadedModule[132]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Xml\7147fa233a070283dba824da40089bf1\System.Xml.ni.dll

LoadedModule[133]=C:\Windows\assembly\NativeImages_v4.0.30319_32\System.Configuration\0648dbecb7e3fb9523565107e04a5caf\System.Configuration.ni.dll

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

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

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

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

LoadedModule[138]=C:\Windows\system32\nvwgf2um.dll

LoadedModule[139]=C:\Windows\system32\bcrypt.dll

LoadedModule[140]=C:\Windows\system32\nvapi.dll

LoadedModule[141]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll

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

LoadedModule[143]=C:\Windows\system32\ntmarta.dll

LoadedModule[144]=C:\Windows\syswow64\WLDAP32.dll

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

LoadedModule[146]=C:\Windows\system32\ntshrui.dll

LoadedModule[147]=C:\Windows\system32\srvcli.dll

LoadedModule[148]=C:\Windows\system32\cscapi.dll

LoadedModule[149]=C:\Windows\system32\slc.dll

LoadedModule[150]=C:\Windows\system32\netutils.dll

LoadedModule[151]=C:\Windows\system32\mssprxy.dll

LoadedModule[152]=C:\Windows\System32\MMDevApi.dll

LoadedModule[153]=C:\Windows\system32\AUDIOSES.DLL

LoadedModule[154]=C:\Windows\system32\HID.DLL

LoadedModule[155]=C:\Windows\system32\XInput9_1_0.dll

LoadedModule[156]=D:\Prepar3D v2\Gauges\TargetInfo.dll

LoadedModule[157]=C:\Windows\system32\wdmaud.drv

LoadedModule[158]=C:\Windows\system32\ksuser.dll

LoadedModule[159]=C:\Windows\system32\AVRT.dll

LoadedModule[160]=C:\Windows\system32\msacm32.drv

LoadedModule[161]=C:\Windows\system32\midimap.dll

LoadedModule[162]=C:\Windows\System32\wship6.dll

LoadedModule[163]=C:\Windows\System32\wshtcpip.dll

LoadedModule[164]=D:\Prepar3D v2\radar.dll

LoadedModule[165]=D:\Prepar3D v2\bglmanx.dll

LoadedModule[166]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll

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

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

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

LoadedModule[170]=D:\Prepar3D v2\Modules\FSUIPC4.dll

LoadedModule[171]=C:\Windows\system32\IPHLPAPI.DLL

LoadedModule[172]=C:\Windows\system32\WINNSI.DLL

LoadedModule[173]=D:\Prepar3D v2\Modules\SimConnectP3D2.dll

LoadedModule[174]=C:\Windows\system32\DINPUT.DLL

LoadedModule[175]=D:\Prepar3D v2\Aerosoft\Flight Recorder\AS-FlightRecorder.dll

LoadedModule[176]=D:\Prepar3D v2\RAASPRO\RAASPRO.dll

LoadedModule[177]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll

LoadedModule[178]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll

LoadedModule[179]=C:\Windows\system32\MSDART.DLL

LoadedModule[180]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll

LoadedModule[181]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL

LoadedModule[182]=C:\Windows\system32\comsvcs.dll

LoadedModule[183]=C:\Windows\system32\ATL.DLL

LoadedModule[184]=C:\Windows\SysWOW64\bcryptprimitives.dll

LoadedModule[185]=C:\Windows\SysWOW64\msjetoledb40.dll

LoadedModule[186]=C:\Windows\SysWOW64\msjet40.dll

LoadedModule[187]=C:\Windows\SysWOW64\mswstr10.dll

LoadedModule[188]=C:\Windows\SysWOW64\msjter40.dll

LoadedModule[189]=C:\Windows\SysWOW64\MSJINT40.DLL

LoadedModule[190]=C:\Windows\SysWOW64\mstext40.dll

LoadedModule[191]=C:\Windows\system32\mlang.dll

LoadedModule[192]=C:\Windows\system32\RAASAUDIO32.DLL

LoadedModule[193]=C:\Windows\system32\X3DAudio1_6.dll

LoadedModule[194]=C:\Windows\SysWow64\xactengine3_4.dll

LoadedModule[195]=C:\Windows\SysWow64\XAudio2_4.dll

LoadedModule[196]=D:\Prepar3D v2\CMeteoXml.dll

LoadedModule[197]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll

LoadedModule[198]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll

LoadedModule[199]=D:\Prepar3D v2\PMDG\DLLs\PMDG_HUD_interface.dll

LoadedModule[200]=D:\Prepar3D v2\PMDG\DLLs\PMDGOptions.dll

LoadedModule[201]=D:\Prepar3D v2\PMDG_SimConnect_Ldr.dll

LoadedModule[202]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll

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

LoadedModule[204]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90ENU.DLL

LoadedModule[205]=D:\Prepar3D v2\PMDG\DLLs\PMDGEvents.dll

LoadedModule[206]=D:\Prepar3D v2\PMDG\DLLs\PMDGSounds.dll

LoadedModule[207]=D:\Prepar3D v2\WaveLib.dll

LoadedModule[208]=D:\Prepar3D v2\SimDirector.dll

LoadedModule[209]=D:\Prepar3D v2\simpropext.dll

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

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

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

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

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

LoadedModule[215]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\webengine4.dll

LoadedModule[216]=C:\Windows\system32\MSVCR120_CLR0400.dll

LoadedModule[217]=D:\Prepar3D v2\SlimDX.dll

LoadedModule[218]=C:\Windows\system32\Secur32.dll

LoadedModule[219]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll

LoadedModule[220]=C:\Windows\system32\sxs.dll

LoadedModule[221]=C:\Windows\SysWOW64\ieframe.dll

LoadedModule[222]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll

LoadedModule[223]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll

LoadedModule[224]=C:\Windows\SysWOW64\mshtml.dll

FriendlyEventName=Stopped working

ConsentKey=APPCRASH

AppName=Prepar3D exe

AppPath=D:\Prepar3D v2\Prepar3D.exe

 
My system is overclocked to 4.0GHZ from 3.4GHZ and I still havr FSX installed on my computer. Thank you.

Share this post


Link to post
Share on other sites

Sorry to hear you are having crashes.  Your crash was caused by a StackHash.  You can learn more about a StackHash in the AVSIM CTD Guide under the Probable fixes area.  There is no known fix for StackHash other than lowering your settings.

 

If you look in the P3D forum you will see I have run into some frustrations too with P3D running out of VAS but I'm getting the d3d11.dll crash which is related to DirectX.  I have found the only solution to CTD's in P3D and FSX is to set your settings to the default.  The default is what Lockheed Martin techs say are the best settings for your computer system.  In my case, I thought I had a very powerful system with the i7 4770K Haswell and GTX 780 video card but I do not.  Anything above the default settings may, repeat may, cause a crash.  What I find frustrating is the fact that when I install the PMDG 777 or FSDT scenery, they recommend higher settings than what P3D techs said was best for my system.  They therefore are pushing me toward a crash.  Why can't they make their products so they don't push me to higher settings and still have the eye-candy?  In PMDG's case, the PMDG looks awesome in default settings so I don't have to move my settings higher for that product.

 

So, my suggestion is to return your settings to the default and see if that fixes the problem.  It should.

 

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

 

 


I recently just switched from FSX to P3D v2.5 and i have gotten some fatal errors.

 

I had the same crash and error this morning after installing the P3Dv2.5 hotfix.  I had loaded a default aircraft and went to Flight Beam's Phoenix International and decided to see if the PMDG777 would load okay.  Got the Stackhash error when I tried that.  I don't think it was the PMDG but a problem with the P3D menu items.  I had fixed the problem with FSDT airports not showing up and no Addon Manager menu by reinstalling just one of my many FSDT and FlightBeam airports.  After restarting I got the Addon Manager menu back but the airport buildings were still not showing.  I simply opened up the Addon Manager and clicked on Couatl Products and selected Restart Couatl and the airports all showed up.

 

After the StackHash I had another item in the dll.xml that was not showing up on the P3D Menu - RAAS Pro this may have caused the Stackhash as when I clicked on the Menu to load another aircraft, the program was probably looking for RAAS Pro so as to tell me I'm close to Runway 34L.  I reinstalled RAAS Pro and so far no more StackHash errors.  PMDG 777 works great too as well as ASN.  So hope this explanation helps.  It definitely has something to do with the P3D hotfix.

 

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

 

 


So hope this explanation helps.  It definitely has something to do with the P3D hotfix.

 

It really does, thanks for the big help Jim! Hopefully LM will release a hotfix for this. I will try reinstalling some stuff and check the dll.xml, appreciate it!


Is this crash the "white screen" crash? Feeling quite annoyed :/

Not exactly sure of what you mean - when the sim crashes, the background turns white?

Share this post


Link to post
Share on other sites

There is a thread on the FSDT forums regarding this issue which infers an issue with the Addon Manager since the P3D 2.5 update.

Umberto cannot understand it at this point, but there is definitely a pattern, i.e. people uninstall GSX/Addon Manager and the error go away.

 

|Regards,

 

Daz

Share this post


Link to post
Share on other sites

Thanks for the tip, I will try that.

 

Jim - I set settings to default and no luck still, this time the sim crashed on the start up screen.

Share this post


Link to post
Share on other sites
Guest

Hi Jim,

 

Just to let you know, I haven't installed FSDT yet on my new setup and have NOT experienced this crash and I do use high graphics settings well above the defaults.

 

 


Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=2.5.12942.0

 

FYI, you're not running the latest "hot fix" from LM ... that would bring your P3D version to 2.5.12943.0.

 

Suggest you list your DLL.XML and EXE.XML to see what your loading.

 

To verify your OC is working without errors you can run RealBench ... free download here: http://rog.asus.com/file/?download=RealBench_v2.4.zip .

 

Cheers, Rob.

Share this post


Link to post
Share on other sites

 

 


FYI, you're not running the latest "hot fix" from LM ... that would bring your P3D version to 2.5.12943.0.

 

This is the forum post I was referring to:

http://www.fsdreamteam.com/forum/index.php/topic,11597.0.html

 

It is possible that the crash is due to a combination of P3D 2.5 (.12942 or .12943) and the updated Addon Manager.

 

I have disabled the Addon Manager in the dll.xml and the crashes no longer occur.

 

Regards,

 

Daz

Share this post


Link to post
Share on other sites

Thanks for all suggestions! I disable addon manager and couatl, and now my simulator works completely fine. 

I will now download the P3d hotfix and the updated addon manager, let's see how that goes. I'll also check RealBench out too, thanks!

 

dll.exe here :

 

<?xml version="1.0" encoding="windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

  <Descr>Launch</Descr>

  <Filename>dll.xml</Filename>

  <Disabled>False</Disabled>

  <Launch.ManualLoad>False</Launch.ManualLoad>

  <Launch.Addon>

    <Name>Addon Manager</Name>

    <Disabled>True</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>bglmanx.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>FSUIPC 4</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>Modules\FSUIPC4.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>Flight Recorder</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>RAASPRO</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

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

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>

  <Launch.Addon>

    <Name>VistaMare Core</Name>

    <Disabled>True</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>VistaMare\ViMaCoreX.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>CMeteoXml</Name>

    <Disabled>False</Disabled>

    <Path>.\CMeteoXml.dll</Path>

  </Launch.Addon>

</SimBase.Document>

 

exe.xml : 

 

<?xml version="1.0" encoding="windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

  <Descr>Launch</Descr>

  <Filename>exe.xml</Filename>

  <Disabled>False</Disabled>

  <Launch.ManualLoad>False</Launch.ManualLoad>

  <Launch.Addon>

    <Name>Couatl</Name>

    <Disabled>True</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>fsdreamteam\couatl\couatl.exe</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>EZdok camera addon</Name>

    <Disabled>false</Disabled>

    <Path>C:\Program Files (x86)\EZCA\EZCA_P3D.exe</Path>

  </Launch.Addon>

</SimBase.Document>

 

 

Share this post


Link to post
Share on other sites

 

 


To verify your OC is working without errors you can run RealBench

 

Thanks Rob.  I am not overclocked.  I think the OP is though.  Thanks for coming in here and trying to find a solution with me for the OP.  Now I'm having the same issues as the OP!!

 

 

 


It is possible that the crash is due to a combination of P3D 2.5 (.12942 or .12943) and the updated Addon Manager.

 

Thanks to you too Daz for your assistance.

 

I am still getting this error and I uninstalled the PMDG 777 and was going to reinstall it but the crashes still occur.  I disabled ASN to see if it might be the culprit and still got the StackHash. Next going to uninstall GSX (which has been working properly as I reported above).  I have several FSDT airports plus all of the FlightBeam stuff too.  It's a shame none of it will work in P3D until FSDT finds a solution.  Right now, P3D with the hotfix is the most unstable product on my computer.

 

As requested by Rob, here are my dll.xml -

 

 



Launch
dll.xml
False
False.manualload>

Addon Manager
False
False
bglmanx.dll.addon>


RAASPRO
False
.\RAASPRO\RAASPRO.dll
module_init
module_deinit.addon>


FSUIPC 4
False
Modules\FSUIPC4.dll.addon>.document>

 

 

and exe.dll files -

 

 



Launch
exe.xml
False
False.manualload>

Couatl
False
False
fsdreamteam\couatl\couatl.exe
--mode=prepar3dv2.addon>


as_btstrp_config_manager
False
as_srv\as_btstrp_config_manager.exe.addon>.document>

 

 

I cannot see what would cause the problem other than FSDT stuff and the Addon_Manager are looking for a previous version of P3D2.5, doesn't see it, and goes memory crazy (which is basically what a StackHash is). 


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
Guest

Daz,

 

Umberto is working on it ... so lets hope he can get it sorted out.  My only comments after reading his thread:

 

1.  VS debug session runs under a different security context

 

 

 

 Usually, when we need to support a new build of the sim, we need to change a few internal pointers to access directly in memory, that always (almost) change between builds.

 

2.  I'm not sure how Umberto is directly accessing memory, but if he is using ReadProcessMemory he'll need to make sure he has appropriate privileges.

 

I'm sure Umberto will come up with a solution, he always does.

 

Cheers, Rob.

Share this post


Link to post
Share on other sites

Daz,

 

Umberto is working on it ... so lets hope he can get it sorted out.  My only comments after reading his thread:

 

1.  VS debug session runs under a different security context

 

 

2.  I'm not sure how Umberto is directly accessing memory, but if he is using ReadProcessMemory he'll need to make sure he has appropriate privileges.

 

I'm sure Umberto will come up with a solution, he always does.

 

Cheers, Rob.

 

Rob,

 

Just tested Umberto's potential fix and all seems OK so far.

 

He recompiled to VC++ 2013 and provided a new dll etc.

 

Regards,

Daz

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  

  • 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.
×
×
  • Create New...