Timmo wrote:Hi Steve
Are there any 'artifacts' before the crashes that you have noticed (i.e. screen flickering etc)?
Is your case/laptop well cooled and free from dust build up? If you run a CPU/GPU temperature logging software, do these show any rise in temps?
Have you recently updated your graphics card drivers? Alternatively, when was the last time you did update?
And as mentioned by mike- What other scenery are you running around Napier?
hi everyone.
thanks for the support and all of the questions. i can answer a few of the questions, but most of the answers will require several days of investigation.
firstly, i am not sure whether the problem is specific to the napier area. this happened to be the location where the hangup finally drove me to desperate measures, although the crashes were occurring elswhere on both north and south islands. at that time i had mike's napier scenery installed and checked for duplicate napier afcads (negative), but subsequently uninstalled his napier scenery without resolution of the crashes. so the napier addon was not the cause, although some other problem around napier has not been ruled out. i will try a bunch of short flights in several different areas of both islands and let you know the results. last night, i realised that i had ruled out the vlc scenery as the primary cause of the problem, but i had not looked closely at other new zealand sceneries i have used. most of the ones i have installed are designed specifically for vlc, but i will systematically disable all possible suspects to see if the crash pattern changes.
my computer has win 7 running an i7 920 processor and a gtx 275 graphics card. i am overclocked to 4.0 ghz and the sim runs beautifully with high detail aircraft, scenery and all sliders way over to the right. the computer is cooled with a noctua unit, and the temp at rest is around 48-50 degrees C; when fsx is running, it rises to 52-60 degrees C but never higher.
the crashes can occur at any time in a flight, sometimes within the first couple of minutes, but other times not for aan hour or so. the first sign of a problem is the scenery starts to do momentary halts (usually with fps dropping from its usual 30fps max down to 5-10fps). this jumpiness might continue for 1-2 minutes but usually less. the scenery itself remains as sharply focussed as before, and i cannot appreciate any flickering. eventually the sound and the cursor freeze. fsx usually crashes to desktop within a minute or so, sometimes preceded by one of microsoft's ever-helpful messages that a "serious problem has occurred and the application will shut down, and microsoft will notify me if it can figure out what the problem is". microsoft's sleuthing has not yet born any fruit. sometimes, i wait for fsx to crash (ever hopeful that it will not do so) but usually i hit control/alt/delete to end my misery and curtail my disappointment. event viewer/window logs/applications sometimes shows an error message implicating fsx.exe in addition to terrain.dll (or occasionally a different .dll file). about half the time, there is no error message related to the crash.
that's about all i can tell you at this time. sorry for the detail, but you never know what is relevant. i will proceed with my testing and get back to the forum with a more concise note. thanks again for the help, interest and encouragement. i will surely miss vector land class while flying over your beautiful islands.
steve chavin