October 30, 201213 yr Try a system restore. Restore it back to the soonest time you can remember that you didn't have this problem
October 30, 201213 yr I remember I had a very similar problem with FS9 some years back and it had something to to with landclass files for roads. Did you also remove all landclass files when unchecking your add-ons? Another problem is that some addons REPLACE default scenery bgls. These are very difficult to trace but to find out if this is the case you should back up your scenery/world/scenery folder and then delete it. Put in the scenery/world/scenery folder from your cdefault FS9 install and see if your problem still persists. Good luck! Sascha Sascha Rieger | EVO Developer What is EVO • How to get Evo 2016 • FS9 Evolution Forum
October 30, 201213 yr Wouldn't happen to be on the Homeland Security No Fly list? I was about to ask the same question when I saw this reply. Watch out for F-16's Chris Magnus HR Manager Air Jamaica Virtual Airlines and Cargo (http://www.airjamaicavirtualairlinesandcargo.org)
October 30, 201213 yr This might be a little OT, however it might make things easier. Not sure why you need a separate install for multi-player, but if you rename that fs9.exe to something like fs9_multi.exe it will generate a fs9_multi.cfg and allow you to have different settings than your non-online fs9.cfg without having to switch back and forth between the two. regards, Joe The best gift you can give your children is your time.
October 30, 201213 yr Download and install App Crash View - http://www.nirsoft.net/utils/app_crash_view.html and copy and paste the information for the latest crash here. Thanks. 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
October 31, 201213 yr Author Hey! First of all this... I made every addon scenery another time inactive, so I did already twice. There were 5 folders that I could nog make inactive, all in the main scenery folder of FS9, i.e.Defaualt Terrain, Default Scenery, Generic Library, Vehicle Libraries and Propeller Objects, so I tried these 5 items by replacing them with the original clean ones, but that did not help neighter. The result of the CrashView App is hereunder ( Plse note that I added the duych translation as it was available ) Version=1 EventType=APPCRASH EventTime=129961437114148667 ReportType=2 Consent=1 UploadTime=129961437114608694 ReportIdentifier=4b560aec-2330-11e2-92fc-38607713b92a IntegratorReportIdentifier=4b560aeb-2330-11e2-92fc-38607713b92a WOW64=1 Response.type=4 Sig[0].Name=Naam van de toepassing Sig[0].Value=fs9.exe Sig[1].Name=Versie van toepassing Sig[1].Value=9.1.0.40901 Sig[2].Name=Tijdstempel van toepassing Sig[2].Value=4135a208 Sig[3].Name=Naam van foutmodule Sig[3].Value=StackHash_fb8b Sig[4].Name=Versie van foutmodule Sig[4].Value=0.0.0.0 Sig[5].Name=Tijdstempel van foutmodule Sig[5].Value=00000000 Sig[6].Name=Uitzonderingscode Sig[6].Value=c0000005 Sig[7].Name=Uitzonderingsmarge Sig[7].Value=00000000 DynamicSig[1].Name=Versie van besturingssysteem DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Landinstelling-id DynamicSig[2].Value=2067 DynamicSig[22].Name=Aanvullende informatie 1 DynamicSig[22].Value=fb8b DynamicSig[23].Name=Aanvullende informatie 2 DynamicSig[23].Value=fb8bd1bf7dcc44d047c58f37f56ad727 DynamicSig[24].Name=Aanvullende informatie 3 DynamicSig[24].Value=fa63 DynamicSig[25].Name=Aanvullende informatie 4 DynamicSig[25].Value=fa63c80ebf2b9d98cfa9fc211d9a92ad UI[2]=E:\FS9\fs9.exe UI[3]=Microsoft Flight Simulator werkt niet meer UI[4]=U kunt online naar een oplossing voor het probleem zoeken. UI[5]=Online naar een oplossing zoeken en dit programma sluiten UI[6]=Later online naar een oplossing zoeken en dit programma sluiten UI[7]=Het programma sluiten LoadedModule[0]=E:\FS9\fs9.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\syswow64\USER32.dll LoadedModule[5]=C:\Windows\syswow64\GDI32.dll LoadedModule[6]=C:\Windows\syswow64\LPK.dll LoadedModule[7]=C:\Windows\syswow64\USP10.dll LoadedModule[8]=C:\Windows\syswow64\msvcrt.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\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll LoadedModule[15]=E:\FS9\SHFOLDER.dll LoadedModule[16]=C:\Windows\system32\WINMM.dll LoadedModule[17]=C:\Windows\syswow64\IMM32.dll LoadedModule[18]=C:\Windows\syswow64\MSCTF.dll LoadedModule[19]=C:\Windows\system32\MSACM32.dll LoadedModule[20]=C:\Windows\system32\VERSION.dll LoadedModule[21]=E:\FS9\MSVCR70.dll LoadedModule[22]=E:\FS9\MFC70.DLL LoadedModule[23]=C:\Windows\system32\OLEACC.dll LoadedModule[24]=C:\Windows\syswow64\ole32.dll LoadedModule[25]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[28]=E:\FS9\MSVCP70.dll LoadedModule[29]=C:\Windows\system32\apphelp.dll LoadedModule[30]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[31]=C:\Windows\system32\UxTheme.dll LoadedModule[32]=C:\Windows\system32\samcli.dll LoadedModule[33]=C:\Windows\system32\sfc.dll LoadedModule[34]=C:\Windows\system32\sfc_os.DLL LoadedModule[35]=C:\Windows\system32\USERENV.dll LoadedModule[36]=C:\Windows\system32\profapi.dll LoadedModule[37]=C:\Windows\system32\dwmapi.dll LoadedModule[38]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[39]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[40]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[41]=C:\Windows\syswow64\urlmon.dll LoadedModule[42]=C:\Windows\syswow64\iertutil.dll LoadedModule[43]=C:\Windows\syswow64\WININET.dll LoadedModule[44]=C:\Windows\syswow64\Normaliz.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\system32\mscms.dll LoadedModule[50]=C:\Windows\system32\DDRAW.dll LoadedModule[51]=C:\Windows\system32\DCIMAN32.dll LoadedModule[52]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[53]=C:\Windows\syswow64\WS2_32.dll LoadedModule[54]=C:\Windows\syswow64\NSI.dll LoadedModule[55]=C:\Windows\system32\msi.dll LoadedModule[56]=C:\Windows\system32\D3D9.DLL LoadedModule[57]=C:\Windows\system32\d3d8thk.dll LoadedModule[58]=C:\Windows\system32\RICHED32.DLL LoadedModule[59]=E:\FS9\RICHED20.dll LoadedModule[60]=E:\FS9\language.dll LoadedModule[61]=C:\Windows\system32\nvd3dum.dll LoadedModule[62]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[63]=C:\ProgramData\Anti-phishing Domain Advisor\visicom_antiphishing.dll LoadedModule[64]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[65]=C:\Windows\SysWOW64\POWRPROF.dll LoadedModule[66]=C:\Windows\system32\CRYPTSP.dll LoadedModule[67]=C:\Windows\system32\rsaenh.dll LoadedModule[68]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[69]=C:\Windows\system32\winbrand.dll LoadedModule[70]=C:\Windows\system32\dsound.dll LoadedModule[71]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[72]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[73]=C:\Windows\syswow64\MSASN1.dll LoadedModule[74]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[75]=C:\Windows\system32\WINSTA.dll LoadedModule[76]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[77]=C:\Windows\system32\dxgi.dll LoadedModule[78]=E:\FS9\MODULES\ABLSCPT.DLL LoadedModule[79]=E:\FS9\MODULES\ACONTAIN.DLL LoadedModule[80]=E:\FS9\MODULES\UTIL.DLL LoadedModule[81]=E:\FS9\MODULES\ActiGate.dll LoadedModule[82]=E:\FS9\MODULES\ActiveCamera2004.dll LoadedModule[83]=C:\Windows\system32\DINPUT8.dll LoadedModule[84]=C:\Windows\system32\HID.DLL LoadedModule[85]=E:\FS9\MODULES\ActiveRadar.dll LoadedModule[86]=E:\FS9\MODULES\AeroCore.dll LoadedModule[87]=E:\FS9\MODULES\AFXModuleFS9.dll LoadedModule[88]=E:\FS9\MODULES\AI_PLAYR.DLL LoadedModule[89]=E:\FS9\MODULES\ATC.DLL LoadedModule[90]=E:\FS9\MODULES\autower.dll LoadedModule[91]=E:\FS9\MODULES\ConfigModule.dll LoadedModule[92]=E:\FS9\MODULES\CONTROLS.DLL LoadedModule[93]=E:\FS9\MODULES\FSUI.DLL LoadedModule[94]=E:\FS9\MODULES\DEMO.DLL LoadedModule[95]=E:\FS9\MODULES\DYNAMIC.DLL LoadedModule[96]=E:\FS9\MODULES\Erj145H.dll LoadedModule[97]=E:\FS9\MODULES\F1_view.dll LoadedModule[98]=E:\FS9\MODULES\FACILITIES.DLL LoadedModule[99]=E:\FS9\MODULES\FDSConnection.dll LoadedModule[100]=E:\FS9\MODULES\FE.DLL LoadedModule[101]=E:\FS9\MODULES\FLIGHT.DLL LoadedModule[102]=E:\FS9\MODULES\FSConnect.dll LoadedModule[103]=E:\FS9\MODULES\FSNav.dll LoadedModule[104]=E:\FS9\MODULES\FSSound.dll LoadedModule[105]=E:\FS9\MODULES\FSUIPC.dll LoadedModule[106]=E:\FS9\MODULES\G2D.DLL LoadedModule[107]=E:\FS9\pixomatic.dll LoadedModule[108]=E:\FS9\MODULES\G3D.DLL LoadedModule[109]=E:\FS9\MODULES\GLOBAL.DLL LoadedModule[110]=E:\FS9\MODULES\gps.DLL LoadedModule[111]=E:\FS9\MODULES\gps_export.dll LoadedModule[112]=E:\FS9\MODULES\INSTRUCTOR.DLL LoadedModule[113]=E:\FS9\MODULES\MAIN.DLL LoadedModule[114]=E:\FS9\MODULES\mpchat.DLL LoadedModule[115]=E:\FS9\MODULES\MULTIPLAYER.DLL LoadedModule[116]=E:\FS9\MODULES\PANELS.DLL LoadedModule[117]=E:\FS9\MODULES\REALITY.DLL LoadedModule[118]=E:\FS9\MODULES\Recorder.dll LoadedModule[119]=E:\FS9\MODULES\SIM1.dll LoadedModule[120]=E:\FS9\MODULES\SimScheduler.DLL LoadedModule[121]=E:\FS9\MODULES\SOUND.DLL LoadedModule[122]=E:\FS9\MODULES\SYMMAP.DLL LoadedModule[123]=E:\FS9\MODULES\TERRAIN.DLL LoadedModule[124]=E:\FS9\MODULES\Traffic.DLL LoadedModule[125]=E:\FS9\MODULES\TrafficInfo.DLL LoadedModule[126]=E:\FS9\MODULES\TrafficToolbox.dll LoadedModule[127]=E:\FS9\MODULES\ViMaCore2004.dll LoadedModule[128]=E:\FS9\MODULES\ViMaIScn.DLL LoadedModule[129]=E:\FS9\MODULES\VISUALFX.DLL LoadedModule[130]=E:\FS9\MODULES\Weather.DLL LoadedModule[131]=E:\FS9\MODULES\window.DLL LoadedModule[132]=C:\Windows\System32\MMDevApi.dll LoadedModule[133]=C:\Windows\System32\PROPSYS.dll LoadedModule[134]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[135]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.DLL LoadedModule[136]=C:\Windows\syswow64\imagehlp.dll LoadedModule[137]=C:\Windows\system32\ncrypt.dll LoadedModule[138]=C:\Windows\system32\bcrypt.dll LoadedModule[139]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[140]=C:\Windows\system32\GPAPI.dll LoadedModule[141]=C:\Windows\SysWOW64\msxml4.dll LoadedModule[142]=C:\Windows\system32\wdmaud.drv LoadedModule[143]=C:\Windows\system32\ksuser.dll LoadedModule[144]=C:\Windows\system32\AVRT.dll LoadedModule[145]=C:\Windows\system32\msacm32.drv LoadedModule[146]=C:\Windows\system32\midimap.dll LoadedModule[147]=C:\Windows\system32\dinput.DLL LoadedModule[148]=C:\Windows\system32\dpnet.dll LoadedModule[149]=C:\Windows\system32\msadp32.acm LoadedModule[150]=E:\FS9\GAUGES\Cessna.GAU LoadedModule[151]=E:\FS9\GAUGES\Cessna172.GAU LoadedModule[152]=E:\FS9\GAUGES\Cessna182s.GAU LoadedModule[153]=E:\FS9\GAUGES\Bendix_King_Radio.GAU LoadedModule[154]=E:\FS9\GAUGES\Magnetic_Compass.GAU LoadedModule[155]=E:\FS9\LAGO\FSE\FSEPlay.DLL FriendlyEventName=Werkt niet meer ConsentKey=APPCRASH AppName=Microsoft Flight Simulator AppPath=E:\FS9\fs9.exe End of the report, I hope something gices an indication of tghe occuring error? Greetz Jive1
October 31, 201213 yr Author Hey! I was looking deeper to all results of the CrashViewApp and could see that the first time the error happened wat in August. All the time since I was from time to time looking for the origin of the error. But, you know, that Win7 changes de date of installing a scenery, and so all my addon scenery folders have the same date of today. That means that I cannot find out what addon I installed in august on that particular date, or some days before... All the reports of CrashViewApp since then should then show some similar error. So if I will know what I will have to look for, I can possibly watch all the separate reports ( they are many, you know! ) and mauby we will be able to conclude something important?.... So please JIm, tell me what I have mainly looking for and so find the origin of the error? Greetz Jive1
October 31, 201213 yr I have had problems in the past with FS9 where you enter a route in the FMC and it causes FS to crash. Could be a waypoint is corrupt in your nav database. When it crashes are you using the same route? Craig
October 31, 201213 yr Author Hey! It crashes in almost the whole USA, and only there.... Greetz Jive1
October 31, 201213 yr Try allocating more memory to fs. From another forum: (originaly posted by NickN) For XP: disable hidden files and folders (including hidden OS files), then on the root C:\ you will find a file named: boot.ini Open it in notepad and add the following to the end of the OS boot line: /3GB/Userva=2560 EXAMPLE LINE EDIT: multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows XP Professsional" /fastdetect /3GB /Userva=2560 <---- add it here save and close the file reboot to set that back to default, simply remove the edit If you are using XP SP2 and are running a dual, quad, OR a single core Intel HYPERTHREAD processor, make sure this update is applied http://www.microsoft.com/downloads/details.aspx?familyid=C2AB5A48-8240-4934-BBD8-34FB8A0FCE3B&displaylang=en XP SP3 users do not need that update For Vista: WINDOWS VISTA ONLY: 1. Open a command prompt with Administration rights. You find the command prompt box under "Programs-Accessories-Command prompt" 2. Right Click the command prompt and select "run as administrator". 3. Enter in the box at the prompt: (copy/paste if you wish) bcdedit /set IncreaseUserVA 2560 and press enter 4. Reboot TO set that back to default in VISTA just start the command line prompt with Admin right again and type: bcdedit /set IncreaseUserVA 2048 Hit enter and reboot
October 31, 201213 yr You have the infamous StackHash error. Your memory is not properly configured. I have no known solution to StackHash errors other than invoking DEP but that is not possible with FS9. If you try to exclude FS9 in Data Execution Prevention (DEP), you'll get a message that FS9 cannot be excluded. Here's sort of a layman's explanation of StackHash errors: StackHashes are basically data from programs that are in memory, that is unreserved for that program. You see there is memory reserved for each program when it starts. The data from the program is extrapolated by the processor and sorted out in the processor cache if it overloads the processor cache it is feed into memory addresses that are reserved for that use, for the use of the processor to sort out the program, as it is loading. FS9 will fail, or crash when that code is copied into memory and it loses some data. Data loss happens because the memory still has static built up in it that was not cleared properly or it simply ran out of room and over wrote the memory that was previously there, stringing the data together confusing the processor when it tried to load fs9. The hexadecimal code, fb8b at the end of your StackHash error is the address in memory of the faulty code. One of the things I recommend frequently here is to reset your virtual memory (page file) so that it shows 'system managed size'. It seems to work best with this old FS9 application. Several people try to set their own settings and those are frequently wrong or FS9 doesn't like them. You also received the Memory_Access_Violation exception code (0000005) and that normally happens with every crash but it's another sign you have a system memory and/or virtual memory issue caused by corrupted scenery, bad memory, bad fs9 settings, etc. I was receiving StackHash errors in FSX and could not find a solution but discovered I always got the crash if I closed FSX in Full Screen mode with DX10 enabled. If I closed FSX in Windowed Mode, I would not get the StackHash error. (This can't happen with you as FS9 is not DX10 compatible). Besides my recommendations above, I would suggest disabling any addon scenery in the Scenery Library and see if you still get the error. If not, then you can start reenabling the scenery maybe 3-4 at a time until you find the problem. Good luck! Best regards, Jim I 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
October 31, 201213 yr The most likey reason you're crashing is a croupt texture in the scenery\world\texture folder. I you need to reinstall the original textures from the Disk 4 of FS9 install disc. If you're switching textures sets it's easy the one gets corrupt. I always keep the originals from disc 4 handy when FS9 crashes unexpectly Bill McIntyre Asus StrixB650E-F Gamer, AMD Ryzen 9 7900X3D, Corsair Titanium DDR5 64GB, Samsung 990 PRO-4TB M.2, (4) 2TB SSD's, Corsair H1150i liquid cooler, RTX 2080TI Founders Edition, (2) LG 34" HD Curved Monitor, Sound Blaster Audigy X, 1Kw PC Power & Cooling Power Supply, Corsair Obsidian Full tower Case. MSFS 2024, WIN11 Pro x64
November 1, 201213 yr Author Hey! My first question is... How do I allocate more memory to FS9? I recently doubled my RAM from 4Gig to 8Gig... Is'nt that good enough? Furthermore I'm flying in FS9, nothing to do with FSX.... And more.... I don't know StackHash error, my memory would not be properly configured.... What can I do, as a flightsimmer, and not being a computer specialist, in order to solve that? I'm affraid I cannot. And above that, the explanation on that error is complete like Chinese to me... Sorry! But according to your last words, Jim, I will even not be able to solve that StackHash error?... A crorrupt texture in the scenery\world\texture folder... I did already before replace all the textures in that folder, and I did it now again, but no solution. So I tried anything possible what has been told here, up to now nothing helps. About the memory not properly configured, or not enough allocated to FS9, maybe some solution could be in there, because I did not yet do something in that respect, because I'm possibly not a computer specialist... If somebody could explain me how to do both of thesethings, maybe I could find solution? Greetz Jive1
Create an account or sign in to comment