Official Soldat Forums
Soldat Talk => Need Help? Report Bugs! => Topic started by: Ray on April 21, 2008, 10:11:46 pm
-
Today I have been BattleEye banned on about 10 different servers.
Is there like.... a reason for this? I am not doing anything I shouldn't be.......
It is ALWAYS Battle Eye blah Corrupted memory #0-5........
I have re-installed about twice now.
Date Posted: April 21, 2008, 11:10:32 pm
Sorry, my connection is very slow atm. I didn't mean to post two threads.
-
This could be that your internet is extremely laggy which means your computer and the server's battleye are not communicating fully. You mentioned that your connection is very slow, that is probably why.
It could also be that your computer's ram is corrupt. This probably isn't the case since you'd be getting blue screen of deaths a lot. Are you?
-
I was playing fine all day yesterday with no problems, not one Battle Eye error.
I haven't had a BSoD on this computer once.
-
Date Posted: April 21, 2008, 11:10:32 pm
Sorry, my connection is very slow atm.
Was your connection "very slow" yesterday?
-
No, it was not. At the time I was posting the thread my connection was slow, its back to normal now.
-
Try playing Soldat now.
Does your connection frequently get slow? What kind of connection are you on? Cable, DSL, Dial-Up, wireless, etc.
-
Do a virus scan and check to see what programs are running at the same time as Soldat. Have you installed any programs in the past few days (besides Soldat)?
The only other explanation (I think the only one) is that a hack is loading.
-
Everyone's getting this, not just Ray...
-
Well, it could be something wrong with BattlEye, but I doubt Sable will ever admit it. Lol.
-
Aha. +1 ;D
Something is certainly awry though.
-
indeed, been getting this all day, also saw other people getting kicked in mass numbers =o
-
Battle eye got updated. Still works fine for me. Try closing other applications.
-
when I downloaded stuff I got battleeye bollocks.. but I closed the program, and now it works..
I don't think I have been kicked like that before,..
-
yeah, yesterday I saw like 5-6 BattlEye currupet memory #1 happen on the same server as my BattlEye was updated.
-
I am not accusing anyone, but if people didn't get this before the update and now they get it, then they are most likely hacking (except in case of mass kicks).
There is no known problem on BE's side atm (and it is not related to slow connections). I haven't seen mass kicks either.
-
mweh, while you're at it.. this happened in Snipe and Slice (u13.net:30004) yesterday..
(03:18:40) BattlEye Server: |FA| [@]c3 0f H34r7$ : Corrupted Memory #4
(03:18:40) |FA| [@]c3 0f H34r7$ has been kicked and banned for 5 minutes (BE - Corrupted Memory #4)
(03:18:40) BattlEye Server: Colin : Corrupted Memory #2
(03:18:40) Colin has been kicked and banned for 5 minutes (BE - Corrupted Memory #2)
(03:18:40) BattlEye Server: Burp : Corrupted Memory #0
(03:18:40) Burp has been kicked and banned for 5 minutes (BE - Corrupted Memory #0)
(03:18:41) BattlEye Server: ^^Vengence^^ : Corrupted Memory #3
(03:18:41) ^^Vengence^^ has been kicked and banned for 5 minutes (BE - Corrupted Memory #3)
(03:18:41) BattlEye Server: Black_Knight : Corrupted Memory #3
(03:18:41) Black_Knight has been kicked and banned for 5 minutes (BE - Corrupted Memory #3)
(03:18:41) BattlEye Server: Best Shooter In Town : Corrupted Memory #4
(03:18:41) Best Shooter In Town has been kicked and banned for 5 minutes (BE - Corrupted Memory #4)
(03:18:41) BattlEye Server: {[ZX]} -[+]- : Corrupted Memory #2
(03:18:41) {[ZX]} -[+]- has been kicked and banned for 5 minutes (BE - Corrupted Memory #2)
(03:18:41) BattlEye Server: leftupdown : Corrupted Memory #1
(03:18:41) leftupdown has been kicked and banned for 5 minutes (BE - Corrupted Memory #1)
(03:18:42) BattlEye Server: Lysergic Tripper : Corrupted Memory #1
(03:18:42) Lysergic Tripper has been kicked and banned for 5 minutes (BE - Corrupted Memory #1)
(03:18:42) BattlEye Server: =ProM= Vile Maverick : Corrupted Memory #2
(03:18:42) =ProM= Vile Maverick has been kicked and banned for 5 minutes (BE - Corrupted Memory #2)
(03:18:42) BattlEye Server: Slivnot : Corrupted Memory #4
(03:18:42) Slivnot has been kicked and banned for 5 minutes (BE - Corrupted Memory #4)
(03:18:42) BattlEye Server: ROFL : Corrupted Memory #3
(03:18:42) ROFL has been kicked and banned for 5 minutes (BE - Corrupted Memory #3)
(03:18:42) BattlEye Server: BOX : Corrupted Memory #1
(03:18:42) BOX has been kicked and banned for 5 minutes (BE - Corrupted Memory #1)
(03:18:43) BattlEye Server: "Who Dares Wins" : Corrupted Memory #4
(03:18:43) "Who Dares Wins" has been kicked and banned for 5 minutes (BE - Corrupted Memory #4)
-
JFK, did that only happen at the time you posted?
-
Yep, never encountered before, time is in GMT +1:00
-
I meant, after that?
Date Posted: 22-04-2008, 15:37:48
mweh, while you're at it.. this happened in Snipe and Slice (u13.net:30004) yesterday..
Hm, yesterday, on 21/04/2008, or this morning/night?
-
it has happened on my server too, about 3 hours ago. everyone got kicked for corrupted memory as reported by a user
i dont have a log of it..
-
Happend THIS morning (22/04).. i re-checked my logs and also found this (also this morning):
(06:35:00) BattlEye Server: {CB}Kraus : Client not responding
(06:35:00) {CB}Kraus has been kicked and banned for 5 minutes (BE - Client not responding)
(06:35:00) BattlEye Server: TeH_OwnZage : Client not responding
(06:35:00) TeH_OwnZage has been kicked and banned for 5 minutes (BE - Client not responding)
(06:35:01) BattlEye Server: |Cats_Fart |Kuhmo| : Client not responding
(06:35:01) |Cats_Fart |Kuhmo| has been kicked and banned for 5 minutes (BE - Client not responding)
(06:35:01) BattlEye Server: Brawn : Client not responding
(06:35:01) Brawn has been kicked and banned for 5 minutes (BE - Client not responding)
(06:35:01) BattlEye Server: Sharp Point : Client not responding
(06:35:01) Sharp Point has been kicked and banned for 5 minutes (BE - Client not responding)
(06:35:01) SkyMan's Brazil captured the Red Flag
(06:35:01) REx Banner returned the Blue Flag
(06:35:02) Dabuh^^Mato styl... could not respond
(06:35:02) Toyman could not respond
(06:35:02) SkyMan's Brazil could not respond
(06:35:04) BattlEye Server: Fate|WM|Wolfman14=ProM= : Client not responding
(06:35:04) Fate|WM|Wolfman14=ProM= has been kicked and banned for 5 minutes (BE - Client not responding)
(06:35:06) BattlEye Server: REx Banner : Client not responding
(06:35:06) REx Banner has been kicked and banned for 5 minutes (BE - Client not responding)
(06:35:06) BattlEye Server: Clayman.aK : Client not responding
(06:35:06) Clayman.aK has been kicked and banned for 5 minutes (BE - Client not responding)
It is however because of client not responding and only 8 ppl. Im not sure if this means if was the whole server. It's pretty hard to find out how many ppl have been online at a certain moment. The server carries 14 slots.
-
Check the "could not respond" non-BE messages. The server probably timed out / was unreachable.
-
Probably.. actually i don't really mind if this happens once i a while.. ppl only get banned for 5 mins and they should be able to live with that. I just post this hoping that I could help you with something.
Is it possible that the corrupted memory error also was generated by time-out's? Or do you think i'ts a BE-problem?
-
No, it cannot be caused by this.
Actually I don't trust the Soldat netcode.
-
it happens in every server (i've been in 3 various already)
-
it has happened on my server too, about 3 hours ago. everyone got kicked for corrupted memory as reported by a user
i dont have a log of it..
Same here.
Everyone still getting kick on my servers.
I'm going to disable BattlEye until the problem is solved.
-
Actually I don't trust the Soldat netcode.
hehe, then force enesce to fix it ^^.
-
i have the same problem....
-
From what I've noted, if people have a lag-spike or their connection siezes during a mapchange, which happens all the time, they get kicked.
Which means it's Battleye.
Don't trust the Soldat netcode all you like, but a Battleye update that causes mass problems over every server = a problem.
Did I really just say that? *cough*
-
Believe it or not, but it seems to be the Soldat netcode causing this.
The BattlEye update changed things which seem to reveal the problems in the Soldat netcode - I won't go into details here for obvious reasons.
Anyway, there is a new BE update that should fix the problem. Please report back if there are still problems.
-
No matter how you look at it, the updates before that one were fine and the one after was fine, so no matter how bad the SNC is... Oh, it's futile. [retard]
Here's hoping the new one works. ^_^
-
Been banned for corrupted memory #0 from three servers in the past 20 minutes.
-
Now its Battle eye not responding or something.....
-
Yep, with Ray.
-
Hmm...BE update probably causing this or the netcode ??? been having all these frequantly.. :'(
-
Randomly got kicked for a Corrupted Memory #4. I noticed that just before it happened, my game froze for about a second for some reason.
-
I really enjoy being kicked out of every server I enter, yessir.
-
when will this get fixed? not to nag, just wondering, Im also beeng kicked for no reason, and I have never been close to hax or anything. :-* only thing is that my favorites in mozilla is suddainly gone .. but that might have been something else.. ::) :'(
-
What is your exact violation?
-
Usually
BattleEye Server: TC ~ Chariot ~ : Corrupted Memory #0
Sometimes #3
-
At graveyard inf about every game someone gets kicked usually for #1 or #4. Also the logs show that the connection to the BE master server gets dropped not quite sure what that is about but it is a u13 rented server.
-
When is this going to be fixed? I'd like to be able to play a game for longer than 5 minutes for a change.
-
Chariot, it should be fixed already.
Did you try to reinstall Soldat? Also scan for virus/spyware and check your RAM for errors (e.g. using Memtest86).
To those that get kicked for "Client not responding" while playing now: Unfortunately, there is nothing I can do about this at the moment. Either the Soldat client or server seems to corrupt the BE packets sometimes. Now, corrupted packets are ignored by the BE Client/Server and in bad cases, if it doesn't recover, you will be kicked for not responding after a while.
It's definitely not BE causing this, it seems that the Soldat netcode can't handle the increased number of BE packets being sent now.
-
Reinstalled, still happening. No viruses.
-
It looks like this when someone gets kicked
(http://i28.tinypic.com/29ljz1f.jpg)
-
Thanks for not taking any responisbility for it as usual, but it's not just 'not responding after a while'. The slightest lag-spike (or map change), wireless or wired, will give anyone an instant 'Client not responding' 5 minute ban.
Seriously, stop blaming it on Soldat, RAM, viruses - Anything other than your programme. It was fine up until two releases ago, then you fixed one problem and created another. I'm bored of your excuses and I'm bored of being booted from servers
-
Yes, I never take any responsibility, I am ignorant and I don't give a shit about the community.
Seriously, normally this is not my tone, but people like you should really shut up if they don't know what they are talking about.
I have verified with multiple server admins (Leo and Toumaz) using a special BE version that it IS Soldat corrupting BE packets. Now, why didn't it happen before? I think that it also happened before (players post here from time to time), but not that often due to the significantly lower amount of BE packets being sent. You might also find it interesting that there is an exploit in the current server version where a hacker can cause all players to be kicked by BE for "Bad Packet" by sending a special (non-BE) packet to the server. So there ARE indeed problems with the current Soldat netcode.
I created a workaround fix so that a corrupted packet won't lead to a "Corrupted Memory" kick anymore but is instead ignored. Now, as I said, if the netcode doesn't recover, you will logically be kicked for "Client not responding" after a while.
So I neither actually fixed the problem nor did I create another.
Also, what you say about lag-spikes and map changes is just not true. BE always ensures that packets actually arrive, so unless you really time out for quite a while, you won't be kicked.
-
Rubbish. I know for a fact and have seen it happen to others, that it kicks for not responding whenever it damn well feels like it. There doesn't need to be a non-responsive period for it to kick. It happens in every server I've been in and not just to me and only since things started going wrong with the corrupt code.
You did create another problem, because it wasn't there a week ago. End of. If you want to blame it on everything under the sun that's your problem. Just don't expect people to be kind to you when they can't play for more than 5 minutes. Also, I never said there weren't problems with the Soldat netcode.
Stop deviating from the subject, fix whatever you did that screwed it up and let us play Soldat.
-
Did you even read my post?
You obviously didn't, otherwise you would know why "it kicks for not responding whenever it damn well feels like it".
-
Rubbish. I know for a fact and have seen it happen to others, that it kicks for not responding whenever it damn well feels like it. There doesn't need to be a non-responsive period for it to kick. It happens in every server I've been in and not just to me and only since things started going wrong with the corrupt code.
You did create another problem, because it wasn't there a week ago. End of. If you want to blame it on everything under the sun that's your problem. Just don't expect people to be kind to you when they can't play for more than 5 minutes. Also, I never said there weren't problems with the Soldat netcode.
Stop deviating from the subject, fix whatever you did that screwed it up and let us play Soldat.
$able's done his job, so now it's up to EnEsCe to do his, so go annoy him instead.
-
well no matter whos fault it is, BE kicks seems to happen more often and also without reason
today i got BE kicked from my own server for corrupted memory, never had that before.
-
Just fyi, I am already talking to EnEsCe and MM about this.
-
$able... Did you release a battle-eye update in the last few days? Ever since that update (my Soldat auto-updated) I've been kicked from every server I join, and I can't spectate any servers (I get told the server is full when theres 5 people/30 slot server).
-
$able... Did you release a battle-eye update in the last few days? Ever since that update (my Soldat auto-updated) I've been kicked from every server I join, and I can't spectate any servers (I get told the server is full when theres 5 people/30 slot server).
Servers limit the max number of spectators; you'll be told the server is full if this is the case.
-
Rubbish. I know for a fact and have seen it happen to others, that it kicks for not responding whenever it damn well feels like it. There doesn't need to be a non-responsive period for it to kick. It happens in every server I've been in and not just to me and only since things started going wrong with the corrupt code.
You did create another problem, because it wasn't there a week ago. End of. If you want to blame it on everything under the sun that's your problem. Just don't expect people to be kind to you when they can't play for more than 5 minutes. Also, I never said there weren't problems with the Soldat netcode.
Stop deviating from the subject, fix whatever you did that screwed it up and let us play Soldat.
$able's done his job, so now it's up to EnEsCe to do his, so go annoy him instead.
Try reading what I said. Battleye could deal with it before onesingleupdate and then suddenly all hell broke loose. + what BombSki said.
-
Try reading what I said. Battleye could deal with it before onesingleupdate and then suddenly all hell broke loose. + what BombSki said.
I think that there is something that you should realize, bloo. Battle-eye is a constantly changing piece of software, which has to be patched and maybe even redesigned whenever a bunch of geeky 'hackers' find another exploit in it. If you read sable's post you must have seen that one of those exploits was that a hacker could use BE to kick you!
This means two things: BattleEye was, is and will be updated CONSTANTLY. If it stands still, the exploiters win. Another thing is that maintaining such a piece of software is everything accept easy. Creating some software is one thing, but making sure it will be adaptable for the future and on top of that keeping it compatible with third party software (like the soldat netcode) looks like a hell of a job to me.
Therefor I think sable deserves a little more respect than you give him.
-
@The Bone Collector: You are kicked for "Client not responding"?
I have now released another workaround fix that reduces the amount of BE packets being sent. Could everyone who had problems before please post if that fixes it for him/her?
-
The problems seem to have stopped for me.
-
You were kicked for "Client not responding" before (the last days)?
-
No, I was kicked for the same thing that the title of the topic says...
Although it just happened again less than 30 seconds ago.
-
Good news! I no longer get Corrupted Memory #x!
Now the client's not responding. =D
-
Rubbish. I know for a fact and have seen it happen to others, that it kicks for not responding whenever it damn well feels like it. There doesn't need to be a non-responsive period for it to kick. It happens in every server I've been in and not just to me and only since things started going wrong with the corrupt code.
You did create another problem, because it wasn't there a week ago. End of. If you want to blame it on everything under the sun that's your problem. Just don't expect people to be kind to you when they can't play for more than 5 minutes. Also, I never said there weren't problems with the Soldat netcode.
Stop deviating from the subject, fix whatever you did that screwed it up and let us play Soldat.
$able's done his job, so now it's up to EnEsCe to do his, so go annoy him instead.
Try reading what I said. Battleye could deal with it before onesingleupdate and then suddenly all hell broke loose. + what BombSki said.
Oh, you should have seen the servers before this. At least every server in Australia had a hacker in it making everyone get kicked for bad packets. At the moment, the kicks that are occuring are extremely mild in comparison.
-
I think that there is something that you should realize, bloo. Battle-eye is a constantly changing piece of software, which has to be patched and maybe even redesigned whenever a bunch of geeky 'hackers' find another exploit in it. If you read sable's post you must have seen that one of those exploits was that a hacker could use BE to kick you!
This means two things: BattleEye was, is and will be updated CONSTANTLY. If it stands still, the exploiters win. Another thing is that maintaining such a piece of software is everything accept easy. Creating some software is one thing, but making sure it will be adaptable for the future and on top of that keeping it compatible with third party software (like the soldat netcode) looks like a hell of a job to me.
Therefor I think sable deserves a little more respect than you give him.
I have now released another workaround fix that reduces the amount of BE packets being sent. Could everyone who had problems before please post if that fixes it for him/her?
All he had to do was release the fix days ago or tell us he was going to do it and there would have been no problem. I'm not entirely stupid and I have a pretty fair idea of how this stuff works, so thank you for your pointless rant, but I do understand.
Also, thank you $able for releasing a fix - It seems to have worked. :)
-
Omg ray, your sig is huge!!!
-
I vote that enesce shall fix the netcode instead of having sable work his ass off.
-
I vote that enesce shall fix the netcode instead of having sable work his ass off.
It's probably easier for $able to work his arse off for a year than for Enesce to 'fix' the netcode.
-
All he had to do was release the fix days ago or tell us he was going to do it and there would have been no problem. I'm not entirely stupid and I have a pretty fair idea of how this stuff works, so thank you for your pointless rant, but I do understand.
Also, thank you $able for releasing a fix - It seems to have worked. :)
See, you still don't get it.
I have not really fixed anything, I have only worked around it to cope with the problems in the Soldat netcode. The reason I didn't do this immediately was that I first wanted to find out what the actual problem is and look into a possible real solution.
-
See, you still don't get it.
I have not really fixed anything, I have only worked around it to cope with the problems in the Soldat netcode. The reason I didn't do this immediately was that I first wanted to find out what the actual problem is and look into a possible real solution.
Yeah, bored hearing about the Soldat netcode now. There are several other ways to look into a 'possible real solution' - Most of which don't involve banning the general public from Soldat for a week.
It's not like this hasn't happened in the past.
-
No, something like that never happened in the past.
What I'm trying to make clear is that it's not BE's fault. But, oh well, you will still think it is, so I give up trying to convince you now.
-
No, something like that never happened in the past.
What I'm trying to make clear is that it's not BE's fault. But, oh well, you will still think it is, so I give up trying to convince you now.
Er, yeah it has. And I never said it was BE's fault, I said it was yours.
Thanks, though. ^_^
-
There was never a bug like this in the past.
And come on, that bug isn't my fault, blame MM or EnEsCe for it.
Fyi, it's still there, but much less likely to happen now (no real fix).
-
Do i have to update the client/Server manually? i still get corrupted #1, and not only me.
-
I feel so sad for Sabel right now :P. how come this only happens for some people? are you sure it isn't something with their ISP? or some sort of port-forwarding?
-
I'm not blaming anyone, but obviously somewhere is a problem, so i'm just asking if there will be a solution in the next days.
-
Woot! I only got kicked for Client not responding once today! I can finally play on BE servers now >_>
For those of you that are still getting it, I guess you guys just gotta be patient and wait.
-
If anyone is still experiencing corrupted memory kicks, have a look and see if you have Punkbuster's process resident. Should be called "PnkBstrA.exe".
Before turning it off I was getting kick banned every couple of minutes. Hasn't happened once since I got rid of PB's process.
-
or it could be that your hacking or tried to hack?
-
I feel so sad for Sabel right now :P. how come this only happens for some people? are you sure it isn't something with their ISP? or some sort of port-forwarding?
I think it has something to do with people playing on bad servers and because Soldat's netcode is bad according to $able then maybe the worse the connection to the server the most likely it'll happen(i guess).
Bloo you're an idiot.
-
If anyone is still experiencing corrupted memory kicks, have a look and see if you have Punkbuster's process resident. Should be called "PnkBstrA.exe".
Before turning it off I was getting kick banned every couple of minutes. Hasn't happened once since I got rid of PB's process.
Battlefield? I think I remember my friend telling me about PunkBuster running OUTSIDE of the game...
-
Yes, but PunkBuster shouldn't be active while you are not playing the PB game.
-
I still get Problems Corrupted Memory #1, it's just not like before this update three or four days ago.
cat ConsoleLog-*|grep BattlEye|tail -n 30
08-04-28 17:31:19 BattlEye Server: NozowniK : Corrupted Memory #1
08-04-28 17:32:44 BattlEye Server: twardy skurwiel : Corrupted Memory #1
08-04-28 18:18:19 BattlEye Server: abzikro : Direct3D Hook #1
08-04-28 18:44:39 BattlEye Server: Nyuo : Corrupted Memory #1
08-04-28 18:51:18 BattlEye Server: Nationalist : Corrupted Memory #1
08-04-28 19:11:45 BattlEye Server: Credo : Corrupted Memory #1
08-04-28 19:13:38 BattlEye Server: mgterrorist : Corrupted Memory #1
08-04-28 19:14:08 BattlEye Server: twardy skurwiel : Corrupted Memory #1
08-04-28 19:14:11 BattlEye Server: King Kongg : Corrupted Memory #1
08-04-28 19:17:08 BattlEye Server: Credo : Corrupted Memory #1
08-04-28 19:17:27 BattlEye Server: Uzdrowiciel z filipin x : Corrupted Memory #1
08-04-28 19:27:34 BattlEye Server: Rokato : Direct3D Hook #1
08-04-28 19:57:11 BattlEye Server: Update successfully completed. Restarting...
08-04-28 19:57:11 BattlEye Server: Initialized
08-04-28 20:15:30 BattlEye Server: matan awat : Client not responding
08-04-28 20:31:52 BattlEye Server: WestCat : Direct3D Hook #1
08-04-28 20:54:14 BattlEye Server: Definitive (a) Solegro : Corrupted Memory #2
08-04-28 22:00:34 BattlEye Server: (.)(.) : Client not responding
08-04-28 22:26:07 BattlEye Server: [82nd]EastFrisian : Corrupted Memory #1
08-04-28 22:27:17 BattlEye Server: Double Decker : Direct3D Hook #1
08-04-28 22:27:47 BattlEye Server: MaRCiN eM : Corrupted Memory #1
08-04-28 22:30:45 BattlEye Server: Nightmare : Corrupted Memory #1
08-04-28 23:11:15 BattlEye Server: October : Client not responding
08-04-28 23:12:41 BattlEye Server: SchinkenBrot : Corrupted Memory #1
08-04-28 23:38:05 BattlEye Server: Source : Corrupted Memory #1
08-04-28 23:51:32 BattlEye Server: garyel : Corrupted Memory #1
08-04-28 23:54:21 BattlEye Server: Major : Corrupted Memory #1
08-04-28 23:57:13 BattlEye Server: Stop! Hammertime : Corrupted Memory #1
08-04-29 10:36:33 BattlEye Server: Earthworm Jim : Corrupted Memory #1
08-04-29 10:42:30 BattlEye Server: Dante : Corrupted Memory #1
Will there be a solution?
-
No.
Maybe they are just trying to cheat (seeing that it is mainly CM #1)?
-
I hope, i m not bumping an old topic but since in this one was such an active discussion~~ ;)
i m running my own server (again ^^) on dedicated debian machine~
As i can remember, about 1 year ago i neved had BE kicks from the server..
After a while the server froze (and blocked whole system by using 100% of cpu ..) and since then i didnt use soldat anymore in fear to have such an freeze again. Now i reinstalled everything again, new server, new client.
I'm getting a lot of "corrupted memory" kicks from my own server, i dont have anything "illegal" running, same with players on my serv.
example:
08-05-01 22:52:02 BattlEye Server: [euRO]crckdns : Corrupted Memory #1
08-05-01 22:53:57 BattlEye Server: [euRO]crckdns : Corrupted Memory #1
08-05-02 19:37:08 BattlEye Server: [euRO]crckdns : Corrupted Memory #1
08-05-02 20:39:49 BattlEye Server: [euRO]crckdns : Corrupted Memory #1
08-05-02 20:53:57 BattlEye Server: [euRO]crckdns : Corrupted Memory #1
08-05-02 21:46:27 BattlEye Server: [euRO]crckdns : Corrupted Memory #1
Here a tail of the log from other players..
08-05-03 22:51:15 BattlEye Server: DeadWalker1990 [GER] : Corrupted Memory #1
08-05-03 22:57:56 BattlEye Server: wojak[elo] : Corrupted Memory #1
08-05-03 22:58:01 BattlEye Server: Adamo$$$ T*T : Corrupted Memory #1
08-05-03 23:21:55 BattlEye Server: Hunt3r : Corrupted Memory #1
08-05-04 13:07:16 BattlEye Server: Major : Failed to update
08-05-04 13:54:04 BattlEye Server: Aquil : Corrupted Memory #1
08-05-04 15:01:11 BattlEye Server: Mirek Pieron : Corrupted Memory #1
08-05-04 15:06:33 BattlEye Server: D|eSaStE|r_UcHiHa_ClAn : Corrupted Memory #1
08-05-04 15:47:45 BattlEye Server: Rocksoad : Corrupted Memory #1
08-05-04 16:57:37 BattlEye Server: [T*T]Magik : Corrupted Memory #1
08-05-04 17:07:45 BattlEye Server: Ded_mazdai : Client not responding
08-05-04 18:15:08 BattlEye Server: Nationalist : Corrupted Memory #1
08-05-04 18:20:24 BattlEye Server: -=PAINKILLER=-RUSSIA : Corrupted Memory #1
08-05-04 20:17:01 BattlEye Server: Mr. |und [selss] : Corrupted Memory #1
08-05-04 20:32:21 BattlEye Server: feck : Corrupted Memory #1
08-05-04 21:33:33 BattlEye Server: [euRO]Dirk Diggler : Corrupted Memory #1
08-05-04 21:40:30 BattlEye Server: Ashanti : Corrupted Memory #1
08-05-04 21:40:38 BattlEye Server: Kazzor : Corrupted Memory #1
08-05-04 21:49:09 BattlEye Server: [DT|VoIodia] : Corrupted Memory #1
08-05-04 21:51:02 BattlEye Server: Ashanti : Corrupted Memory #1
08-05-04 21:58:39 BattlEye Server: -==cinek==- : Client not responding
08-05-04 22:05:42 BattlEye Server: SkRzYdLiK : Client not responding
08-05-04 22:05:55 BattlEye Server: [euRO]Dirk Diggler : Corrupted Memory #1
08-05-04 22:10:00 BattlEye Server: :D! : Corrupted Memory #1
08-05-04 22:19:25 BattlEye Server: :D! : Corrupted Memory #1
08-05-04 22:29:48 BattlEye Server: Toto007 : Corrupted Memory #1
08-05-05 08:10:51 BattlEye Server: <PrKl> Kaaos : Corrupted Memory #1
08-05-05 12:08:30 BattlEye Server: Noobzhader : Corrupted Memory #1
08-05-05 12:28:36 BattlEye Server: Major : Corrupted Memory #1
08-05-05 12:33:06 BattlEye Server: Cineck : Corrupted Memory #1Most of it is corrupted memory, same goes to some friends and/or default users who are everytime there, who arent using for sure anything.
Still no idea what it could be or solution? ^^
regards
cracky
-
Do you have a decent internet connection to the server?
-
16-33ms ping~ never goes over 50ms ..i would assume its "decent" ^^
its an 16k DSL from telecom (germany)
only thing is left to try is really to turn almost everything off and play then~~but...i m not feeling comfortable to turn kaspersky off ;)
-
16k? are you sure it's 16k? that's the worst connection I've ever heard of.
-
crckdns, when are you kicked (time after joining)?
Also, do you use any Soldat mods?
-
@ $able most of the time after a kill.
That means, most of users are getting this #1 kick after they get killed.
And nope, no mod at all, its a fresh install.
about 16k .. its 16.000 kbit ^^; so.. 16mbit sry
-
Could you please post the server IP, so I could check this myself?
CM #1 is related to memory that should always be constant (obviously), I am checking with MM now though.
Date Posted: 05-05-2008, 22:25:35
Alright, I just verified myself, this memory is not always constant (as I was told).
The problem has been fixed now. I am really sorry for the inconveniences caused by this.
-
So you dont need the ip anymore? ^^
Will the BE update itself automaticaly? Sry, i m noobish about BE <_<
regards
cracky
-
Yes, the BE Server was updated.
-
Yep, CM#1 Problems with my server disappeared, too. thx for fix