9 replies to this topic

[EinDinHander]

So I've been twisting my head around this. If you haven't read the longer threads on peoples experiences with this error please do. Here is how I see it.

There isn't a smoking gun commonality in which this happens across the board for everyone.

It occurs on both 7/xp 32/64 bit os's.

It can happen on a retail release of crysis.

Some have stated replacing system memory worked even though it passed a memory test. Since this error happens so randomly for me, and since the thread he posted that in is locked, who is to say that is the fix? Not me, so if that was you please post here if you have experienced it again. I've done a memory dance myself and it did not help.

No os or hardware settings seem to matter either. Page file. Amount and type of card.

People have said it came after UI2.0. Then others say after the latest patch.

So what is the main commanality in my opinion? Windoze enviroment and 3rd party exploitation of the engine. I said it. I believe we have malicious software running in memory, that cannot be moved/read or seen by the os otherwise. Or anything in it's shell. Either a rootkit or keylogger was my suspicion. It was confirmed when rkill, combofix, and fixTDSS were run. fixTDSS did not show the one thing it was designed to detect, but rkill and combofix had some fun removing some adware I had. I wish I had the log from the first run, I ran it all again with different names (to trick any potential possibilities from knowing the program is running) and it made a new log.

Here is what worries me, if this is true. It's basically a clean install. I don't visit questionable sites, or even sites with allot of ads (like free tv/movie whatever.) I'm a warranty tech, and even I have clicked on the wrong x. So I prevent myself, but still I fall victim somehow.. I know rootkits can survive formats in the MBR, but this would be nuts if a new undetectable software was out there yet to be realized, lurking in all our mem/engine bufferoverflow.

I'd like everyone experiencing this issue to run your scans. If everyone had something they didn't know it'd be interesting. I'm really looking for the guy with the clean hdd, getting the problem. That would rule out the memory, but the security of the engine could still be in question.

Please read what Chip Ninja had to say in this topic here about cry engine being exploited, botnet, etc.

https://forums.rober...-how-to-stop-it

Heh, perhaps my theory isn't far off the track here. I'm going to try playing again after my cleaning. Thoughts/scan results please!!

Edited by EinDinHander, 22 July 2014 - 09:35 PM.

[Lyoto Machida]

Even after running the repair tool or clean installs, I consistently crash most of the time on Alpine and Terra Therma since one of the recent patches. Not as big a deal anymore since you can reconnect but occasionally, the reconnect doesn't work.

[EinDinHander]

I used to think it was just river city for me. But it's by now it has happened on all of them. Not all varriations of the map maybe, but every map for sure. I really don't think it's a game content or function issue. As ninja states in the thread, I also think we are being exploited. Don't be so surprised people do it.

This is like someone making a mistake/problem picking someone's pocket, and they notice. Memory isn't as forgiving, as we can be.

Edited by EinDinHander, 22 July 2014 - 10:15 PM.

[Mcgral18]

I used to get them fairly often when I had 2 gigs of ram, although they normally occurred when loading one of the larger maps.

When I upgraded to 4 gigs (and still a 32 bit OS) not much changed, although the crashes did get more frequent with the release of the Clans. Not sure why.

Switching to a 64 bit OS installed on an SSD along with the 4 gigs of RAM seems to have fixed all the Mem Alloc errors. I haven't had one in weeks.

[Sephlock]

I fixed this problem by getting more ram.

Seriously.

I am also using a 64 bit OS but no SSD.

[EinDinHander]

To further clairify on that, I am using an SSD. So that seems now not to be a factor. GJ

Sephlock, on 22 July 2014 - 10:24 PM, said:

I fixed this problem by getting more ram.

I understand, but I'm concerned now that just makes our pocket bigger, and easier to pick without us noticing (error)

Mcgral18, on 22 July 2014 - 10:17 PM, said:

I used to get them fairly often when I had 2 gigs of ram, although they normally occurred when loading one of the larger maps.

When I upgraded to 4 gigs (and still a 32 bit OS) not much changed, although the crashes did get more frequent with the release of the Clans. Not sure why.

Switching to a 64 bit OS installed on an SSD along with the 4 gigs of RAM seems to have fixed all the Mem Alloc errors. I haven't had one in weeks.

4gigs ddr3 here, also happened on a 4gig ddr2 older machine I recently had. Eye of the beholder here. As stated, this has happened on windows 7, so I am interested to know what is different about your enviroment vs someone who is crashing under win 7. Please chime in if you are out there. 64bit would probably be the difference.

To me, upgrading the enviroment, so that abuse of remote arbitrary code execution can't happen, isn't a game fix. A fix yes but, there are still many others than XP users that refuse to go to 7/8 for other and obvious reasons. When memory can't be read, it's being used. By who and what, and reading what, is the question. Obviously the influence is outside the os or the os would have moved or choose different memory to write/read to.

Interested to see if this happens in xp64. If we got an odd ball out there.

Edited by EinDinHander, 22 July 2014 - 10:47 PM.

[cSand]

Seems to happen to me when my VRAM usage is going above a certain level. Windows gets all b*tchy and minimizes my game with a "This program is using too much memory" thing.

I can't imagine it being normal RAM for me, cause usage is under 3GB (out of 16GB) while I'm playing

Edited by cSand, 22 July 2014 - 10:38 PM.

[EinDinHander]

vram like video card ram? Or vram like virtual mem like page file? I believe the error to be system memory related, as it's number in the error changes for me if I add more or pull ram.

Edited by EinDinHander, 22 July 2014 - 11:08 PM.

[ProtoformX]

The OP is confusing a memory leak with malicious coding. O_o

[EinDinHander]

Have I? When we seemingly rule out everything except an old executable environment capable of running such code REMOTELY. 32 bit of course can run code remotely but win7 x64 would seem to have to means to stop this type of exploit whatever the means, IF this is all the case. Perhaps the engine dev's figured m$ solved it for them. Would be nice to know for sure.

If PGI investigated further, we could confirm for sure. In addition, I've asked for your inputs which I appreciate. I'd be more willing to believe this 'mem leak' were just that if I had event logs tied to mwo. Every time it happens, nothing significant is there. I haven't found on my pc nor have seen an engine generated log posted. Come on, am I to blindly believe?

If you look at the links, you can see how steam voip among other client/server engines are exploited.

I've hacked cs1.6. I'll say it. For the fact being, you can do some **** q.q

Please I would be glad to be proved this is just an engine fault on the client side only. I've not ever experienced thrashing or other symptoms of memory leaks prior to this failure. It's golden until, click. Processor arch shouldn't matter in what causes a leak, whether it's 4 or 8 octet. It's how the program handles memory. In this case, closely tied to windoze and a client/server environment. So you can't rule out 3rd party or abuse on a client end.

Edited by EinDinHander, 23 July 2014 - 12:31 AM.