October 31, 201213 yr Hi I had 2 FE.dll ctds and 4 Out of Memory crashes in less than 2 hours. I tried like 7 times in the same airport, in the same gate, same FS time and the same aircraft. 6 attempts, 6 ctds. Since moving to Windows 7 and upgrading to intel i5 2500k, I never had Out of Memory crashes, it says my hard drive is full. From what I have been searching, FE.dll is mainly caused by faulty textures, either AI or scenery. And I had OOM when using XP years ago and had hard times dealing with OOM and BSOD, and Windows 7 has been stable until today. My question is, can faulty texture (FE.dll) cause Out of Memory? can faulty textures be read as Out of Memory? I have 4 GB RAM, and my hard drives are far from full. What should I do now, run a tool that allows all the textures to DXT3? Then I moved to a bigger airport, way bigger... with 100% traffic, and NO CRASHES at all, either FE.dll or OOM. I really appreciate your help and suggestions Respectully
October 31, 201213 yr Hi I had 2 FE.dll ctds and 4 Out of Memory crashes in less than 2 hours. I tried like 7 times in the same airport, in the same gate, same FS time and the same aircraft. 6 attempts, 6 ctds. Since moving to Windows 7 and upgrading to intel i5 2500k, I never had Out of Memory crashes, it says my hard drive is full. From what I have been searching, FE.dll is mainly caused by faulty textures, either AI or scenery. And I had OOM when using XP years ago and had hard times dealing with OOM and BSOD, and Windows 7 has been stable until today. My question is, can faulty texture (FE.dll) cause Out of Memory? can faulty textures be read as Out of Memory? I have 4 GB RAM, and my hard drives are far from full. What should I do now, run a tool that allows all the textures to DXT3? Then I moved to a bigger airport, way bigger... with 100% traffic, and NO CRASHES at all, either FE.dll or OOM. I really appreciate your help and suggestions Respectully The times that I have had a fe.dll ctd it has been a corrupt AI texture. Since it could be just one aircraft livery, you might not see it very often (ie at another airport even with way more traffic) but the continued crashing at the same position makes me suspect that. What to do: go through any AI and see what aircraft are on the airport when the crash happens - get ACA2005 and use the timetabe feature if you don't have it already... Then try and isolate which is the offending aircraft and replace it's textures. You could also think about trying to go through looking for a bmp file with an odd size, but that has never had any mileage for me! Good luck! Geoff
October 31, 201213 yr AC2005 is an invaluable tool indeed. Quick and dirty test though, disable all AI - if that works then you know for certain it's AI related. THEN go hunting. Regards, Mark
October 31, 201213 yr If you are using ultimate terrain like me I was getting a FE.DLL error around the New York area, a corrupt file or texture was the cause. I re-downloaded UT USA and re-installed it and seems to have solved my problem.
November 1, 201213 yr Thank You guys for the suggestions. Yes I guess the AI texture(s) is the cause. I am using WoAI for global traffic and IMT for south east asia regions. I am downloading AC2005 now. As an addition, I patch my fs9.exe with 4GB switch. I have never encountered any Out of Memory since moving to windows 7, I am not sure I need that patch.. wont hurt to try Thanks
Create an account or sign in to comment