[CLOSED]Game Crashes since 1.2.6 - 64 Bit OS

[NineLine]

Which modules do you own?

[PondLife]

It is being done, but at the same time you can never have too much data, and I will tell you that a number of problems can be solved with troubleshooting, we have to exhaust those first... ED cant replicate every possible PC configuration out there... so we need to help, specially if we are effected by issues.

 

Noted, and I agree it's virtually impossible to replicate all hardware and software configurations for developers, however this doesn't appear to be related to a specific edge case of software or hardware incompatibility as it occurs on multiple configurations with a large number of online servers and clients.

 

Anyway, I'm glad to hear ED is tacking it seriously and looking into it.

[Spectre_USA]

I agree on it being the "it's a software thing" statement.

 

The error message I get while flying the F-15C, twice in a row now, pretty much

confirms it for me;

 

[gregecslo]

Which modules do you own?

Just FC3

[NineLine]

Any chance you could try a clean install of DCS World without FC3, and just see if it runs? Then add in FC3 back in?

[Antimon]

Multiplayer is crashing due to low memory warnings since 1.2.6. I have tried it with FaceTrackNOIR and without because I thought it was eating ram but no luck, done repair and updates to DCS World, defragged system etc. etc. but problem remains. I've also tried different settings on pagefile, but no effect. 4Gb pagefile on SSD and System allocated on other HD which makes it total of about 12Gb, system RAM is 8Gb, which should be enough according to specs recommendations...

 

I join multiplayer (simple freeflight missions) normally and after a while I'm getting graphic anomalies. Windows pops up a few warnings about low mem and after couple of minutes "DCS has stopped working" Specs are over recommended and there was no problem except the long loading times before 1.2.6 patch. I'm quite new to DCS, so if logs etc. are needed, could somebody guide me trhough what to check from where and what else is needed?

 

From what I've read here, a lot of people are having similar issues since 1.2.6, so it must be a problem with DCS, not pc-related...

Edited September 21, 2013 by Antimon

[KewlerMouh]

# -------------- 20130920-180337 --------------

 

# C0000005 ACCESS_VIOLATION at E41C4601 00:00000000

00000000 00000000 0000:00000000

E41C4601 002BF190 0000:00000000 ?startMessageTransmition@wCommunicator@@MEAAXAEBV?$Ptr@VwMessage@@@Mem@@@Z()+51

E41CDEFC 002BF220 0000:00000000 ?transmitMessage@@YAXPEAVwCommunicator@@AEBUwMessageData@@@Z()+33C

3FE998F3 002BF400 0000:00000000

E326EA9D 002BF440 0000:00000000 ??1Reader@Mail@@UEAA@XZ()+27D

E2C195DE 002BF4B0 0000:00000000

E2C196B1 002BF500 0000:00000000

E2C136CE 002BF530 0000:00000000

E2C26994 002BF5A0 0000:00000000

E2C3F403 002BF5D0 0000:00000000

E2C53A73 002BF600 0000:00000000

3FF2AA45 002BF660 0000:00000000

3FF40A14 002BF690 0000:00000000

3FF408EB 002BF6C0 0000:00000000

3FFD4B38 002BF730 0000:00000000

3FFD6139 002BFD30 0000:00000000

3FFD8DAB 002BFDE0 0000:00000000

76F9652D 002BFE10 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D

771CC541 002BFE60 0001:0002B541 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

[KewlerMouh]

# -------------- 20130921-012739 --------------

 

# C0000005 ACCESS_VIOLATION at E5BC4601 00:00000000

00000000 00000000 0000:00000000

E5BC4601 0017ED00 0000:00000000 ?startMessageTransmition@wCommunicator@@MEAAXAEBV?$Ptr@VwMessage@@@Mem@@@Z()+51

E5BCDEFC 0017ED90 0000:00000000 ?transmitMessage@@YAXPEAVwCommunicator@@AEBUwMessageData@@@Z()+33C

3F4F98F3 0017EF70 0000:00000000

E8E9EA9D 0017EFB0 0000:00000000 ??1Reader@Mail@@UEAA@XZ()+27D

E26C95DE 0017F020 0000:00000000

E26C96B1 0017F070 0000:00000000

E26C36CE 0017F0A0 0000:00000000

E26D6994 0017F110 0000:00000000

E26EF403 0017F140 0000:00000000

E2703A73 0017F170 0000:00000000

3F58AA45 0017F1D0 0000:00000000

3F5A0A14 0017F200 0000:00000000

3F5A08EB 0017F230 0000:00000000

3F634B38 0017F2A0 0000:00000000

3F636139 0017F8A0 0000:00000000

3F638DAB 0017F950 0000:00000000

7701652D 0017F980 0001:0001552D C:\Windows\system32\kernel32.dll BaseThreadInitThunk()+D

7714C541 0017F9D0 0001:0002B541 C:\Windows\SYSTEM32\ntdll.dll RtlUserThreadStart()+21

[KewlerMouh]

It ran quite stable, only had 2 crashes in somewhat like 10h of flying time.

 

The size of page file/virtual memory seems to have an impact.

 

Which is odd, because DCS doesn't seem to use even the 8GB physical RAM on our machines completely (around 5GB during missions).

 

Before I had the setting to "Automatically manage paging file size for all drives", which resulted in instant crashes and rendered 1.2.6 unplayable.

 

Then I allocated 8GB manually, got I crash after one hour (first one above), allocated to 12GB manually, got 1 crash in approx. 9h that followed (second one).

 

We played maps, which where last week unplayable like sochi starvation, blindsighted and sepperatists aggression campagin with ka50, a10c and su25.

 

Btw my friend with same system specs had with 12 GB allocated on his Win8 Machine no single crash.

[SkateZilla]

I understand you...

But now you have to understand me.

I paid for this game and now I see more and more errors.

 

OK back to problem.

There is no crash file even created, see image here:

http://shrani.si/f/2e/m6/3qvI4jzB/imag0017.jpg

 

Furthermore event log shows this error:

Faulting application name: DCS.exe, version: 1.2.6.17746, time stamp: 0x5225b96f
Faulting module name: fc3_protect.dll, version: 5.70.46.4, time stamp: 0x5225bdb7
Exception code: 0x40000015
Fault offset: 0x000000000002e2ce
Faulting process id: 0x63c
Faulting application start time: 0x01ceb55d0c9aafe2
Faulting application path: D:\Games\DCS World\bin\DCS.exe
Faulting module path: D:\Games\DCS World\mods\aircrafts\Flaming Cliffs\bin\fc3_protect.dll
Report Id: bca105c2-2151-11e3-be83-0015af2279ac
Faulting package full name: 
Faulting package-relative application ID:

 

This is all I have.

 

BTW, 8GB RAM and 4GB pagefile, this should do it.

 

TBH, Any Page file should be Equal or Larger than the Total Amount of Physical RAM.

 

Not saying that's your problem.

 

To note, my system, sets it at 16 GB when on Auto, and I Use the "Recommended" Setting of 24 GB.

 

But if windows triggers a Command to move all memory to the Page File for later use and the Page file is only half the size of the amount of ram used, your gonna get hit with a ACCESS_VIOLATION Error.

 

If Windows has a 12 GB Page File and Stores 10GB worth of Data for later Use (Usually it's Skype Logs, Photoshop Files, Clipboard data etc etc), and you Boot DCS and Windows wants to Store 6 GB worth of Data for that Process, which causes the process to terminate with Access_Violation.

Edited September 21, 2013 by SkateZilla

[Zeke]

What do you guys recommend to set the file sizes at? When I go into the options for virtual mem and try to set it manual, I see an "Initial" and a "Maximum" setting.

[SkateZilla]

Initial is the General Setting,

 

Maximum is the Max you want windows to expand it too.

 

they both should be about 3x your physical ram.

[apollomaker]

Chasing Witches

 

Hello All --- well, after trying a few of the recommended "fixes" posted, it is clear that the problem with 1.2.6 crashing is 1.2.6. I have reverted back to 1.2.5 (again) which continues to work just fine. Have tried it all, trying to find a clue, but nothing.

 

As before, my system is up-to-date, works fine with all major programs, as well as DCS 1.2.5. My system resources should be more than adequate and well beyond the average system.

 

So PLEASE!!! :helpsmilie: Please find the issue/difference in 1.2.6 so we ardent supporters of DCS can get on with gaming --- :D

 

Thanks, Bob

[AtaliaA1]

Hello All --- well, after trying a few of the recommended "fixes" posted, it is clear that the problem with 1.2.6 crashing is 1.2.6. I have reverted back to 1.2.5 (again) which continues to work just fine. Have tried it all, trying to find a clue, but nothing.

 

As before, my system is up-to-date, works fine with all major programs, as well as DCS 1.2.5. My system resources should be more than adequate and well beyond the average system.

 

So PLEASE!!! :helpsmilie: Please find the issue/difference in 1.2.6 so we ardent supporters of DCS can get on with gaming --- :D

 

Thanks, Bob

 

 

Sorry to hear that you had problems. I love this Sim.

 

Take a look here I believe you will see a fix as others did.

 

http://forums.eagle.ru/showthread.php?t=114200

[apollomaker]

Sorry to hear that you had problems. I love this Sim.

 

Take a look here I believe you will see a fix as others did.

 

http://forums.eagle.ru/showthread.php?t=114200

 

Hi AtaliaA1 --- Thanks for your comment, but this is really not the way to "fix" the problem(s) with 1.2.6. Only the devs can do this, the right way, by identifying the ACTUAL CAUSE of the problem, patching the code, then putting out a new release. Guessing and hoping that we know what the problem is can do more harm than good. This is a job for the professionals to fix properly.

 

Thanks / Cheers --- Bob :D

[NineLine]

Guys, if I could please ask you to start your own threads when you have an issue unless you know for a fact that it is related, if you are unsure its related start a new thread anyways... I can always merge...

[KewlerMouh]

I increased the virtual memory step by step, had the last crash with 20GB allocated, now I am at 24GB and game runs quite stable so far. Last crash has been at 21st of September.

 

But now I have an another strange problem: sometimes, especially in self created missions or instand missions, the mission won't load, but the game doesn't crash. Just the Windows Mouse Cursor or Loading "Donut" appears and the game doesn't do anything at all anymore. But if I end the game alt-tabing and finishing it in the system tray, I get in-game the message "Do you want really to quit" and can exit it this way. At 2-3 attempts it loads the Mission as wanted. I will try to rebuild my DCS folder again.

 

Anyhow, I am quite satisfied with the game how it works now, thanks for your help guys, you can close the topic if you want.