Problems in AUS/NZ area

[nwadc10]

I've had repeated problems with flying into the Australia/New Zealand area with CTD. Previously I recall a HNL-SYD flight crashing during the descent into SYD multiple times before it finally worked. Now, I'm flying NZAA-YMML and in NZAA FS crashed a couple times before getting off the ground and once right after takeoff. I thought it was an Active Sky problem as that was crashing too so I left AS off and FS seemed to be a bit more stable. Now, descending into YMML FS has crashed twice at about the same location. Anybody know what the problem is? I believe it has something to do with scenery which all I have is default and no addon scenery.

Thankfully GCP had saved my flight a few minutes before FS crashes.

[Brogs]

Justin My last Flight was PHNL-YSSY "Sidney" and my FSFK crashed on app, this is the first time this has happened ! I wasn,t running GCP at the time, but I always have the FS9 Logbook on so the HRS weren,t lost,could this be part of the same problem, I don,t have any addon OZ Scenery,so I haven,t a clue what caused this !

[yoni63]

Its Dr. Evil and his ultra powered super magnetic tractor beam.

[Ken S]

Could it have something to do with crossing the International Dateline???


Ken S

[Greg Goodavish]

I've flown that route a number of times, with no problem. My problem area is just outside Seattle, at the ELMAA intersection. Every time I approach that, I get a CTD. No idea why. Guess we all have our gremlins!

[nwadc10]

Could it have something to do with crossing the International Dateline???


Ken S

Interesting thought. I looked it up and unfortunately the dateline passes about 20 deg longitude east of NZAA so my flight doesn't cross it.

[eek]

Several years ago, I would get an occasional CTD if I made a turn during dusk/dawn hours. On one flight, I was able to get the CTD to repeat at the same location, at the same time. I thought maybe I had a corrupted texture file, but after a while, I noticed it wasn't happening, anymore. By then, I was using a newer video card, and a more recent driver. I don't know which one fixed it, but I haven't had a CTD in several years, now.

Maybe trying a newer/older display driver could help. Didn't you recently upgrade your hardware?

[nwadc10]

Several years ago, I would get an occasional CTD if I made a turn during dusk/dawn hours. On one flight, I was able to get the CTD to repeat at the same location, at the same time. I thought maybe I had a corrupted texture file, but after a while, I noticed it wasn't happening, anymore. By then, I was using a newer video card, and a more recent driver. I don't know which one fixed it, but I haven't had a CTD in several years, now.

Maybe trying a newer/older display driver could help. Didn't you recently upgrade your hardware?

No, I didn't update my hardware. I decided to hold off and put my money into a new system in a year or so.

I had actually updated my video driver before doing this flight the first time. I'll try going back to an older driver to see what happens. The flight was saved just a couple minutes before the CTD and it's crashing at the same location so it's easy to test. I had tried going to HDG mode and taking a 90 deg turn to try to fly around the trouble area if it is scenery related but I think I may be too close to the CTD for that to work.

[Brogs]

Several years ago, I would get an occasional CTD if I made a turn during dusk/dawn hours. On one flight, I was able to get the CTD to repeat at the same location, at the same time. I thought maybe I had a corrupted texture file, but after a while, I noticed it wasn't happening, anymore. By then, I was using a newer video card, and a more recent driver. I don't know which one fixed it, but I haven't had a CTD in several years, now.

Maybe trying a newer/older display driver could help. Didn't you recently upgrade your hardware?

No, I didn't update my hardware. I decided to hold off and put my money into a new system in a year or so.

I had actually updated my video driver before doing this flight the first time. I'll try going back to an older driver to see what happens. The flight was saved just a couple minutes before the CTD and it's crashing at the same location so it's easy to test. I had tried going to HDG mode and taking a 90 deg turn to try to fly around the trouble area if it is scenery related but I think I may be too close to the CTD for that to work.

Could it be a similar problem to the R/way one we had a few months ago? with the different runway texture causing a CTD ie a Scenery Bug ?

[nwadc10]

Unfortunately it's not the runway issue because that was a problem with crash detection on the physical runway. This is a FS shutting down type of crash and at about FL260 on the descent.

I updated the video driver to the offical driver of the manufacturer and that didn't help. I checked the system event log and found the crashes were recorded. Below is a copy of one of the events, which is the same for all CTD's that I got.

Code: Select all

Event Type:	Error
Event Source:	ati2mtag
Event Category:	CRT 
Event ID:	45062
Date:		5/31/2008
Time:		5:48:57 PM
User:		N/A
Computer:	DESKTOP
Description:
CRT invalid display type
Data:
0000: 00 00 00 00 01 00 5a 00   ......Z.
0008: 2c 00 00 00 06 b0 00 c0   ,....°.À
0010: 00 00 00 00 00 00 00 00   ........
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........

Per the description, I don't understand how all of a sudden the video driver thought my CRT (which I have a flat panel monitor) was invalid. So, I assume that this isn't really the problem. Beyond taking the description literally I can't decode what the problem is. Anyone have ideas?

I've scrapped the flight and will pickup an open board to replace NZAA-YMML because I can't figure this one out. I still have the saved flight though so I can continue troubleshooting the problem in the future.

[Mike Schmitt]

I have had this problem too, when I flew out Honolulu to New Zealand the sim would CTD not far from HNL using RFPv2. I thought maybe this was due to HNL not being recognized with Active Sky 4.5 (I can't afford to upgrade just yet) due a successful flight using default Weather download. However a few weeks later trying to fly to New Zealand from Hong Kong using PMDG 747(PAX) I found the same problem usually as I approached Auckland and switched to an exterior view. On this flight I noticed when I switched to the exterior view (for some screen shots), my textures would not fill in with color and then the sim went to desktop.

I am about to try that flight again now with the new updates in place to PMDG maybe they have been corrected this. We will see.

[Mike Schmitt]

Made it without a CTD. Now we did loose power thanks to this wonderful spring here in the Midwest during the flight and GCP worked great the flight back and continuing. Unfortunately not much you can do for that besides buying UPS system. Maybe those fixes from PMDG had something to do with it.

[nwadc10]

I'm very very pleased to report that I think this problem is fixed. Originally the Windows Event Viewer was showing the problem to be in one of the files for the video card. Well, I went to the store to get a DVI cable and ended up coming home with a new NVidia 1GB card as well.

Hoping a new card would fix the problem because the supposed problem file would no longer be used. Unfortunately that didn't work but now the Event Viewer was reporting the problem as FS's weather.dll.

Tomas sent me his weather.dll which interestingly was more than a year newer than the file it was replacing. Viola! I am now able to complete a flight in FS again including the original NZAA/YMML that was giving me problems.

If you have never heard of the Event Viewer, which I hadn't until researching a problem months ago, it's a very handy tool in diagnosing a problem. To access it go to (Windows XP, I don't know where it is or if it exists in Vista) Control Panel->Administration Tools->Event Viewer. Once there you will see several different categories of events. My problem was contained in the System category and was shown as errors. Click on the error to see more details. Keep in mind that every now and then even your computer doesn't know what happened and can't give you a file that caused the problem. Also, as apparently in my case, the wrong file was reported (the video driver file) when the real problem was in weather.dll, which was reported after I took care of the video driver file.

Louis: I was able to complete my NZAA/YMML flight that I had emailed you about. Pirep submitted and I had not taken an open board to replace it.

[eek]

I wish I had checked Event Viewer when I had my CTD since I never knew what actually caused it. I reproduced the crash several times and resolved it by simply flying my flight 30 minutes later in FS. Glad you got it straightened out.

[esurfman]

What an absolutely crazy year it was! But you look brilliant as always as Naruto Cosplay,maybe Naruto Costumes oh yeah well thanks 4 telling me that, of cause, i should share my interesting Naruto Cosplay Costumes cosplay wigs

I feel a spammer or something.....