Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

My CTD Log - Chapter 1: The problem

Featured Replies

Hi all,After one month, not being able to complete A SINGLE flight because of those CTDs, aplying all kind of fixes and not getting a single result I decided to wipe out FS from my computer and start all over again, this time I am going to check what is really happening and hopefully try and find a fix.This will be my log, I am going to write every single piece of data that I can and start solving one step at a time... This is my last try, it is really annoying, I do not think I will hold much more.I hope some fellow simmers that have my problem will be benefited from this research.Ok lets start with the begining..Computer: (self built)Processor: 3.2 Intel HTMoBo: 800FSBRAM: 1Gb 3200Video Card: Nvidia Gforce 5900 256MbHard drive: Barracuda 7200 120 GbSound Card: Audigy 2 ZSAll components to their factor clock speed, CPU temperature on the 60s C range.(This rig has 9 Fans )All XP updates installedAll drivers up to date (this one checked carefully)Symptoms:Random generated CTDs in every flight - Began 1 month ago. CTDs without warning - Freeze, no notification dialog afterCTDs With Warning: Frequently a sound lock - mouse Keyboard lock not responsive to any measure other thant hard-shut down of the computerCTDs with or Without warning/freeze and posterior error notification dialogNo other failure in any other game/application - I play Call of Duty multiplayer, sometimes for hours, without a single Hiccup (that directs me towards a conflict within FS rather that a Hardware-driver failure that would be more generalized)Since I had an infinity of Add Ons Payware and Freeware and after trying every single solution I could not find the culprit, so I decided to start with a clean copy of FS, out of the box to see if the CTDs repeated.My Prototype CTD flight is KTPA RSW PIE CTY SZW MAI CEW SJI PCU KMSY AT FL350This flight produces CTD always, sometimes just before RSW at FL250-270 and during cruise also very frequent After SJI on the descentSo I unistalled FS, completely, errased all plans and files outside from FS, and also errased the FS CFG file.So all in all with my settings on the default (most sliders to the right ) except:Mesh 60%AI: 30%Ok I start FS, no problems. This time I am trying this with a complete clean installation of FS.After 20 minutes with the default 737-400 at FL230 just before RSW I had a CTD - Sound Lock, not responsive to any measure. Had to shut down.This raise a few questions and some conclussions:1. The CTD is happening completly out of the box2. The CTD keeps its regular pattern, same presentation in the "clean" installation.now the Philosophical one: Should MS give attention to this issue?Next up: I am going to check my settings, try and find something strange in there. As I said I had my drivers up to date.Comments and suggestions are welcome, I am going to try and keep a ordered sequence here.

Ok, Here I am again.This will be the plan to discover the cause of this disease:1. Clean copy of FS - Check if CTD is present2. Check of settings inside FS, sliders etc.3. Check Drivers and comp settings, (this one After FS settings, since it is not logical that a otherwise healthy comp that crashes with only one software title could be the problem)4. Start applying fixes - Checking for CTDs in prototype flight5. Start installing - Add Ons - Checking for CTDs in prototype flightNext Up: MS Settings

Ok, Hi all:The only new thing here is this, in the Display settings under Hardware Tab in Display name:There are 2 entries:1. Nvdia Gforce FX 5950 Ultra.0 with several entries available in the resolution optionsAnd2. Nvdia Gforce FX 5950 Ultra.1 with a limited list of options inthe resolution display.This is repeated also in the CFG there are 2 entries with these names.If I errase the CFG and let FS build a new one I get the duplicates.Does anybody know the meaning of this? Is there any way to fix it????maybe remnants of old drivers? by the way my version of drivers for my Video card are 6.1.7.6 7/12/04 and the CTDs were ocurring with previous set of drivers.

If I could add to your list of things to do...3a. Remove left side from case and apply house fan to innards of computer. :-) In your first post your mentioned a temp of 60C. If that's what you're seeing at idle then you almost certainly have a heat problem.Hope this helps,Greg

Hi Gabriel."After 20 minutes with the default 737-400 at FL230 just before RSW I had a CTD - Sound Lock, not responsive to any measure. Had to shut down."If this only happens after 20 minutes it is certainly a hardware issue. I'm assumung the screen and sound lock up...and full screen mode? CTDs caused by the sim are not time dependant. You will find them at specific locations, and you can save a FLT file just prioir to the CTD, and it will repeat on all other systems. So far, only the seasonal CTD has been found to be repeatable on a default install.My computer will do the same thing if I have 8xAGP set... moving it to 4xAGP solved the problem. It also happens in CFS2. FS is a pretty good CPU, chipset, video workout for a PC... so if you have a weakness in your system, it will show up during flight.Dick

Yeah, it can be a real nightmare trying to track these problems, down.I have too had some CTD's in the past, but they have always been linked to either the "seasonal" bug, or dodgy AFCAD2 files, and it was nearly always dodgy AFCAD2 files that I had downloaded.I did also read a post over at Project AI that stated some AI repaints could cause CTD's, might be worth investigating.Good LuckDan.

As pointed out by Greg - your CPU temps are IMHO way too high.I would suggest that you obtain a copy of Motherboard Monitor 5, install it and set it to keep a text log. You can set the logging intervals to whatever you want - say every 10/15 secs would be a good start. Then - after the crash/freeze,. look at the log and see how temps and voltages have performed.My bet is that you'll find either the CPU temp has climbed just before the crash or there has been a "blip" in the voltages- equally important .Altho you say you have 9 fans - they don't seem to be doing much.............?Two years ago , using a K7S5A/xp2000/Ti4200/512MB DDRAM - I suffered similar problems (With FS2002) The eventual cure was better (more stable and powerful )PSU and much better ventilation/cooling.Present system (KT6V-LSR/xp3000/768mbDDRAM and TI4200) runs at (peak) around 44C after prolonged FS use- room temp right now 26C,System 32C, CPU 42CFS is highly CPU dependant and will use everything you have so temps can climb very quickly and produce the problems you describe.Voltages must be within 5% of the nominal ( +3.3, +5 and +12V) any major variation from these values will also contribute to instability in the system.You can get MBM5(Free) here.........www.pcworld.com/downloads/file_description/0%2Cfid%2C7309%2C00.aspGood luckDave

Hi Gabriel. Let me agree with the idea that the CPU Temp is too high. Since you did build your system ( as I did mine) let me just asked if you used thermal compound, and assuming that you did, did you do it EXACTLY the way that the manufacturer suggested. The reason that I ask is that I used too much the first time and had a similar temp problem. Cleaning off the excess and re-applying the compound properly did the trick. I was astonished at how little compound and how thin a layer it takes to do the job properly. Just a thought..Ed GreenKCLThttp://www.panelshop.com/DEV.jpghttp://www.globecargo.org/images/VAA_Sen_captain.jpg

Ok, guys.I've read all the responses. Thanks for your support. Yes the CTDs have not been time dependent, they appear from the cockpit preparation, up until the descent, so that would mean from the first 15mins up to 2 and a half hours during flight.I am going to download the application and start checking for the CPU temps here, the 60C figure comes from a cpu temperature sensor that I installed when I built the machine, so it is an external measure device.I know my MoBo also measures the Temperature from inside, Now the Plan is to compare if these measures are similar and what is the recommended/usual temp for a cpu/Mobo of its characteristics. I will do that at home tonight.Yesterday part of my "research was to check the fans, they are working alright, they are clean and seem to blow a lot of air... not sure why those temps so high.My CPU has no thermal compound, should that be the case?.Thanks, I am going to concentrate on this hardware issue... but what really worries me is that this started happening a month ago, and this comp run FS during a long time without any problem.Thaks I'll keep you guys posted.*EDIT*Thanks SoarPic, I am getting a house fan and blow the hell of that comp tonight! That should also give me a new sense of realism If I fly the wright brother's prototype with the **wind** on my face, wow this FS is as real as is gets!

I certainly would recommend the use of a Thermal Compound ( I use Artic Silver 3 but there are a number of them). My idle temps now run 29-31oC where they were in the 50-60oC range before. FS9 ( with FSMeteo etc. running) now maxes out at 41-43oC and CTD's a not a problem. I do run MotherBoard Monitor and would highly recommend that also.There is also the possibility that you are not getting really good air circulation inside the case. I have noticed that I have a dust problem that requires me to vacuum out the vents about every 6 weeks: a nuisance but keeps things running well. My fans run about 180 Cu Ft of air in and out of the case per minute. Also look at the way that your IDE cables and other wiring are laid out, sometimes that can either obstruct or divert airflow away from the CPU heatsink.Finally, make certain that you are getting enough power from your power supply to adequately run everything ( fans, processor coolers etc).My system details:giaByte 8IXNPP4 @ 3.06 (3.11)HT enabled1024 pc266DDRRadeon 9700Pro 128TurtleBeach Santa Cruz sound3 7200RPM ATA133 HDWinXP ProI use two intake fans, 2 exhaust fans ( one of them is a 120CuFT/min 110VAC) and one internal case fan to move air from the bottom of the case ( where the intakes are) to the top the the case ( where the exhuasts are).Best Regards and Good Luck Ed GreenKCLThttp://www.panelshop.com/DEV.jpghttp://www.globecargo.org/images/VAA_Sen_captain.jpg

"My CPU has no thermal compound"I think you just found the source of your problems.AS5 works very well for a thermal compound. And make sure you clean away all the dust that has collected between the fins of your CPU heatsink. That dust is one of the reasons I use Thermalright CPU coolers... the fan is quickly removed so that the dust can be easily blown out between the cooling fins.Cheers,Greg

Thanks guys for all the support.As you predicted, yes this CPU temperatures are quite high the manufacturer reports a ceiling of 80 C but I've read some place else that when above 60C look ups and slowdowns are quite common, I am going to check on the inboard Temp sensor and take note of this temp also.http://www.thermaltake.com/xaserCase/xaser3/v2000a.htmThis is my case, it has a 420W power supply, for what I've seen that is enough to run all the equipment inside.tonight I will be:1. Checking on-board Temperatures2. Checking Wires: I think That if I have a overheat problem it is due to this, my wife always laughs about the "mess" of the wires inside the computer3. Apply heating compoud (I expect this to have some instructions, I have never done this before.MOre of the CTD saga tonight... stay tunned

Gabriel.......The fact that your PSU is nominally 420W might sound OK but that doesn't neccessarily mean that it's working OK - it may be just perhaps occasionally not rising to the needs of the system, nor does that rating neccessarily mean that it can give you exactly what you want in terms of available amps for each V line .That said - it seems far more likely that the temps are your problem. What you plan to do is certainly a step in the right direction.Re ...."3. Apply heating compoud (I expect this to have some instructions, I have never done this before."Just don't put too much on - only a smear- you don't want loads of the stuff squishing out all around the die when you clamp the HS on- excess compound can cause problems of it's own.Dave

Hi,I've got a rig similar to yours, and I'm having the exact same problems.During the last 2 month, I've been going the same troubleshooting pains that you have. I've even reinstalled XP several times done reformat's to ensure that no "old cached drivers" were causing the trouble.I was sure I had a heat problem, so I was running with an open cabinet, a new CPU cooler and I also used the "Arctic Silver 3" thermal compound.In a low load situation I have approx. 45 C. and on a high load ~62 C.Well, I'm still having problems. I've even pulled every thing out of computer, tryed two different video cards (Radeon and Gforce) with the same effect.....Then I read this:http://www6.tomshardware.com/howto/20040122/index.htmlIt begins:Quote:"It happens more often than many users realize. An old graphics card or a slow processor runs smoothly and without a peep for weeks, and then suddenly, after a system upgrade, system failures start occurring with nasty regularity. Frequently users blame problems like this on sloppily programmed drivers or hardware mined with errors."It also states that you should look at how many Amp you can pull from the specific voltages, and not only the amount of W.Power cables connected to your Hard disks, CD-ROMs can also be a problem, you should have one cable attach to one unit. It could strain your PSU even more. I

Cheers

 

-Lars

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.