P3D V 3.1 CTD Kernelbase every flight

[PhilH 15]

Thank you very much Jim for your detailed explanation.

 

I don't own any FTX/Orbx products for now, and do not own any AI traffic program at all, as I generally do not really care about AI traffic. I pretty much always fly with all traffic sliders set to 0%.

 

I've only had the ai_player.dll crash one time so far, but it was over the middle of the Pacific, not near SFO, and I had only been flying farther and farther away from SFO before I got the crash (it crashed after about 5 hours of flight).

 

I was just thinking of uninstalling SFO + GSX because they were the only things installed on my system that could possibly cause the ai_player.dll crash, I thought, but now that I think harder, I also have a copy of UK2000 EGLL installed, and I remember that during the install, it said something about AFCADS. I wasn't anywhere near EGLL when I got the crash last night, but it's worth a try I suppose, in the worst case I'll just reinstall it.

 

Since I have so little scenery addons (KSFO HD, UK2000 EGLL, GSX), I guess I might just uninstall them all and see if I still get the ai_player.dll error. Maybe it has nothing to do with them either.

 

I'll check my Scenery.CFG, I have not even looked at it yet. Maybe I can also rename that file and let P3D generate a new one. That would of course disable all my addon scenery I suppose. I'll look into it.

[PhilH 15]

UPDATE:

I re ran the exact same flight as last time, but got a CTD blaming api.dll now. I think that:

-The Kernelbase.dll crash seems to be fixed. It was probably my corrupter NVIDIA install

-I am now getting CTD's for some reason, but a different DLL is being blamed each time... so it'll be hard to find the exact cause??

 

NOTE: The Avsim CTD guide says that "api.dll" crash means that I might be close to running out of memory. I am unable to confirm, as I have FSUIPC disabled (because I disabled all addons) so I wasn't monitoring VAS. However, I highly doubt that this was the case.. I have flown between many high detailed airports in P3D and never ran out of memory, so I don't think a flight over the Pacific should result in an OOM.

 

AppCrashViewer:

 

 

Version=1
EventType=APPCRASH
EventTime=130967600583208237
ReportType=2
Consent=1
UploadTime=130967600584080433
ReportIdentifier=fb7edf66-b649-11e5-9c96-902b34da2abb
IntegratorReportIdentifier=f00813e1-30d4-4292-bcf2-51aa23153fb0
WOW64=1
NsAppName=Prepar3D.exe
Response.BucketId=ea33fb8cd21ce4d68957e8647fb64ea7
Response.BucketTable=1
Response.LegacyBucketId=107827610678
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.1.2.15831
Sig[2].Name=Application Timestamp
Sig[2].Value=5672b60a
Sig[3].Name=Fault Module Name
Sig[3].Value=api.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=3.1.2.15831
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=5672b6b9
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00125f91
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.10586.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=bdcb
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=bdcb33e65a9843796b7ec31cc25bda3b
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=7ae5
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=7ae5ff970d16e403baf57c3408d06e56
UI[2]=C:\Lockheed Martin\Prepar3D v3\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]=C:\Lockheed Martin\Prepar3D v3\Prepar3D.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\system32\apphelp.dll
LoadedModule[5]=C:\WINDOWS\SYSTEM32\USER32.dll
LoadedModule[6]=C:\WINDOWS\SYSTEM32\GDI32.dll
LoadedModule[7]=C:\WINDOWS\SYSTEM32\ole32.dll
LoadedModule[8]=C:\WINDOWS\SYSTEM32\combase.dll
LoadedModule[9]=C:\WINDOWS\SYSTEM32\msvcrt.dll
LoadedModule[10]=C:\WINDOWS\SYSTEM32\RPCRT4.dll
LoadedModule[11]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[12]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[13]=C:\WINDOWS\SYSTEM32\bcryptPrimitives.dll
LoadedModule[14]=C:\WINDOWS\SYSTEM32\sechost.dll
LoadedModule[15]=C:\Lockheed Martin\Prepar3D v3\api.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\MSVCP120.dll
LoadedModule[17]=C:\WINDOWS\SYSTEM32\MSVCR120.dll
LoadedModule[18]=C:\WINDOWS\SYSTEM32\IMM32.dll
LoadedModule[19]=C:\WINDOWS\SYSTEM32\Cabinet.dll
LoadedModule[20]=C:\WINDOWS\SYSTEM32\WS2_32.dll
LoadedModule[21]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll
LoadedModule[22]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll
LoadedModule[23]=C:\WINDOWS\SYSTEM32\SHELL32.dll
LoadedModule[24]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll
LoadedModule[25]=C:\WINDOWS\SYSTEM32\WINHTTP.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[27]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10586.0_none_811bc0006c44242b\COMCTL32.dll
LoadedModule[28]=C:\WINDOWS\SYSTEM32\shlwapi.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\shcore.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\powrprof.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\profapi.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\CRYPT32.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\MSASN1.dll
LoadedModule[38]=C:\Lockheed Martin\Prepar3D v3\acontain.dll
LoadedModule[39]=C:\Lockheed Martin\Prepar3D v3\ai_player.dll
LoadedModule[40]=C:\Lockheed Martin\Prepar3D v3\atc.dll
LoadedModule[41]=C:\Lockheed Martin\Prepar3D v3\demo.dll
LoadedModule[42]=C:\Lockheed Martin\Prepar3D v3\facilities.dll
LoadedModule[43]=C:\Lockheed Martin\Prepar3D v3\controls.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\SETUPAPI.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\OLEAUT32.dll
LoadedModule[46]=C:\Lockheed Martin\Prepar3D v3\fe.dll
LoadedModule[47]=C:\Lockheed Martin\Prepar3D v3\flight.dll
LoadedModule[48]=C:\Lockheed Martin\Prepar3D v3\fs-traffic.dll
LoadedModule[49]=C:\Lockheed Martin\Prepar3D v3\g2d.dll
LoadedModule[50]=C:\Lockheed Martin\Prepar3D v3\gps.dll
LoadedModule[51]=C:\Lockheed Martin\Prepar3D v3\g3d.dll
LoadedModule[52]=C:\WINDOWS\SYSTEM32\WLDAP32.dll
LoadedModule[53]=C:\Lockheed Martin\Prepar3D v3\livingwater.dll
LoadedModule[54]=C:\Lockheed Martin\Prepar3D v3\main.dll
LoadedModule[55]=C:\Lockheed Martin\Prepar3D v3\menus.dll
LoadedModule[56]=C:\Lockheed Martin\Prepar3D v3\multiplayer.dll
LoadedModule[57]=C:\WINDOWS\SYSTEM32\COMDLG32.dll
LoadedModule[58]=C:\WINDOWS\SYSTEM32\FirewallAPI.dll
LoadedModule[59]=C:\WINDOWS\SYSTEM32\NETAPI32.dll
LoadedModule[60]=C:\Lockheed Martin\Prepar3D v3\pdk.dll
LoadedModule[61]=C:\Lockheed Martin\Prepar3D v3\panels.dll
LoadedModule[62]=C:\Lockheed Martin\Prepar3D v3\sim1.dll
LoadedModule[63]=C:\Lockheed Martin\Prepar3D v3\simscheduler.dll
LoadedModule[64]=C:\Lockheed Martin\Prepar3D v3\simprop.dll
LoadedModule[65]=C:\Lockheed Martin\Prepar3D v3\sound.dll
LoadedModule[66]=C:\Lockheed Martin\Prepar3D v3\symmap.dll
LoadedModule[67]=C:\Lockheed Martin\Prepar3D v3\terrain.dll
LoadedModule[68]=C:\Lockheed Martin\Prepar3D v3\util.dll
LoadedModule[69]=C:\Lockheed Martin\Prepar3D v3\visualfx.dll
LoadedModule[70]=C:\Lockheed Martin\Prepar3D v3\weather.dll
LoadedModule[71]=C:\Lockheed Martin\Prepar3D v3\window.dll
LoadedModule[72]=C:\WINDOWS\SYSTEM32\HID.DLL
LoadedModule[73]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[74]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[75]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[76]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[77]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_43.dll
LoadedModule[78]=C:\WINDOWS\SYSTEM32\OPENGL32.dll
LoadedModule[79]=C:\WINDOWS\SYSTEM32\GLU32.dll
LoadedModule[80]=C:\WINDOWS\SYSTEM32\d3dx9_43.dll
LoadedModule[81]=C:\WINDOWS\SYSTEM32\d3dx11_43.dll
LoadedModule[82]=C:\WINDOWS\SYSTEM32\DSOUND.dll
LoadedModule[83]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[84]=C:\Lockheed Martin\Prepar3D v3\audiere.dll
LoadedModule[85]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[86]=C:\WINDOWS\SYSTEM32\DDRAW.dll
LoadedModule[87]=C:\WINDOWS\SYSTEM32\DAVHLPR.DLL
LoadedModule[88]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll
LoadedModule[89]=C:\WINDOWS\SYSTEM32\fwbase.dll
LoadedModule[90]=C:\Lockheed Martin\Prepar3D v3\language.dll
LoadedModule[91]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[92]=C:\WINDOWS\SYSTEM32\MSXML6.DLL
LoadedModule[93]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[94]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[95]=C:\Lockheed Martin\Prepar3D v3\uiInterface.dll
LoadedModule[96]=C:\WINDOWS\SYSTEM32\mscoree.dll
LoadedModule[97]=C:\Lockheed Martin\Prepar3D v3\DIS.dll
LoadedModule[98]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[99]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[100]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[101]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\7861e52ba2d943b167d29bdb87ff9d05\mscorlib.ni.dll
LoadedModule[102]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[103]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\8c1bf096dad3b4896e2f1919c481e2d4\System.ni.dll
LoadedModule[104]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\fa75df10aab62382ffc6abc09eb3d8b9\System.Core.ni.dll
LoadedModule[105]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\WindowsBase\a375de75e262fc768f9f3177f5f136bf\WindowsBase.ni.dll
LoadedModule[106]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[107]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[108]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[109]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationCore\58468fc69f2ff97425eb461808aea208\PresentationCore.ni.dll
LoadedModule[110]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\3ceb2fae7344952c25574f287b4138b8\PresentationFramework.ni.dll
LoadedModule[111]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xaml\c0ce748e93a379e53fe79b4d61302fe6\System.Xaml.ni.dll
LoadedModule[112]=C:\WINDOWS\SYSTEM32\dwrite.dll
LoadedModule[113]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[114]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[115]=C:\WINDOWS\SYSTEM32\iphlpapi.dll
LoadedModule[116]=C:\WINDOWS\SYSTEM32\NSI.dll
LoadedModule[117]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[118]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
LoadedModule[119]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[120]=C:\WINDOWS\SYSTEM32\NETUTILS.DLL
LoadedModule[121]=C:\WINDOWS\SYSTEM32\wkscli.dll
LoadedModule[122]=C:\WINDOWS\SYSTEM32\srvcli.dll
LoadedModule[123]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[124]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[125]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[126]=C:\Windows\System32\rasadhlp.dll
LoadedModule[127]=C:\WINDOWS\SYSTEM32\MSCTF.dll
LoadedModule[128]=C:\WINDOWS\SYSTEM32\nvwgf2um.dll
LoadedModule[129]=C:\WINDOWS\system32\nvspcap.dll
LoadedModule[130]=C:\WINDOWS\SYSTEM32\PSAPI.DLL
LoadedModule[131]=C:\WINDOWS\system32\nvapi.dll
LoadedModule[132]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL
LoadedModule[133]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[134]=C:\WINDOWS\SYSTEM32\clbcatq.dll
LoadedModule[135]=C:\Program Files (x86)\Dropbox\Client\DropboxExt.28.dll
LoadedModule[136]=C:\WINDOWS\system32\ntshrui.dll
LoadedModule[137]=C:\WINDOWS\SYSTEM32\cscapi.dll
LoadedModule[138]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_d3c2e4e965da4528\comctl32.dll
LoadedModule[139]=C:\WINDOWS\SYSTEM32\coml2.dll
LoadedModule[140]=C:\WINDOWS\SYSTEM32\LINKINFO.dll
LoadedModule[141]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[142]=C:\WINDOWS\System32\DEVOBJ.dll
LoadedModule[143]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[144]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[145]=C:\Lockheed Martin\Prepar3D v3\Gauges\TargetInfo.dll
LoadedModule[146]=C:\WINDOWS\SYSTEM32\wdmaud.drv
LoadedModule[147]=C:\WINDOWS\SYSTEM32\ksuser.dll
LoadedModule[148]=C:\WINDOWS\SYSTEM32\AVRT.dll
LoadedModule[149]=C:\WINDOWS\SYSTEM32\msacm32.drv
LoadedModule[150]=C:\WINDOWS\SYSTEM32\midimap.dll
LoadedModule[151]=C:\Lockheed Martin\Prepar3D v3\radar.dll
LoadedModule[152]=C:\Lockheed Martin\Prepar3D v3\D3DCOMPILER_47.dll
LoadedModule[153]=C:\Lockheed Martin\Prepar3D v3\Oculus.dll
LoadedModule[154]=C:\WINDOWS\SYSTEM32\dbghelp.dll
LoadedModule[155]=C:\Lockheed Martin\Prepar3D v3\ControllableCamera.dll
LoadedModule[156]=C:\Lockheed Martin\Prepar3D v3\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[157]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[158]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll
LoadedModule[159]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9193_none_d09188224426efcd\MSVCR80.dll
LoadedModule[160]=C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9193_none_d09188224426efcd\MSVCP80.dll
LoadedModule[161]=C:\Lockheed Martin\Prepar3D v3\RAASPRO\RAASPRO.dll
LoadedModule[162]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[163]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[164]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[165]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[166]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[167]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[168]=C:\WINDOWS\SYSTEM32\MSDART.DLL
LoadedModule[169]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[170]=C:\WINDOWS\SYSTEM32\DPAPI.dll
LoadedModule[171]=C:\Windows\SYSTEM32\comsvcs.dll
LoadedModule[172]=C:\Windows\SYSTEM32\msjetoledb40.dll
LoadedModule[173]=C:\Windows\SYSTEM32\msjter40.dll
LoadedModule[174]=C:\Windows\SYSTEM32\msjet40.dll
LoadedModule[175]=C:\Windows\SYSTEM32\MSJINT40.DLL
LoadedModule[176]=C:\Windows\SYSTEM32\mswstr10.dll
LoadedModule[177]=C:\Windows\SYSTEM32\mstext40.dll
LoadedModule[178]=C:\WINDOWS\SYSTEM32\mlang.dll
LoadedModule[179]=C:\WINDOWS\SYSTEM32\RAASAUDIO32.DLL
LoadedModule[180]=C:\WINDOWS\SYSTEM32\X3DAudio1_6.dll
LoadedModule[181]=C:\WINDOWS\SYSTEM32\xactengine3_4.dll
LoadedModule[182]=C:\WINDOWS\SYSTEM32\XAudio2_4.dll
LoadedModule[183]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatioaec034ca#\5ce46961217223418df9cd94802b5533\PresentationFramework.Aero2.ni.dll
LoadedModule[184]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[185]=C:\WINDOWS\SYSTEM32\nvd3dum.dll
LoadedModule[186]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\87769badf74f3d502479fc783e8ff03b\System.Configuration.ni.dll
LoadedModule[187]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\a5f3bb0e5a94ea3c1395d8ec54192a5d\System.Xml.ni.dll
LoadedModule[188]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationUI\a934b9199c44f153886c7aeee8e15505\PresentationUI.ni.dll
LoadedModule[189]=C:\Lockheed Martin\Prepar3D v3\SimDirector.dll
LoadedModule[190]=C:\Lockheed Martin\Prepar3D v3\BGLCompLib.dll
LoadedModule[191]=C:\Lockheed Martin\Prepar3D v3\simpropext.dll
LoadedModule[192]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\efe9d0badb47c80d05a57f5cbd4672a7\System.Drawing.ni.dll
LoadedModule[193]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\a713a31cc026bd369343b6338aa7c2fa\System.Windows.Forms.ni.dll
LoadedModule[194]=C:\WINDOWS\system32\wbem\wbemprox.dll
LoadedModule[195]=C:\WINDOWS\SYSTEM32\wbemcomn.dll
LoadedModule[196]=C:\WINDOWS\system32\wbem\wbemsvc.dll
LoadedModule[197]=C:\WINDOWS\system32\wbem\fastprox.dll
LoadedModule[198]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[199]=C:\WINDOWS\SYSTEM32\WindowsCodecsExt.dll
LoadedModule[200]=C:\WINDOWS\SYSTEM32\icm32.dll
LoadedModule[201]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Web\85f3cecb18d3b0da553e10a60d520495\System.Web.ni.dll
LoadedModule[202]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\webengine4.dll
LoadedModule[203]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\852c13f2650583ed98e9b9741dcd25af\UIAutomationTypes.ni.dll
LoadedModule[204]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll
LoadedModule[205]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[206]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[207]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[208]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[209]=C:\WINDOWS\system32\msctfui.dll
LoadedModule[210]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\8d4236c66f5f95dc31659c010f647c55\System.Runtime.Serialization.ni.dll
LoadedModule[211]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\ec3b40b905ca03ceef9942409dd2d51a\SMDiagnostics.ni.dll
LoadedModule[212]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\2b046a608fcad5c41cfef901117459b0\System.ServiceModel.Internals.ni.dll
LoadedModule[213]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.20_none_22adb5eaa762c7fa\gdiplus.dll
LoadedModule[214]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\UIAutomationProvider\50ba5238ccc747b6421a9e86f7067cb7\UIAutomationProvider.ni.dll
LoadedModule[215]=C:\Lockheed Martin\Prepar3D v3\Gauges\PMDG_777X.dll
LoadedModule[216]=C:\WINDOWS\SYSTEM32\WSOCK32.dll
LoadedModule[217]=C:\WINDOWS\SYSTEM32\XAudio2_7.dll
LoadedModule[218]=C:\Lockheed Martin\Prepar3D v3\Gauges\PMDG_777X_2.dll
LoadedModule[219]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[220]=C:\WINDOWS\SYSTEM32\OLEACC.dll
LoadedModule[221]=C:\WINDOWS\SYSTEM32\snmpapi.dll
LoadedModule[222]=C:\WINDOWS\SYSTEM32\WINTRUST.dll
LoadedModule[223]=C:\WINDOWS\system32\napinsp.dll
LoadedModule[224]=C:\WINDOWS\system32\pnrpnsp.dll
LoadedModule[225]=C:\WINDOWS\system32\NLAapi.dll
LoadedModule[226]=C:\WINDOWS\System32\winrnr.dll
LoadedModule[227]=C:\WINDOWS\System32\wshbth.dll
LoadedModule[228]=C:\WINDOWS\SYSTEM32\icmp.Dll
LoadedModule[229]=C:\Windows\SYSTEM32\ieframe.dll
LoadedModule[230]=C:\Windows\SYSTEM32\mshtml.dll
LoadedModule[231]=C:\WINDOWS\SYSTEM32\srpapi.dll
LoadedModule[232]=C:\Windows\System32\vaultcli.dll
LoadedModule[233]=C:\WINDOWS\SYSTEM32\Secur32.dll
LoadedModule[234]=C:\Windows\SYSTEM32\msjtes40.dll
LoadedModule[235]=C:\WINDOWS\SYSTEM32\VBAJET32.DLL
LoadedModule[236]=C:\WINDOWS\SYSTEM32\expsrv.dll
LoadedModule[237]=C:\Program Files (x86)\Common Files\System\ado\msadrh15.dll
LoadedModule[238]=C:\WINDOWS\SYSTEM32\efswrt.dll
LoadedModule[239]=C:\WINDOWS\SYSTEM32\edputil.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Prepar3D exe
AppPath=C:\Lockheed Martin\Prepar3D v3\Prepar3D.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=4006C8BD124F1E4F93B96289AD2AE031

 

 

[Jim Young 2,356]

Did you install anything using the EMT tool?  This tool is known to cause crashes.  The information in the AVSIM CTD Guide is based on a search of the Internet for API.dll crash.  It finds the problems and solutions posted on all of the flight simulation websites, not just AVSIM.  The API.dll is the thingy that makes P3D run.  You get the error and you are definitely running low on memory resources, either your virtual memory or virtual address space.  What's causes that to happen is high settings in both the P3D.cfg and the video card display settings.  There is no other cause for this type of crash.  You have a tweak or something running in your system that is eating up your memory and/or VAS.

 

Best regards,

[Jim Young 2,356]

I want to add that you can have a massive amount of fps even when you are running out of memory.  Your sim could be running smoothly.  These things do not have anything to do with P3D running out of memory.  When you run out of VAS, you run out of VAS and your sim can run smoothly at 50-60 fps with 400-500 MB's of VAS remaining.  When it runs out of VAS or extremely low (around 200-300 MB's), it will crash your sim.  I've had cases where my fps are very high then suddenly it hits a single digit (in a millisecond) and the sim will crash. Same goes with system memory/virtual memory (where I recommend System Managed Size instead of trying to set up your own settings).  I use to run out of memory when I set up my own virtual memory (page file) and, when I changed it to System Managed Size, the issues went away. 

 

Best regards,

[PhilH 15]

Hi Jim,

 

Thanks a lot for your replies. I have never used the EMT for anything, but thanks for the suggestion. I only got the api.dll crash once, and I wasn't monitoring available VAS using FSUIPC on that flight, so perhaps I did run out of memory. However, I usually monitor the VAS and I often still have 1.5 to 2GB left when the sim crashes.

 

Last night, I thought my save file (cruise over the Pacific) could be corrupted, as I was always loading the same file for my tests. So I decided to just start a new flight with the PMDG 777, take-off from KLAX and fly on a heading 070. I had re-enabled my addons as I had just reinstalled my sceneries and rebuilt the Scenery.cfg file. I thought my kernelbase.dll problem was fixed, and that I was just trying to fix the api.dll and ai_player.dll crash... but I was wrong.

 

When I checked on my PC this morning, it hadn't crashed! I had been flying on heading 070 for 7 hours, and P3D hadn't crashed. FSUIPC showed I still had 1.6GB of VAS left, the same as last night, so no problem there. I played with the views a bit, everything was fine and stable. I chose to leave P3D running a bit longer and returned to my computer 5 minutes later to find that the sim had crashed... and it reported a kernelbase.dll error. I am possibly back at square one.

 

It is odd that the sim would crash like that on it's own, over the Atlantic this time... Last night I flew several approaches just for fun and I got absolutely no issues.

 

The problem is so odd that I feel like something is probably corrupted. I won't be home tonight, but tomorrow I'll probably try to reinstall the whole sim again, and hope it fixes my issue. I am hoping my problem isn't in Windows, but rather in something that will get fixed by reinstalling Prepar3d.

 

I currently also use "System managed size" for the virtual memory, thanks for the tip though.

 

Thanks again for all your help and time!! I am really curious about this issue.. I can run the sim and throw anything at it for a couple of hours with no crashes; change airport, change time and weather, change aircraft, change view multiple times, etc. I can't even make it crash! But leave it flying for hours in a straight line and boom, it crashes after approximately 5-7 hours. Very weird.

[PhilH 15]

Well I re-disabled all my overclocks again and uninstalled every single flight sim addon on my system (except PFPX because it isn't really connected to P3D as far as I can tell). I ​also uninstalled P3D completely using the guide in the "P3D Tips and Tricks" forum.

 

I then reinstalled P3D v3.1 from scratch, and installed the PMDG 777 + 300ER expansion and FSUIPC to monitor VAS. That's all I have. No EZDok, no REX, no weather, no ReShade.

 

I used the default Prepar3d settings (no cfg tweaks), except that I unlocked framerate because the default 20fps was making me want to throw my computer away. I took off from KLAX on a heading of 070 with full fuel tanks in the PMDG 777-200LR and let it fly in a straight line for several hours to see if I would get a crash.

 

 

I got a crash as usual, after about 9 hours or so of flying in a straight line. Once again, with about the same VAS remaining as when I left the PC. 1.8GB of VAS left, and MSI Afterburner (program I use to monitor CPU/GPU temps and usage) shows nothing of interest. This time, kernelbase.dll got blamed again. At this point, I guess the only possibilities are that there is something wrong with my Windows/User Profile/Drivers, or that I have faulty hardware. Considering the fact that I reinstalled Windows from scratch just last September, I am really not in the mood to reinstall again. So for now, I will just not fly long hauls, or fly some but using time-acceleration. Personally I don't like time-acceleration but I prefer that to not flying at all. Or perhaps I'll register FSUIPC so I can get an autosave function.

 

Thanks to all of you who took their time to try and help me, and I hope this thread will be useful to others facing similar issues one day. I really do appreciate all the time you spent trying to help me.

 

It's too bad that in the past 2 weeks I have spent as much money on P3D addons (which are currently all uninstalled by the way) as I would usually spend in a year, just because I really got in the mood of flying again, but I haven't been able to complete a single long-haul flight without having crash.

 

I give up. I'll come back when I feel like going through another Windows reinstall again.

[carlito777 712]

Maybe a faulty RAM module? I would download a RAM test and see if that gives you a hint on what is going on...

[PhilH 15]

Thanks for the suggestion, but I ran Memtest86 for 14h last week and got 0 errors. I'm currently running "Driver verifier", as I have always had problems with the USB ports on my motherboard (it's a known issue...Z77X-UD3H) so maybe I have a driver for something that's screwing it up. I don't know

[PhilH 15]

Well, here's something a little odd. You're probably going to ask, "Why didn't I tell you this before?" And the reason is simply because I thought it was unrelated.

 

 

For the past couple of months, I have been getting a random BSOD (I use BlueScreenViewer) on the first boot of the day. Basically, if the computer hasn't been running for a certain amount of time, I am almost certain to have a BSOD on the next boot. The computer then restarts and never crashes again (until the next "cold" boot). I have really been struggling to solve this, I did Memtest86 runs, I tested my power supply, I disabled all overclocks... Nothing ever worked. All the BSOD had a different error code, but using BlueScreenViewer they all pointed to some kind of kernel file, most often "ntoskrnl.exe"

 

I decided to run the "Windows Driver Verifier" today, according to a guide I found online, which is a built in program that stress tests selected drivers on your PC. When you get a BSOD, you can then analyze it to see what driver crashed the system.

 

Well guess what, my PC crashed instantly to a BSOD as soon as I enabled the verifier. And it was pointing to 2 files: "ntoskrnl.dll" and "chdrvr03.sys", which is the "CH root device" for my CH Products yoke. After a bit of online research, I figured that this file is installed with the "CH Control Manager", which hasn't been updated in years, but is not required for the yoke. I decided to uninstall the control manager and rerun the Driver Verifier, and I got no BSOD. I tried to reinstall a fresh version of the CH control manager, and after reactivating the Driver Verifier, I got a BSOD once again pointing to the same files.

 

The CH Control Manager doesn't seem to be causing problems to others on Windows 10, generally, but I already know that my motherboard is known for it's USB issues... So I'm thinking, and hoping, that uninstalling the CH Control Manager software has cured my daily cold boot BSOD. And considering the BSOD was pointing to kernel files, and that my P3D crashes due to kernelbase.dll.... I'm hoping I've fixed it.

 

 

Honestly it would make no sense at all. Why would my PC only crash on cold boot due to this CH driver? As far as I can tell, the driver isn't just loaded once a day?! And also, why would the driver suddenly crash P3D after hours of stability? It makes 0 sense.

 

Even though it sounds stupid, I've still got hope and I will try flying in a straight line again tonight. Maybe, just maybe the issue was caused by this old CH driver.sys file.

 

If that's the case, I'll use my yoke without the CH software. I was only using the program to map a couple of my buttons to some PMDG keyboard shortcuts. I'll gladly pay to register FSUIPC and use it instead (I believe it has the function of mapping keys to joystick buttons) if the problem is solved.

 

If anyone wants to tell me my idea makes no sense and it is impossible that it will have cured the CTD, go ahead, because I agree with you.

[carlito777 712]

Getting crashes after 9 hours of flight is weird, too. ;-) So maybe there is a weird explanation for it. I hope you found the solution or are at least getting closer. Keeping fingers crossed...

[PhilH 15]

Thanks Carlo. I'll do my "flight in a straight line" overnight and post the results tomorrow afternoon most likely.

[PhilH 15]

Well, change of plan. I didn't set up my flight last night... I shutdown the computer instead and waited for about 2 hours before starting it, to see if my "BSOD on first cold boot every few hours" problem was solved as expected. It was not! On boot, I got a new BSOD I had never seen before: "PFN_LIST_CORRUPT". Although all of my BSODS on boot have always been different, I noticed they all point to the same address, which is ntoskrnl.dll+142760.

 

Here's my problem. All of my research online points to memory. Everyone says I either have a driver that's corrupting memory, or my RAM is bad. I did add 8GB of RAM in last August, (my BSODS started in October), but I've tried memtest86 for HOURS and it never finds anything wrong. I've tried chkdsk, SFC /scannow, and they both say everything is fine. Yet the first boot of the day almost always crashes with a random BSOD but pointing to ntoskrnl.dll+142760, or sometimes but very rarely hal.dll.

 

I honestly thought I had fixed it yesterday with the CH thing, because "Driver Verifier" used to crash instantly (reference the CH driver), but I am now able to run the "Driver Verifier" fine with no crashes.

 

With all the BSOD's I'm getting, people online seem to always say: "It's memory or drivers. Run Driver Verifier and Memtest". But I've done both now and nothing is wrong!

 

Since I have only run Memtest using both sticks at the same time though, I have decided to remove one of them and run it on a single stick for about 24 hours. I'll then try the other stick, as I can't remember which one is the new one, and the BSODs started a few months after adding it. It is worth noting that when I added the RAM in august, I also added an SSD and completely reinstalled Windows onto it. 

 

I'll see if Memtest finds an error on my sticks individually, and even if it doesn't, I feel like trying a flight with only one stick... Maybe the faulty RAM is not being detected by Memtest. Anyway, I'll see what happens.

[Jim Young 2,356]

Are you sure you have a licensed version of P3Dv3.1?  If you do have a licensed version of 3.1, please uninstall it immediately and then reinstall it.  I would recommend installing the full 3.1 version. 
 
A BSOD indicates a major hardware issue.  If your computer is overclocked, return your overclock to the optimized default settings.  If not overclocked, then you have something seriously wrong with one of your components.  You need to download and run BlueScreenView and provide us with the Bug Check Code and String - http://www.nirsoft.net/utils/blue_screen_view.html. This will tell you what's wrong.
 
Best regards,

[PhilH 15]

Hi Jim,

 

Yes of course I do have a licensed version of P3Dv3.1. I uninstalled it completely and reinstalled just yesterday. The BSOD I am talking about never happens when I am using P3D, it only happens on boot, on the first boot of the day. I know it is a major problem, I have been trying to fix it for months. It has nothing to do with P3D, although since my P3D CTD is always referencing the kernel, I am hoping that fixing my boot BSDO will fix my P3D problem.

Everything is currently running at stock clocks. I have been having the BSODs on boot like this since October, which is about 2 months after I bought an SSD and extra RAM, and completely reinstalled Windows.

 

The BSOD is almost certainly caused by faulty RAM, but Memtest86 hasn't found anything...

 

I have always been using BlueScreenView, I can give you the bug check code if you like, but it is very often different. I'll have access to my main PC later today. The only thing I have found all the BSOD's to have in common is the address, which is always ntoskrnl.dll+142760.

 

I will try to run my PC for a few days with just 8GB of RAM, like I did before my reinstall last August. Hopefully, the problems go away.

[Jim Young 2,356]

 

 

es of course I do have a licensed version of P3Dv3.1. I uninstalled it completely and reinstalled just yesterday.

 

Okay, thanks for that.  That was a good idea to reinstall as something probably got messed up in the registry or with permissions.  Hopefully you reinstalled the full package and not just one of those client.msi's. 

 

If you run BlueScreenView and provide your BugString(s) (most likely IRQL_NOT_LESS_OR_EQUAL) and BugStringCode, then that will tell you whether it is a driver for a piece of hardware or a faulty SSD/HHD or other piece of hardware.  The error ntoskrnl.dll is certainly memory related but not an indicator your system memory is at fault.  This is a common error.  You ran driver verifier and that puts stress on your drivers to make your computer crash and you say you got no BSOD so it must not be your drivers.  It could be faulty RAM and I doubt MemTest86 will detect this as just one stick of RAM could run your system.  The only way to test is to pull out a SIMM RAM module one at a time, restart your computer and see if this fixes the problem.  If not, then you will have to pull out the next piece of RAM and try again until the BSOD's go away.  If they continue even after checking all of your RAM, then the problem is elsewhere and probably in your BIOS. 

 

A too high or too low CPU or RAM voltage setting in your BIOS will cause this problem.  This is why you should reset your BIOS to the optimized defaults.