LeeWang

I still get CTD with 3.719, but less frequent now. Thanks for efferts pete, I sticking with FSUIPC 3.70. Lee

sorry pete, you must of misunderstood. I was unable to do any tests overweekend because of other comments (busy). You very rude man. Sorry for my bad english. Just trying to help. I will stop bothering you. Good luck Lee

Pete, 3.7.18 is still causing CTD's and now strange hang problem. Happen within 1-5 minute of selecting different aircraft. I start FS2004 and select fly (default aircraft is Cessna 172). I hit S key to go to spot view. I then click on aircraft - select aircraft. The select aircraft window opens up with default C172. I then use my mouse wheel to select a different aircraft like the B737-400. I then do the same and select the mooney. I then go back to the b737-400. I then select the piper cub etc. FS2004 will eventually CTD or now hang using 3.7.18. When FS2004 hangs, my FS2004 menu disappears and I no longer have a menu to select anything? Pete, I read in your forums that you use the NO CD crack? I am not. I have my FS2004 CD4 in my cdrom and a process named ~e5d141.tmp is running (related to Microsoft copywirte). Could this an issue? Lee

Hi Pete.. Sorry but I have little time to play with FS9 and test the new FSUIPC version. But I wonder what a handful of people have in common to create a problem like this? We all have different hardware, but I wonder if CH Manager is in conflict with FSUIPC? I used CH Manager 4.0 and then tried CH manager 4.1 and still had CTD's. After I reformatted my HDD, I had a clean machine with only CH manager 4.1 installed, WinXP SP2 updated via microsoft updates, and FS2004 with patch installed. No other software installed, no fs9 addons etc. I have since re-installed all my add-ons, and tweaked many things, but have found no time to fly :cry: So, do other people have CH Manager installed? Lee

Pete.. Let me play with FSUIPC 3.7.17 some more before you start changing things with it. I tested it on my development HDD, and it crashed very quickly which has more programs installed on it. When I use FSUIPC 3.7.1.7 on my "Flying only" HDD, which contains only XP, CH Control Manger 4.1 and FS9.1, I have not re-created the CTD. But I did have one strange hang event when switching aircraft (which I never had before). This time FS9 closed and indicated it had a problem and needed to close. Maybe or may not be related. First time seeing that. Event log showed: Hanging application FS9.EXE, version 9.1.0.40901, hang module hungapp, version 0.0.0.0, hang address 0x00000000. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. which means nothing... Lee

Pete, My Video Card is MSI NVidia Geforce 6800GS My MB is MSI K8N Neo4 (AMD 3500+ single core 939 Socket) (Nforce4 Chipset). Thanks for FSUIPC 3.717. Just tried it and I still get CTD's with same error in Windows XP event log. If I just fly, the CTD is very random. It can be 1 minute, 15minutes, or 30 minutes etc. I think it has to do how many times I switch views while flying before CTD happens. When I switch between default aircraft as described above, it happens with in minutes. CTD happens mainly when swtiching from B737 to the Piper cub or to Mooney and back to the B737. It also happens when switching to the B777, or B747. I wish people at Avsim (the registerd users) would report their findings here. Maybe you could get more data from them to help with this. http://forums.avsim.net/dcboard.php?az=7819&page= FSUIPC 3.70 can be found here: http://files.fsnordic.net/cool/ Lee

"Well, that isn't "fixed" in my book." Correct statement. FSUIPC 3.716 causing CTD also.. moved back to 3.70. and all is fine. "I would have thought obvious to try" I did not post entire log and I left out all the obvious steps. I never had CTD's before. My system has been rock solid for 2 years, with no hardware changes. After my CTD's started about 1-2 months ago, I assume I had intermittent hardware problem (memory, sound card, Video card, etc). Almost went out and bought different memory until decieded to format C: and start over. "The only posting related to FSUIPC in that thread is your own. You say there "Read pete's forums and other have same problem." but that is very misleading as the only un-resolved post here like that is yours." Funny how some poeple have this CTD with FSUIPC 3.71 and others don't. If you read various forums, thier are many posts on CTD and FS9 just quiting of late. I'am I the only one with this? WebMaximus had ctd's. He went back to FSUIPC 3.70 and so far so good? http://forums.avsim.net/dcboard.php?az=819&page=2 Raptor483 had CTD's. He went back to FSUIPC 3.70. http://forums.avsim.net/dcboard.php?az==174&page= FSUIPC 3.716 is causing CTD's also. I move on, and won't waste your time. Good luck and all the best Pete Lee

Thanks Pete for suggestions and support. I did not know of new version of FSUIPC until Bob at Avsim give me link to the beta FSUIC. I was using FSUIPC 3.71 from you home page. Assume that was the current version. Mistake on my part. I spend many days trying to resolve my CTD, and can confirm now it is fixed with FSUIPC 3.70 I will try the beta versions later, but rigt now to busy re-installing all my add-on aircraft (that require FSUIPC, which is why I install FSUIPC in first place). "You're not using internet explorer 7 are you?" No I use a removable HDD. My FS2004 HDD only has XP sp2 installed with IE6, and FS2004, and any supporting software like CH control mgr, FSmetar, FSrealtime, etc. No anti virus is installed on my FS2004 HDD (used only for flying). I don't use this HDD for internet use either, it only for playing FS2004 and nothing else. I have 2nd HDD (my FS2004 developement HDD) used for testing addons etc. I keep a basic log of things I did to resolve my CTD. Did not want to go in circles. Many searches in forums give me many things to try, and many such items I didn't write down. I did one step at a time, time consuming, but I had to find my recent CTD problem. Here is the log.. My error (CTD) 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. 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: 6. --------------------------------------------------------------------------------------------- Things I done --------------------------------------------------------------------------------------------- Under DXDIAG moved Sourd Acceleration down to Standard acceleration. Under DXDIAG disabled AGP Texture acceleration. In BIOS, changed Default memory voltage from 2.65v to 2.60v. - No CTD to date. - had CTD with Stardard acceleration. - Run memtest86 all night. No errors. have read posts that memtest86 runs clean and people still have ctd's. They replace memory and CTD fixed. - monitor memoy usage for mem leak. Commit Charge at 450676. Physical memory 2096624. when CTD happen commit charge always under 510000. - Removed 2nd stick of RAM 2Gb installed. Tested with sound Acceleration to FULL and had CTD. - Bump down to standard acceleration, basic, sound off in FS2004. Still CTD - Swapped stick of Ram. Still only one stick in (1GB). Sound at Standard acceleration. Still CTD - Reinstalled memeory stick. Now at 2GB again. Note. Memory chips are now in different slots then when I started. Did this next: Method 5: Disable NVIDIA Driver Helper Service To disable the NVIDIA Driver Help Service, follow these steps: 1. Click Start, click Run, type services.msc in the Open box, and then click OK. 2. Right-click Nvidia Driver Helper Service, and then click Properties. 3. In the Startup Type box, select Disabled. 4. Click OK, and then quit the Services program. If these steps do not correct the problem, go to the next method. - Entered BIOS and Disabled Onboard gigabit Lan, Disabled Onboard SiI3144 Raid, Disabled IEEE1394 Controller. Note: Onboard Gigabit Lan ROM was already disabled, I didn't change this. Also the Memory voltage was set at 2.65v. I tried 2.5v, and made no diff. Tried 2.60, still getting CTD's. Still got CTD Removed Sound card still getting ctd's. Tried different airports with no afcad's. Still CTD's Reseated video card, reinstalled sound card. deleted fs9.cfg file. During load is detected fssound.dll 1.50 as being old. accept yes. Removed FSConnect.dll and FSSound.dll V1.50 and no CTD. Reinstalled FSSound.dll 1.50 and now cdt. tested severals times. replaced FSSOund.dll with 1.50.1 and removed FSconnect.dll. Work for a while like this, then got one CDT. Appeared like FSConnect.dll and FSSound.dll conflict?? Currenly have FSConnect.dll removed and FSSound 1.5.0.1 removed. Installed FSSound 1.60.15 . Testing. Had three CTD with FSSound 1.60.15 installed and FSConnect.dll removed. Entered BIOS and changed PCI Express maximum payload size from 4096 to 256. Also changed my Anti-ALising from 4x to 2x Had one CTD Entered BIOS and changed PCI express max payload back to 4096. Changed memory voltage to auto. Still Had CTD Removed Soft Horizons textures. Still CTD Remove modified Lanuage.dll and reinstall default. still CTD. Removed All my scenery. Still CTD. Removed FS9.cfg and let rebuild. Testing no problems. Increased Res to 1280x960x32 - no problems. Re-installed my tweaked FS9.cfg file. CTD. CHanged my desktop res to 1024x768 changed FS res to 1024x768. Have my tweaked fs9.cfg installed. Had CTD.. Reinstalled New FS9.cfg file. Res set at 1280x960x32 CTD --------------------------- will continue on.... Suspect might have hardware issue causing CTD's. Sound card was removed. Never did remove the usenglishbig.gvp. also never removed the traffic bgl.s yet. ---------------- Reinstalled Soft horizons, language.dll, FSSound.dll CTD within 1 minute. delete OLEACC.DLL.. CTD reinstall OLEACC.DLL uninstall video driver 93.71 installed 81.85. video drivers. CTD. ------------------------------------- Re-enabled onboard sound in BIOS. Adjusted Memory DDR voltage from auto to 2.65v (back to default) Installed drivers for onboard sound Removed Sound blaster sound card. Testing... CTD.... Not a sound card issue. Must be video problem. -------------------------------------------- Deleted onboard sound drivers. Disabled Onboard sound in BIOS Reinstalled my SOund card. Removed 81.85 vid drivers. Install 84.21. CTD Install 85.97. CTD Intall 91.31. CTD Re-installed 93.71 vid drivers (that have work for months) CTD. time to start over - tomorrow. format hdd. Install window xp-sp2. apply all xp updates. update all system drivers: SyStem Drivers Installed: Nvidea Video card - 93.71_forceware_winxp2k_english_whql.exe Dell Monitor - R73595.exe installed. Refresh rate set to 75Hz. Nvidia nForce4 AMD Drivers for MotherBoard - 6.86_nforce_win2kxp_international_whql.exe Silcon Image SiI SoftRaid5 - 3114r5_x86_15100_logo.zip Marvel Yukon PCI-E Gigabit Ethernet - SetupYukonWin_x32w-v85673.zip Sound Blaster Audigy SE - SBA_PCDRV_LB_1_04_0061.exe AMD CPU WinXP Driver - amdcpusetup.exe (Driver Version 1.3.2.0 dated: 5/27/2006) install CH control manager 4.1 Reinstalled FS2004. used FS9.cfg that was produced at install No changes. Testing NO CTD.s Second day no CTD's Install FS2004 update 9.1. Testing no ctd Installed FSUIPC 3.71 and FSSound.dll 1.60.15 Testing 1 ctd. Still CTD's Removed FSSOUND.dll 1.60.15... Testing... Still CTD's.. Removed FSUIPC 3.71.... No CTD's Installed FSUIPC 3.71... Now CTD's again. Installed FSUIPC 3.70 Testing... No CTD's with FSUIPC 3.70.. ------------------------------------------------------------ I am currently using unregister version FSUIPC 3.70 and have no more CTD's. Will try the beta FSUIPC. Thanks Lee

Hi Pete. Sorry to bother you but I have a CTD (crash to desktop) problem with FSUIPC 3.71. I not a paying customer and use the unregister version, so don't expect support. Maybe CTD is because I use unregister version? I post only for a FYI for others in case they have CTDs. I spend 2 weeks finding my CTD cause. FSUIPC 3.71 is causing CTD on my Machine. FSUIPC 3.70 is ok. No CTD's with FSUIPC 3.70. I tried FSUIP 3.70 after reading this post: http://forums.simflight.com/viewtopic.phlight=ctd My CTD was random with FS9 while flying. CTD mainly would happen while switch veiws, either look left or go to spot view and boom, CTD. No error at all given. Only error is found in Windows XP-SP2 event log. This is error I get: 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. Another user post same error as mine on you site: http://forums.simflight.com/viewtopic.phlight=ctd and Jared has same error: http://forums.avsim.net/dcboard.php?az==174&page= I have formated HDD, Installed Win XP-SP2 and installed all updates. Then I install CH Control Manager 4.1. I use a CH Throttle, a CH pedals, and Microsoft FF2 joystick. I then install FS2004. Tested FS9 using default aircraft and no CTD's. I installed FS9 patch by running the update in the FS2004 folder. Tested with no CTD's I installed FSUIPC 3.71 and I have CTD's. I have no add-ons installed, all default. Even FS9.cfg is untouched. Only add FSUIPC 3.71.dll. I use the 4th FS9 CD in CDROM to Start up FS9. I can recreate the crash by doing this: 1. I save a flight and called it CTD test. It loads up the default b737 everytime. With parking brake set, I increase to full throttle. Look in all directions in 2D panel. 2. I hit the "S" key to go to spot view. 3. I than select another default aircraft, over and over until my CTD happens. I remain in spot view all the time. Within the first 5-10 aircraft selections, FS2004 will usually crash to desk top (CTD) with no error message. Also i note that by going back and forth from Full screen to window, CTD sometime happen. With FSUIPC 3.70 I have no error doing this. I post this for other in case the have same problem Thanks Pete. Lee