It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Having been a huge fan of the Earth series since it first started, I took the opportunity to grab E2150 from here as I lost my discs for it.

I managed to run it fine on my old rig - Vista 64, E6600 @2.4Ghz, Radeon 4870's in crossfire, 8Gigs Ram, 19' Monitor at 1440 x 900. It looked gorgeous, ran well, never had a crash- not one problem. Didn't even have to patch it as I never really needed to, as didn't try multiplayer and played campaign or skirmish only. (Nobody I knew liked the Earth series, which was depressing).

However, years later on my new rig, Win 7 64, I7 980 @3.33Ghz, Radeon HD9990, 24' Monitor using 1080p (or 1920 x 1080 or thereabouts as I had to stretch it a little to fit). It won't even go beyond the menus.

Game loads up fine, no matter what resolution or settings I've used- however when I try to start a Skirmish game, I get as far as selecting my profile but once I click "Enter the Game" it crashes. Same for the Campaign and also Multiplayer.

I've tried everything in the troubleshooting section (I.e updates, restart, re-download, make sure it's verified, scan PC for errors, DirectX, etc) as well as what I've seen in this forum in terms of changing resolutions (tried both with the game and with the monitor in general).

I've tried every possible combination of resolution, compatibility mode and disabled UAC throughout- no joy.

No dice. Nothing seems to work. I can get E2160 working without a hitch, however I fancy some E2150, as it is obviously different- but no joy. I've scoured the internet to try different things but nothing seems to work, every solution results in the same result- crashes at the same point.

I've not even -heard- of this happening before, nobody seems to have the same issue, so I'm at a loss as to how to solve it.

If anyone can help or offer advice I'd greatly appreciate it. This is, as far as I'm concerned, a mint game. Granted it can be hard, it isn't to everyone's tastes and obviously it can be troublesome to get working, but I love my Earth series! It's inhumane to wave it in front of me and yet deny me it's tastiness.




EDIT: In case this is remotely helpful, this is the error file that repeatedly gets created at each crash.


******************************************************************
D:\GOG Games\earth_2150\Earth 2150 Trilogy\Escape from the Blue Planet\Earth2150.exe
Wed Jul 26 16:09:02 2000
Thu Mar 01 12:33:11 2012
------------------------------------------------------------------
Unhandled Exception
Code: c0000005
Description: EXCEPTION_ACCESS_VIOLATION
Exception address: 0x033135de
Registers: EAX = 0x033135de EBX = 0x03bcf0c0 ECX = 0x03bd0740 EDX = 0x0000002c
Registers: ESI = 0x03bd0bac EDI = 0x0000053c EBP = 0x0018f27c ESP = 0x0018f270
Registers: EIP = 0x033135de CS = 0x00000023 SS = 0x0000002b Flg = 0x00210206
Registers: DS = 0x0000002b ES = 0x0000002b FS = 0x00000053 GS = 0x0000002b

Call stack:
------------------------------------------------------------------
module not accessible
address: 0x033135DE
Module: D:\GOG Games\earth_2150\Earth 2150 Trilogy\Escape from the Blue Planet\Earth2150.exe
module not accessible
address: 0x0063DDBC
module not accessible
address: 0x0063BD9C
module not accessible
address: 0x00654E8B
module not accessible
address: 0x00629460
module not accessible
address: 0x0064F9BA
module not accessible
address: 0x006557B2
module not accessible
address: 0x0062B003
module not accessible
address: 0x00627953
module not accessible
address: 0x0062989A
module not accessible
address: 0x00655B70
module not accessible
address: 0x0062B003
module not accessible
address: 0x0062AD46
module not accessible
address: 0x006680DA
module not accessible
address: 0x0040A9FF
module not accessible
address: 0x00409F49
module not accessible
address: 0x00720C83
Module: C:\Windows\syswow64\kernel32.dll
module not accessible
address: 0x757E339A
Module: C:\Windows\SysWOW64\ntdll.dll
module not accessible
address: 0x77D19EF2
module not accessible
address: 0x77D19EC5
------------------------------------------------------------------
Post edited March 01, 2012 by FeralSquirrel
No posts in this topic were marked as the solution yet. If you can help, add your reply
avatar
FeralSquirrel: Having been a huge fan of the Earth series since it first started, I took the opportunity to grab E2150 from here as I lost my discs for it.

I managed to run it fine on my old rig - Vista 64, E6600 @2.4Ghz, Radeon 4870's in crossfire, 8Gigs Ram, 19' Monitor at 1440 x 900. It looked gorgeous, ran well, never had a crash- not one problem. Didn't even have to patch it as I never really needed to, as didn't try multiplayer and played campaign or skirmish only. (Nobody I knew liked the Earth series, which was depressing).

However, years later on my new rig, Win 7 64, I7 980 @3.33Ghz, Radeon HD9990, 24' Monitor using 1080p (or 1920 x 1080 or thereabouts as I had to stretch it a little to fit). It won't even go beyond the menus.

Game loads up fine, no matter what resolution or settings I've used- however when I try to start a Skirmish game, I get as far as selecting my profile but once I click "Enter the Game" it crashes. Same for the Campaign and also Multiplayer.

I've tried everything in the troubleshooting section (I.e updates, restart, re-download, make sure it's verified, scan PC for errors, DirectX, etc) as well as what I've seen in this forum in terms of changing resolutions (tried both with the game and with the monitor in general).

I've tried every possible combination of resolution, compatibility mode and disabled UAC throughout- no joy.

No dice. Nothing seems to work. I can get E2160 working without a hitch, however I fancy some E2150, as it is obviously different- but no joy. I've scoured the internet to try different things but nothing seems to work, every solution results in the same result- crashes at the same point.

I've not even -heard- of this happening before, nobody seems to have the same issue, so I'm at a loss as to how to solve it.

If anyone can help or offer advice I'd greatly appreciate it. This is, as far as I'm concerned, a mint game. Granted it can be hard, it isn't to everyone's tastes and obviously it can be troublesome to get working, but I love my Earth series! It's inhumane to wave it in front of me and yet deny me it's tastiness.

EDIT: In case this is remotely helpful, this is the error file that repeatedly gets created at each crash.

******************************************************************
D:\GOG Games\earth_2150\Earth 2150 Trilogy\Escape from the Blue Planet\Earth2150.exe
Wed Jul 26 16:09:02 2000
Thu Mar 01 12:33:11 2012
------------------------------------------------------------------
Unhandled Exception
Code: c0000005
Description: EXCEPTION_ACCESS_VIOLATION
Exception address: 0x033135de
Registers: EAX = 0x033135de EBX = 0x03bcf0c0 ECX = 0x03bd0740 EDX = 0x0000002c
Registers: ESI = 0x03bd0bac EDI = 0x0000053c EBP = 0x0018f27c ESP = 0x0018f270
Registers: EIP = 0x033135de CS = 0x00000023 SS = 0x0000002b Flg = 0x00210206
Registers: DS = 0x0000002b ES = 0x0000002b FS = 0x00000053 GS = 0x0000002b

Call stack:
------------------------------------------------------------------
module not accessible
address: 0x033135DE
Module: D:\GOG Games\earth_2150\Earth 2150 Trilogy\Escape from the Blue Planet\Earth2150.exe
module not accessible
address: 0x0063DDBC
module not accessible
address: 0x0063BD9C
module not accessible
address: 0x00654E8B
module not accessible
address: 0x00629460
module not accessible
address: 0x0064F9BA
module not accessible
address: 0x006557B2
module not accessible
address: 0x0062B003
module not accessible
address: 0x00627953
module not accessible
address: 0x0062989A
module not accessible
address: 0x00655B70
module not accessible
address: 0x0062B003
module not accessible
address: 0x0062AD46
module not accessible
address: 0x006680DA
module not accessible
address: 0x0040A9FF
module not accessible
address: 0x00409F49
module not accessible
address: 0x00720C83
Module: C:\Windows\syswow64\kernel32.dll
module not accessible
address: 0x757E339A
Module: C:\Windows\SysWOW64\ntdll.dll
module not accessible
address: 0x77D19EF2
module not accessible
address: 0x77D19EC5
------------------------------------------------------------------
It's DEP that's the problem on Win 7 x64.

I had the exact same problem as you and this fixed it. Open "Computer" then right click -> Properties -> System Protection -> Advanced -> Performance -> Data Execution Prevention then "Add" the executable for the game. Not the shortcut but the .exe file.
The funny thing is, for me the DEP thing only works for EftBP and LS but not for TMP. I really don't know why and it ticks me off

Edit:
Found a solution. For some reason TMP.exe was not ecxluded from DEP by just adding it as an exemption like the other two so I had to do it manually. Found a good source for it here: https://blogs.technet.microsoft.com/askperf/2008/06/17/to-dep-or-not-to-dep/
There's a paragraph that tells you how to edit the exe file ( in your registry) to be exempt from DEP. This finally worked for me, so hopefully if someone runs into the same problem this
Post edited March 25, 2017 by Roxas1410
Hi, I have a similar problem: Earth 2150 crashed whenever trying to play an ingame video. I tried the hint above and now it already crashes when I try to start a game or tutorial.

Windows 7, 64 bit, I5 2410M, GeforceGT 525M

Here is the most recent error message:
******************************************************************
C:\GOG Games\Earth 2150\Earth2150.exe
Wed Jul 26 15:09:02 2000
Sat Feb 17 18:10:05 2018
------------------------------------------------------------------
Unhandled Exception
Code: c0000005
Description: EXCEPTION_ACCESS_VIOLATION
Exception address: 0x07bf49c0
Registers: EAX = 0x07bf49c0 EBX = 0x00000004 ECX = 0x00000000 EDX = 0x00000018
Registers: ESI = 0x037dae90 EDI = 0x037dae9c EBP = 0x0018f748 ESP = 0x0018f738
Registers: EIP = 0x07bf49c0 CS = 0x00000023 SS = 0x0000002b Flg = 0x00210206
Registers: DS = 0x0000002b ES = 0x0000002b FS = 0x00000053 GS = 0x0000002b

Call stack:
------------------------------------------------------------------
module not accessible
address: 0x07BF49C0
Module: C:\GOG Games\Earth 2150\Earth2150.exe
module not accessible
address: 0x00570E40
module not accessible
address: 0x00463890
module not accessible
address: 0x00655983
module not accessible
address: 0x0062B003
module not accessible
address: 0x00627953
module not accessible
address: 0x0062989A
module not accessible
address: 0x00655B70
module not accessible
address: 0x0062B003
module not accessible
address: 0x0062AD46
module not accessible
address: 0x006680DA
module not accessible
address: 0x0040A9FF
module not accessible
address: 0x00409F49
module not accessible
address: 0x00720C83
Module: C:\Windows\syswow64\kernel32.dll
module not accessible
address: 0x767F343D
Module: C:\Windows\SysWOW64\ntdll.dll
module not accessible
address: 0x77569832
module not accessible
address: 0x77569805
------------------------------------------------------------------
ive got the same crash on gamemode issue but adding the exe to the dep exetion list seems t have done nothing
Post edited October 13, 2019 by bigpixxle
avatar
bigpixxle: ive got the same crash on gamemode issue but adding the exe to the dep exetion list seems t have done nothing
In case if problem is still present. Windows can break DEP exclusions if you have other compatibility parameters active, in this case you need to manually fix the issue in registry.

I have Windows 8.1 and for me it was in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

You need to find exe you want to have excluded from DEP there in the list and check if space is present before or after DisableNXShowUI. I my case with 2150 EftBP it was DISABLETHEMES HIGHDPIAWAREDisableNXShowUI (no space between last two parameters). After adding space game works fine (DISABLETHEMES HIGHDPIAWARE DisableNXShowUI).
Post edited January 24, 2020 by TearOfTheStar
Dont know if you're still interested, but I found a solution that worked for me:
make a custom shortcut of the .exe file directly. No idea why it works, but it does. Something is apparently hinky with the gog provided shortcut. Although directly activating the exe file itself also had the problem too. Regardless this worked so gl.