Just about every flight i have, end in a crash to desktop. Apparently it is the scenery.cfg that is responsible for this. What happens is this: Im on an airport (happens on both default and addon scenery), and I am taxiing either to thegate or to the active. As im just looking around inside the cockpit, the screen goes black. When it goes black the sounds disappear, but if I slam the brakes on, the message in red "BRAKES" still shows, andso does the all the menus. In other words its only the very sim itself that goes black.Sometimes it comes back again for a couple of seconds until it CTD. In the report the scenery.cfg is accused for this.Could a messy scenery.cfg file cause this?Thanks for all help!

What does it say exactly in the report?A messy scenery.cfg file can definitely cause issues. Personally, I use FlightSim Manager's scenery.cfg scanner regularly (Diagnostics Tools > Scenery tab > Scan for Errors), it will catch most errors and renumber it logically (and save a backup just in case).(Many solutions to get FlightSim Manager working can be found here, just ignore the rest of the discussion...)

What does it say exactly in the report?A messy scenery.cfg file can definitely cause issues. Personally, I use FlightSim Manager's scenery.cfg scanner regularly (Diagnostics Tools > Scenery tab > Scan for Errors), it will catch most errors and renumber it logically (and save a backup just in case).

The crash report (standard Windows XP) says the problem occured in the scenery.cfg. Its not more specific in human language than that. What puzzles me is that ive had my Fs9 the way it is now, for a long time. So when its starting to give trouble now, is a little bit strange. However, i have alot of addon scenery on it, and as well, ive experimentet with it so its not all scenery that works the way it should. But get this; Ive never crashed when am at airports where the addon scenery is messed up, only at default airports or addon scenery airportsthat are just fine.. I definetly give the scanner a try. I just dont want to start cleaning up all the scenery and installing it again. Thats gonna take me a week..!Thanks for the tip and the help!

Well, I did install the FSM with its patch. It works fine and I cleaned up my scenery.cfg file. Unfortunately my flightsim crashedagain, this time on approach to PMI. Here`s what the Win XP crash report had to say:"A fatal error occurredModName: util.dllIncluded in error report:C:documents and settings..\FS9..\fs9.cfg.txtC:documents and settings..\FS9..\dxdiag.xmlC:documents and settings..\FS9..\scenery.cfg"Once again, the screen suddenly, and without any warning, goes black. I was using the Flight1 Md80from CoolSky, and the scenery was Aerosoft Balearen&Gibraltar. FsPassengers keeps on running in the background (the blue square with pax info is visible when the screen goes black).What I dont understand about this, is the fact that my desktop computer is not connected to internet and I`ve hadmy FS9 setup the way it currently is, for a long time, so there is no newly installed addon that can be blamed for this.This is the first time it has happened while I was airborne. Usually FS9 will crash while Im still on the ground. Its really anoying, so any help will be very very appreciated.Thanks!

I`ve had my FS9 setup the way it currently is, for a long time, so there is no newly installed addon that can be blamed for this.

Are you 100% sure? It's enough to add one measly AI texture FS doesn't like and voil

Are you 100% sure? It's enough to add one measly AI texture FS doesn't like and voil

Most definately a hardware issue as you have not added much to FS9, very likely an overheating problem if you have not cleaned your case for a while.What about video drivers and DirectX, are they up to date?Hope you get some more feedback and figure this problem out.Good luck,

I have no idea what a util.dll is

Well, it's a FS dll, found in the modules folder, what it does exactly, other than crash FS, I'm not sure.:(

I havent cleaned my PC for too long, and I think its seriously time for a hard drive defrag.

Definitely also check for errors. (Or defrag, check, defrag.)If you're unsure on how to check for errors, try this KB article: http://support.microsoft.com/kb/315265. I'd go for the "Manual steps to run Chkdsk from My Computer or Windows Explorer" method. Be sure to check both boxes when you come across them.I also just found a great PDF with screen shots and everything, including checking the log afterwards: http://www.answersthatwork.com/Library_pages/winxp_home.htm, "Tip

Hello,http://adventure-unlimited.org/faultfinding.phpRegards.Gus.

You folks are great! Youve all given me loads of tips and tricks and whatever i need to getthis up and running again. Thank you very much!