Jump to content

dwrite.dll crash with Qualitywings 787


LitMW

Recommended Posts

Hey Avsim,

It's been around 3 months now with this problem. I've submitted my problem to the QW 787 support forum 3 months ago, but i still didn't get an answer from anybody (i'm not the only one getting no answer, QW support is a joke)

So i decided to ask in the Avsim forum 😊

My problem is that i get a ctd. Sometimes after 1 minute in flight, sometimes after 30 minutes and so on...

everything is going normal but then suddenly my P3D V4 freezes. That freez occcurs for like 3 seconds and then the game continues for like 1 second. After the 1 second it crashes to desktop. It only happens with the QW 787. I own other aircraft from PMDG and other well known devs, and they all run very smooth, P3d did never crash with them (i'm using P3D about a year now)

What i've already tried so far:

-Complete reinstall of windows

-Updated all drivers

-Did a test flight with not a single addon but the 787

-Lowered graphics settings as much as possible

Here's some information:

Version=1
EventType=APPCRASH
EventTime=131799336449433820
ReportType=2
Consent=1
UploadTime=131799336476543424
ReportStatus=268435456
ReportIdentifier=3f90837e-699c-4f8b-88e6-f301a956bc38
IntegratorReportIdentifier=0d370093-68c6-4e27-8dc4-58032975851e
Wow64Host=34404
NsAppName=Prepar3D.exe
OriginalFilename=Prepar3D.exe
AppSessionGuid=00000d54-0001-004e-113c-1b5ac83ed401
TargetAppId=W:0000abbabf4c877ad6b145a2cc9b02b7c3cb00000904!0000d5fc0d7ce97f85830080d86c7b00cc081e7b7730!Prepar3D.exe
TargetAppVer=2018//06//21:23:18:59!2d5e49!Prepar3D.exe
BootId=4294967295
TargetAsId=689
UserImpactVector=858796848
IsFatal=1
Response.BucketId=23670da09cf5cd1f9f94048091273802
Response.BucketTable=4
Response.LegacyBucketId=2275448661966534658
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=4.3.29.25520
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=5b2c3263
Sig[3].Name=Fehlermodulname
Sig[3].Value=dwrite.dll
Sig[4].Name=Fehlermodulversion
Sig[4].Value=10.0.17134.1
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=6b20f7fc
Sig[6].Name=Ausnahmecode
Sig[6].Value=c0000005
Sig[7].Name=Ausnahmeoffset
Sig[7].Value=0000000000068c7d
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=10.0.17134.2.0.0.768.101
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=4177
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=41772c044badd8f962a804b8bd0cff09
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=30b2
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=30b2458675bfa35e99c02e537e76856e
UI[2]=C:\Prepar3D V4\Prepar3D.exe
LoadedModule[0]=C:\Prepar3D V4\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\win32u.dll
LoadedModule[7]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[8]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[9]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[10]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[11]=C:\WINDOWS\System32\ole32.dll
LoadedModule[12]=C:\WINDOWS\System32\combase.dll
LoadedModule[13]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[14]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[15]=C:\WINDOWS\System32\sechost.dll
LoadedModule[16]=C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll
LoadedModule[17]=C:\Prepar3D V4\api.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\MSWSOCK.dll
LoadedModule[22]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[23]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[24]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[25]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[26]=C:\WINDOWS\SYSTEM32\WINHTTP.dll
LoadedModule[27]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.17134.228_none_f95000f73097dead\COMCTL32.dll
LoadedModule[28]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[29]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[30]=C:\WINDOWS\System32\shcore.dll
LoadedModule[31]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[34]=C:\WINDOWS\System32\shlwapi.dll
LoadedModule[35]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[36]=C:\WINDOWS\System32\profapi.dll
LoadedModule[37]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[38]=C:\WINDOWS\System32\FLTLIB.DLL
LoadedModule[39]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[40]=C:\Prepar3D V4\acontain.dll
LoadedModule[41]=C:\Prepar3D V4\ai_player.dll
LoadedModule[42]=C:\Prepar3D V4\atc.dll
LoadedModule[43]=C:\Prepar3D V4\controls.dll
LoadedModule[44]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[45]=C:\Prepar3D V4\demo.dll
LoadedModule[46]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[47]=C:\Prepar3D V4\DIS.dll
LoadedModule[48]=C:\Prepar3D V4\facilities.dll
LoadedModule[49]=C:\Prepar3D V4\flight.dll
LoadedModule[50]=C:\Prepar3D V4\fe.dll
LoadedModule[51]=C:\Prepar3D V4\fs-traffic.dll
LoadedModule[52]=C:\Prepar3D V4\g3d.dll
LoadedModule[53]=C:\Prepar3D V4\gps.dll
LoadedModule[54]=C:\Prepar3D V4\livingwater.dll
LoadedModule[55]=C:\Prepar3D V4\main.dll
LoadedModule[56]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[57]=C:\Prepar3D V4\g2d.dll
LoadedModule[58]=C:\Prepar3D V4\menus.dll
LoadedModule[59]=C:\Prepar3D V4\multiplayer.dll
LoadedModule[60]=C:\WINDOWS\System32\WLDAP32.dll
LoadedModule[61]=C:\Prepar3D V4\pdk.dll
LoadedModule[62]=C:\Prepar3D V4\panels.dll
LoadedModule[63]=C:\Prepar3D V4\sim1.dll
LoadedModule[64]=C:\Prepar3D V4\simscheduler.dll
LoadedModule[65]=C:\Prepar3D V4\simprop.dll
LoadedModule[66]=C:\Prepar3D V4\sound.dll
LoadedModule[67]=C:\Prepar3D V4\symmap.dll
LoadedModule[68]=C:\Prepar3D V4\terrain.dll
LoadedModule[69]=C:\Prepar3D V4\util.dll
LoadedModule[70]=C:\Prepar3D V4\visualfx.dll
LoadedModule[71]=C:\Prepar3D V4\weather.dll
LoadedModule[72]=C:\Prepar3D V4\window.dll
LoadedModule[73]=C:\WINDOWS\SYSTEM32\MSVCP140.dll
LoadedModule[74]=C:\WINDOWS\SYSTEM32\CONCRT140.dll
LoadedModule[75]=C:\WINDOWS\SYSTEM32\HID.DLL
LoadedModule[76]=C:\WINDOWS\SYSTEM32\DINPUT8.dll
LoadedModule[77]=C:\Prepar3D V4\librti1516e.dll
LoadedModule[78]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[79]=C:\WINDOWS\SYSTEM32\MFReadWrite.dll
LoadedModule[80]=C:\WINDOWS\SYSTEM32\MFPlat.DLL
LoadedModule[81]=C:\Prepar3D V4\mplEasyBlendSDKDX1164.dll
LoadedModule[82]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[83]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[84]=C:\WINDOWS\SYSTEM32\OPENGL32.dll
LoadedModule[85]=C:\WINDOWS\SYSTEM32\GLU32.dll
LoadedModule[86]=C:\Prepar3D V4\D3DCOMPILER_47.dll
LoadedModule[87]=C:\WINDOWS\SYSTEM32\d3dx9_43.dll
LoadedModule[88]=C:\WINDOWS\SYSTEM32\DSOUND.dll
LoadedModule[89]=C:\Prepar3D V4\audiere.dll
LoadedModule[90]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[91]=C:\WINDOWS\SYSTEM32\MSIMG32.dll
LoadedModule[92]=C:\Prepar3D V4\libfedtime1516e.dll
LoadedModule[93]=C:\Prepar3D V4\OpenRTI.dll
LoadedModule[94]=C:\WINDOWS\SYSTEM32\d3dx11_43.dll
LoadedModule[95]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_43.dll
LoadedModule[96]=C:\WINDOWS\SYSTEM32\RTWorkQ.DLL
LoadedModule[97]=C:\Prepar3D V4\language.dll
LoadedModule[98]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[99]=C:\Program Files (x86)\Razer\Razer Cortex\x64\k_fps64.dll
LoadedModule[100]=C:\Program Files (x86)\Razer\Razer Cortex\x64\d3dx10_43.dll
LoadedModule[101]=C:\Program Files (x86)\Razer\Razer Cortex\x64\EasyHook64.dll
LoadedModule[102]=C:\WINDOWS\SYSTEM32\dbghelp.dll
LoadedModule[103]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[104]=C:\WINDOWS\SYSTEM32\inputhost.dll
LoadedModule[105]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[106]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll
LoadedModule[107]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll
LoadedModule[108]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[109]=C:\WINDOWS\SYSTEM32\MSXML6.DLL
LoadedModule[110]=C:\WINDOWS\SYSTEM32\SspiCli.dll
LoadedModule[111]=C:\Prepar3D V4\uiInterface.dll
LoadedModule[112]=C:\WINDOWS\SYSTEM32\mscoree.dll
LoadedModule[113]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
LoadedModule[114]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
LoadedModule[115]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[116]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\649c6a53d1a3a182e6eac793694a733f\mscorlib.ni.dll
LoadedModule[117]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
LoadedModule[118]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\7e7ba461137d6faf674666f208bb34c2\System.ni.dll
LoadedModule[119]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Core\6a9fe8d059ff70adb50f5b340a4ad8ee\System.Core.ni.dll
LoadedModule[120]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\WindowsBase\f007fdd65bfa47fdd5d985fb66e9ade9\WindowsBase.ni.dll
LoadedModule[121]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[122]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[123]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[124]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll
LoadedModule[125]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\PresentationCore\20c8fb61f94136af2a6f3fdbc97c82ae\PresentationCore.ni.dll
LoadedModule[126]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\54386d1f1c47c77cc8cb74c71c7b331e\PresentationFramework.ni.dll
LoadedModule[127]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xaml\015ae8afe89b32a4adcc9679a273021b\System.Xaml.ni.dll
LoadedModule[128]=C:\WINDOWS\SYSTEM32\dwrite.dll
LoadedModule[129]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[130]=C:\WINDOWS\SYSTEM32\MSVCP120_CLR0400.dll
LoadedModule[131]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[132]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Configuration\19daa5f5a704db96e4a812fa16f847fc\System.Configuration.ni.dll
LoadedModule[133]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xml\08e8fa67f0a711551a8a00ad6c5880fc\System.Xml.ni.dll
LoadedModule[134]=C:\WINDOWS\system32\dwmapi.dll
LoadedModule[135]=C:\WINDOWS\SYSTEM32\iphlpapi.dll
LoadedModule[136]=C:\WINDOWS\System32\NSI.dll
LoadedModule[137]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[138]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
LoadedModule[139]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[140]=C:\WINDOWS\SYSTEM32\secur32.dll
LoadedModule[141]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[142]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[143]=C:\Windows\System32\rasadhlp.dll
LoadedModule[144]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[145]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Drawing\cf9625cf0f5fdb35d7171e09723e3fbb\System.Drawing.ni.dll
LoadedModule[146]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[147]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[148]=C:\WINDOWS\System32\DriverStore\FileRepository\c0331834.inf_amd64_598c38be6d6a3fce\B331820\aticfx64.dll
LoadedModule[149]=C:\WINDOWS\System32\DriverStore\FileRepository\c0331834.inf_amd64_598c38be6d6a3fce\B331820\atiuxp64.dll
LoadedModule[150]=C:\WINDOWS\System32\DriverStore\FileRepository\c0331834.inf_amd64_598c38be6d6a3fce\B331820\atidxx64.dll
LoadedModule[151]=C:\WINDOWS\SYSTEM32\amdihk64.dll
LoadedModule[152]=C:\WINDOWS\SYSTEM32\WTSAPI32.DLL
LoadedModule[153]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[154]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[155]=C:\WINDOWS\SYSTEM32\CLDAPI.dll
LoadedModule[156]=C:\Windows\System32\Windows.StateRepositoryPS.dll
LoadedModule[157]=C:\WINDOWS\system32\ntshrui.dll
LoadedModule[158]=C:\WINDOWS\system32\srvcli.dll
LoadedModule[159]=C:\WINDOWS\SYSTEM32\cscapi.dll
LoadedModule[160]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17134.228_none_fb4599993062b194\comctl32.dll
LoadedModule[161]=C:\WINDOWS\system32\netutils.dll
LoadedModule[162]=C:\WINDOWS\System32\coml2.dll
LoadedModule[163]=C:\WINDOWS\system32\mssprxy.dll
LoadedModule[164]=C:\WINDOWS\SYSTEM32\LINKINFO.dll
LoadedModule[165]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[166]=C:\WINDOWS\System32\drprov.dll
LoadedModule[167]=C:\WINDOWS\System32\ntlanman.dll
LoadedModule[168]=C:\WINDOWS\System32\davclnt.dll
LoadedModule[169]=C:\WINDOWS\System32\DAVHLPR.dll
LoadedModule[170]=C:\WINDOWS\System32\wkscli.dll
LoadedModule[171]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[172]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[173]=C:\WINDOWS\SYSTEM32\AVRT.dll
LoadedModule[174]=C:\Windows\System32\Windows.UI.dll
LoadedModule[175]=C:\Windows\System32\TextInputFramework.dll
LoadedModule[176]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll
LoadedModule[177]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Presentatioaec034ca#\026d52dd4e86ea795eb906ebc04a4a40\PresentationFramework.Aero2.ni.dll
LoadedModule[178]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[179]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[180]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[181]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[182]=C:\WINDOWS\System32\DriverStore\FileRepository\c0331834.inf_amd64_598c38be6d6a3fce\B331820\atiu9p64.dll
LoadedModule[183]=C:\WINDOWS\System32\DriverStore\FileRepository\c0331834.inf_amd64_598c38be6d6a3fce\B331820\atiumd64.dll
LoadedModule[184]=C:\WINDOWS\System32\DriverStore\FileRepository\c0331834.inf_amd64_598c38be6d6a3fce\B331820\atiumd6a.dll
LoadedModule[185]=C:\WINDOWS\System32\DriverStore\FileRepository\c0331834.inf_amd64_598c38be6d6a3fce\B331820\atiumd6t.dll
LoadedModule[186]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\69ff356ffaef4c4c137570836532ba4d\System.Windows.Forms.ni.dll
LoadedModule[187]=C:\WINDOWS\SYSTEM32\wdmaud.drv
LoadedModule[188]=C:\WINDOWS\SYSTEM32\ksuser.dll
LoadedModule[189]=C:\WINDOWS\SYSTEM32\msacm32.drv
LoadedModule[190]=C:\WINDOWS\SYSTEM32\midimap.dll
LoadedModule[191]=C:\Prepar3D V4\SimObjects\Modules\Utilities.dll
LoadedModule[192]=C:\Prepar3D V4\CIGI.dll
LoadedModule[193]=C:\Prepar3D V4\radar.dll
LoadedModule[194]=C:\Prepar3D V4\VirtualReality.dll
LoadedModule[195]=C:\Prepar3D V4\openvr_api.dll
LoadedModule[196]=C:\Prepar3D V4\ovrvision.dll
LoadedModule[197]=C:\WINDOWS\SYSTEM32\OpenCL.dll
LoadedModule[198]=C:\Prepar3D V4\ControllableCamera.dll
LoadedModule[199]=C:\Prepar3D V4\Gauges\TargetInfo.dll
LoadedModule[200]=C:\Prepar3D V4\Gauges\Fury_1500.dll
LoadedModule[201]=C:\Prepar3D V4\Gauges\F-16.dll
LoadedModule[202]=C:\Prepar3D V4\SimObjects\Modules\Driver.dll
LoadedModule[203]=C:\Prepar3D V4\SimObjects\Modules\Orion MPCV.dll
LoadedModule[204]=C:\Prepar3D V4\SimObjects\Modules\SLS Block 1.dll
LoadedModule[205]=C:\Prepar3D V4\SimDirector.dll
LoadedModule[206]=C:\Users\LitMW\AppData\Local\Orbx\FTXCentral\v3.2.5.9\Orbx_ObjectFlow_x64.dll
LoadedModule[207]=C:\Program Files (x86)\Addon Manager\bglmanx64.dll
LoadedModule[208]=C:\WINDOWS\SYSTEM32\SHFolder.dll
LoadedModule[209]=C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule64.dll
LoadedModule[210]=C:\Prepar3D V4\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[211]=C:\Prepar3D V4\RAASPRO\RAASPRO.dll
LoadedModule[212]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[213]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[214]=C:\WINDOWS\SYSTEM32\WINNSI.DLL
LoadedModule[215]=C:\Program Files\Common Files\System\ado\msado15.dll
LoadedModule[216]=C:\WINDOWS\SYSTEM32\MSDART.DLL
LoadedModule[217]=C:\Program Files\Common Files\System\Ole DB\oledb32.dll
LoadedModule[218]=C:\WINDOWS\SYSTEM32\DPAPI.dll
LoadedModule[219]=C:\Windows\System32\comsvcs.dll
LoadedModule[220]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\ACEOLEDB.DLL
LoadedModule[221]=C:\WINDOWS\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9415_none_08e0c10ba840a28a\MSVCR90.dll
LoadedModule[222]=C:\Program Files\Common Files\Microsoft Shared\office14\mso.dll
LoadedModule[223]=C:\WINDOWS\SYSTEM32\msi.dll
LoadedModule[224]=C:\WINDOWS\SYSTEM32\srpapi.dll
LoadedModule[225]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\ACECORE.DLL
LoadedModule[226]=C:\WINDOWS\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.9415_none_08e0c10ba840a28a\MSVCP90.dll
LoadedModule[227]=C:\Program Files\Common Files\Microsoft Shared\office14\Cultures\office.odf
LoadedModule[228]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\3082\ACEWSTR.DLL
LoadedModule[229]=C:\Program Files\Common Files\Microsoft Shared\office14\MSORES.DLL
LoadedModule[230]=C:\Program Files\Common Files\Microsoft Shared\office14\3082\MSOINTL.DLL
LoadedModule[231]=C:\PROGRA~1\COMMON~1\MICROS~1\OFFICE14\ACETXT.DLL
LoadedModule[232]=C:\WINDOWS\SYSTEM32\mlang.dll
LoadedModule[233]=C:\Program Files\Common Files\Microsoft Shared\OFFICE14\3082\ACEINTL.DLL
LoadedModule[234]=C:\Prepar3D V4\RAASPRO\DLLs\64bit\RAASAUDIO64.DLL
LoadedModule[235]=C:\WINDOWS\SYSTEM32\X3DAudio1_6.dll
LoadedModule[236]=C:\WINDOWS\system32\xactengine3_4.dll
LoadedModule[237]=C:\WINDOWS\system32\XAudio2_4.dll
LoadedModule[238]=C:\Prepar3D V4\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[239]=C:\Prepar3D V4\Modules\FSUIPC5.dll
LoadedModule[240]=C:\Prepar3D V4\as_srv\as_connect_64.dll
LoadedModule[241]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\PresentationUI\234a7b67cde6022339a7dffd8bbc6f6e\PresentationUI.ni.dll
LoadedModule[242]=C:\WINDOWS\SYSTEM32\XInput1_4.dll
LoadedModule[243]=C:\Windows\System32\deviceaccess.dll
LoadedModule[244]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Web\fec6d2319d2c43d3665130c6d8031827\System.Web.ni.dll
LoadedModule[245]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\webengine4.dll
LoadedModule[246]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\UIAutomationTypes\74bf1b94cf47a3a4ba1b2e7e938b9f4c\UIAutomationTypes.ni.dll
LoadedModule[247]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll
LoadedModule[248]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[249]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[250]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[251]=C:\WINDOWS\system32\RMCLIENT.dll
LoadedModule[252]=C:\WINDOWS\system32\msctfui.dll
LoadedModule[253]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Runteb92aa12#\58e715328cda5c62eec5e0e431b57633\System.Runtime.Serialization.ni.dll
LoadedModule[254]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\SMDiagnostics\3e2cfe4b7b5aad70fe419a21b2b6ac57\SMDiagnostics.ni.dll
LoadedModule[255]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Servd1dec626#\125add414d79bcba4209a9ac340c5ee0\System.ServiceModel.Internals.ni.dll
LoadedModule[256]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.17134.228_none_2c308c7e8af52b62\gdiplus.dll
LoadedModule[257]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\UIAutomationProvider\24a0c2454bf9f485c1d13c606ebfbe06\UIAutomationProvider.ni.dll
LoadedModule[258]=C:\Prepar3D V4\Gauges\qw787.gau
LoadedModule[259]=C:\Prepar3D V4\Gauges\QW787_2.gau
LoadedModule[260]=C:\Prepar3D V4\Gauges\TrueGlass.dll
LoadedModule[261]=C:\Prepar3D V4\Gauges\FSFX\787\fsfx_RealEffects_1.dll
LoadedModule[262]=C:\WINDOWS\system32\wbem\wbemprox.dll
LoadedModule[263]=C:\WINDOWS\SYSTEM32\wbemcomn.dll
LoadedModule[264]=C:\WINDOWS\system32\wbem\wbemsvc.dll
LoadedModule[265]=C:\WINDOWS\system32\wbem\fastprox.dll
LoadedModule[266]=C:\WINDOWS\System32\imagehlp.dll
LoadedModule[267]=C:\WINDOWS\SYSTEM32\gpapi.dll
LoadedModule[268]=C:\Windows\System32\cryptnet.dll
LoadedModule[269]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[270]=C:\Windows\System32\ieframe.dll
LoadedModule[271]=C:\Windows\System32\NETAPI32.dll
LoadedModule[272]=C:\WINDOWS\SYSTEM32\msIso.dll
LoadedModule[273]=C:\Windows\System32\mshtml.dll
LoadedModule[274]=C:\WINDOWS\SYSTEM32\WLDP.DLL
LoadedModule[275]=C:\Windows\System32\vaultcli.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=17134
OsInfo[3].Key=ubr
OsInfo[3].Value=228
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1031
OsInfo[7].Key=geoid
OsInfo[7].Value=94
OsInfo[8].Key=sku
OsInfo[8].Value=101
OsInfo[9].Key=domain
OsInfo[9].Value=0
OsInfo[10].Key=prodsuite
OsInfo[10].Value=768
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=116387
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.228.17134.0-11.0.80
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16323
OsInfo[19].Key=svolsz
OsInfo[19].Value=930
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=180410
OsInfo[22].Key=bldtm
OsInfo[22].Value=1804
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs4_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.17134.228.amd64fre.rs4_release.180410-1804
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Core
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=expid
OsInfo[34].Key=containerid
OsInfo[35].Key=containertype
OsInfo[36].Key=edu
OsInfo[36].Value=0
FriendlyEventName=Nicht mehr funktionsfähig
ConsentKey=APPCRASH
AppName=Prepar3D exe
AppPath=C:\Prepar3D V4\Prepar3D.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=DED48A47CD06CBA637AF1CD9393BD4FC
MetadataHash=-2062044679

My rig:

Sapphire RX 580 8GB

I5-4460

ASRock B85M Pro 3

16 GB of RAM

P3D on a 1TB HDD

Many thanks,

Eren

Link to comment
Share on other sites

dwrite.dll is a Windows 7/8/10 system file developed by Microsoft.  It could be corrupt.  To check, open the Command Prompt in elevated status (click on search box>type cmd>right click on Command Prompt and select Run as Administrator).  Once open, type SFC /scannow and then click on Enter (note the space between SFC and /).  It will scan your system for corrupt and missing files and replace any if found. 

I do see where it loaded successfully as module 128 so it is not missing but still could be corrupted.  The dll is responsible for "Microsoft DirectX Typography Services" which, to me, is related to your graphics card and terrain mapping.  Perhaps just reinstalling the drivers for your Radeon graphics card will fix it.

Windows 10 is out of date too.  There was an update released on 14 August. Run Windows Update.

I have never seen anyone get this error before.  Does the error only occur when running the QW787?  What about any default or other aircraft installed (must be at the same airport and scenery where the QW787 crashed).  It could be a problem too with scenery.

It could also be one of the modules loading via your dll.xml (there are two in P3D)(see page 10, AVSIM CTD Guide).  Whenever I get an error, the first thing I do is to disable the dll.xml's and remove all Add-on Scenery from the Documents/Prepar3D v4 Add-ons folder and move them to a Temp folder.  I then run P3DV4 with the same scenario where I got the crash and see if this fixes the problem.  If it does, I know my problem is associated with a loaded module or an add-on scenery.  The AVSIM CTD Guide has further guidance.

 

 

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 

 

Link to comment
Share on other sites

Now i'm confused. I'm often using my pc and always check for updates (so windows doesn't automatically install updates while playing). I checked it again and windows update says windows is up to date. I think the last time it installed updates was just a few days ago.

A new driver for my gpu (18.8.2) was just released so i downloaded that and made a full reinstall of the driver.

I also ran sfc /scannow back then and it said all files are OK. Now i ran it again and it said the same. I ran it a second time, but now it sais it found a few corrupted files and replaced them. I looked the files up in the DCS log but it seems that it didn't replace the dwrite.dll, so i think the dll is ok. But it's still confusing that it sometimes finds corrupted files and sometimes not.

The ctd only happens with the QW 787. I've done a test flight with a few default aircraft and all the addon aircrafts i own and all run fine. I tried the 787 at addon airports, default airports, with ORBX Global, without it. Still crashes. So it has nothing to do with the scenery i think.

Gonna try to disable the dll.xml now. Haven't tried that one yet.

Link to comment
Share on other sites

44 minutes ago, LitMW said:

Now i'm confused. I'm often using my pc and always check for updates (so windows doesn't automatically install updates while playing). I checked it again and windows update says windows is up to date. I think the last time it installed updates was just a few days ago.

Apologize.  I was looking at the version of your dwrite.dll and that version is the same as mine.  I have a recent crash report and my OS version is the same as yours.  I got the build number from going to the Windows Update page, clicking on OS Build Info on the right side of the page.  So I was wrong.

I have the QW787 and flew it just today (and a couple of times yesterday) and have yet to get a crash.  It is difficult for me to believe your crashes are caused by the QW787.  There are thousands of users and so far only you have reported an error showing the faulting module as dwrite.dll.  By the way, just because the error report showed dwrite.dll was the faulting module, it does not indicate it was the cause of the crash.  It just provides a clue and, in this case, the Internet shows dwrite.dll is associated with DirectX and Topography and this is why I suggested your video card drivers were corrupted or out of date.  Your video card is DX12 capable so the specifications indicate it is compatible.

Do you have any utility that is overclocking or adjusting the vram on the video card?  For me I have a utility called the ASUS GPU Tweak II.  Some GPU makers have gadgets like this they provide with their cards.  I did some searching and your card might have come with the Radeon Software Crimson ReLive Edition which is AMD's advanced graphics software for enabling high-performance gaming and engaging VR experiences.  So I believe this package is equal to the ASUS GPU Tweak II that I have installed.  I had issues with the ASUS Tweak II as it was causing random crashes with P3D but mostly with the PMDG aircraft.  I had a crash with the CS757 too but do not recall having crashes with the QW787.  As I recalled, I had so many crashes, I reset Windows 10 and reinstalled everything (which did not help).  I just recently reinstalled the QW787 as I wasn't going to reinstall everything until I got my crashes fixed.  

The ASUS GPU Tweak utility was showing no issues.  The fans were working and I did not see anything abnormal.  I had the tweak utility set at OC Mode or Game Mode.  It controlled the fans well and they remained in the 60C range.  I decided to go the User Profile Mode.  For the ASUS GPU utility, the Profile Mode allows you to set your own settings so I left everything at default but raised the GPU fans to 100%.  No more crashes since doing this.  I believe it was a setting ASUS set up in Game Mode and/or OC Mode. 

I have seen a lot of members having unexplained crashes and believe it is the utility that controls the GPU.  Try doing what I did (if you have a similar utility) by using the default settings for the GPU but increase the speed of the fans as the default settings does not control the fans very well.

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 

 

Link to comment
Share on other sites

Yeah i use Radeon ReLife and played with the settings a little. I also thought it is my graphics card. It didn't solve it for me...

But good news! By deactivating the 2 .xml files in both locations, i've managed do to a complete 2 hour flight. I did all the things i did last time that lead to a ctd, but this time the game didn't crash. So yeah, that's how i got rid of it. My apologize for not doing that at first. It is just on page 10 on the ctd guide, but somehow i didn't see that when i read the guide. I think i was tired 😅. So now, i'll just follow what's described in the guide, then everything should be alright.

Thank you so much for helping me and solving the issue in just 1 day. Your support and AVSIM is awesome! (And nice Corvette by the way😉)

  • Like 1
Link to comment
Share on other sites

It's me again. Looks like i celebrated too early. The fix i tried yesterday did not fix the problem. I've done another flight now with completely disabling all the addons and the dll/exe.xml files. But it crashed again.

I don't think that it's a problem with my GPU, since i've the RX 580 for just a month now and with my old GPU, an R9 380, i had the same ctd. But i also don't think it's windows cause i already reinstalled it 2 times. And i also don't think its a problem with the 787 itself, because i'm pretty much the only one with this error (i mean i could not find anyone else on the internet with this problem). So what else could it be? Drivers maybe?

Link to comment
Share on other sites

What is happening to you has happened to me but, for me, it does not matter the aircraft.  For me it was the GPU Tweak utility for my Nvidia GTX 1080ti.  Can you disable the Radeon Relife and see if this fixes your problem?  You have to do these things one at a time until you find a solution.  If you did a bunch of things to try to fix the problem and the problem was fixed, you would not know what you did to fix it.

It is not Windows 10.  Of course it could be drivers but again, please do not check your drivers and update until you have tried the disabling or uninstalling of the Radeon Relife.  Page 16 suggests updating drivers and has a recommended freeware program to use.  Fixing drivers has fixed problems for others in the past but not for all so it is another hit or miss fix. 

The fact that P3D worked okay by disabling the dll.xml's and made you think it was fixed but all it did was take some load off of your sim.  If any of the modules being loaded by the dll.xml, I would think it is the fsuipc.  That causes crashes many times if it is not kept up to date.  The fsuipc has caused crashes for me even though I only use it to log my FPS until I updated it.  Still it has also caused serious pausing in the P3DV4 and making the game unplayable until it is updated.  It's a nice utility but it can cause issues.

I have did not get crashes after setting up a default profile for my GPU overclocking program but today I ran P3D in "Silent Mode" and got another crash.  I should have changed the profile to the default but decided to try the Silent Mode and see it I could keep it at that.  Now I have totally uninstalled the ASUS tweaking program.  I did that to see if I get any more crashes.  If so, my issue is narrowed to the motherboard pins that hold the CPU.  If any are bent and touching another pin, it causes this problem too. 

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 

 

Link to comment
Share on other sites

18 minutes ago, LitMW said:

So i uninstalled ReLife and guess what, it didnt fix it.

I strongly believed the ASUS GPU Tweak II program was causing my random crashes but have since determined the program was NOT causing my strange random crashes.  I ended up taking my system apart, removing the CPU and then checking the pins the CPU sits on.  I built my current system and wanted to be sure I did not accidentally bend any of the pins.  Looking closely with my eyes, they all looked in perfect condition but decided to use a magnifying glass and look closer.  The pins were all straight but I did see some microscopic "trash" around several pins.  Believe it was some thermal paste that accidentally dropped on the pins.  Removed it with a needle and installed the CPU and put the system back together and all seems well again.  The ASUS GPU Tweak can be put into any mode (Game or OC Mode) and no crash.

The reason I suspected your ReLife GPU program was because dwrite.dll is related to Microsoft DirectX Typography which, according to Google means: "the style and appearance of printed matter. The art or procedure of arranging type or processing data and printing from it."  According to Google, the primary cause of dwrite.dll errors is a corrupted registry.  If you have a registry cleaner like CCleaner, I would run that program.  I use Advanced System Care's registry cleaner about twice a month.

 

Your crashes did stop when you disabled the dll.xml's and it could be related to a process there.  Make sure you have P3D set to start up in Administrative Mode for ALL users as there are several users on your computer (even though you are the only user).  To do that, right click on the P3D icon on your desktop, right click Prepar3D and select properties, click on the compatibility tab and then look all the way down and make sure it is set for ALL users.  I believe it is not by default.

 

 
 

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 

 

Link to comment
Share on other sites

ok im gonna try to clean my registry. I didnt do that for a long time now, good idea Jim. I have also "ripped" my pc appart to clean it. Prepar3D is already on Administrative mode for all users.

But what i have noticed is that sometimes im able to complete a fllight. For example, i did another flight today with everything on normal (without deleting the xml.dml, without relife deactivated and so on...) and it crashed, as expected. But then i did that flight again without changing anything and that time i completed the flight, even tho not doing anything different than last flight. That's confusing.

Link to comment
Share on other sites

21 minutes ago, LitMW said:

But what i have noticed is that sometimes im able to complete a fllight. For example, i did another flight today with everything on normal (without deleting the xml.dml, without relife deactivated and so on...) and it crashed, as expected. But then i did that flight again without changing anything and that time i completed the flight, even tho not doing anything different than last flight. That's confusing.

That sounds exactly what was happening to me. After using my new build for a month or two, I decided one day to rip apart my system and clean it up as things were working so well. After doing this, I would complete some flights but suddenly get a BSOD or crash the next time.  There was no consistent scenario except it happened only if using Prepar3D.  Thought I had it fixed by identifying the GPU Tweak utility and going to a default user mode but suddenly started getting more crashes so ripped the system apart two nights ago and found some "garbage" in between some cpu pins. 

I also searched and made sure I had the latest cpu chipset driver and also installed the latest BIOS again.  But that was later and after I put my computer back together and found it running great again. 

If you have any scenery or aircraft not specifically made for Prepar3DV4, I would temporarily disable them to make sure they are not the cause of your problem. Some gauges made for previous versions may not work in P3DV4 properly.

Make sure too you have all of the Microsoft Visuals as some P3D addons use older Microsoft Visuals.  You should have both the 64 bit and 32 (x86) versions.  I have 2005 (x86 version only), 2008, 2010, 2012, 2013, and 2017 installed.  I did not install these MSV's, they were installed by some other program that uses them.  Also make sure you have Microsoft.net versions installed too.  Look in C:\Windows\Microsoft.net\Framework (for x86) and Framework64 (for 64 bit versions). I have the following:

v1.0.3705 (x86 only)

v1.1.4322 (x86 only)

v2.0.50727 (both versions)

v3.0 (both versions)

v3.5 (both versions)

v4.0.30319 (both versions)

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 

 

Link to comment
Share on other sites

  • 5 years later...

Quality wings 787 is a joke. Constantly crashes to desktop every flight.

Every other addon aircraft I have there is no problem.

I now recommend no one purchase there products. As they are only interested in your money, and not interested in fixing the issues that exist with there product.

There customer service is a absolute joke,😞 no one ever gets back to you so you are stuck with a unusable aircraft.

PMDG Fslabs or Aerosoft for me I wont touch Q/Wings products ever again.

Link to comment
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
  • 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...