FSX-Steam edition crashes in TERRAIN.DLL

[Pete Dowson]

TEST VERSION OF FSUIPC4 FOR FSX-SE TERRAIN.DLL CRASH AVOIDANCE

 

[sTOP PRESS]

I don't think it is going to work -- it looks like this crash is not patchable -- too extensive!

 

 

================================================================

 

A number of folks have been reporting crashes in FSX-SE's TERRAIN.DLL, These are probably results of a similar bug to the more common one in G3D.DLL in FSX, and they are probably exacerbated by folks managing to get settings up a lot higher in the Steam edition.

 

So far not many of these reports give any details, but I've seen two with details and both point to the same offset in TERRAIN.DLL for the access violation which is occurring. The offset is 00059BE8.

 

It's only a small sample, but the fact that the only two with details are both at the same place must surely be more than a coincidence. So, though I don't yet know if this is the main or only one. I can still implement a temporary workaround in FSUIPC as I did with he most prevalent G3D.DLL crash in FSX.

 

So, first off, could all of you experiencing this crash please post the actual crash details -- the module offset is really all I need, and confirmation that the error code is C0000005 (= access violation).

 

Meanwhile any registered user who does get (or knows he can get) the Terrain crash at 00059BE8, please try my interim test version -- download link: FSUIPC4938hTEST.zip. Read the "read me" inside for details on how to enable the fix.

 

Let me know how you get on, please.

 

Regards

Pete

26th January 2015

[pracines]

Hi Pete,

 

Patching now and following instructions concerning the INI edit.

 

I'm off to a long flight from EHAM to PANC in the default 747 using default "ultra high" settings. No FSX-SE.cfg edits. This exact same flight and settings always crashes ( terrain.dll) on me in approx. 3-5 hours  

 

I will let you know as soon as the crash happens or if I can complete the flight.

 

Thank you,

 

Paul

[Pete Dowson]

I will let you know as soon as the crash happens or if I can complete the flight.

 

Okay, thanks. 

 

I’ve now seen three crash reports with exactly the same crash address, so I’m hopeful that my fix might help. Just not sure of the consequences of letting the sim try to carry on – it might just result in a different crash later, depending on what the corruption really is.

 

If it does recover from one and carry on, the incident will be logged in the FSUIPC4.LOG file. After closing FSX-SE there will be a total count at the end of the log.

 

I'm off to bed now -- i'll check back in the morning.

 

[LATER]

I think I might have wasted your time. Sorry. The test version I uploaded won't install the patch. I made a error building the ZIP. :sad:  I'm just redoing it now. The link will br

 

FSUIPC4938hTEST.zip

 

 

[LATER STILL]

 

I fear it isn't going to work. The corrupted data may be too extensive. However, it does no harm to leave the facility enabled. Then, after any good (crashless) flight, after closing FSX-SE, look in the Modules folder for FSUIPC4.LOG. Open that in a text editor (Notepad) and look for any entries about TERRAIN.DLL. It just may be trapping some!? If so I'd like to know so I can decide whether to retain the patch code.

 

 

Regards,

Pete

[JRBarrett]

I’ve now seen three crash reports with exactly the same crash address, so I’m hopeful that my fix might help. Just not sure of the consequences of letting the sim try to carry on – it might just result in a different crash later on...

Make that four reports. I just looked back at the log in the Windows event viewer for a terrain.dll crash I had several days ago 4 hours into a planned 9-hour flight. The offset was indeed 00059BE8.

I'll definitely try the latest (Version 2) patch, although I won't have a chance to try another long-duration flight before this weekend.

I have only experienced the one terrain.dll crash to date - most of my subsequent FSX-SE flights have been 2 hours or less.

[pracines]

Ok I see and understand that the original patch was incorrect, no problem.  For me this is no waste of time and I'm so glad to be a part of an attempt to help the simming community. I will install the newer patch and try again.

 

However, in case this may be of help, I did fly with that original patch and crashed with this about 1 hour into the flight:

 

Source

Microsoft Flight Simulator®

Summary

Stopped working

Date

1/26/2015 8:58 PM

Status

Report sent

Description

Faulting Application Path: E:\SteamLibrary\steamapps\common\FSX\fsx.exe

Problem signature

Problem Event Name: APPCRASH

Application Name: fsx.exe

Application Version: 10.0.62608.0

Application Timestamp: 54abe5b4

Fault Module Name: ntdll.dll

Fault Module Version: 6.1.7601.22436

Fault Module Timestamp: 521eaa80

Exception Code: c0000005

Exception Offset: 000343d0

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: 9e27

Additional Information 2: 9e2778096e7e1e2a2e0302fe58f3eea8

Additional Information 3: 9e27

Additional Information 4: 9e2778096e7e1e2a2e0302fe58f3eea8

Extra information about the problem

 

Bucket ID: 817181142

[pracines]

Just got the terrain.dll crash using the new TEST2 patch:

 

Source

Microsoft Flight Simulator®

Summary

Stopped working

Date

1/26/2015 11:06 PM

Status

Report sent

Description

Faulting Application Path: E:\SteamLibrary\steamapps\common\FSX\fsx.exe

Problem signature

Problem Event Name: APPCRASH

Application Name: fsx.exe

Application Version: 10.0.62608.0

Application Timestamp: 54abe5b4

Fault Module Name: terrain.dll

Fault Module Version: 10.0.62608.0

Fault Module Timestamp: 54abe5e1

Exception Code: c0000005

Exception Offset: 0008fb86

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: 9e27

Additional Information 2: 9e2778096e7e1e2a2e0302fe58f3eea8

Additional Information 3: 9e27

Additional Information 4: 9e2778096e7e1e2a2e0302fe58f3eea8

Extra information about the problem

Bucket ID: 783518908

 

FSUIPC LOG:

 

********* FSUIPC4, Version 4.938g by Pete Dowson *********
Reading options from "E:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 7
Module base=58A80000
User Name="Paul Racines"
User Addr="pxxxxxxxx
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       16 System time = 26/01/2015 21:09:11
       16 FLT path = "C:\Users\NEW\Documents\Flight Simulator X - Steam Edition Files\"
       47 Trying to connect to SimConnect Steam ...
       78 FS path = "E:\SteamLibrary\steamapps\common\FSX\"
      374 LogOptions=00000000 00000001
      374 SIM1 Frictions access gained
      374 Wind smoothing fix is fully installed
      374 TERRAIN.DLL fix attempt installed ok
      374 SimConnect_Open succeeded: waiting to check version okay
      374 Trying to use SimConnect Steam
     2090 Running in "Microsoft Flight Simulator X", Version: 10.0.62608.0 (SimConnect: 10.0.62608.0)
     2090 Initialising SimConnect data requests now
     2090 FSUIPC Menu entry added
     2137 FLIGHTS\OTHER\FLTSIM.FLT
     2137 simobjects\airplanes\Aircreation_582SL\Aircreation_582SL.AIR
    28735 C:\Users\NEW\Documents\Flight Simulator X - Steam Edition Files\IFR Schiphol to Stevens Anchorage Intl.PLN
   133381 simobjects\airplanes\b747_400\Boeing747-400.AIR
   151992 Weather Mode now = Theme
   168341 C:\Users\NEW\Documents\Flight Simulator X - Steam Edition Files\IFR Schiphol to Stevens Anchorage Intl.PLN
   184487 System time = 26/01/2015 21:12:16, Simulator time = 03:11:13 (02:11Z)
   184487 Aircraft="Boeing 747-400 Paint2"
   199884 Starting everything now ...
   203394 Advanced Weather Interface Enabled
   231318 Sim stopped: average frame rate for last 33 secs = 25.8 fps
 

[Pete Dowson]

Just got the terrain.dll crash using the new TEST2 patch:

 

Ouch. It is as I feared. It looks like I've only succeeded in moving it on a bit. Drat! 

 

I'm afraid it may not be as easy as the old G3D patch I did for FSX.

 

There is one glimmer of hope. Possibly the new crash you got isn't related to the one I'm patching. There's no entry in the FSUIPC log file saying it "fixed" one, and there should be, though one reason for that might just be that there wasn't time for the output to get into the log before the crash.

 

Thanks for testing.

 

Pete

[pracines]

Glad to help anyway I can.

 

I will continue to monitor this thread and other terrain.dll error threads if there are any other possible patches/solutions to test.

 

Thank you Pete,

 

Paul

[Pete Dowson]

I will continue to monitor this thread and other terrain.dll error threads if there are any other possible patches/solutions to test.

 

Well, you might as well keep that existing option enabled. After any good (crashless) flight, just look at the FSUIPC4.LOG file and see if it logged any TERRAIN.DLL crashes trapped. I'm still 50:50 whether your latest one was the same one moved on or a different one.

 

Pete

[pracines]

Understood,

 

I will intentionally fly some flights I know I had success with. If I see any terrain.dll crashes logged in the FSUIPC4.LOG then I will post it here.

 

Thank you,

 

Paul

[Pete Dowson]

I will intentionally fly some flights I know I had success with.

 

Er, if you had success without FSUIPC's patch, the patch isn't likely to do anything? Surely you need to fly flights you've not had success with, ones you previous experienced TERRAIN crashes at the most commonly reported offset, the one FSUIPC patches?

 

Really I don't think you should worry about flying specific flights. Just do what flights you want to do, that you'd normally do. Just please check the log afterwards.

 

Once even just one person reports that FSUIPC says it caught one, I'll know it's a success. Unfortunately I'll never be able to prove it isn't.

 

Pete

[JRBarrett]

I think most of us who have experienced the 00059BE8 crash got it after several hours of continuous flight, rather than early on. I saved the flight plan where it happened to me, and will re-fly it to see if I get it again at the same place.

[blueridgeflyer]

_{I ran FSX-SE with the newest module and was able to generate a terrain.dll crash about 4 hours into the flight. The Log file is still not populating with data relevant to the event though.}

_Log.ini

_{********* FSUIPC4, Version 4.938g by Pete Dowson *********}

Reading options from "C:\Program Files (x86)\Steam\steamapps\common\FSX\Modules\FSUIPC4.ini"

Running inside FSX Steam Edition on Windows 7

Module base=55390000

User Name="XXXX"

User Addr="XXXXX"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

32 System time = 27/01/2015 11:01:25

32 FLT path = "C:\Users\Ryan\Documents\Flight Simulator X Files\"

63 Trying to connect to SimConnect Steam ...

94 FS path = "C:\Program Files (x86)\Steam\steamapps\common\FSX\"

328 LogOptions=00000000 00000001

328 SIM1 Frictions access gained

328 Wind smoothing fix is fully installed

328 TERRAIN.DLL fix attempt installed ok

328 SimConnect_Open succeeded: waiting to check version okay

328 Trying to use SimConnect Steam

2762 Running in "Microsoft Flight Simulator X", Version: 10.0.62608.0 (SimConnect: 10.0.62608.0)

2762 Initialising SimConnect data requests now

2762 FSUIPC Menu entry added

2793 C:\Users\Ryan\Documents\Flight Simulator X Files\GLS Default.FLT

2793 simobjects\airplanes\beech_baron_58\Beech_Baron_58.AIR

9204 Weather Mode now = Global

14805 ASE with WX requester detected

32105 simobjects\airplanes\PMDG 777-200LR\B777-200LR.AIR

85052 System time = 27/01/2015 11:02:51, Simulator time = 09:01:28 (17:01Z)

85068 Aircraft="PMDG 777-223LR American Airlines (Fictional)"

98312 Weather Mode now = Theme

98484 Weather Mode now = Global

101011 Starting everything now ...

101370 Advanced Weather Interface Enabled

142897 Weather Mode now = Theme

143381 Weather Mode now = Global

10360495 Sim stopped: average frame rate for last 10264 secs = 29.4 fps

_{reliability file:}

_Description

_{Faulting Application Path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe}

_{Problem signature}

_{Problem Event Name: APPCRASH}

_{Application Name: fsx.exe}

_{Application Version: 10.0.62608.0}

_{Application Timestamp: 54abe5b4}

_{Fault Module Name: terrain.dll}

_{Fault Module Version: 10.0.62608.0}

_{Fault Module Timestamp: 54abe5e1}

_{Exception Code: c0000005}

_{Exception Offset: 00059be8}

_{OS Version: 6.1.7601.2.1.0.768.3}

_{Locale ID: 1033}

_{Additional Information 1: 9e27}

_{Additional Information 2: 9e2778096e7e1e2a2e0302fe58f3eea8}

_{Additional Information 3: 9e27}

_{Additional Information 4: 9e2778096e7e1e2a2e0302fe58f3eea8}

_{Extra information about the problem}

_{Bucket ID: 783840669}

[Pete Dowson]

_{I ran FSX-SE with the newest module and was able to generate a terrain.dll crash about 4 hours into the flight. The Log file is still not populating with data relevant to the event though}

 

This one is a real puzzler!  This logged line:

 

_{328 TERRAIN.DLL fix attempt installed ok}

 

means the patch location has been verified, and patched. Yet this:

 

_{Fault Module Name: terrain.dll}

_{Fault Module Version: 10.0.62608.0}

_{Fault Module Timestamp: 54abe5e1}

_{Exception Code: c0000005}

_{Exception Offset: 00059be8}

 

is a crash in exactly the place being protected. I can understand it maybe moving on, but this is odd.

 

I'll have to think about this one. 

 

Pete

 

[Pete Dowson]

I've made some small changes, and, though I don't think they'll really help, it's worth replacing your FSUIPC 4.938g with this one:

 

FSUIPC4938hTEST.zip

 

Pete

[pracines]

I will give this new patch a go with the same EHAM-PANC flight that always results in a terrain.dll crash.

 

I wonder if DTG would allow us to be on a beta team to get this resolved?? In my view Pete, this problem should be fixed by DTG, so you can work on bigger and better things :-) I sure do appreciate all your efforts to help us simmers.

 

Paul

[pracines]

Same results with the "h" patch except the last line "sim stopped" on the log is missing (?)

 

Source

Microsoft Flight Simulator®

Summary

Stopped working

Date

1/27/2015 11:23 PM

Status

Report sent

Description

Faulting Application Path: E:\SteamLibrary\steamapps\common\FSX\fsx.exe

Problem signature

Problem Event Name: APPCRASH

Application Name: fsx.exe

Application Version: 10.0.62608.0

Application Timestamp: 54abe5b4

Fault Module Name: terrain.dll

Fault Module Version: 10.0.62608.0

Fault Module Timestamp: 54abe5e1

Exception Code: 40000015

Exception Offset: 000206f3

OS Version: 6.1.7601.2.1.0.256.1

Locale ID: 1033

Additional Information 1: cc34

Additional Information 2: cc34e419b58ad83ddc8d831af8eab4dc

Additional Information 3: a387

Additional Information 4: a38733490bfb42f884e0bed7bc2cfe87

Extra information about the problem

Bucket ID: 783463565

 

********* FSUIPC4, Version 4.938h by Pete Dowson *********
Reading options from "E:\SteamLibrary\steamapps\common\FSX\Modules\FSUIPC4.ini"
Running inside FSX Steam Edition on Windows 7
Module base=57550000
User Name="Paul Racines"
User Addr="xxxxxx"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 27/01/2015 21:54:25
        0 FLT path = "C:\Users\NEW\Documents\Flight Simulator X - Steam Edition Files\"
       31 Trying to connect to SimConnect Steam ...
       31 FS path = "E:\SteamLibrary\steamapps\common\FSX\"
      343 LogOptions=00000000 00000001
      343 SIM1 Frictions access gained
      343 Wind smoothing fix is fully installed
      343 TERRAIN.DLL fix attempt installed ok
      343 SimConnect_Open succeeded: waiting to check version okay
      343 Trying to use SimConnect Steam
     1575 Running in "Microsoft Flight Simulator X", Version: 10.0.62608.0 (SimConnect: 10.0.62608.0)
     1575 Initialising SimConnect data requests now
     1575 FSUIPC Menu entry added
     1606 FLIGHTS\OTHER\FLTSIM.FLT
     1606 simobjects\airplanes\Aircreation_582SL\Aircreation_582SL.AIR
    13618 simobjects\airplanes\b747_400\Boeing747-400.AIR
    29843 C:\Users\NEW\Documents\Flight Simulator X - Steam Edition Files\IFR Schiphol to Stevens Anchorage Intl.PLN
    42635 Aircraft="Boeing 747-400 Paint2"
    42635 System time = 27/01/2015 21:55:08, Simulator time = 03:54:26 (02:54Z)
    49639 Starting everything now ...
    53289 Advanced Weather Interface Enabled
 

[Pete Dowson]

Same results with the "h" patch except the last line "sim stopped" on the log is missing (?)

 

Hmm. I think that, unless I can reproduce the problem here, I'll have to give up. If anyone has a sure-fire way of making this happen within a reasonable time (I'm not willing to fly it for hours, it needs to happen quickly, like 30 mins or less, please, because I'll need to do it several times and I do have other things to do) then perhaps they'd describe it. I'd need their main FSX or FSX-SE CFG file because I'm pretty sure it's going to also depend on settings. And hopefully it will not involve any payware add-on I'm unlikely to have -- like PMDG, iFly etc etc.

 

Pete

[pracines]

I agree that this is like chasing the wind. I went ahead and uninstalled FSX-SE. Since DTG ( on the steam forum) is not even acknowledging that there is a problem or at least that they will look into it, I will let them concentrate on their DLC.

 

Its likely that I will remove all flight sims from all my PC's; they all have "chase the wind" issues to one degree or another, and since there is nothing I can do to help, there is no sense being frustrated.

 

Until there is a good reason for "me" ( I speak only for me ) to care about flight simming, I will take up another hobby for now. SCS Euro truck sim is stable, looks great/real , is now 64bit (before it needed to be), there is steady progress, and good steady communication from the developers.   

 

Take care Pete,

 

paul

[blueridgeflyer]

I agree that this is like chasing the wind. I went ahead and uninstalled FSX-SE. Since DTG ( on the steam forum) is not even acknowledging that there is a problem or at least that they will look into it, I will let them concentrate on their DLC.

Its likely that I will remove all flight sims from all my PC's; they all have "chase the wind" issues to one degree or another, and since there is nothing I can do to help, there is no sense being frustrated.

Until there is a good reason for "me" ( I speak only for me ) to care about flight simming, I will take up another hobby for now. SCS Euro truck sim is stable, looks great/real , is now 64bit (before it needed to be), there is steady progress, and good steady communication from the developers.

Take care Pete,

paul

I wouldn't throw in the towel on DTG & SE just yet. Granted the terrain.dll issue seems to be isolated and germane to the Long Haul crowd. The FSX franchise as it relates to this niche customer is hanging in the balance. I'm certainly pulling for them.

I am standing by for P3D 2.5 as it will likely take over as my primary flight sim platform with the release of PMDG licensed products.

[jabloomf1230]

Pete,

 

I thought that I would thank you here for all your hard work on this and also for trying to help me out over at AVSim. Maybe DTG will figure this out at some point and the few of us that have this CTD can use the sim again. 

 

Jay

[NadRush]

Is this possible to fix G3D.dll ? 

[Pete Dowson]

Which G3D.DLL error? There are lots of different ones.

 

Pete

[NadRush]

Hi,

 

Sorry i didn't mention it clearly 

 

Here's my log :

 

Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd

Exception code: 0xc0000005

Fault offset: 0x000c7c0a

Faulting process id: 0x1240

Faulting application start time: 0x01d03ddb014f33d9

Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\g3d.dll

Report Id: 53357eb7-a9f2-11e4-be8a-d43d7e4ef386

Faulting package full name: 

Faulting package-relative application ID: 

 

But i'm still investigating the cause of this error , because it looks like , it's not from FSUIPC . So, i'll update it soon ..  

 

Best Regards,

Nadim

Edited February 1, 2015 by NadRush

[Pete Dowson]

Well, that is one I've seen mentioned before, so it might be worth looking at, but I can't promise anything. It depends on what the code looks like, whether there's an easy way to bypass the crash area without just moving it elsewhere.

 

I won't be able to look at it for a week or so, too many other commitments, but it is on my list.

 

Pete