+- FsPassengers Forums (http://www.fspassengers.com/forum)
+-- Forum: FsPassengers (http://www.fspassengers.com/forum/forumdisplay.php?fid=3)
+--- Forum: FsPassengers Support (http://www.fspassengers.com/forum/forumdisplay.php?fid=5)
+--- Thread: Crash to desktop (/showthread.php?tid=5716)
Crash to desktop - papatango - 12-12-2005
I have so far had 2 CTDs out of the 2 flights that I have started. This is frustrating. They happened when:
1) I had clicked on one of the items in the Company Manager dialog. The screen froze and then I received the infamous error report
dialog to send the bug to MS.
2) I crashed my plane and the dialog with a cross came up. I then just got a blue screen with no text and had to manually reboot my
computer.
My machine is very stable and I am up to date on all of my drivers. I have a few commercial add-ons but no FS freeware installed. I have
not had CTDs prior to installing FsP. I have purchased FsP and am running the current version. I have looked through the posts
regarding CTDs but have not seen anything that applies.
It seems there are many people who have not had their CTD issues resolved.
This looks like a terrific addon and I am looking forward to using it. Is there any way to solved these CTD issues? What information do
you need to help diagnose these issues? I do not believe that there is anything for me to uninstall or update on my system regarding
drivers and other software. I would hate to have to uninstall this and waste the $37 that I paid for this. Please provide assistance. I will
continue to use FsP to see if I can find any pattern to the CTDs.
Thanks,
Scott
Re: Crash to desktop - olseric - 12-12-2005
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!
Re: Crash to desktop - DanSteph - 12-12-2005
For the 1) obviously you might have an old version because the CTD of company manager was resolved.
see here: http://www.fspassengers.com/?action=faq&question=17
for the 2) please have a look here: http://www.fspassengers.com/forum/showthread.php?tid=4818
Hope this help ?
Dan
Re: Crash to desktop - papatango - 13-12-2005
Thanks for the replies. I just had 2 successful flights without a CTD, including a crash in my Cessna which had previously caused a
CTD. The difference these last two times (as opposed to my first two times using FsPassenger and had CTDs) is that I shut everything
down that was unnecessary in Windows XP. Hopefully this was the issue. To shut everything down, here is what I did:
1. Go to Start | Control Panel | Administrative Tools | Services.
Shut down all services except:
Ati HotKey Poller (only for ATI video cards)
DCOM Server Process Launcher
DHCP Client
Event Log
Plug and Play
Remote Access Connection Manager
Remote Procedure Call (RPC)
Security Accounts Manager
Telephony
Terminal Services
Windows Audio
2. Shut down any processes running in your system tray.
3. Bring up Task Manager.
Shut down everything in your task list except:
csrss.exe
explorer.exe
lsass.exe
services.exe
svchost.exe (may be in multiple times)
System
System Idle Prcoess
smss.exe
winlogon.exe
Keep in mind that I shut down everything, including my Windows firewall. So shut down items at your own risk. One good thing is that my
memory useage went from 198 MB down to 128 MB after everthing was shut down and I think that FS runs better as well. Of course on
reboot, everything is back up running again.
Now I can hopefully start building my flight career! I will post if I get any CTDs in this configuration.
Scott
Re: Crash to desktop - samiranks - 13-12-2005
hmmm risky risky papatango. i guess i will stick to http://www.fstweaks.com thats a good link to try. it helps alot for alot of issues with fs9
as well as cp issues