January 12, 201610 yr Author Hi Jim, Yes I did reinstall the full P3D package. The BIOS has also been reset to the optimized defaults since a few days. I just got back home, and Memtest has been running on a single stick for 16 hours with no crash. I will test the other stick tonight probably, but even with both sticks, it had given me no errors in 14 hours. Who knows. The bugchecks are mostly MEMORY_MANAGEMENT. I also had a couple of IRQL_NOT_LESS_OR_EQUAL, and SYSTEM_THREAD_EXCEPTION_NOT_HANDLED, but they almost always all point to ntoskrnl.exe (sorry, it's .exe not .dll, my mistake) +142760. I have been trying to search what exactly those bugcheck codes mean for a long time, you don't have to bother searching for me. I am currenly running the system on one stick. The BSOD is kind of hard to reproduce, so I'll have to wait a couple of days. Also, I might try a flight, just in case the entire CTD thing is caused by a faulty stick. Thanks, Phil Philippe Hewett"It's not a bug, it's an undocumented feature."
January 13, 201610 yr Author Fresh install, PMDG777 only installed, same old CTD. Even with just one stick of RAM. I'll continue with just one stick, to see if I still get the BSODs at boot or if that, at least, is fixed. But whatever, even if it is fixed, still got the crash in P3D after about 6.5-7 hours... I am really out of ideas now. <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-01-13T11:30:56.740222600Z" /> <EventRecordID>8339</EventRecordID> <Channel>Application</Channel> <Computer>Phil-PC</Computer> <Security /> </System> - <EventData> <Data>Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0020001, exception address 740DD8A8 Stack:</Data> </EventData> </Event> ****** - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-01-13T11:30:56.887843200Z" /> <EventRecordID>8340</EventRecordID> <Channel>Application</Channel> <Computer>Phil-PC</Computer> <Security /> </System> - <EventData> <Data>Prepar3D.exe</Data> <Data>3.1.2.15831</Data> <Data>5672b60a</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.10586.0</Data> <Data>5632da1c</Data> <Data>c0020001</Data> <Data>000bd8a8</Data> <Data>1790</Data> <Data>01d14dbb1128f9e4</Data> <Data>C:\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data> <Data>C:\WINDOWS\SYSTEM32\KERNELBASE.dll</Data> <Data>6d49b005-6531-47c8-bc0b-e40bb747b5d9</Data> <Data /> <Data /> </EventData> </Event> I had plenty of VAS remaining, of course. They only thing I'm starting to notice is that the crash always seems to occur after 6-7 hours of flying. I've never timed it, but it has not crashed after 4 hours, and has never been able to fly for 9-10+. Odd. Philippe Hewett"It's not a bug, it's an undocumented feature."
January 14, 201610 yr Author Here's an.. update? I re-ran driver verifier but with different settings, and it found a bad driver from "Net Balancer" which is something I installed last September, on the 6th... exactly the same date my daily BSOD started! I uninstalled it immediately. I haven't turned off the computer long enough yet to have my daily BSOD trigger, so I do not know if it is fixed, but I still got a crash in PMDG 777 straight line flight last night... so even if my "cold boot BSOD" problem is fixed, I still get the same .NET runtime error. I got it after 9 hours into the flight this time. Here's the crash again, but it's the same as usual.. Version=1 EventType=APPCRASH EventTime=130972623061155098 ReportType=2 Consent=1 UploadTime=130972623062175613 ReportIdentifier=5e7a430c-badb-11e5-9cb0-902b34da2abb IntegratorReportIdentifier=51db173f-c8a7-4d44-9d18-8ec7e60fc686 WOW64=1 NsAppName=Prepar3D.exe Response.BucketId=bdfa56aef1659a6f73d5d933787aef79 Response.BucketTable=1 Response.LegacyBucketId=107835700227 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=KERNELBASE.dll Sig[4].Name=Fault Module Version Sig[4].Value=10.0.10586.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=5632da1c Sig[6].Name=Exception Code Sig[6].Value=c0020001 Sig[7].Name=Exception Offset Sig[7].Value=000bd8a8 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=8516 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=8516a80090f3cbb9702f0fefaa0d7ffd DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=16c8 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=16c8e00e03104d164b865103ad38cb78 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\MSWSOCK.dll LoadedModule[19]=C:\WINDOWS\SYSTEM32\IMM32.dll LoadedModule[20]=C:\WINDOWS\SYSTEM32\Cabinet.dll LoadedModule[21]=C:\WINDOWS\SYSTEM32\WS2_32.dll LoadedModule[22]=C:\WINDOWS\SYSTEM32\ADVAPI32.dll LoadedModule[23]=C:\WINDOWS\SYSTEM32\WINHTTP.dll LoadedModule[24]=C:\WINDOWS\SYSTEM32\SHELL32.dll LoadedModule[25]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.10586.0_none_811bc0006c44242b\COMCTL32.dll LoadedModule[26]=C:\WINDOWS\SYSTEM32\cfgmgr32.dll LoadedModule[27]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[28]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[29]=C:\WINDOWS\SYSTEM32\windows.storage.dll LoadedModule[30]=C:\WINDOWS\SYSTEM32\shlwapi.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\WINMMBASE.dll LoadedModule[35]=C:\WINDOWS\SYSTEM32\profapi.dll LoadedModule[36]=C:\WINDOWS\SYSTEM32\CRYPT32.dll LoadedModule[37]=C:\WINDOWS\SYSTEM32\MSASN1.dll LoadedModule[38]=C:\Lockheed Martin\Prepar3D v3\ai_player.dll LoadedModule[39]=C:\Lockheed Martin\Prepar3D v3\acontain.dll LoadedModule[40]=C:\Lockheed Martin\Prepar3D v3\atc.dll LoadedModule[41]=C:\Lockheed Martin\Prepar3D v3\controls.dll LoadedModule[42]=C:\Lockheed Martin\Prepar3D v3\demo.dll LoadedModule[43]=C:\Lockheed Martin\Prepar3D v3\facilities.dll LoadedModule[44]=C:\WINDOWS\SYSTEM32\SETUPAPI.dll LoadedModule[45]=C:\Lockheed Martin\Prepar3D v3\fe.dll LoadedModule[46]=C:\WINDOWS\SYSTEM32\OLEAUT32.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\g3d.dll LoadedModule[51]=C:\Lockheed Martin\Prepar3D v3\gps.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:\WINDOWS\SYSTEM32\COMDLG32.dll LoadedModule[57]=C:\Lockheed Martin\Prepar3D v3\multiplayer.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\d3d9.dll LoadedModule[75]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[76]=C:\Lockheed Martin\Prepar3D v3\dxgi.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:\Lockheed Martin\Prepar3D v3\audiere.dll LoadedModule[84]=C:\WINDOWS\SYSTEM32\MSACM32.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\dxgi.dll LoadedModule[92]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[93]=C:\WINDOWS\SYSTEM32\MSXML6.DLL LoadedModule[94]=C:\WINDOWS\SYSTEM32\ntmarta.dll LoadedModule[95]=C:\WINDOWS\SYSTEM32\PROPSYS.dll LoadedModule[96]=C:\Lockheed Martin\Prepar3D v3\uiInterface.dll LoadedModule[97]=C:\WINDOWS\SYSTEM32\mscoree.dll LoadedModule[98]=C:\Lockheed Martin\Prepar3D v3\DIS.dll LoadedModule[99]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll LoadedModule[100]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll LoadedModule[101]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll LoadedModule[102]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\7861e52ba2d943b167d29bdb87ff9d05\mscorlib.ni.dll LoadedModule[103]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll LoadedModule[104]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\8c1bf096dad3b4896e2f1919c481e2d4\System.ni.dll LoadedModule[105]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\fa75df10aab62382ffc6abc09eb3d8b9\System.Core.ni.dll LoadedModule[106]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\WindowsBase\a375de75e262fc768f9f3177f5f136bf\WindowsBase.ni.dll LoadedModule[107]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[108]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[109]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[110]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationCore\58468fc69f2ff97425eb461808aea208\PresentationCore.ni.dll LoadedModule[111]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\3ceb2fae7344952c25574f287b4138b8\PresentationFramework.ni.dll LoadedModule[112]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xaml\c0ce748e93a379e53fe79b4d61302fe6\System.Xaml.ni.dll LoadedModule[113]=C:\WINDOWS\SYSTEM32\dwrite.dll LoadedModule[114]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll LoadedModule[115]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll LoadedModule[116]=C:\WINDOWS\SYSTEM32\iphlpapi.dll LoadedModule[117]=C:\WINDOWS\SYSTEM32\NSI.dll LoadedModule[118]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL LoadedModule[119]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL LoadedModule[120]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll LoadedModule[121]=C:\WINDOWS\SYSTEM32\NETUTILS.DLL LoadedModule[122]=C:\WINDOWS\SYSTEM32\wkscli.dll LoadedModule[123]=C:\WINDOWS\SYSTEM32\srvcli.dll LoadedModule[124]=C:\WINDOWS\SYSTEM32\DNSAPI.dll LoadedModule[125]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll LoadedModule[126]=C:\WINDOWS\System32\fwpuclnt.dll LoadedModule[127]=C:\Windows\System32\rasadhlp.dll LoadedModule[128]=C:\WINDOWS\SYSTEM32\MSCTF.dll LoadedModule[129]=C:\WINDOWS\SYSTEM32\nvwgf2um.dll LoadedModule[130]=C:\WINDOWS\system32\nvspcap.dll LoadedModule[131]=C:\WINDOWS\SYSTEM32\PSAPI.DLL LoadedModule[132]=C:\WINDOWS\system32\nvapi.dll LoadedModule[133]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL LoadedModule[134]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[135]=C:\WINDOWS\SYSTEM32\clbcatq.dll LoadedModule[136]=C:\Program Files (x86)\Dropbox\Client\DropboxExt.28.dll LoadedModule[137]=C:\WINDOWS\system32\ntshrui.dll LoadedModule[138]=C:\WINDOWS\SYSTEM32\cscapi.dll LoadedModule[139]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.10586.0_none_d3c2e4e965da4528\comctl32.dll LoadedModule[140]=C:\WINDOWS\SYSTEM32\coml2.dll LoadedModule[141]=C:\WINDOWS\SYSTEM32\LINKINFO.dll LoadedModule[142]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[143]=C:\WINDOWS\System32\DEVOBJ.dll LoadedModule[144]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[145]=C:\WINDOWS\SYSTEM32\wintypes.dll LoadedModule[146]=C:\Lockheed Martin\Prepar3D v3\Gauges\TargetInfo.dll LoadedModule[147]=C:\WINDOWS\SYSTEM32\wdmaud.drv LoadedModule[148]=C:\WINDOWS\SYSTEM32\ksuser.dll LoadedModule[149]=C:\WINDOWS\SYSTEM32\AVRT.dll LoadedModule[150]=C:\WINDOWS\SYSTEM32\msacm32.drv LoadedModule[151]=C:\WINDOWS\SYSTEM32\midimap.dll LoadedModule[152]=C:\Lockheed Martin\Prepar3D v3\radar.dll LoadedModule[153]=C:\Lockheed Martin\Prepar3D v3\D3DCOMPILER_47.dll LoadedModule[154]=C:\Lockheed Martin\Prepar3D v3\Oculus.dll LoadedModule[155]=C:\WINDOWS\SYSTEM32\dbghelp.dll LoadedModule[156]=C:\Lockheed Martin\Prepar3D v3\ControllableCamera.dll LoadedModule[157]=C:\Lockheed Martin\Prepar3D v3\bglmanx.dll LoadedModule[158]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.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:\WINDOWS\SYSTEM32\SHFOLDER.dll LoadedModule[162]=C:\Lockheed Martin\Prepar3D v3\PMDG\DLLs\PMDG_Interface.dll LoadedModule[163]=C:\Lockheed Martin\Prepar3D v3\RAASPRO\RAASPRO.dll LoadedModule[164]=C:\WINDOWS\SYSTEM32\WININET.dll LoadedModule[165]=C:\WINDOWS\SYSTEM32\iertutil.dll LoadedModule[166]=C:\WINDOWS\SYSTEM32\WINNSI.DLL LoadedModule[167]=C:\WINDOWS\SYSTEM32\urlmon.dll LoadedModule[168]=C:\WINDOWS\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[169]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll LoadedModule[170]=C:\WINDOWS\SYSTEM32\MSDART.DLL LoadedModule[171]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll LoadedModule[172]=C:\WINDOWS\SYSTEM32\DPAPI.dll LoadedModule[173]=C:\Windows\SYSTEM32\comsvcs.dll LoadedModule[174]=C:\Windows\SYSTEM32\msjetoledb40.dll LoadedModule[175]=C:\Windows\SYSTEM32\msjet40.dll LoadedModule[176]=C:\Windows\SYSTEM32\msjter40.dll LoadedModule[177]=C:\Windows\SYSTEM32\MSJINT40.DLL LoadedModule[178]=C:\Windows\SYSTEM32\mswstr10.dll LoadedModule[179]=C:\Windows\SYSTEM32\mstext40.dll LoadedModule[180]=C:\WINDOWS\SYSTEM32\mlang.dll LoadedModule[181]=C:\WINDOWS\SYSTEM32\RAASAUDIO32.DLL LoadedModule[182]=C:\WINDOWS\SYSTEM32\X3DAudio1_6.dll LoadedModule[183]=C:\WINDOWS\SYSTEM32\xactengine3_4.dll LoadedModule[184]=C:\WINDOWS\SYSTEM32\XAudio2_4.dll LoadedModule[185]=C:\Lockheed Martin\Prepar3D v3\Modules\FSUIPC4.dll LoadedModule[186]=C:\WINDOWS\SYSTEM32\DINPUT8.dll LoadedModule[187]=C:\Lockheed Martin\Prepar3D v3\Modules\SimConnectP3D2.dll LoadedModule[188]=C:\WINDOWS\SYSTEM32\MSVCP100.dll LoadedModule[189]=C:\WINDOWS\SYSTEM32\MSVCR100.dll LoadedModule[190]=C:\Lockheed Martin\Prepar3D v3\as_srv\as_btstrp.dll LoadedModule[191]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatioaec034ca#\5ce46961217223418df9cd94802b5533\PresentationFramework.Aero2.ni.dll LoadedModule[192]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll LoadedModule[193]=C:\WINDOWS\SYSTEM32\nvd3dum.dll LoadedModule[194]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\87769badf74f3d502479fc783e8ff03b\System.Configuration.ni.dll LoadedModule[195]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\a5f3bb0e5a94ea3c1395d8ec54192a5d\System.Xml.ni.dll LoadedModule[196]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationUI\a934b9199c44f153886c7aeee8e15505\PresentationUI.ni.dll LoadedModule[197]=C:\Lockheed Martin\Prepar3D v3\SimDirector.dll LoadedModule[198]=C:\Lockheed Martin\Prepar3D v3\simpropext.dll LoadedModule[199]=C:\Lockheed Martin\Prepar3D v3\BGLCompLib.dll LoadedModule[200]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\efe9d0badb47c80d05a57f5cbd4672a7\System.Drawing.ni.dll LoadedModule[201]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\a713a31cc026bd369343b6338aa7c2fa\System.Windows.Forms.ni.dll LoadedModule[202]=C:\WINDOWS\system32\wbem\wbemprox.dll LoadedModule[203]=C:\WINDOWS\SYSTEM32\wbemcomn.dll LoadedModule[204]=C:\WINDOWS\system32\wbem\wbemsvc.dll LoadedModule[205]=C:\WINDOWS\system32\wbem\fastprox.dll LoadedModule[206]=C:\WINDOWS\SYSTEM32\mscms.dll LoadedModule[207]=C:\WINDOWS\SYSTEM32\WindowsCodecsExt.dll LoadedModule[208]=C:\WINDOWS\SYSTEM32\icm32.dll LoadedModule[209]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Web\85f3cecb18d3b0da553e10a60d520495\System.Web.ni.dll LoadedModule[210]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\webengine4.dll LoadedModule[211]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\852c13f2650583ed98e9b9741dcd25af\UIAutomationTypes.ni.dll LoadedModule[212]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll LoadedModule[213]=C:\WINDOWS\SYSTEM32\sxs.dll LoadedModule[214]=C:\WINDOWS\system32\dataexchange.dll LoadedModule[215]=C:\WINDOWS\system32\dcomp.dll LoadedModule[216]=C:\WINDOWS\system32\twinapi.appcore.dll LoadedModule[217]=C:\WINDOWS\system32\msctfui.dll LoadedModule[218]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\8d4236c66f5f95dc31659c010f647c55\System.Runtime.Serialization.ni.dll LoadedModule[219]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\ec3b40b905ca03ceef9942409dd2d51a\SMDiagnostics.ni.dll LoadedModule[220]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\2b046a608fcad5c41cfef901117459b0\System.ServiceModel.Internals.ni.dll LoadedModule[221]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.10586.20_none_22adb5eaa762c7fa\gdiplus.dll LoadedModule[222]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\UIAutomationProvider\50ba5238ccc747b6421a9e86f7067cb7\UIAutomationProvider.ni.dll LoadedModule[223]=C:\Program Files (x86)\EZCA\ezcacontrol.dll LoadedModule[224]=C:\Lockheed Martin\Prepar3D v3\Gauges\PMDG_777X.dll LoadedModule[225]=C:\WINDOWS\SYSTEM32\WSOCK32.dll LoadedModule[226]=C:\WINDOWS\SYSTEM32\XAudio2_7.dll LoadedModule[227]=C:\Lockheed Martin\Prepar3D v3\Gauges\PMDG_777X_2.dll LoadedModule[228]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV LoadedModule[229]=C:\WINDOWS\SYSTEM32\OLEACC.dll LoadedModule[230]=C:\WINDOWS\SYSTEM32\snmpapi.dll LoadedModule[231]=C:\WINDOWS\system32\napinsp.dll LoadedModule[232]=C:\WINDOWS\SYSTEM32\WINTRUST.dll LoadedModule[233]=C:\WINDOWS\system32\pnrpnsp.dll LoadedModule[234]=C:\WINDOWS\system32\NLAapi.dll LoadedModule[235]=C:\WINDOWS\System32\winrnr.dll LoadedModule[236]=C:\WINDOWS\System32\wshbth.dll LoadedModule[237]=C:\WINDOWS\SYSTEM32\icmp.Dll LoadedModule[238]=C:\Windows\SYSTEM32\ieframe.dll LoadedModule[239]=C:\Windows\SYSTEM32\mshtml.dll LoadedModule[240]=C:\WINDOWS\SYSTEM32\srpapi.dll LoadedModule[241]=C:\Windows\System32\vaultcli.dll LoadedModule[242]=C:\WINDOWS\SYSTEM32\Secur32.dll LoadedModule[243]=C:\Windows\SYSTEM32\msjtes40.dll LoadedModule[244]=C:\WINDOWS\SYSTEM32\VBAJET32.DLL LoadedModule[245]=C:\WINDOWS\SYSTEM32\expsrv.dll LoadedModule[246]=C:\Program Files (x86)\Common Files\System\ado\msadrh15.dll LoadedModule[247]=C:\WINDOWS\SYSTEM32\efswrt.dll LoadedModule[248]=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 So strange that it works fine when I *try* to make it crash by loading a ton of different aircraft, changing the airport, use all my addons at the same time, etc... But try to fly in a straight line? Crash after 7-9 hours for no apparent reason. If I use time acceleration, I am able to fly long-hauls, if it helps anyone to debug my issue. It just seems like after a certain amount of time, the sim crashes. I know I could just use acceleration, but I hate knowing something is wrong. Also, I never like time acceleration anyway so I'd much rather have it working stable. Philippe Hewett"It's not a bug, it's an undocumented feature."
January 14, 201610 yr With all that weird stuff happening, I would definitely do a clean reinstall of the OS. All that time you invested to find the needle in the haystack, you could have easily reinstalled the OS. And don't install this kind of bloatware. A sim PC should be as clean as it can be. [email protected] ∣ Asus ROG Strix B650E-E ∣ 64Gb@6000MT ∣ NVidia 5090 FE
January 14, 201610 yr Author Yeah, I'll probably end up doing that but I'll wait a couple of weeks when I get more time off work, I don't want to get into it now. As for the bloatware, I try to avoid it, but I have a yet to figure out a way to limit my bandwidth.. I'm the only one in the house with a wired connection, and whenever I download a file from Chrome, no one else can use the internet connection. Chrome takes all the bandwidth. Anyway, that'a minor issue compared to the main one I'm tackling. There are a couple of people on the official P3D forums (on their website) who are getting the exact same crashes as me, midflight with the 777 or the 737 (I only have the 777). Obviously if more people were getting the crash, PMDG would have made a comment (and there would be more people complaining), but I'll keep monitoring the forums on the P3D website, just in case someone manages to find what triggers the crash. Thanks for your suggestion, the reinstall is definitely coming up. Philippe Hewett"It's not a bug, it's an undocumented feature."
January 16, 201610 yr Author ****UPDATE**** Well here is a very interesting "plot twist"... The CTD has happened on every single long haul flight with the PMDG777, but I just discovered that it only happens with that particular aircraft. Last night, I flew my Majestic Q400 for about 1.5 hours on a flight north of Montreal aiport, and that is with ALL of my addons reinstalled and running (EZDok, Reshade, ActiveSky, GSX, airport sceneries, etc). I then proceeded to change aircraft (without quitting the sim) and choose an aircraft I knew had an autopilot: the default Mooney. I took off, set the autopilot, and went to bed. This morning it was still flying, and I let it run while at work. So basically, I flew from the north of Quebec all the way down to Brazil, with the default Mooney (unlimited fuel of course, for testing), and I got no crash. The flight took 23.9 hours in real time, with Active Sky weather in 4K textures running all day. I landed the aircraft at a random airport in Brazil a few minutes ago. It was quite fun, actually! I finished with 1.7GB of VAS left, which is also very nice after having the sim running for over 26 hours total with no crash. Don't forget I actually flew a 1.5 hour full flight with the Q400 before, without quitting.. I did everything I could to make it crash. And it didn't. Considering this is an issue I know only have with the PMDG 777, I will not reinstall Windows for now. It appears there are many threads both here and on the P3D Forums of people getting another .dll crash with the PMDG 777. I am not getting the same crash, but perhaps when a solution is discovered for the other crash people are getting, my problem will also be fixed. I am not considering this issue solved, but I am very pleased to know that I was able to fly a "long-haul" flight sim session with no crash. For now, I will try to use the PMDG777's autocruise feature, even though I am not a fan of it, I will be able to fly long-hauls at least!! Thank you very much for all your assistance, perhaps next time I have a problem, I will test with a default aircraft earlier in the process. I'll update my progress with getting the PMDG 777 issue fixed in this thread. Philippe Hewett"It's not a bug, it's an undocumented feature."
January 21, 201610 yr Author I have tested, and my workaround works and proves a few things. I was finally able, for the first time in 10-15 attempts, to complete KSFO-NZAA without CTD. Solution? Enable PMDG-777 autocruise and set to 4x or more. My CTD appears to happen after 6-9 hours of sim real-time. I flew my flight overnight again, but turned on autocruise just before bed. I have never liked using time compression but it is the only way of preventing a CTD for me. When I woke up, the sim was paused 10nm before TOD as it should be. I decided to leave it running all day, and 12 hours later it was still paused before TOD. I saved the flight, just in case, and unpaused - flew the approach and quit. I am happy to have a working way of flying longhauls. Hopefully, knowing that the CTD only happens with the PMDG aircraft, and knowing it only happens after X amount of real time, will help someone/P3D or PMDG developers find a real solution. Thanks! Philippe Hewett"It's not a bug, it's an undocumented feature."
January 21, 201610 yr Just FYI you can prevent the crash from occurring by just not enlarging the left PFD on the 777 or NGX. This type of random crash only occurs on PMDG aircraft and nobody from either company can reproduce the issue to find the cause. There is a 30 page thread on the Prepar3d forum about this issue. There was the same thread on the PMDG General Forum but niether PMDG nor LM are responding to either post. Most people get the MSCVR120.dll crash but I've had no error reports, atc.dll, and various others. Sean Green
January 21, 201610 yr How come just a few have this problem and thousands of others do not? Whenever you use EMT or manually jerry rig a product not designed for a simulator, you are going to have problems. I have not jerry rigged a product into P3D (other than the Carenado Phenom 300 which is compatible with P3D3) or used the garbage I call the "EMT". There are hundred and hundreds of computer experts in our community and they have not found a solution for this mscvr120.dll crash that happens to just a few individuals. Probably because they have no idea what you jerry rigged into P3D or your settings or your BIOS settings, etc., etc. Microsoft Visuals are used by developers (i.e., LM, Microsoft, Carenado, Orbx, REX, etc., etc.), to make sure your product is installed properly as intended by the developer. Then they use a Microsoft.net to make sure that program runs properly, including memory management. FSX uses Microsoft.net 2.0 and Microsoft Visual C++ 2005 w/SP1 (not Microsoft.net 4.0 or Microsoft Visual 2012 or 2013 but the 2005 version because they are not backward compatible). Many older products still use Microsoft Visual 2008 and Microsoft.net 3.0 and 3.5 because the developer has not updated his/her product. I can uninstall Microsoft Visual 2005 and FSX won't even start up. So, when you jerry rig a product or use EMT, you are violating their installation instructions of that product and you will most likely get a Microsoft Visual error. So please do not blame LM or PMDG. LM built their product to work with a certain Microsoft Visual and Microsoft.net. There are some products that they have found compatible with P3D and one of them is the PMDG 777 and the PMDG 737. All you need to do is throw a wrench into an installation by installing untested or not compatible products into P3D (and just because EMT allows the installation does not mean it is compatible). The products you are installing using EMT or jerry rigging, are obviously not compatible with P3D and P3D is doing the proper thing by crashing your sim with the Microsoft Visual error. If you have this problem, recommend you completely reinstall Windows and then P3D/PMDG and stay away from jerry rigging or the EMT until the developer of the product can make it totally compatible with his/her own installer. It just takes one incompatible product to throw a wrench into an otherwise perfect installation. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
January 21, 201610 yr Although I agree with Jim that EMT is the proverbial spanner in the works, I don't understand why it is anything worse than a "buyer beware" app. It isn't any more of a violation of software legal rights than FSX2XP and there are tons of posts here about that utility.
January 21, 201610 yr I hope I did not indicate it is illegal (even though I might think that). It is used a lot my members here and many have no problems with the utility. I'm just saying that using it might cause problems running P3D, FSX, FSX-SE, and X-Plane. Not all of the time and it won't happen to everyone but all it takes is a nasty CTD and it seems like everyone then blames LM or FSX for the problem and, for some reason, not seeing that maybe one of their legacy programs may be the issue. I can assure you I have no problems running P3Dv3.1 with my GEP3D/UTX/PMDG/FSDT/FlightBeam/ASN/REX/I-Fly/Orbx/FTX products (to name a few) and I didn't need EMT to get them to work. Blizzard coming into the Wash DC area so I expect to be enjoying all of my products extensively for the next week or two! :smile: (I may work on the CTD Guide too...) Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
January 21, 201610 yr Just FYI I do not have EMT installed nor use it. I don't know where you get the idea I am using this product. I have a clean, purchased install of Windows 10 (from Amazon) which I can show you the recipet for if need be! I have a purchased PMDG 777 and 737 for P3D which can be verified, if need be Ill send you those reciepts also. I only have FTX Global, UTX 2, ASN, and EZDOK camera. All these products are made to work with P3D if I'm not mistaken. I use FSDT KLAX and FSDT KJFK which last I checked are compatible. I have a brand new computer with updated BIOS from the mfg and I would not even know how to "jerry rig" a bios. I have all the up to date MB drivers. I have up to date Nvidia drivers from NVIDIA. The only software on this new build is P3D period. Oh I forgot maybe installing Chrome is corrupting my Windows. My goodness the nerve of these moderators! It's like a holier than thou attitude. If you happened to read the thread on the P3D forums even Dan Downs had the issue. I'm sure he is using EMT. Have a wonderful day. Sean Green
January 21, 201610 yr Author Ok, I am sorry but what on Earth are you talking about? You have already asked if I used EMT and I said no. I haven't used anything except the original installers designed for P3D. You ask, why do I have the problem and so many others do not? Here is the most probable answer... Because maybe not that many people fly 7+ hour flights in real time using the PMDG 777 + P3D V3 yet? There is a thread with over 30 pages on the Prepar3D official forums of people getting random crashes after hours in the PMDG products + P3D V3.. I am not alone having this issue, it's just that most people probably don't fly for 7+ hours in real time. Like I said, using time acceleration fixes the problem for me!! Some people however, get the random crash after only 30-60 minutes, so I am lucky to fly that long with no crash. People have completely reinstalled Windows multiple times and still get the crash. I have tried to make it crash. My last flight, I used all my addons and I even bought FS2Crew and had that running. The flight ran for 12 hours of sim time (with time acceleration) while running PMDG777, EZDok, ReShade, ActiveSky Next, FS2Crew, GSX, FlightBeam KSFO, most settings on max in P3D and also all my CPU/GPU overclocks enabled. I did not get the crash. It was my 15th attempt, and I can tell that the only difference is that I used time acceleration to reduce the amount of "real time" the sim was running. I still kept the sim running on pause for 12 hours though, without crashing. Finally, I have to say that this post here, posted by Mr. rsrandazzo himself, states that they might not be able to release the 747v2 for P3D at the same time as the FSX version, because of new bugs that P3Dv3 brought back... I am sure these crashes will eventually be fixed by a PMDG or a P3D patch, or someone with more programming experience will be able to tell what combination of hardware/software is causing the crash. More than one person has reinstalled Windows, then only installed P3Dv3 + PMDG 777 and still get the crash. Thanks for help, but I do not and have never used "EMT". Philippe Hewett"It's not a bug, it's an undocumented feature."
January 21, 201610 yr Just FYI I do not have EMT installed nor use it. I don't know where you get the idea I am using this product. I have a clean, purchased install of Windows 10 (from Amazon) which I can show you the recipet for if need be! I did not say you were using the EMT. I said EMT or jerry rig an installation. Why would you want to show me a receipt for Windows 10? Whenever you have problems, especially with Microsoft Visuals and Microsoft.net's, I recommend reinstalling Windows and then P3D and then your addons. Because maybe not that many people fly 7+ hour flights in real time using the PMDG 777 + P3D V3 yet? You are correct. Not too many members fly 7+ hours (you state "real time" but I read where you accelerate your sim 4X's or more). Plus seven hours in front of a computer is a long time. I personally keep my flights down to 2 hours or less. That's enough enjoyment for me! I hope you find your problems. IMHO, they are NOT with PMDG or LM though (even though Mr. Randazzo said they might not be able to release the 747v2 for P3D because of "new bugs". It is hard to believe he would make a statement like that to the public as I know he and his team are working with LM to resolve any issues). As stated in the AVSIM CTD Guide, "members might be interested in a utility in the AVSIM Library called Quantum Leap which allows you to speed up your trip across the US or any ocean but it requires the payware version of the FSUIPC utility. According to the developer, “this utility was written to allow an FSX aircraft established at cruise to "leap" to a point further along the flight plan track. It allows the user to select a nav fix or manually enter coordinates for the jump-ahead point, as well as setting a new time in the simulation to be set at the designated leap-ahead point. The primary objective was to leap forward on very long haul flights to eliminate long periods of droning or wrestling with accelerated flight. It was tested with the PMDG® 777 and 737NGX simulations, but will most likely work with most other add-ons.” He says it will work with P3D too. It was developed by one of our current moderators, Bob Scott. I think this utility must be neat in that it not only speeds up your simulation but it will accelerate the time to the correct time it would have taken if you flew to that waypoint. I haven't tried it yet but plan on doing it soon as I always have issues flying out of Chicago or St Louis and landing at Wash Dulles in nasty weather. I need more practice but don't have the time to fly the whole route every time. I think running low on VAS or memory might be my issue as I have FlightBeam's KIAD HD and it is heavy on resources. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant 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
January 21, 201610 yr Blizzard coming into the Wash DC area so I expect to be enjoying all of my products extensively for the next week or two! Bundle up. It's supposed to completely miss us up here in the Hudson Valley. We have had one measurable snowfall since last March and it was only an inch worth. The snow is apparently attracted to the mid-Atlantic region for some reason.
Archived
This topic is now archived and is closed to further replies.