July 3, 201312 yr Hi there, I've spent the last week or two looking around and can't find anything to solve this, bar buying the gold ediiton but I don't want to buy something which might not work either and it's rather gutting as I quite fancied the A2A stuff which requires SP2.I've got standard edition FSX and it's fine on SP1 with whatever mods and using the UIAuto.dll to help maintain long flights, however as soon as I install SP2 I get 'A Fatal Error' BEX open start-up after hanging on the splash screen for about 30-60 seconds. I have tried UAC on/off, no firewall/Antivirus, no addon completely clean installations several times. removal of FSX.config which leads to a partially completed config files (literally one lines of data), I really cannot think of the cause as the problem starts with the SP2 update. Error reads as followed: Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Fault Module Name: unknown Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 005fc16c Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 2057 Appcrash gives me this: Version=1 EventType=BEX EventTime=130173627269065393 ReportType=2 Consent=1 ReportIdentifier=aa27cd8c-e42c-11e2-bf7d-10bf48bac486 IntegratorReportIdentifier=aa27cd8b-e42c-11e2-bf7d-10bf48bac486 WOW64=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.61472.0 Sig[2].Name=Application Timestamp Sig[2].Value=475e17d3 Sig[3].Name=Fault Module Name Sig[3].Value=unknown Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=00000000 Sig[6].Name=Exception Offset Sig[6].Value=005fc16c Sig[7].Name=Exception Code Sig[7].Value=c0000005 Sig[8].Name=Exception Data Sig[8].Value=00000008 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:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe UI[3]=A fatal error occurred. 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:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\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\system32\USERENV.dll LoadedModule[30]=C:\Windows\system32\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.17514_none_ec83dffa859149af\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\SysWOW64\guard32.dll LoadedModule[60]=C:\Windows\system32\fltlib.dll LoadedModule[61]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[62]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\language.dll LoadedModule[63]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL LoadedModule[64]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[65]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ablscpt.dll LoadedModule[66]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\flight.dll LoadedModule[67]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll LoadedModule[68]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\acontain.dll LoadedModule[69]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\controls.dll LoadedModule[70]=C:\Windows\system32\DINPUT8.dll LoadedModule[71]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsui.dll LoadedModule[72]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dll LoadedModule[73]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\facilities.dll LoadedModule[74]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\demo.dll LoadedModule[75]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\main.dll LoadedModule[76]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fe.dll LoadedModule[77]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\util.dll LoadedModule[78]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simprop.dll LoadedModule[79]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g2d.dll LoadedModule[80]=C:\Windows\system32\d3dx9_34.dll LoadedModule[81]=C:\Windows\system32\d3dx10_34.dll LoadedModule[82]=C:\Windows\system32\d3d9.dll LoadedModule[83]=C:\Windows\system32\d3d8thk.dll LoadedModule[84]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll LoadedModule[85]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\panels.dll LoadedModule[86]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dll LoadedModule[87]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ui.dll LoadedModule[88]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sound.dll LoadedModule[89]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dll LoadedModule[90]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simscheduler.dll LoadedModule[91]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\visualfx.dll LoadedModule[92]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\window.dll LoadedModule[93]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\terrain.dll LoadedModule[94]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dll LoadedModule[95]=C:\Windows\system32\DSOUND.dll LoadedModule[96]=C:\Windows\system32\POWRPROF.dll LoadedModule[97]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\symmap.dll LoadedModule[98]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[99]=C:\Windows\system32\MSIMG32.dll LoadedModule[100]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\xuipc.dll LoadedModule[101]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\livingwater.dll LoadedModule[102]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fs-traffic.dll LoadedModule[103]=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\gps.dll LoadedModule[104]=C:\Windows\system32\MSWSOCK.dll LoadedModule[105]=C:\Windows\system32\SHFOLDER.dll LoadedModule[106]=C:\Windows\SysWOW64\HsSrv.dll LoadedModule[107]=C:\Windows\system32\RICHED20.DLL LoadedModule[108]=C:\Windows\system32\CRYPTSP.dll LoadedModule[109]=C:\Windows\system32\rsaenh.dll LoadedModule[110]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[111]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[112]=C:\Windows\syswow64\MSASN1.dll LoadedModule[113]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[114]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[115]=C:\Windows\system32\wbemcomn.dll LoadedModule[116]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[117]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[118]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[119]=C:\Windows\system32\NTDSAPI.dll LoadedModule[120]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[121]=C:\Windows\system32\dxgi.dll LoadedModule[122]=C:\Windows\system32\d3d10.dll LoadedModule[123]=C:\Windows\system32\d3d10core.dll LoadedModule[124]=C:\Windows\system32\d3d11.dll LoadedModule[125]=C:\Windows\system32\atklumdisp.dll LoadedModule[126]=C:\Windows\system32\nvd3dum.dll LoadedModule[127]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[128]=C:\Windows\system32\atkdx11disp.dll LoadedModule[129]=C:\Windows\system32\nvwgf2um.dll LoadedModule[130]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[131]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[132]=C:\Windows\system32\d3d10_1.dll LoadedModule[133]=C:\Windows\system32\d3d10_1core.dll LoadedModule[134]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[135]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[136]=C:\Windows\system32\WINSTA.dll LoadedModule[137]=C:\Windows\SysWOW64\gameux.dll LoadedModule[138]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[139]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[140]=C:\Windows\SysWOW64\wer.dll LoadedModule[141]=C:\Windows\System32\Wpc.dll LoadedModule[142]=C:\Windows\System32\wevtapi.dll LoadedModule[143]=C:\Windows\System32\msxml6.dll LoadedModule[144]=C:\Windows\system32\SAMLIB.dll LoadedModule[145]=C:\Windows\system32\netutils.dll LoadedModule[146]=C:\Windows\system32\uiautomationcore.dll LoadedModule[147]=C:\Windows\system32\OLEACC.dll LoadedModule[148]=C:\Windows\System32\MMDevApi.dll LoadedModule[149]=C:\Windows\System32\PROPSYS.dll LoadedModule[150]=C:\Windows\system32\wdmaud.drv LoadedModule[151]=C:\Windows\system32\ksuser.dll LoadedModule[152]=C:\Windows\system32\AVRT.dll LoadedModule[153]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[154]=C:\Windows\system32\msacm32.drv LoadedModule[155]=C:\Windows\system32\midimap.dll LoadedModule[156]=C:\Windows\system32\HID.DLL LoadedModule[157]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[158]=C:\Windows\system32\dinput.DLL Sec[0].Key=LCID Sec[0].Value=2057 FriendlyEventName=Stopped working ConsentKey=BEX AppName=Microsoft® Flight Simulator X AppPath=C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
July 3, 201312 yr I would uninstall SP2 (the crash report shows it is installed properly) then run a freeware registry cleaner from the Internet, like CCleaner. Then reinstall SP2. Make sure the A2A program is uninstalled too (I do not see where any A2A program loaded in the crash report). A BEX means you had a Buffer_Overrun_Exception. The Exception Code indicates you had a Memory_Access_Violation which could be cause by almost anything. Since there was no faulting module, I think you have your settings are set too high for FSX or you have a bad tweak in your Fsx.cfg. I see you have Microsoft Visual C++ 2005 properly installed but did not see MSV 2008 loaded. SP2 and Acceleration require MSV 2005 w/SP1 installed and you have that. I'm not sure what the A2A applications require but believe they all came out long after FSX/Acceleration/SP2. In any case, any addon application, like A2A's would install the proper MSV if it is not seen during the installation. But, just to be sure, you should check in your Add/Remove Programs to see if 2008 and 2010 are installed. Applications will not run properly without the proper MSV installed. Best regards, Jim 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
July 4, 201312 yr Author Hi Jim, Thank you for the response, Ive run CCleaner but I'll try it again with SP2 uninstalled. FSX settings on set to default (v.high i think it is), by MSV do you mean MS Visual if so then I have it going '05.'08,'10 in the add/remove. The A2A is Accu-feel 2. Don't know if this helps at all System Spec is: O/S: Windows 7 64-bit CPU: I5-2500k RAM 16GB GPU: nVidia GeForce GTX 550 Ti Soundcard: ASUS D1 All drivers are upto date.
July 4, 201312 yr Author Just abit of an update, I've tried rolling back to SP1 running CCleaner Register and general clean then installing SP2. Still getting the same BEX crash. Also the installation hangs on DirectX update (about 2/3 completeion bar) then closes and opens the 'installation complete' box, is this normal for windows 7 or is something missing (never thought of that). I'm starting to wonder if Accel would fix this issue with SP2 or if it would suffer the same fate.
July 4, 201312 yr Also the installation hangs on DirectX update (about 2/3 completeion bar) then closes and opens the 'installation complete' box, is this normal for windows 7 or is something missing (never thought of that).I'm starting to wonder if Accel would fix this issue with SP2 or if it would suffer the same fate. That's normal. The program is just making sure you have the latest update installed. The software looked at your system and saw it was up-to-date so did not try to install an earlier version. SP2/Acceleration are the same except that SP2 is free and does not include the scenery, aircraft, and new missions that came with Acceleration. It basically made FSX compatible to DX10 and updated FSX. You can buy Acceleration. It's almost free now. It cost me $19 or $20 when it first came out. If you go this route, make sure you uninstall SP2 first and run that registry cleaner or you may have problems with the installation. The uninstalling/reinstalling SP2 and running CCleaner has worked for many others in the past with crashes so we had to try it. There's one more thing to check (but I doubt this is a problem) and that's to make sure you have Microsoft.net Versions 1.1 through the latest 4.5. You can check this by looking in Windows\Microsoft.net\Framework\then the versions. You need to have the 32 bit versions installed as FSX and all of FSX addons are 32 bit applications installed in a 64 bit Operating System. A lot of people look in their Add/Remove Programs and see a 32 bit and a 64 bit version of Microsoft.net installed so they uninstall the 32 bit version thinking they have a 64 bit system so no need for the 32 bit programs. So, I'm telling you this just to make sure. I just reinstalled FSX and Windows 7 as I updated to latest and greatest hardware. During my reinstallation of FSX, I was receiving a lot of BEX crashes with StackHash as the faulting module. Sometimes the module would be unknown just like what you are getting. The BEX crashes are not shutting FSX down while I'm flying or during startup though. It happens when I hit Ctrl-C to shutdown FSX. After it closes down, I'll get the error message that FSX had a problem and had to shutdown (I'm thinking, okay, well I already did that). I know exactly what causes these not really "crashes". I have two monitors, a 30 inch and a 22 inch secondary monitor. If I close FSX in full screen mode, the crash (or error message) will come up. If I change to Windowed Mode just before shutting down, no error message. So I have to make sure I shutdown FSX in Windowed Mode. A common faulting module for a BEX crash is the StackHash which, in laymen's terms, means something is stuck in memory. In your case, you have no faulting module and this indicates to me there is a problem with your OC or FSX/Display driver settings. They are too high. I was looking at your OP and saw where you stated no Firewall/Anti-virus. Never turn off your firewall. I know of several people who have turned it off (accidentally or on-purpose) and one received a computer virus within 16 seconds of going on the Internet. She had to call in a repairman and reinstall everything. Lastly, have you looked in the Event Viewer for your computer? The Event Viewer shows every event that occurred on your computer since you first installed Windows. The section you should look at is Custom Views\Administrative Events. This will list everything that was recorded when you turned on your computer. Sometimes looking at the Events will show you something else wrong with your system. Best regards, Jim 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
July 4, 201312 yr Author I've got to say Jim you are probably the most helpful person in I've ever spoken to, thank you so much for the time you take todo this.Microsoft .Net frameworks seen are:Framework 1.0.3705 to v4.0.30319 (in /Microsoft.net/Framework)V2.0.50727 to v4.0.30319 (in /Microsoft.net/Framework64)But in Add/Remove Programs only Framework 1.1 and Framework 4 Client Profile/Extended appear.So I'm not sure if the .NETs are installed properly, I will see if I can find downloads for them and check.Just done a completely clean installation (Uninstalled everything, cleared out all files, CCleaner ran) and updated to SP2 without changing anything. Same error As far as I know my system is not Overclocked (left it all since the day I built the machine).Edit:Rolled back to SP1 and got this as I went to change my graphics settings from the default Ultra High to a lower setting to see if it's that: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61355.0 Application Timestamp: 4643ee0a Fault Module Name: HsSrv.dll Fault Module Version: 1.0.8.619 Fault Module Timestamp: 4859e058 Exception Code: c0000005 Exception Offset: 0001200e OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 2057 Though I think this could be because I've not put in the UI.dll fix.Tried lowering my settings to minimal across the board, installed SP2 still for the BEX error
July 4, 201312 yr try to disable DEP globaly, open command prompt - type "bcdedit.exe /set {current} nx AlwaysOff" and hit enter. See if still happens. You can always turn DEP on with "bcdedit.exe /set {current} nx AlwaysOn" in command prompt. Note that i am not so conservative with malware protections, you don't need to folow my advice. I have turned off everything - UAC, DEP, Windows Firewall, Windows Defender. I run Avast antivirus(firewall included) which is very easy on resources, and i have backup of whole system on separate drive - this way i am more then protected. I can put whole system back in 20min if needed But in last 2 years i never had a problem becouse of this. For updating, check direct x http://www.microsoft.com/en-us/download/details.aspx?id=35 and dx SP1 http://www.microsoft.com/en-us/download/details.aspx?id=5582 and install just "ENU (vcredist_x86.exe)" here: http://archive.msdn.microsoft.com/KB961894/Release/ProjectReleases.aspx?ReleaseId=2067 I have a very long list, but let see what happens with this first Zeljko Budovic
July 4, 201312 yr So I'm not sure if the .NETs are installed properly, I will see if I can find downloads for them and check. They probably are all installed properly but there is a dotnet verification tool that you can download and check to make sure everything is properly installed. You can get it here - http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx. In regards to the latest crash, perhaps this link will help - http://www.simforums.com/forums/fsx-crashes-with-hssrvdll-fault_topic43995.html (NickN is considered a computer guru and fsx expert). Best regards, Jim 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
July 4, 201312 yr Author All files validated, only had the HsSrv.dll fault once but I did indeed have GX mode turned on for my ASUS card. Turned it off now, still getting the BEX error, the offset code keeps changing but nothing else.I can't really think of what else could cause the problem with SP2..
July 4, 201312 yr That probably will just fix the HsSrv.dll fault and not the BEX. There was hope though... Did you look in your Event Viewer for any other issues, especially those with red error icons? I'm afraid I've run out of suggestions. If it is a hardware problem, then FSX is never going to run until that issue is fixed. I was hoping it would be just a driver issue. You have an ASUS MB and that's what I had when I had my i7 2600K Sandy Bridge running. Back then I read somewhere on the Internet that ASUS has a hard time discovering system memory and make the proper frequency/timings/and setting the right voltage when they are set at AUTO. They recommended setting the frequency/timings/and voltage manually based on the SPD settings (should be located in the Tools section in the BIOS or under the SPD Tab in CPU-Z. I was having unexplained crashes back then and had done several tests on my system memory and all the reports came back that my system was stable. Then I saw that report and manually changed the settings using the X.M.P. Profile settings. No more crashes. So that might be something to look into. I know the ASUS MB's do a great job now as I have the Z87 ASUS Deluxe board and it sets the memory settings under the X.M.P. profile with the proper settings and does not use Auto. A too high or too low CPU Voltage setting will cause unexplained crashes too. I remember I had my CPU Voltage manually set for my 2600K at 1.4000. I decided to lower it to 1.3800. Suddenly I received unexplained crashes and remembered lowering the CPU voltage. Moved it back to 1.4000 and the crashes stopped. So, the point I'm attempting to make is just a wrong setting somewhere can create havoc elsewhere. It is strange though that it does it only after you install SP2. I just thought of one other possibility and that is sharing. You should right click your fsx folder and select Sharing... and, if the directory/sub-directories are not shared with everyone, you should share them. When installing SP2 you should also right click the .exe and Run the program as an Administrator. I'm sure you are doing this but trying to cover all the bases I know. I'm out of suggestions. Hopefully you will get it figured out soon. I know how frustrating something like this can be. Best regards, Jim 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
July 5, 201312 yr Author I have the ASUS P8v77 MB, would you be able to guide me through setting up the correct values (rather new to fiddling with Hardware).Event Viewer has a few other errors that happen randomly whilst my PC is on:WMI error ID 10 //./root/CIMV2 SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99 0x80041003 ScRegSetValueExW error ID 4001 The ScRegSetValueExW call failed for FailureActions with the following error: Access is denied. Also found Faulting Process ID changes with the FSX BEX error, not sure if that'll help.Warnings:WLAN Auto-config has successfully stoppedGuard32.dll - Error ID 11 Custom dynamic link libraries are being loaded for every application. The system administrator should review the list of libraries to ensure they are related to trusted applications. EDIT:Was going through my BIOS and found where I need to change the timings/etc and found my SPD data but not sure how to use it all, however I found additional Overflow Buffering protections built-in to the MB, turned it off and BEX is now gone I now have this APPCrash: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Fault Module Name: unknown Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 052e006c OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 2057 Still not running right, but atleast it's a step though it looks to me to be the same thing but from the application and not the buffer overflow
July 5, 201312 yr Warnings:WLAN Auto-config has successfully stopped Check this link - http://social.technet.microsoft.com/Forums/windows/en-US/8e71fa0d-8547-45c4-9fb1-39046dce2757/stupid-windows-7-event-id-4001-wlan-autoconfig-service-has-successfully-stopped. ScRegSetValueExW error ID 4001 This one is probably related to the one above but check this link - http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=4001&EvtSrc=MSExchange+System+Attendant+Mailbox&LCID=1033. Here were the settings for my 2600K: Ai Tweaker Tab: *** Ai Overclock Tuner - Set to X.M.P. *** On the next line - Profile #1 *** BCLK/PCIE Frequency - 100.0 *** Turbo Ratio - By All Cores *** Internal PLL Overvoltage - Enabled *** Memory Frequency - mine was set to DDR3-1600MHz. You will have to enter the frequency for your memory. *** EPU Power - Disabled DIGI+ VRM Load-line Calibration - Ultra high VRM Freq - Manual VRM Fixed Freq Mode - 350 Phase Control - Extreme Duty Control - T.Probe CPU Current Capability - 130% CPU Voltage - Manual Mode CPU Manual Voltage - 1.4000 DRAM Voltage - 1.65000 (this is the voltage indicated in the bottom of the SPD column for X.M.P.) Everything else below this was set to Auto. Next go back up on the Ai Tweaker page and click on DRAM Timing Control. Enter the primary timings as indicated under the X.M.P. column under the SPD Tab Mine were - 6 8 6 24 And the Dram Command Mode I left that at auto. Everything else below this is left at Auto. Go back to the main Ai Tweaker Page Click on CPU Power Management CPU Ratio - Auto Enhanced Intel SpeedStep Tech - Enabled Turbo Mode - Enabled Everything else on this page is left at Auto Go back to the main Ai Tweaker page. Click on CPU Configuration Hyper-threading - Disabled. Active Processor Cores - All Intell Virtualization Tech - Enabled Everything else is left alone. Leave at Auto or whatever setting is there. That's it! On the other pages you can do whatever. Now, this was for an i7 2600K so not sure these settings will work on your i5 2500K. If they don't work, your computer will not boot up and you can go back into the BIOS and select the Optimized Default Settings. Down in the AVSIM Hardware Forum there's a pinned topic where people posted pictures of their BIOS settings for an overclock. You might look down there for an i5 2500K. Hope this helps. Best regards, Jim 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
July 5, 201312 yr Author I shall have a look, thank you for the information Just reinstalled again! But this time to E:/Games still have the same APPCRASH c000000005 code, a few google responses claimed it could be due to access errors..Managed to get it to load once until I rebooted my pc by updating my nVidia drivers to the latest, but now it's back to the appcrash error
July 5, 201312 yr Just reinstalled again! But this time to E:/Games still have the same APPCRASH c000000005 code, a few google responses claimed it could be due to access errors.. Which strongly indicates a problem with your OC settings. You can save your current OC by going to the last page in the ASUS BIOS and then saving your current configuration. You can then return ASUS settings to normal or the default. If you are still getting crashes, then you can always go back in and retrieve your former OC settings. Best regards, Jim 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
Create an account or sign in to comment