This is new

[Drayu]

This is new! I got this message in between maps and have not been able to get in yet!

http://img287.imageshack.us/img287/2329/new5un.th.jpg (http://img287.imageshack.us/my.php?image=new5un.jpg)

[Drayu]

and it only happens on our server :dunno:

[SLCoran]

You have to reboot the game usually, at least that has been my experience.

[Wraith]

That's happened to you too, SLCoran? ...... Any clue as to what brings it on? :dunno:

[GorroXXII]

Probably all those beta drivers you got Drayu... :hehehe:

[LeakyNavel]

this happened to me when I made Gun_Man1963. I think it happened because I copied LeakyNavels control files to Gun_man's Dir. once I opened the controls and saved the controls comfigeration it let me in.

[SLCoran]

I think it may have something to do with Punk Buster not reading the code right maybe a glitch in the program. I just restart the game and I'm good to go.

[Merlinex]

I had it happen in beta, but not in release yet.

I think it is caused by RAM corruption, then the verifing client bit fails a CRC check. In WoW Patching or BF2 beta demo I always had a bitch of time patching, did some really extensive (24 hour) ram testing to find a very small glitch. Replaced the RAM and this sceneraio went away.

Now several things can cause RAM corruption, its not always bad hardward, just was in my case. Possiblities:

Bad RAM
Overheated RAM interface
Electrical noise corruption from a loud bus
Software bugs / memory leaks / memory corruption

Rebooting the game will make the problem go away 99% of the time. Although without getting to the bottom, it will happen every once in a while.

EDIT: ... removed link i dont think this is the where i got it from, I'll have to look around again, its been a few months.

[Drayu]

you sure that is the website?

[Merlinex]

nah that was the wrong one thx for pointing it out.

http://www.memtest86.com/

that is the test I used, I made bootable - floppy, but you can do bootable - cdrom as well with it.

edit...
I should also note, make sure you read the 'Troubleshooting Memory Errors' if you detect an error. Detected error means that something went wrong when you wrote / read a pattern from memory, there was a mismatch between what was written and what was read.

However ... most the time it is bad RAM, but it can be caused by other things in certain cases too like noise corruption, insufficient power to the RAM, heat problems ... etc. So if you have errors, go threw some of running one stick at a time in different slots and what not to elimate. If it moves with a stick, then its most likely the stick itself.

[hostyle]

I use this to test my memory oc's. :thumbsup: