January 3, 201511 yr Author Jim these both crashes happened around the same time i just checked appcrash view First NTDLL.DLL 24/5/14 at 19:41 Second NTDLL.DLL 2/01/2015 at 19:24 What do you think? Vernon Howells
January 3, 201511 yr Definitely looks like a voltage error or your CPU Core Ratio is too high. Do you have your Ai Overclock Tuner set to XMP? This ensures the best overclock and best voltage settings for your CPU. 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 3, 201511 yr Author Hi jim, everything is per nicks guide. 41 ghz voltage 1.13 XMP and as you know i've just increased my voltage to 1.14 it can't be mtx because i started at the same time at the same airport and no crash so like you said could be voltage. if i get the crash again i'll drop my CPU core ratio back to 40 ghz before i got the crash what about updating my BIOS again there is another stability fix jim on the 2103 Z87-A BIOS 2103 and BIOS updaterImprove system stability. Vernon Howells
January 3, 201511 yr everything is per nicks guide. 41 ghz voltage 1.13 XMP and as you know i've just increased my voltage to 1.14 Like I told you sometime back, I tried NickN's settings in his Bible. I have the exact same system as his down to the nth degree (I got mine first though). I figured using his settings would be perfecto for me too. No joy. CTD, CTD, and more CTD's until I went back to the Optimal defaults and set my the overclock recommended by JJ at ASUS. No problems. It is almost proof positive no systems are completely the same no matter how hard you try. 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 6, 201511 yr Author I got another NTDLL.DLL jim and followed by a API.DLL when going in and out of FSUIPC ? I have disabled MTX if it continues to crash i'll drop my clock back to 40 ghz and volt 1.12 Also dropped fsx settings! You think its the OC Vernon Howells
January 6, 201511 yr I think so too. At least you have a temporary fix - return to optimal defaults in your BIOS and start over again. Not to worry though. This is how I became somewhat knowledgeable of bad overclocks and overclocking. I wish there was a voltage setting that worked for everyone all of the time. Maybe 10 years from now. Just remember that FSX started out with those XPS Pentium 4 Computer systems and the 'Core2 Duo' systems. Not even seeing the GHz yet. Now we have systems that are 2-3 times faster, maybe even more depending on the overclock. So I wouldn't be too concerned with a big overclocked system. You're still going to have to reduce some settings especially for long flights and you still only have 4 GB's of VAS. I turn my FSX and display driver settings down and let my FSX 'breath'. Give it some room to operate more efficiently. 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 6, 201511 yr Author Well its a process of elimination and i've tried a few things, now its MTX thats been disabled and i'll see how i get on with that. But i'm sure its the OC. If it crashes again i'll drop my OC and test again jim. If continues to crash i'll go back to OPTIMAL. Does this mean i can't OC my system? I'm sure when i first ran my OC at 40 ghz and volts at 1.12 i had no crashes whatsoever so could be my CPU can't handle it? What do you think... Could it be my GPU DRIVER? I'm running the 344.75 Also i shut down fsx and restarted it and got this its not the first time Version=1 EventType=CLR20r3 EventTime=130614274539894750 ReportType=2 Consent=1 UploadTime=130614274540694752 ReportIdentifier=da35e15e-74f0-11e4-8f2b-bcee7b8c5ef9 WOW64=1 Response.BucketId=123241058 Response.BucketTable=22 Response.type=4 Sig[0].Name=Problem Signature 01 Sig[0].Value=fsx.exe Sig[1].Name=Problem Signature 02 Sig[1].Value=10.0.61637.0 Sig[2].Name=Problem Signature 03 Sig[2].Value=46fadb14 Sig[3].Name=Problem Signature 04 Sig[3].Value=System Sig[4].Name=Problem Signature 05 Sig[4].Value=2.0.0.0 Sig[5].Name=Problem Signature 06 Sig[5].Value=53a12529 Sig[6].Name=Problem Signature 07 Sig[6].Value=3b20 Sig[7].Name=Problem Signature 08 Sig[7].Value=fe Sig[8].Name=Problem Signature 09 Sig[8].Value=System.ComponentModel.Win32 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=2057 UI[2]=C:\FSX\fsx.exe UI[3]=Microsoft Flight Simulator® 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:\FSX\fsx.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll LoadedModule[7]=C:\Windows\syswow64\GDI32.dll LoadedModule[8]=C:\Windows\syswow64\USER32.dll LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[14]=C:\Windows\syswow64\LPK.dll LoadedModule[15]=C:\Windows\syswow64\USP10.dll LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[17]=C:\Windows\syswow64\ole32.dll LoadedModule[18]=C:\Windows\system32\apphelp.dll LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[20]=C:\Windows\system32\UxTheme.dll LoadedModule[21]=C:\Windows\system32\WINMM.dll LoadedModule[22]=C:\Windows\system32\samcli.dll LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[24]=C:\Windows\system32\MSACM32.dll LoadedModule[25]=C:\Windows\system32\VERSION.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\system32\sfc.dll LoadedModule[28]=C:\Windows\system32\sfc_os.DLL LoadedModule[29]=C:\Windows\syswow64\USERENV.dll LoadedModule[30]=C:\Windows\syswow64\profapi.dll LoadedModule[31]=C:\Windows\system32\dwmapi.dll LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[35]=C:\Windows\syswow64\urlmon.dll LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL LoadedModule[43]=C:\Windows\syswow64\iertutil.dll LoadedModule[44]=C:\Windows\syswow64\WININET.dll LoadedModule[45]=C:\Windows\system32\MPR.dll LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll LoadedModule[50]=C:\Windows\system32\mscms.dll LoadedModule[51]=C:\Windows\system32\DDRAW.dll LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[54]=C:\Windows\syswow64\IMM32.dll LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll LoadedModule[57]=C:\Windows\syswow64\NSI.dll LoadedModule[58]=C:\Windows\system32\msi.dll LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[60]=C:\FSX\language.dll LoadedModule[61]=C:\FSX\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[63]=C:\FSX\ablscpt.dll LoadedModule[64]=C:\FSX\flight.dll LoadedModule[65]=C:\FSX\ai_player.dll LoadedModule[66]=C:\FSX\acontain.dll LoadedModule[67]=C:\FSX\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=C:\FSX\fsui.dll LoadedModule[70]=C:\FSX\atc.dll LoadedModule[71]=C:\FSX\facilities.dll LoadedModule[72]=C:\FSX\demo.dll LoadedModule[73]=C:\FSX\main.dll LoadedModule[74]=C:\FSX\fe.dll LoadedModule[75]=C:\FSX\util.dll LoadedModule[76]=C:\FSX\simprop.dll LoadedModule[77]=C:\FSX\g2d.dll LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll LoadedModule[80]=C:\Windows\system32\d3d9.dll LoadedModule[81]=C:\Windows\system32\d3d8thk.dll LoadedModule[82]=C:\FSX\g3d.dll LoadedModule[83]=C:\FSX\panels.dll LoadedModule[84]=C:\FSX\multiplayer.dll LoadedModule[85]=C:\FSX\ui.dll LoadedModule[86]=C:\FSX\sound.dll LoadedModule[87]=C:\FSX\sim1.dll LoadedModule[88]=C:\FSX\simscheduler.dll LoadedModule[89]=C:\FSX\visualfx.dll LoadedModule[90]=C:\FSX\window.dll LoadedModule[91]=C:\FSX\terrain.dll LoadedModule[92]=C:\FSX\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=C:\FSX\symmap.dll LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll LoadedModule[97]=C:\Windows\system32\MSIMG32.dll LoadedModule[98]=C:\FSX\xuipc.dll LoadedModule[99]=C:\FSX\livingwater.dll LoadedModule[100]=C:\FSX\fs-traffic.dll LoadedModule[101]=C:\FSX\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll LoadedModule[105]=C:\Windows\system32\rsaenh.dll LoadedModule[106]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[107]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[108]=C:\Windows\syswow64\MSASN1.dll LoadedModule[109]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[111]=C:\Windows\system32\wbemcomn.dll LoadedModule[112]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[114]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[115]=C:\Windows\system32\NTDSAPI.dll LoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[117]=C:\Windows\system32\dxgi.dll LoadedModule[118]=C:\Windows\system32\d3d11.dll LoadedModule[119]=C:\Windows\system32\nvd3dum.dll LoadedModule[120]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[121]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[122]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[123]=C:\Windows\system32\d3d10_1.dll LoadedModule[124]=C:\Windows\system32\d3d10_1core.dll LoadedModule[125]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[126]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[127]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[128]=C:\Windows\system32\winbrand.dll LoadedModule[129]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[130]=C:\Windows\system32\WINSTA.dll LoadedModule[131]=C:\Windows\SysWOW64\gameux.dll LoadedModule[132]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[133]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[134]=C:\Windows\SysWOW64\wer.dll LoadedModule[135]=C:\Windows\System32\Wpc.dll LoadedModule[136]=C:\Windows\System32\wevtapi.dll LoadedModule[137]=C:\Windows\System32\msxml6.dll LoadedModule[138]=C:\Windows\system32\SAMLIB.dll LoadedModule[139]=C:\Windows\system32\netutils.dll LoadedModule[140]=C:\FSX\uiautomationcore.dll LoadedModule[141]=C:\Windows\system32\OLEACC.dll LoadedModule[142]=C:\Windows\System32\MMDevApi.dll LoadedModule[143]=C:\Windows\System32\PROPSYS.dll LoadedModule[144]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[145]=C:\Windows\system32\RICHED20.DLL LoadedModule[146]=C:\Windows\system32\HID.DLL LoadedModule[147]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[148]=C:\Windows\system32\wdmaud.drv LoadedModule[149]=C:\Windows\system32\ksuser.dll LoadedModule[150]=C:\Windows\system32\AVRT.dll LoadedModule[151]=C:\Windows\system32\msacm32.drv LoadedModule[152]=C:\Windows\system32\midimap.dll LoadedModule[153]=C:\Windows\system32\dinput.DLL LoadedModule[154]=C:\Windows\System32\wship6.dll LoadedModule[155]=C:\Windows\System32\wshtcpip.dll LoadedModule[156]=C:\FSX\bglmanx.dll LoadedModule[157]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[158]=I:\Contrails Pro\ContrailsProFSX.dll LoadedModule[159]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[160]=C:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[161]=C:\Windows\system32\MSVCR100.dll LoadedModule[162]=C:\FSX\Modules\FSUIPC4.dll LoadedModule[163]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[164]=C:\Windows\system32\WINNSI.DLL LoadedModule[165]=C:\FSX\as_srv\as_btstrp.dll LoadedModule[166]=C:\Windows\system32\mscoree.dll LoadedModule[167]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll LoadedModule[168]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll LoadedModule[169]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\38bf604432e1a30c954b2ee40d6a2d1c\mscorlib.ni.dll LoadedModule[170]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll LoadedModule[171]=C:\Windows\syswow64\imagehlp.dll LoadedModule[172]=C:\Windows\system32\ncrypt.dll LoadedModule[173]=C:\Windows\system32\bcrypt.dll LoadedModule[174]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[175]=C:\Windows\system32\GPAPI.dll LoadedModule[176]=C:\Windows\system32\cryptnet.dll LoadedModule[177]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[178]=C:\Windows\system32\SensApi.dll LoadedModule[179]=C:\FSX\as_srv\as_connect.dll LoadedModule[180]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll LoadedModule[181]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\908ba9e296e92b4e14bdc2437edac603\System.ni.dll LoadedModule[182]=C:\Windows\system32\ntmarta.dll LoadedModule[183]=C:\Windows\system32\Secur32.dll LoadedModule[184]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\836e10dfd0811b303553216f5cb092ef\System.Drawing.ni.dll LoadedModule[185]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[186]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[187]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll LoadedModule[188]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[189]=C:\Windows\SysWOW64\mshtml.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=CLR20r3 AppName=Microsoft Flight Simulator® AppPath=C:\FSX\fsx.exe ReportDescription=Stopped working Vernon Howells
January 6, 201511 yr The crash was caused by the system.dll for Microsoft.net 2.0 (problem signature 4). I see FE.dll listed too which might be a bad texture of an addon aircraft repaint or an AI aircraft. So, if you just added a texture or an aircraft, suspect that as the cause first. I definitely do not think it is your GPU driver although you do not have the latest installed (347.09). Absolutely positive it is not the GPU driver. In regards to your OC, OC'ing is not an easy task especially if you are trying to bump it above 4.2GHz. OC'ing at 4.2GHz is totally simple because you do not have to mess with any of the voltages. Anything above that and you have to be careful as you are messing with voltages that could instantly destroy your computer system if you are not sure what you are doing. Too low voltages will also crash your system. In my case I let ASUS figure out the hard stuff and just mess with the multiplier. Hope this helps. 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 6, 201511 yr Author It says i have the microsoft.net installed? After running that checker! FE crash i haven't installed anything for a while. If i get the NTDLL.DLL crash again will i raise the voltage up to 1.15 Vernon Howells
January 6, 201511 yr This is Microsoft.net 2.0 telling you that you have an issue. It has nothing to do with the installation of dotnet 2.0. 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 6, 201511 yr I think the system is telling you that there is an issue with an application that uses Microsoft.net 2.0 (which is FSX, Acceleration, and any really old addons). Dotnet 2.0 is installed and loading properly. I wish I were a computer expert and could be able to tell you it's a modification you did to the F16 in Acceleration or the voltages in your overclock caused it but I cannot. Hopefully someone will come along and see your problem and tell you what is wrong. 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 6, 201511 yr Author The thing about the crash is, it only happens when i load FSX for the 2nd or 3rd time maybe more but never on the first load. I've had this crash a few times now! Vernon Howells
Create an account or sign in to comment