KeyCat

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. 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

And why shouldn't I? Something is porked with the memory handling and some of you guys are living in denial. Re-read my post above! /KC

I agree that Windows 7 64-bit may be the future but it's 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. And last time I checked XP was listed on ED's website of supported OS'es for both FC2 and BS. Also this bug/issue is not bound to XP with 2 GB only. My two friends - Salsam and RedOne - are both running Vista with 4 GB RAM and are experiencing the exact same issue. /KC

Sure... Core 2 Duo E6850 Gigabyte GA-EX38-DQ6 (Rev 1.1) with F4B BIOS 2 GB Corsair Dominator CM2X1024-8500C5D Realtek ALC889A High Definition Audio System (Driver version R2.24) GeForce GTX 260-216 896 MB (Driver version 191.07 WHQL) Windows XP Pro SP 2 (32-bit) with DirectX 9.0c (February 2010 release) FLCS & TQS with Digital F22 (Driver Ver: 1.03 SWF22 Hardware Ver: 1.01) Antec TruePower Trio 550 W PSU Also tried changing my paging file to various settings, currently set at min 2048 MB - max 8096 MB. And while at it... Kudos to 104th for having one of the best MP servers up running! And just to clarify the problem is not related to your server, it's that when it gets crowded more RAM is used I guess and thats why I experienced the issue there first. /KC

For thoose who not own FC2 as well and maybe not read Mustangs thread over in the FC2 section http://forums.eagle.ru/showthread.php?t=53874 The issue is somehow related to the sims memory management. At least we now know why and when these CTD's happens. For me the CTD happens everytime the simulator.exe process reaches the ~1.35 GB mark. Since both FC2/BS are /LARGEADDRESSAWARE I also tried booting XP Pro with /3GB (both with and without the /USERVA=XXXX) but problem persists. Additionally, with the /3GB switch enabled FC2/BS do not CTD instead it completely freezes when the simulator.exe RAM-usage reaches the ~1.35 GB mark (no error messages, logs etc) and I have to hard reset my PC :( So on my rig it's not a matter of if FC2/BS CTD/freeze but when and this issue is effectively ruining the MP fun for me in both FC2 and BS! /KC

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

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 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

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

Good to hear you found a solution Mustang! 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!? 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. 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

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

Anyone knows about a utility program that can log a process memory usage to a textfile (not Performance Monitor)? /KC

Have you set/limit your paging file to anything specific in Windows 7? On my XP I have paging file size set to 2 GB on my secondary drive (been running this way for years) but it would be an easy test to change it and see if things changes, will do so later tonight and see. /KC

Just tried to see if it was the same for me in FC2 but after joining 104th server and picking an A-10 then using F11 view for a while spinning around 360 etc. I got my simulator.exe process to peak at 1 373 728 KB and no error for me. Will test more later when getting back. /KC

True, didn't think about that. Maybe the issue can be forced by allocating most of the memory with a tool like Allocator? A handy tool but I don't know how it behaves on Vista/Win 7 tho? http://www.codeproject.com/KB/cpp/alloc.aspx /KC

Sorry for my ramblings above guess I just have to blame the frustration :) I didn't get you wrong and I fully understand that testers/dev's need to be able to reproduce the issue somehow in order to be able to fix it. Lets hope we are on to something with that "2 GB RAM" mentioned in Mustangs thread but I see Dredge have 4 GB so maybe not. Time and more testing will tell I guess... /KC

Thats a better word for it ;) BTW, would be interesting to know how much RAM you have Panzertard since you haven't got this issue? And if it indeed is this thats causing the issue it should be quite easy for you to replicate by pulling out some RAM sticks. /KC

I'm also on 2 GB RAM so maybe you guys are on to something here, at least now we may have a "common dominator" that makes some sense. Gonna check with my friends how much RAM they have... Why? If it indeed is a bug I'm sure ED will fix it. /KC

Yea, I agree this is a wierd issue and still unanswered why it only affects some on the same server!? But non the less it's a real issue for several FC2/BS pilots and I'm also sure the hidden numbers are quite high as well since it's still early days after the patches and few people find there way to this support forums and have the time/energy/skill/will to report things like this (like my two friends) they just want to fly and if it doesn't work many just drops it for something else. Anyway just to add some more facts in case it can shed some light on this issue. Along with the info in the "C:\WINDOWS\system32\kernel32.dll" crashes I noticed that this is written in the Event logger.... Faulting application simulator.exe, version 1.2.1.0, [b]faulting module [/b] [b]protect.dll[/b], version 5.70.13.2, fault address 0x00e4ab94. Without the insight (and knowledge) the dev's have all I can do is keep guessing like you but "what if" it's the StarForce protection thing that for some reason are playing tricks on some of us after the patching? Unlikely yes but just to add another theory to the mix ;) /KC

First time I heard it happening on another server than 104th's. Dredge, if you can please also share your crashlog/s and/or details about the server including number of players, mission etc. See Panzertards post for details... http://forums.eagle.ru/showthread.php?p=738467#post738467 Don't know if this information will help the dev's or anyone else but since I'm most likely busy the rest of the week I post the last set of crashlogs and error message received for reference... # -------------- 20100517-185359 -------------- C:\WINDOWS\system32\kernel32.dll # E06D7363 at 7C81EB33 01:0001DB33 # # EAX = 0013F6C0 # EBX = 76C6EBC8 # ECX = 00000000 # EDX = 00006E6F # ESI = 0013F750 # EDI = 0013F750 # CS:EIP = 001B:7C81EB33 # SS:ESP = 0023:0013F6BC EBP = 0013F710 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00200206 # -------------- 20100517-203434 -------------- C:\WINDOWS\system32\kernel32.dll # E06D7363 at 7C81EB33 01:0001DB33 # # EAX = 0013EE54 # EBX = 00000000 # ECX = 00000000 # EDX = 00000000 # ESI = 0013EEE4 # EDI = 0013EEE4 # CS:EIP = 001B:7C81EB33 # SS:ESP = 0023:0013EE50 EBP = 0013EEA4 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00200206 # -------------- 20100517-214129 -------------- C:\WINDOWS\system32\kernel32.dll # E06D7363 at 7C81EB33 01:0001DB33 # # EAX = 0013F6C0 # EBX = 76AB9C48 # ECX = 00000000 # EDX = FF006E6F # ESI = 0013F750 # EDI = 0013F750 # CS:EIP = 001B:7C81EB33 # SS:ESP = 0023:0013F6BC EBP = 0013F710 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00200206 # -------------- 20100518-170034 -------------- C:\WINDOWS\system32\kernel32.dll # E06D7363 at 7C81EB33 01:0001DB33 # # EAX = 0013F6C0 # EBX = 703EF028 # ECX = 00000000 # EDX = 7B006E6F # ESI = 0013F750 # EDI = 0013F750 # CS:EIP = 001B:7C81EB33 # SS:ESP = 0023:0013F6BC EBP = 0013F710 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00200206 # -------------- 20100518-202606 -------------- C:\WINDOWS\system32\kernel32.dll # E06D7363 at 7C81EB33 01:0001DB33 # # EAX = 0013F7FC # EBX = 7F61A168 # ECX = 00000000 # EDX = 40006E6F # ESI = 0013F88C # EDI = 0013F88C # CS:EIP = 001B:7C81EB33 # SS:ESP = 0023:0013F7F8 EBP = 0013F84C # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00200206 # -------------- 20100518-202621 -------------- D:\Games\DCS - Ka-50\bin\x86\stable\AsyncNet.dll # C0000005 ACCESS_VIOLATION at 03DBBC08 01:0000AC08 # # EAX = 4F26F53C # EBX = 00000000 # ECX = 00000000 # EDX = 5C6BF238 # ESI = 5C6BF238 # EDI = 00000000 # CS:EIP = 001B:03DBBC08 # SS:ESP = 0023:5C6BF200 EBP = 00000041 # DS = 0023 ES = 0023 FS = 003B GS = 0000 # Flags = 00010206 Also at one time only I got the runtime error window before the CTD, see attachment. /KC

As promised yesterday I posted Salsams (and one of mine) crashlogs in Mustangs thread over in FC2 section since thats what he flew but I'm pretty sure we are dealing with the same issue in both sims here... http://forums.eagle.ru/showpost.php?p=907077&postcount=42 /KC

Here is one from me when I took an A-10 for a spin after the 1.2.1 patch on 104th... For my system specifiations see thread in BS part of forum, I'm pretty sure we are dealing with the same issue in both sims here... http://forums.eagle.ru/showthread.php?t=54162 Below is four crashlogs and breif specifications from a friend named Salsam (he is not active on this forum so I told him I would post it) all while flying A-10/Su-25T on 104th server. I only managed to get a brief system specification from Salsam over TS yesterday but he told me that the first three crashlogs was with 191.07 WHQL drivers and before yesterdays flight he had upgraded to latest 197.45 WHQL drivers. OS: Vista GPU: nVidia 9800 GX2 (tested with both 191.07 WHQL and latest 197.45 WHQL) Been looking at the posted logs and they are "all over it" and no real pattern shows up but it's a complicated piece of software (and a pretty complex MP mission on 104th) so I guess anything can happen. Only the devs will be able to figure out the exact cause of this bug/issue and all we can do is guessing and (more importantly) provide them with as much facts and data as possible so they hopefully can reproduce it on their end... /KC

Yes, I think we are experiencing the same problem here and whats interesting is that we have very different systems - which may rule out GFX driver issues etc... You run Win 7 - I run Windows XP Pro You have a ATI GFX card - I have a nVidia My other two friends (Salsam and RedOne) also flew A-10's for a short while on 104th before they again CTD'ed, this time almost simultaneously (they where in very close proximity to each other)? They are not active on this forum but I managed to ask Salsam if he could e-mail me the *.crash + error*.* files for comparsion. It's getting to late here now so it have to wait until tomorrow but then I will upload his files here along with their brief systems specifications... /KC

To bad, same old CTD after about ~2.5 hours but this was the longest MP session I had on 104th server after the patches! I noticed that the player count started to increase from ~20 to ~40 players the last 30 minutes before the crash so... Ohh well time will tell I guess... /KC

Tonight I'm trying ALT-TAB trick and currently 2+ hours and counting on 104th server with 32+ players and no CTD so far - lets hope it continues this way :) /KC

Just to keep ruling things out I tried 104th again last night with minimum apps/services running (i.e not loading TS etc. and also removed DirectX.cpl just for test) - 19 processes running at OS boot - but no go, got CTD's twice. Numbers of players (network traffic/chat/events?) seems to play part - I CTD faster if server is crowded, keyword is "seems" since this issue is damn random it's hard to say for sure and I could be wrong. Also talked with some friends (will try to get them to post here) that tried MP on 104th and in our little "group" 3 out of 5 got same/similar CTD's in FC2/BS while on 104th server. More tests will follow, hopefully tonight when I get back home... /KC