Hi,

I just started a natural-selection server less than a week ago and it has worked fine so far with adminmod. but for some reason, recently, whenever people try to go into my server, the server crashes. Here is what happens when someone joins (a friend helped me reproduce this so I know its not just luck that it happened when someone joined)




this is the error that poped up

what should I do?

Have you tried updating metamod? There's a new project out there called AMXMod X which I think has a metamod compatible with NS 3 beta, try that. Have you tried re-extracting the NS binaries again and running it vanilla? If that runs then try adding adminmod back in. Other then that I'm really not sure how to help you.

Also don't forget to keep the motd.txt under 192 characters.

i just reinstalled my NS server fresh and that worked

also, im using the same MOTD from my other servers (which work) so that shouldn't be a problem

oh god... now i installed WhichBot (which includes the NS compatible metamod)

i started playing with it and it worked, other people joined, we had a good game.

then all of a sudden (the servers computer is next to me) i see the computer with the server pop up with an error thats similar to the first one... im not sure if its 100% the same but the same type of error message box

why is it doing this to me?

[edit] could it be firedaemon?

If it were me, I'd run a memory check, just to make sure it wasn't bad memory. I'd also make sure I had a stable vanilla install running, before modifying it.

ive made sure with the stable vanilla install

also, i put in MetamodX (from amxmodx.org) and it works with it... so far. Also, im running AdminMod and im thinking of putting in AmxModX in with it

how would i run a memory check?

Don't run AdminMod and AmxX at the same time, preformance will suffer.
Try getting rid of winbooster

Is that 2k? It looks like it.
What version? All windows updates? Start> Run> Winver

My server started doing this to me as well. Is the server Win2k Pro or Server 2000? If it is server, shut off active directory. When you enable active directory, the server will disable disk caching, which when shut off is a huge performance hit. I ran chkdsk and came up with quite a few bad sectors on the hard drive. I would recommend running chkdsk to make sure that your disk does not have any bad sectors as well. That would explain why you are getting that type of error above.

Its Windows 2000 Pro... I'll run chkdsk when I have a chance

Check out http://www.unknownworlds.com/forums/in...showtopic=70410 . It could be related