12-12-2005, 12:12 PM
Hi Scott,
CTD issues can be hard to diagnose because there is a wide variation of things that can cause it, among the top "culprits" are:
1. Excessive heat (generally leads to sluggish performance prior to any lock-ups or random reboots though)
2. Insufficient memory (FS is a hog!)
3. Poorly coded 3rd party add-ons (scenery is generally the main problem here)
4. Corrupted modules/DLLs
Start by ruling out #1 by looking into your CMOS to make sure the temps are within manufactuers specified limits. Then check #2. Look
at the size of your swap file (virtual memory as Windows calls it). If you have a decent size HDD, max this value out to 2X the total
installed RAM (i.e. You have 512MB RAM, make your swap file 1GB/1024MB).
Reboot and retry. If that's not helping move on to the other two. I wouldn't even bother with #4 though unless the fatal error that you get is
pointing to a specific DLL every time it happens.
Let us know how that works and if you need more suggestions, we're all happy to help!
CTD issues can be hard to diagnose because there is a wide variation of things that can cause it, among the top "culprits" are:
1. Excessive heat (generally leads to sluggish performance prior to any lock-ups or random reboots though)
2. Insufficient memory (FS is a hog!)
3. Poorly coded 3rd party add-ons (scenery is generally the main problem here)
4. Corrupted modules/DLLs
Start by ruling out #1 by looking into your CMOS to make sure the temps are within manufactuers specified limits. Then check #2. Look
at the size of your swap file (virtual memory as Windows calls it). If you have a decent size HDD, max this value out to 2X the total
installed RAM (i.e. You have 512MB RAM, make your swap file 1GB/1024MB).
Reboot and retry. If that's not helping move on to the other two. I wouldn't even bother with #4 though unless the fatal error that you get is
pointing to a specific DLL every time it happens.
Let us know how that works and if you need more suggestions, we're all happy to help!
![[Image: 101031.png]](http://status.ivao.aero/101031.png)