Runtime error and crash

[KeyCat]

At least the mystery now seems to be cleared up so we know why and when these CTD's happens and people can stop chasing "ghosts" in their systems by swapping hardware/drivers etc. (since it's about the programs own adressing space the Allocator utility is no help at all, my bad).

 

Tried last night and I can also reproduce the crash in my end by using F11 view and cruise around in the 3D world until my RAM fills up, my magic number is ~1 350 000 KB then simulator.exe CTD.

 

I don't know much about game/sim coding (and no offence to anyone) but writing a program that doesn't clean up unused data/resources and just keep filling up the RAM seems like a bad design choice to me!?

 

A couple of questions...

 

1. Since this issue appeared after the 1.2.1 patch in FC2 and I never had any CTD issues flying several hours on 104th for example (using the same settings) first question would be - why was it changed?

 

Probably not an quick answer to that one but I had to ask :)

 

2. Good to hear it's /LARGEADDRESSAWARE and I guess that means that I can use the /3GB switch on XP to upper that limit of "~1.35 GB RAM use then CTD" even if being RAM challenged at 2 GB RAM + SWAP?

 

/KC

Edited May 21, 2010 by KeyCat

[winz]

I don't know much about game/sim coding (and no offence to anyone) but writing a program that doesn't clean up unused data/resources and just keep filling up the RAM seems like a bad design choice to me!?

This engine is an iteration of the same engine eagle dynamics uses for years. Fitting a something that determinates what textures/geographic date/sounds... can be free up might not be an easy task, and can lead to stability issues. The 2GB limit was not an issue before, graphic cards had less VRAM, computers couldn't cope with that amount of info...

 

1. Since this issue appeared after the 1.2.1 patch in FC2 and I never had any CTD issues flying several hours on 104th for example (using the same settings) first question would be - why was it changed?

They may added something that increases the memory consumption. Maybe you were just under the CTD limit and this little something cause it to step the line.

 

2. Good to hear it's /LARGEADDRESSAWARE and I guess that means that I can use the /3GB switch on XP to upper that limit of "~1.35 GB RAM then CTD" even if being RAM challenged at 2 GB?

Yes, I too have 2GB of ram and gave it a try yesterday. Without the /3GB switch the simulator crashed around 1,4GB allocated. With it I managed to take to 1,6GB without problem.

There were some minor issues cause by the 2GB, when they ran out the swap file kicked in and game freezes for few seconds every time it tried to allocated another chunk of memory. I even got a loading screen. But the simulator survived and game didn't crash. (another job well done on the stability for ED team)

Edited May 21, 2010 by winz

[71st_Mastiff]

you need to go the your mother boards manufactures web page and read the bios release specs. or ask them or check there forums. I always check for bios updates every month .

:book:

 

It's still all good :)

 

Man, i had to crash out lastnight and get some sleep, this PC has had me up for too long and stressing me out, so damn happy it's finally resolved :D

 

Have to say big thankyou to everyone who helped me out, no doubt the discussions we've all been having on here will help out others who are still encountering runtime errors or crashes.

 

Now i'm wondering, was it the BIOS update i did, or the virtual memorysize change that corrected my issues......

[Pilotasso]

Once everything is working ok avoid further BIOS updates unless your going to upgrade your hardware.

[71st_Mastiff]

Once everything is working ok avoid further BIOS updates unless your going to upgrade your hardware.

 

or theres a fix for the OS and I/O's

[104th_Taipan]

This is my error code

 

Problemsignatur:

Problemereignisname: APPCRASH

Anwendungsname: simulator.exe

Anwendungsversion: 1.2.1.0

Anwendungszeitstempel: 4be3ce15

Fehlermodulname: AsyncNet.dll

Fehlermodulversion: 0.0.0.0

Fehlermodulzeitstempel: 4be3ce17

Ausnahmecode: c0000005

Ausnahmeoffset: 0000bcd8

Betriebsystemversion: 6.0.6002.2.2.0.256.6

Gebietsschema-ID: 3079

Lesen Sie unsere Datenschutzrichtlinie:

http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0407

[Panzertard]

Gents, I'll just add some observations I've done over the years.

 

AMD architecture may present some challenges for games.

My intel is somewhat dated on the subject, so sorry if I mislead you here - but the builtin memory bus/manager for on the CPU have caused myself a bit of grief over the years. Quite often I had to rely on BIOS updates and tweaking my hardware (downclocking memory timings / bus speeds) to make the computer run stable in a few titles.

But due to how many Intel users there are out there, problems on the intel platform is more likely to get detected earlier.

 

Please do not understand this as "stay away from AMD", instead take it as a advice to try to keep yourself updated on the architecture in your computer - especially when you plan to use it for demanding titles.

AMD is still a great platform, efficient, cost-wise and overclocking friendly.

 

Free hint: This is why we so often for your DxDiag reports - so we can get a bigger picture of all of those who have problems:

ATI vs Nvidia, AMD vs Intel, O/C or not etc.

But most important, digging a bit deeper into your PC-configuration to assist you directly.

 

We still need to be able to reproduce your issues before they can be fixed.

Luckily for us, there's been a few more AMD & ATI testers joining (and lo-spec computers) - more possible configurations are being tested with the sims. Hopefully this will improve detection of crashes for PC-configurations outside the hi-spec mainstream so many testers like to use. ;)

 

------------------------

 

For those with crash issues - please read post #1:

TROUBLESHOOTING - Help us helping you (FC2 edition)

 

-

[Mustang]

You know, i feel kinda bad now that my PC is stable with FC2.0 and DCS, that BIOS update i did really did fix it, and now we still have a whole load of people still crashing badly and we haven't got an answer for them.

 

I personally will still be looking for a solution, and if i do come up with any ideas i won't hesitate to post them!

[KeyCat]

Good to hear you found a solution Mustang!

 

This engine is an iteration of the same engine eagle dynamics uses for years. Fitting a something that determinates what textures/geographic date/sounds... can be free up might not be an easy task, and can lead to stability issues. The 2GB limit was not an issue before, graphic cards had less VRAM, computers couldn't cope with that amount of info...

 

Agree the foundation is old but to me that would suggest that it was even more important back then when we had 256-512MB RAM to release unused RAM/resources!?

 

They may added something that increases the memory consumption. Maybe you were just under the CTD limit and this little something cause it to step the line.

 

True and that crossed my mind as well but it would be interesting to know the real answer from the people in the knows a.k.a developers.

 

Yes, I too have 2GB of ram and gave it a try yesterday. Without the /3GB switch the simulator crashed around 1,4GB allocated. With it I managed to take to 1,6GB without problem.

There were some minor issues cause by the 2GB, when they ran out the swap file kicked in and game freezes for few seconds every time it tried to allocated another chunk of memory. I even got a loading screen. But the simulator survived and game didn't crash. (another job well done on the stability for ED team)

 

Hmm, tried the /3GB switch in Boot.ini on my XP Pro but now when FC2 is hitting the ~1.35 GB RAM mark it do not CTD instead it completely freezes (no error messages, logs etc) and I have to hard reset my PC :(

 

Do you mind sharing your line in your Boot.ini as well as the rest of your hardware combo?

 

/KC

Edited May 22, 2010 by KeyCat

[KeyCat]

Anyone else tested the /3GB switch in XP Pro? If so can you please share your line in Boot.ini?

 

Lowering settings doesn't really solve this issue it just delays the CTD (or freeze with the /3GB switch) but it will happend in both FC2 and BS, it's just a matter of how long time you can fly around in the 3D world until the simulator.exe RAM-usage reaches the ~1.35 GB mark then you will experience it (at least on my machine and I can reproduce it over and over just by using the free camera view - F11).

 

Is this issue being looked into by the developers?

 

Edit: Just wanted to add that the RAM-size my other friends running on Vista was 4 GB for both of them.

 

/KC

Edited May 23, 2010 by KeyCat

[winz]

Well, I'm runnig vista, so cannot help you much on the boot.ini

I assume that the freeze is a sign that your system cannot handle the /3GB switch

[RvEYoda]

Well, I'm runnig vista, so cannot help you much on the boot.ini

I assume that the freeze is a sign that your system cannot handle the /3GB switch

 

My gpu drivers dont even load if I have this switch activated, so I recommend using a 64bit OS - then you dont have to worry about it.

[Breakshot]

Anyone else tested the /3GB switch in XP Pro? If so can you please share your line in Boot.ini?

 

Here is my 3gb modded boot.ini line below... In my case i havent noticed any issues with this tweak, rather so far everything "seems" more stable... no CTDs or such yet... so im def keeping this unless something pops up...

 

[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP 3GB Expanded" /noexecute=optin /fastdetect /3GB /USERVA=2500

Needless to say... try at your own risk!

Oh and i got 4gb of Corsair XMS2 ram... XP Pro SP2

Edited May 23, 2010 by Breakshot

[KeyCat]

Well, I'm runnig vista, so cannot help you much on the boot.ini

I assume that the freeze is a sign that your system cannot handle the /3GB switch

 

Thanks for letting me know winz, I may have missunderstood you running XP, my bad...

 

And yes, MS do warn about other side effects when using the /3GB switch and I did noticed some wierd stuff when I tested ArmA 2, got CTD twice there within 30 minutes and never had before, also had problems to connect via RDP to this machine!?

 

http://msdn.microsoft.com/en-us/library/Aa366521

 

Here is my 3gb modded boot.ini line below... In my case i havent noticed any issues with this tweak, rather so far everything "seems" more stable... no CTDs or such yet... so im def keeping this unless something pops up...

 

Thanks for sharing Breakshot, I will try with your /USERVA value. I did try both without and with /USERVA=2900 (MS recommendation).

 

@Yoda: Windows 7 64-bit/32-bit is not an option for me at the moment since MS decided to stop supporting the game port since Vista. I'm still using my old (but perfectly working) TM FLCS + TQS SWF22 Digital and flying FC2/BS without HOTAS is just not working for me.

 

/KC

Edited May 24, 2010 by KeyCat

[Kuky]

I have an issue where in most mission I fly online or offline I get my RAM usage increasing constantly, sometimes it goes quicker then others, probably depends how much is going in the mission. If RAM usage increases pretty rapidly (say 10MB every 7-10sec) it will reach almost 4GB and that's how much RAM I have installed. ALT/TAB out and RAM gets freed up so I can fly more but it keeps rising again.

 

I have latest BIOS for my motherboard, I use Windows 7 64bit (so no need to try this 3GB switch) and I can figure out what's causing this RAM usage to go up. Sometimes it stays steady even if I fly around, but sadly this doesn't happen too often.

[HiJack]

edit: changed VirtualRAM/pagefile back down to system managed, and i haven't encountered any crashes, so i believe it was something in my BIOS update that fixed it for me.

 

You have 2 disks Mustang! Select system managed swap on both your drives and get a swap file for 8192 anyway :smartass: Cant hurt :music_whistling:

 

(HJ)

[KeyCat]

Last night I tried several different /USERVA settings along with the /3GB switch on XP Pro but no go. This issue is effectively ruining the MP fun for me in both FC2 and BS!

 

/KC

[71st_Mastiff]

WIN XP users 32bit; for the 64bit XP users, I'm not sure if your system is over 4gb use?

 

Just increase you virtual page file in a separate partition from low 512mb to 4094mb high.

 

you need to make sure it's on a separate partition due to the fact the write head for the drive can work both ends more efficiently.

 

FC2 and BS both demand higher ram usage.

even though it states in the read me the lowest but it seems to be the culprit.

 

:joystick:

:book:

 

try that or test it.

this day in age the more ram the better off you are, as games are starting to load in the front-side more and more ram usage.plus all the inputs controllers and resident programs usage too.

Edited May 26, 2010 by Mastiff

[71st_Mastiff]

jack what Mobo you running? theres seems to be an issue with ASUS and more than 2TB new bios out for that. if not Asus just check your manufactures bios updates for any if. :thumbup:

 

You have 2 disks Mustang! Select system managed swap on both your drives and get a swap file for 8192 anyway :smartass: Cant hurt :music_whistling:

 

(HJ)

[KeyCat]

WIN XP users 32bit; for the 64bit XP users, I'm not sure if your system is over 4gb use?

 

Just increase you virtual page file in a separate partition from low 512mb to 4094mb high.

 

you need to make sure it's on a separate partition due to the fact the write head for the drive can work both ends more efficiently.

 

Been running the page file on separate drive for ages and tried up it to min 2048 MB - max 8096 MB already, it makes no change.

 

FC2 and BS both demand higher ram usage.

even though it states in the read me the lowest but it seems to be the culprit.

 

So tell me, why did I not have these problem before the compabilty patches!?

 

As sayed before, with exact same machine I could fly for hours on end at any graphic settings in MP without CTD's, no issues at all!

 

Now I'm lucky if I can fly for ~60-80 minutes with lowered graphic settings before the CTD comes and thats if I remember to regulary ALT-TAB back to the desktop and "flush" the RAM usage of simulator.exe (often this ALT-TAB to the Desktop and back also screws up the graphics and I have to quit and restart FC2/BS due to this).

 

/KC

Edited May 27, 2010 by KeyCat

[joker_89]

No one's got a solution? Same annoying problem here... The patch does not make big difference so far, then we could try a revert to previous version copying new campaigns in the rigth folder

[Panzertard]

Joker, try to give a bit more detail before you start hammering the thread. Please be specific. :)

"Same annoying problem" - what does that mean?

 

There's probably 123 different reasons for the crashes reported.

Which one's is yours?

Symptoms and data needed, like dxdiag reports - crashreports etc.

 

"No one's got a solution"? To which symptom?

Some of them who have been reported here there is:

- BIOS incompatibility, firmware BIOS upgrade.

- More memory / upgrade to Win7 x64.

- Sanitize memory by minizing application at regular interval.

- Broken Windows, reinstall it.

- Fly on another server, with smaller missions.

- Bad upgrades - old install contained too many customizations/mods. Reinstall with a fresh 1.0.

[joker_89]

ops my apologies :poster_oops:

 

I've patched from a fresh install of FC2 and after 1 hour or little more i got the same problem reported at the beginning of this thread playing the "Spring Blood" campaign in SP. No CDTs before the patch.

 

I'm using Windows 7 recently installed, latest drivers and MB Bios.

RAM 2Gb.

 

attached last file .ERROR

DCS-20100525-181206.zip

[Panzertard]

Okai, thats the "annoying" one yes, which we have little understanding of yet.

All I can is to encurourage you to try some of the workarounds suggested by a few of our fellow community members here.

[Garuda000001]

Yeah I'm havin the same problem except mine does it when i click play game. My computer used to be XP but i upgraded it to vista not too long ago. please help.