CTD's out the afterburner

[maturin]

When I tried to fly a mission with the default resolution of 1000x700 on my widescreen laptop (with a much higher native res), I crashed.

 

And afterwards, when I started changing the keyboard controls, I crashed. I only got to fly for a few seconds in-between these two episodes.

 

Crashes attached in one .txt file.

 

 

# -------------- 20120503-044349 --------------

C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

# C0000005 ACCESS_VIOLATION at 610B3F07 01:00052F07

#

# EAX = 00000004

# EBX = 00215E53

# ECX = 00215E52

# EDX = 0013DE28

# ESI = 00000000

# EDI = 00000000

# CS:EIP = 001B:610B3F07

# SS:ESP = 0023:0013DDB8 EBP = 0013DE04

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

 

# -------------- 20120503-044036 --------------

C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

# C0000005 ACCESS_VIOLATION at 610B3F07 01:00052F07

#

# EAX = 00000004

# EBX = 00215E53

# ECX = 00215E52

# EDX = 001BE528

# ESI = 00000000

# EDI = 00000000

# CS:EIP = 001B:610B3F07

# SS:ESP = 0023:001BE4B8 EBP = 001BE504

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

 

 

# -------------- 20120503-043924 --------------

C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

# C0000005 ACCESS_VIOLATION at 610B3F07 01:00052F07

#

# EAX = 00000004

# EBX = 00215E53

# ECX = 00215E52

# EDX = 0020E3A8

# ESI = 00000000

# EDI = 00000000

# CS:EIP = 001B:610B3F07

# SS:ESP = 0023:0020E338 EBP = 0020E384

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

 

 

# -------------- 20120503-041937 --------------

C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

# C0000005 ACCESS_VIOLATION at 610B3F07 01:00052F07

#

# EAX = 00000004

# EBX = 00215E53

# ECX = 00215E52

# EDX = 0025E168

# ESI = 00000000

# EDI = 00000000

# CS:EIP = 001B:610B3F07

# SS:ESP = 0023:0025E0F8 EBP = 0025E144

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

 

 

# -------------- 20120503-041558 --------------

C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

# C0000005 ACCESS_VIOLATION at 640E3F07 01:00052F07

#

# EAX = 00000004

# EBX = 00215E53

# ECX = 00215E52

# EDX = 0023E0A8

# ESI = 00000000

# EDI = 00000000

# CS:EIP = 001B:640E3F07

# SS:ESP = 0023:0023E038 EBP = 0023E084

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00010202

640E3F07 0023E084 0001:00052F07 C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

640E3F07 0023E084 0001:00052F07 C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

6414A468 0023E2F4 0001:000B9468 C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

63D16228 0023E49C 0001:00035228 C:\Program Files\Eagle Dynamics\DCS World\bin\edterraingraphics3.dll ?ParseSurface@edtg@@YA_NPAUhandle_renderitem@1@ABVVec3f@osg@@ABVMatrixf@4@2ABUGlobalLights@1@ABVFog@edcg@@ABUTerrainOptions@1@PAX@Z()+4A8

64FFCAD2 0023E4A0 0001:0001BAD2 C:\Program Files\Eagle Dynamics\DCS World\bin\Visualizer.dll ?RenderSurface@SceneManager_Implement@@AAEXPAVsmCamera_Implement@@W4eDrawRoutines@edtg@@PAUhandle_renderitem@4@ABUTerrainOptions@4@@Z()+AC2

21E38C70 0023E4A4 0000:00000000

0023E9C4 0023E4A8 0000:00000000

0023EAC4 0023E9C4 0000:00000000

44FA1DE1 0023E9C8 0000:00000000

48EEC4A1 0023E9CC 0000:00000000

Edited May 3, 2012 by maturin

[maturin]

Any insight? The crash dump clearly references a particular file, and it's not like the forum is swamped right now.

[Nate--IRL--]

Any insight? The crash dump clearly references a particular file, and it's not like the forum is swamped right now.

 

Please provide detailed information about your hardware and OS - install the specific DIrectX and Visual C++ from my sig also.

 

Nate

[maturin]

I couldn't install the C++ because my computer has newer version.

 

Dxdiag attached

DxDiag.txt

Edited May 5, 2012 by maturin

[maturin]

dxdiag attached

[ALDEGA]

It appears you are running a 32-bit version of Windows which is limiting the available RAM to 3036MB. Moreover, the video controller in your laptop (ATI Mobility Radeon HD 3650) may not be sufficient.

 

You may want to try the workaround for 32-bit Windows to increase the amount of memory that DCS can use: http://forums.eagle.ru/showpost.php?p=1084420&postcount=8

Still, I'm afraid it won't help.

[maturin]

Could that really have caused an instant CTD? I manage to play ArmA 2 with this laptop, and it's sort of ridiculous if a game requires 64-bit.

[sobek]

I manage to play ArmA 2 with this laptop, and it's sort of ridiculous if a game requires 64-bit.

 

Not at all. Compare draw distances/unit numbers per mission of ARMA to DCS.

[EtherealN]

Could that really have caused an instant CTD? I manage to play ArmA 2 with this laptop, and it's sort of ridiculous if a game requires 64-bit.

 

"640K of memory should be enough for anybody."

- Bill Gates

 

(Well, Gates actually never said that, it's a myth, but you get the point. :) )

 

The exact same thing happened back in the 16- to 32-bit transition.

 

And of course, one very important thing to note is that in your case you have a full gigabyte of physical RAM that you just don't use. The only reason for this is you being on a 32-bit operating system. For that reason alone (nevermind specific software), I'd say you're better off with a 64-bit OS.

 

Try the linked 32-bit fixes and you should be fine, however.

[joey45]

..... and it's sort of ridiculous if a game requires 64-bit.

Welcome to the future.:)

[maturin]

Welcome to the future.:)

Minimal system requirements: Windows XP, Vista, 7; CPU P4 2 GHz; RAM 2 Gb; Video nVidia/ATI 256 Mb RAM, DirectX9; 6 Gb of free space on HDD; Sound card;

 

Nothing in the futuristic system reqs about 64 bit, and 2 GB RAM is not much at all.

 

Compare draw distances/unit numbers per mission of ARMA to DCS.

LOMAC had a long draw distance too, and DCS world has a view distance slider. Also, I can run ArmA 2 missions with hundreds of units. This game crashes if I load an empty map with a bicycle on it. I'm not complaining about performance, but instantaneous CTDs that prevent me from starting the game.

 

I'm still not clear on whether or how a lack of RAM is causing an 'access violation' with one particular file named edTerrain.dll

Edited May 9, 2012 by maturin

[ALDEGA]

64-bit Windows?

[ALDEGA]

"640K of memory should be enough for anybody."

- Bill Gates

 

(Well, Gates actually never said that, it's a myth, but you get the point. :) )

 

I laid out memory so the bottom 640K was general purpose RAM and the upper 384 I reserved for video and ROM, and things like that. That is why they talk about the 640K limit. It is actually a limit, not of the software, in any way, shape, or form, it is the limit of the microprocessor. That thing generates addresses, 20-bits addresses, that only can address a megabyte of memory. And, therefore, all the applications are tied to that limit. It was ten times what we had before. But to my surprise, we ran out of that address base for applications within -- oh five or six years people were complaining.

Source

[maturin]

The CMD trick did not work. Is there anything else I should try?

[Tez]

Try setting the lowest settings in the in-game options.

[maturin]

That's not the culprit.

 

The one time I got the game to run, it was with default settings and highest possible (native) resolution. What do I have to do to convince you guys that's not just my hardware being weak? The game ran. There's a very clear crash dump pointing to a single file.

[Tez]

I don't question capabilities of your hardware, the bottle neck is operation system in your case.

[maturin]

Can anyone show me where in the system reqs it says that 64 bit is required?

 

Because I find it hard to believe that this game is poorly coded enough to crash on empty map on low settings simply because less than 3GB of RAM is available in that instant. Surely someone can say something informed about the crash dump I posted.

[BigfootMSR]

The people that have posted suggestions for you have done so with a lot of experience. Try EtherealN's 32 bit switch suggestions, if that is not working, some people who have had problems with a particular file, have fixed their constant crashing due a single file by reinstalling the game.

 

This game is optimized to run on a 64 bit operating system, but through some tweaking, it is possible to run on a 32 bit system which is why the game requirements say it can run on a 32 bit system. The future is in the 64 bit operating system. Your operating system is holding you back from utilizing the full extent of the game.

[maturin]

Your operating system is holding you back from utilizing the full extent of the game.

By which you mean, crashing instantly. Absolutely no extent of the game. Optimized for 64 bit shouldn't mean unable to run on 32 bit.

 

The suggested solution didn't work, and I have reinstalled multiple times.

 

The reason I remain skeptical is that none of the experienced posters explain the connection between RAM and the specific crash report, and I seem to be the only one who thinks that Eagle Dynamics' false advertizing regarding operating system is odd.

[ShuRugal]

Optimized for 64 bit shouldn't mean unable to run on 32 bit.

 

 

on an unrelated note: 32 bit operating systems should have ended with Vista. Since the release of 7, there are no 32-bit processors on the market, so why is M$ still selling 32-bit versions of their OS? any processor capable of running windows 7 (Core 2 and newer) is based on AMD's x86-64 architecture.

 

is there some hidden advantage to using an operating system which A: hard-caps your RAM at 3.5 GB and B: fails to utilize the full instruction pipeline of your processor?

[maturin]

Laptops.

 

I am well aware of the advantages of 64 bit, but since DCS is the only game I have ever heard of to require 64 bit, alone amongst more hardware intensive, eyecandy-centric PC games, I do not enjoy being lectured about the future of gaming.

 

In any case, applying the tweak shown here has no effect: http://forums.eagle.ru/showpost.php?p=1084420&postcount=8

 

# -------------- 20120803-050512 --------------

C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

# C0000005 ACCESS_VIOLATION at 63F54B67 01:00053B67

#

# EAX = 00000004

# EBX = 00215E53

# ECX = 00215E52

# EDX = 002CE6A8

# ESI = 00000000

# EDI = 00000000

# CS:EIP = 001B:63F54B67

# SS:ESP = 0023:002CE638 EBP = 002CE684

# DS = 0023 ES = 0023 FS = 003B GS = 0000

# Flags = 00210202

63F54B67 002CE684 0001:00053B67 C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

63F54B67 002CE684 0001:00053B67 C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

63F1F6C8 002CE8F4 0001:0001E6C8 C:\Program Files\Eagle Dynamics\DCS World\bin\edTerrain.dll

65C65F0B 002CEA80 0001:00034F0B C:\Program Files\Eagle Dynamics\DCS World\bin\edterraingraphics3.dll ?ParseSurface@edtg@@YA_NPAUhandle_renderitem@1@ABVVec3f@osg@@ABVMatrixf@4@2ABUGlobalLights@1@ABVFog@edcg@@ABUTerrainOptions@1@PAX@Z()+4AB

6EDAC1DF 002CEA84 0001:0001B1DF C:\Program Files\Eagle Dynamics\DCS World\bin\Visualizer.dll ?RenderSurface@SceneManager_Implement@@AAEXPAVsmCamera_Implement@@W4eDrawRoutines@edtg@@PAUhandle_renderitem@4@ABUTerrainOptions@4@@Z()+ADF

1EC715B8 002CEA88 0000:00000000

002CEFE8 002CEA8C 0000:00000000

002CF0C4 002CEFE8 0000:00000000

44473D40 002CEFEC 0000:00000000

49196F82 002CEFF0 0000:00000000

 

Among the questions left unanswered by the overwhelming 'lol, buy better computer' response:

Is it vital to install the game's version of Microsoft C++ even though it is older than what I currently have installed?

Which of the two versions in Nate IRL's sig should I install?

Do I have to roll back my DirectX to June 2010 even though I already have DirectX 2011? I am reluctant to go monkeying around with my computer's code based on a one-size-fits-all recommendation.

Edited August 3, 2012 by maturin

[ALDEGA]

is there some hidden advantage to using an operating system which A: hard-caps your RAM at 3.5 GB and B: fails to utilize the full instruction pipeline of your processor?

Compatibility. Much more important than A and B for most consumers and enterprises.

[Nate--IRL--]

You are not rolling back you Direct X - you are updating it to the latest version of DX9 - it leaves the DX11 version untouched on your computer. Also install the C++ in my sig.

 

Nate