KDTW to EGLL and My First CTD! Not Cool...

More than a 7 hour flight and just as I'm approaching London, the dreaded Crash to Desktop (CTD). It was such a beautiful approach and I was enjoying the scenery but never made it to the airport.

Headed out of Detroit on a rainy day

Making the approach into London

It was looking good

And that was it! No further would I go.

Now I just need time to find time to read the AVSIM CTD guide...:mad:

I hate when that happens, but what you have looks good. :cool: :)

Thanks Larry. Guess I’ll have to take my 172 and cruise around the city.

Even not so long haulers crash. That's due to a more crowded environment when your flight nears arrival aiport.

Only one solution: to save your flight intermittently ($ key I think)

Or, in the worst cases, save the flight when about the descent and approach's beginning. Then close-restart FSX. That's decluttering your PC and you gain FSP back

Otherwise a fine flight!

Even not so long haulers crash. That's due to a more crowded environment when your flight nears arrival aiport.

Only one solution: to save your flight intermittently ($ key I think)

Or, in the worst cases, save the flight when about the descent and approach's beginning. Then close-restart FSX. That's decluttering your PC and you gain FSP back

Otherwise a fine flight!

Thanks Gerard. Good advice!

David - I guess my issues are the same? I can fly non-stop from Charleston, SC to Boston in one of the fighter jets, when I ILS approach Boston it does not engage at all. If I break up the trip in 2 pieces all work good! I think I will try what Gerard and Jan has suggested!

I agree, nice pics of what you did get! Rick :cool:

trip in 2 pieces all work good

Yes that's one of the solution!

Save-restart FSX before a dense area OR save at intervals and keep flying as FSX may not crash. Should it, you get the latest saved step of the flight (and the Peer's Academy option seems good too: last interval is when reaching to a dense area :):) )

About sure it's that transatlantic flight. Just imagine what a 6-7 hour flight is clogging even a strong computer chip!

Excellent point

The dreaded BSOD (Blue Screen Of Death) is the most loathsome thing anyone runs into. Once in a blue moon, I do get the odd OOM (Out Of Memory) condition when using the sim for too long, but the BSOD is even worse. Best practice on a long flight is to save, and save often. Then whatever happens you just load the flight and pick up from last save. BSOD's are typically associated with a certain driver update, especially display adapter drivers, and more especially if it is Nvidia based. Windows does give an error code and saves a log of the BSOD. You can decrypt these error codes and this may just give you a hint as to what went wrong.

This link may come in handy

Best wishes.

Khalid

The dreaded BSOD (Blue Screen Of Death) is the most loathsome thing anyone runs into. Once in a blue moon, I do get the odd OOM (Out Of Memory) condition when using the sim for too long, but the BSOD is even worse. Best practice on a long flight is to save, and save often. Then whatever happens you just load the flight and pick up from last save. BSOD's are typically associated with a certain driver update, especially display adapter drivers, and more especially if it is Nvidia based. Windows does give an error code and saves a log of the BSOD. You can decrypt these error codes and this may just give you a hint as to what went wrong.

 

This link may come in handy

 

Best wishes.

 

Khalid

Thanks Khalid. I need to find the time. A lot going in my crazy life right now! Thanks for the information!