Guys I hope someone can really help me here. I have narrowed down a CTD problem I am having ( at least i hope i did). It happens when trying to connect to vatsim. I just flew my pmdg 747 (NOT ONLINE) for about 1200 miles with NO probs. Now when i start to connect to vatsim using FSINN (not yet connected but you know when you click the FSINN on the top of the fsinn control panel and it starts a mutliplayer session) then it crashes. Sometimes right away, sometimes 5 minsutes but sooner or latewr it crashes. I got rid of fsuipc and reinstalled it with new .ini file. This is getting very frustrating and I hope someone has had the same problem at some point in time and can lend me a hand. It was working fine for the last 2 months with no problem. Maybe it has to do with files that pmdg 747 installed. i tried with the default C172 but still crashes. Thx guys.

Go into your event viewer and copy past here exactly what the error is. That will help us out allot in figuring this out...

Thx for the suggestion. i take it the box that appears after a program crashes and say "such and such crashed due to device driver or whatever crashed it". i don't even get that box that pops up so i have no leads.

If you

Event Type: ErrorEvent Source: Event Category: NoneEvent ID: 0Date: 07/08/2005Time: 6:05:38 PMUser: N/AComputer: mineDescription:The description for Event ID ( 0 ) in Source ( ) 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: 7.Data:0000: 71 67 88 72 bb b9 ca 75 qg?r

Great, first off it would help if you knew an area in FS that crashed faithfully everytime you tried it. That's where to start. Find a faithful CTD spot and then find the .dll... Next go into your modules folder and remove each .dll one at a time (as you remove one put the other one back) until you find the problem .dll. Report back to us the problem .dll.

I don't see "Administrative Tools". I believe I am the administrator, as this is a single user PC. Any suggestions?Tony

Tony,Try Start/Control Panel/Administrative tools (assuming you're using WinXP).Hope this helps,Dugald

The problem with removing these dll's is that most of them are required to run FS9. Like I said, it only happens when connecting to vatsim with both fsinn and sb3. any ideas?

Reinstall the involved applications that run on top of FS9. I could send you a screenshot of all the critical .dlls to run FS9. Any of those as well could have gotten corrupted. You can't hurt FS9 by testing. You want to get to the bottom of this as the problem .dll could be something you totally didn't expect. I just had a similar problem only to find it was Lago's VSM .dll's. When you run various uninstallers (including the default Add & Remove) many times critical information is mistakenly deleted out of the registry. What's ironic is crap that should be gone actually stays most of the time but critical stuff can disappear.I had to reinstall FSE to solve a CTD problem that happened over various GA airports that I never thought about applying scenery objects to. I could be flying at 28,000ft over the middle of Georgia and have a CTD. Who would have ever thought Lago's .dll's for FSE and Emma Field would have been the problem. I reinstalled FSE and the problems were solved. Whatever information that had gotten deleted out the registry a reinstall fixed it. I was blaming everyone from Flight'1's UT USA to Ariane. Investigation proved something totally different. I would be willing to bet you deleted something (might not be related to FS at all) right before this problem started. A FS .dll somewhere needed that information to run and now the link is broken causing a problem with a totally unrelated add-on. The great thing is the event viewer log is telling you a .dll is looking for something. Your problem is half solved, you just need to go into the modules folder and find the problem .dll. As you go through them and find FS refusing to load (critical .dll), that excludes that particular .dll from being the problem child. Put it back and move to the next. It's not rocket science. If you don't do this, reinstalling FS is only going to produce the same problems you had before until you mistakenly run across the add-on that contains the critical information the original problem was looking for in the registry. I'd rather make my life easier and go through the modules folder instead.With computers you have to being willing to troubleshoot. The last thing anyone should do is reinstall FS9. You do yourself and injustice by not finding out the root cause of issues.

Ok I have tried just about every dll that isnt required to load fs but it keeps crashing. Why does it crash ONLY when i connect to vatsim? thats what i cant figure out

How are you connecting to Vatsim???

With both remote computer and with SB3 on the same computer as FS.

SB3???

squawkbox 3? You never tried it???????