Hi Everyone, 1stly let me apologise for posting this message,you must all be sick of hearing about this by now,and 2ndly,I promise I haven't posted this message 'lightly',I've spent the last 4-5 weeks trying to sort the problem out for myself before bringing it to you guys-have visited numerous forums and read God knows how many posts on the subject,none of which have seemed to help.Now I'm just totally confused and fed up,so I thought I'd bring my problem to the experts!!! ;-)To help you so far,I think I've narrowed down the problem to one specific area,I only get CTDs when I'm connected to Squawkbox/VATSIM-doing what I call 'online' flights. FS9 works fine when I'm doing 'offline' flights (still connected to the net for charts e.t.c,but not through Squawkbox) and doesn't CTD at all,but as soon as I connect to Squawkbox the CTDs start.This is where I'm at now:- tried EVERYTHING-updates-patches e.t.c and resorted to drastic measures-a format and a clean install of Windows XP Pro with service pack 2. Installed FS9 (its the latest version 9.1) installed PMDG 737 600-700 and PMDG 737 800-900 (both latest versions),and finally Squawkbox 3. Am STILL getting totally random CTDs-anytime,any place any where,no pattern to them. They occur at any season,any time of day and at ANY point in the flight,even stationary at the gate waiting for clearence.Apart from the 2 planes,I have absolutely no add-ons whatsoever,no scenery,no nothing,just FS9 as it came out of the box with the 2 planes added on. Oh B.T.W FS9 CTD's with the default planes ('online') as well (tried it before i installed the PMDG's).Now,here's the kicker:-Took my computer over to a mates house as he said he wanted to help and may have a few ideas to try,and while I was there,actually managed to totally complete 2 'online' flights in Squawkbox,both from KMEM to KATL-one connected via an ADSL router and the other connected via an ADSL modem-ok guarenteed,there wasn't much traffic around at the time,but I DID complete them,which I've NEVER done before. Took my computer back to my house,did exactly the same flight-yup,you guessed it,CTD 5 mins into the flight. The ONLY differences between flights at my mates house and my house were....different phone line,different I.S.P and different moniter. So this raises 2 points 1:-either the 2 flights at my mates house were SUPREME coincidences or 2:-I'm left with 4 options:-1:-My computer doesn't like the colour of my bedroom (can't you tell I'm clutching at straws here!!!):-)2:-Its a telelphone line problem3:-Its an I.S.P problem (I'm with pipex 2MB connection,my mate is with BT 2MB connection).4:-It's a moniter problem (surely not???!!?!?)Just to throw a spanner in the works I called BT and they did a line check....everything was fine,no problems reported,so I'm now back to the I.S.P option.......tell me it CAN'T seriously be a moniter problem??!?!!My sound card (Audigy 2 ZS platinum pro) has an external drive which I didn't take to my mates house.Thinking it was that,I disconnected it-still CTD,I even removed the sound card altogether and used the onboard sound-still CTD.PLEASE PLEASE can someone help me,as my new hobby is being totally spoiled and I'm getting very disheartened with the whole thing.:-( If someone can find a solution to this problem for me,I'll gladly buy their alcohol for the next 24 months!!! :-) I promise you all,I really have tried almost everything I can think of. Thank you in advance to everyone who took the time to read this post and for any advice given.Very Best Wishes,Kimbers.P.S. I'm pretty thick,so could you please make all explanations idiot proof!!! :(ASUS P5P800 Motherboard.Intel Pentium 4 550 3.2ghz512MB PC 2700 RAMWestern Digital 80GB HDDRadeon 9200 SE graphics card (with latest CATALYST drivers)Audigy 2 ZS Platinum Pro sound card. (with external drive)AOC 14" LCD TFT moniter.Matshita DVD Rom (Don't laff!!! :()Liteon DVD-RW2 8cm Akasa case fans.D-Link DSL-502T ADSL Router.Pipex 2MB Broadband Connection.FS9 (9.1 version)PMDG 737NG 600-700 (latest version)PMDG 737 800-900 (latest version)FSUIPC 3.47 unregistered (came with the PMDG 737 600-700)Squawkbox 3.CH Flightsim Yoke.Windows XP ProfessionalService Pack 2.

Had a similar problem some time ago when I kept getting line-drop through lack of signal. Although BT did a line check and said there was no problem I asked that they turn the gain up a bit and voila - no problems any more. I'm clutching at straws too but one never knows.Any chance your pal can bring his computer to your house so you can check out the ISP angle?

I was having similair problems for about 2 weeks. I was about to format MY PC and sling FS2004 into the bin along with my

Thanks for all the help and advice guys,I REALLY appreciate it. I'll definitely try the 'line gain' thing. I'm just about running out of ideas here.Maybe I should have said earlier but,FS2002 runs perfectly (same add on aircraft) through Squawkbox,never had a crash,but I realise FS9 is a completely different animal altogether. I just resent having to go back to 2002 just to complete a flight after seeing the graphics in FS9 and plus the addition of taxi/rwy markers and lights makes FS9 so much more realistic.After my post last night I tried a flight from KMEM to KDFW and it crashed as I was turning onto final approach.I managed to retrieve this from the event log,but havent a clue what it all means.Can anyone decipher it??? :-Event Type: ErrorEvent Source: Microsoft Flight Simulator 9.0Event Category: NoneEvent ID: 1000Date: 30/05/2005Time: 04:47:57User: N/AComputer: ****************Description:The description for Event ID ( 1000 ) in Source ( Microsoft Flight Simulator 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: fs9.exe, 9.1.0.40901, d3d9.dll, 5.3.2600.2180, 0002d05c.Data:0000: 41 70 70 6c 69 63 61 74 Applicat0008: 69 6f 6e 20 46 61 69 6c ion Fail0010: 75 72 65 20 20 66 73 39 ure fs90018: 2e 65 78 65 20 39 2e 31 .exe 9.10020: 2e 30 2e 34 30 39 30 31 .0.409010028: 20 69 6e 20 64 33 64 39 in d3d90030: 2e 64 6c 6c 20 35 2e 33 .dll 5.30038: 2e 32 36 30 30 2e 32 31 .2600.210040: 38 30 20 61 74 20 6f 66 80 at of0048: 66 73 65 74 20 30 30 30 fset 0000050: 32 64 30 35 63 0d 0a 2d05c.. Nice idea about bringing my mates computer to my house Bill,I'll give it a try....infact I'll try ANYTHING to get this #### thing working. If someone told me to dance around a cup of camel urine totally naked at midnight on a full moon to get it working....I'd try that!!! :-)How desperate am I???!!?!?! Thanks again to all.Best Wishes,Kimbers.

D3d9.dll is an ActiveX file and required by Windows. I searched google and some people were having problems with on-line games because the d3d9.dll was missing. FS9 may be calling for this dll and it's not there. Make sure it is on your system and in your Windows/System folder. Reinstall DirectX if necessary. Hope this helps.Jim

Have you posted in the Procontroller and Sqawkbox Support Forum? It's found on the Avsim Forum page about half-way down.I Googled your Event ID:1000 FS9 and it is apparently a known item. In some cases, causes could be traced to add-ons; scenery, afcad, planes, panels, certain GPS gauges, etc., but you seem to have eliminated any of these. However, error messages can be generic in nature and not always pointing to the direct cause, but instead to a symptom; maybe the suggested forum above will prove more valuable in tracking your problem.

Hey Kimbers,If you have truly spent that much time to get your system to work and still no luck I would look into a professional. Check out www.FSGS.com. They do "system unification". They will go through your entire system with you step-by-step. From what I see they spend hours with you on your system and you do not pay unless you are satisfied. $60US I think. If you value your time, this is a bargain!Can't hurt to look...

Hey Jim, Thank you for your time and help searching for a solution to my problem.I've checked and I've got 2 d3d9.dlls.One in C:WINDOWSSystem32 and the other in C:WINDOWSServicePackFilesi386. Is this a problem,should there only be one of them???All The Best,Kimbers

Hey GCBarni, Thank you as well for taking the time and troubleto search for a solution to my problem,infact a huge thank you to EVERYONE that replied to my post with ideas and possible solutions.Big respect to you all.As soon as I've finished writing this I'll copy/paste my 1st post onto the forum that you suggested.Once again,huge thanks all roundVery Best Wishes,Kimbers.

I have the same dll's in my system 32 folder and i386. The one in the i386 folder is older though and probably a backup when WinXP SP2 was installed as I understand SP2 upgraded this dll. The one in the system 32 folder is required and should not be removed. Make sure it is the latest version (right click on the dll and check properties). My version is 5.03.2600.2180. Again I suggest you do a google search at google.com and do a seach for d3d9.dll. There are several forums and discussions concerning this dll and something there may apply to you. Good luck in getting this issue resolved.Jim

Hey Everyone, I think I may have solved my problem. There was one piece of information I forgot to mention that may have saved everyone some of their precious time and trouble looking for solutions for me.....I'm using NOD32 anti-virus.....this will become clear in a minute.The strange thing is,if I use the original fs9.exe thats on Disk 4,when it crashes,it crashes straight to the desktop,creates an 'error' in the event log,but doesn't say what the source of the error is,so I had no way of tracing what or where the error was coming from. But if I use the 'other' fs9.exe from Microsoft (the disks have been in my bottom drawer for the last 2 days,but I'm still using the program)when it crashes I get the 'Windows encountered a problem and the program needs to be shut down' e.t.c message and an error log is created and this time it tells me that the problem is to do with fs9.exe and imon.dll....which seems to point to NOD32.After a little more homework,I found a post where someone had EXACTLY the same problem,and was told by NOD32 tech to exclude fs9.exe and the FSFDT folder (where do i find that folder please,can't see it anywhere??) from AMON and this would probably cure the problem.Also,I found a post where someone had written 'FS does not like multiplayer with NOD32 (tested with FS2004).Crashes occurred with FS9.1',so hopefully I'm on the right track. Haven't had the guts to try it yet,but I'll give it a go when I get home from work tonight and let you all know how it goes. Thanks again to everyone for all their help and time. Keep your fingers crossed for me please!!!Best Wishes,Kimbers.

HI Kimbers,I totally empathize with you. I have CTD problems similar to you. I have had enough though and i am throwing the towel in. I have spent hours,no sorry that is an understatemnet, years, on trying to get FS9 the way I wanted it, and yes I came so close but oh no....Microsoft had to spoil it.....Crash. I am honestly sick of it. Sure I know, itis a complext thing etc.resignedA very very very disheartened X simmerpaul

Hey Kinbers. I was just reading your post and of course the first thing tht popped in my head was NOD32. It was probably me who posted on this topic of NOD32. It took me a year and a half to figure it out. The first thing you should tis UNINSTALL NOD32 all together. Then try and fly you FS while connected to vatsim. If all works out reinstall NOD32 BUT there are some things you have to set up in NOD32 for it to work. But FIRST UNINSTALL it and try FS. IF bo CTD's then you know it is NOD32. If you need help let me know and I can hook up with you on skype. Hey if it IS NOD32 and that WAS my post you were reading, do I still get the free booze? lol. j/kJack