Posts: 586
Threads: 24
Joined: Jun 2010
Thanks: 2
Given 2 thank(s) in 1 post(s)
Hmm. The only thing I see here is that people are connecting with 1103 clients .. that's not right; possibly they're crashing the server. I wouldn't think it's RAM.
Posts: 586
Threads: 24
Joined: Jun 2010
Thanks: 2
Given 2 thank(s) in 1 post(s)
?? not your server - the clients - they're using 1103
You said "latest AC", so I'm assuming you're running 1104.
Posts: 2,136
Threads: 50
Joined: Jun 2010
Thanks: 0
Given 7 thank(s) in 2 post(s)
It's not the 1103 clients. Since December 1st my server has had about 60% 1104 and 40% 1103 clients.
Have you scanned for viruses/other malware? These can cause 0xc0000005 errors.
Posts: 76
Threads: 1
Joined: Jun 2010
Thanks: 0
Given 0 thank(s) in 0 post(s)
That's a generic access violation exception, ie attempted to read/write an invalid memory address - the number in [] - both of those are clearly not in process memory space (well, "clearly" to a Windows developer).
The error message itself is AC's own though, so the exception has been caught internally.
flowtron, consider extending fatal() function to have the caller info (eg __FILE__ and __LINE__) to help trace the source of these errors in general.
Posts: 586
Threads: 24
Joined: Jun 2010
Thanks: 2
Given 2 thank(s) in 1 post(s)
We used to have this - and I found it very helpful; this wonderful feature needed to be discontinued though, since the underlying information-files can be used by those "out there" that want to circumvent the anticheat-code. Not that this actually stops them - nothing really can - it just raises the bar a little more; which is all one can do against it.
Posts: 44
Threads: 6
Joined: Aug 2010
Thanks: 0
Given 0 thank(s) in 0 post(s)
15 Dec 10, 07:43PM
(This post was last modified: 15 Dec 10, 07:44PM by eynstyne.)
Guys the reason the server crashed is because server version is 1103 which had a "ban vote" flaw. Calling a ban vote with an invalid client number can potentially crash the server so it's best if you update to 1104.
As you can see from the previous attempts of trying to ban and being denied, the person may have accidentally put an invalid cn# and BOOM!
It took a while to figure it out, but it was annoying as fk to have your server go down ALL the time when some noob wanted someone out real bad.
Running 1104 and so far, no probs...
Posts: 3,780
Threads: 33
Joined: Jun 2010
Thanks: 0
Given 7 thank(s) in 6 post(s)
15 Dec 10, 07:54PM
(This post was last modified: 15 Dec 10, 07:56PM by V-Man.)
Wait... How can you tell he's running 1103 server?