There are now a couple of airports (possibly more, but I only find them by chance) which, when I load a flight through 'Create a Flight', cause my PC to crash (not just FS9, mind - the whole PC, blue screen and all). One is GMAD, another 'Halley' - part of Jim Keir's Antarctic scenery addon ("brunt.zip").What I don't understand is why loading a flight can cause my PC to crash. I never have any problems other than when I am in FS9. If it were a hardware problem, surely it wouldn't restrict itself to Flight Simulator, and just a few locations at that? Maybe someone can help explain what might be going on here? The STOP error is as below:http://img.photobucket.com/albums/v68/martinlest/STOP.jpgThanks,Martin

BTW, the crash always occurs during 'Loading Terrain', if that's any help.M.

I strongly suspect it's your video card. Make sure it is properly seated and if so, you should try uninstalling/reinstalling the card drivers. I had a BSOD once like yours and it turned out to be a failing hard drive. Have you checked the system event viewer and look for any error messages. Possibly the event viewer will provide you more information. Also, check your FS9.cfg and make sure your video card has been properly identified under "DISPLAY". Hope this helps.Best regards,JimYoung

Hi Jim. As this is a laptop, that's no easy task. I have already resinstalled the drivers (should have siad in the first post - sorry). In Event Viewer Errors ('Event 1003') are shown under System - System Error (102). The parameters are similar each time, apart from 3.:Error code 1000008e, parameter1 c000008e, parameter2 20f3faac, parameter3 f1684a54, parameter4 00000000.Error code 1000008e, parameter1 c000008e, parameter2 20f3faac, parameter3 f1223a54, parameter4 00000000.Error code 1000008e, parameter1 c000008e, parameter2 20f3faac, parameter3 f1955a54, parameter4 00000000.None of that means much to me I'm afraid. Dell just replied to my e-mail saying I should reinstall Windows! Typical - their cure-all solution. Forget it, for now at least.I'll double-check the FS9.cfg Thanks,Martin

Gooblygook to me too. But I Googled "error code 1000008e" and I think you might find this link helpful:http://www.experts-exchange.com/Operating_...Q_20912978.htmlBest regards,JimYoung

Martin: the first thing I would do is disable those two scenery areas, and then restart and create a flight at GMAD, for example, and see if you still get the BSOD.That way, you can isolate the source of the problem.I have read that the way in which textures are used with some add-on sceneries, will cause such an error. In your FS9.cfg file, in the section for your video driver parameters, there are some entries that can go there, such as TextureAGP=0. I would research those entries here on the forum. I think the way in which those add-on scenery developers use their textures, is the source of your BSOD.Rhett

I'll certainly follow up those leads and suggestions. Unfortunately I have to go away for two months today (some residential teaching) so will not have access to my Flight Simulator PC for most of that time, home visits apart. I'll post back here if there is any progress!Thanks,Martin

Last time this happened to me it turned out it was a bad memory stick.I had to use the memtest program and by trial and error found the offendeding stick. After removal, it hasn't happened since.RegardsDavid

I had the same issue on my laptop. Nothing to do with flight sim. I took out that extra 1 gig ram memory (out the 2 gig ram) and the problem went away. I had bad memory hardware.just try rebooting again. if it keeps happening. it could be your memory. loading sceneries means its just using those parts of the memory?Its a possibility.Manny

I am now away and will not have access to my FS9 PC for some weeks, but I will run a MemTest. Dell replaced faulty memory sticks a few months ago - it'll be a real pain if they new ones are faulty as well! M.

Still away from home (working), but in another two weeks will be back and will be able to test things out a bit more. (Just wanted to keep this thread going!).Dell insist I simply wipe my hard drive and start again. Typical ! (The college where I am teaching is just outside Heathrow airport, right under the flight path from runways 27L & 27R. Planes flying over at very low altitude all day. I can't concentrate on my work at all - I spend all day looking up at the sky! It's REALLY making me regret my decision to give up training as a pilot for British Airways, thirty years ago! Torture.....).Martin :-)

I am 99% sure now that this is a software problem, as by installing some extra scenery (bgl) files into FS9 I have managed to cure the problem at some of the airports. Doubtless when I find the root cause at other locations I will be able to fix those as well. Odd though that the error causes XP to crash to a blue screen - I'd have thought that FS9 would crash, but not the PC.(One of the problems was worx9.zip - FACT, from AVSIM. I reinstalled it, adding the texture files to the main folder, but it still causes my PC to crash. No idea why).Martin

Martin,Please run Memtest86 ( http://www.memtest86.com/ ) as that error has nothing to do with software and everytning to do with drivers or Bios. I had the same BSOD and it turned out to be a bad stick of RAM.Cheers,John

John,I did run memtest - and it all works out OK, no errors found; I let it run for quite some time. I have so far found three airports that lead to the XP crash, and by removing one bgl file in each case (found by trial and error) the crash no longer happens. I've tried this several times, so I am pretty sure: with the bgls, crash: without, fine, FS9 loads the airport.Odd, I admit, but the proof of the pudding and all that.... !M.