It's almost never bad memory. It's Winbloze way of saying "I'm confused and don't know how to properly report the error". It's frequently caused by a buffer overflow, and maybe a corrupted pointer or a pointer that you left pointing to the wrong place. It's usually programming errors of some sort cause this, like I overwrote my pointer or forgot to initialize it and the compiler just leaves random garbage in it instead of initializing it to zero (are there any compilers that still do this?). Can rarely be caused by cosmic rays toggling bits in ram - I've actually seen this occur in files copied across the network - you could see the pattern of the stuck bit in a binary dump of the file, but it's very very rare - arc welders next door, you name it.
However, the OP said it happens all the time. I would bet there is a mod/module running that is buggy, or there is a mod install issue, as others have suggested. Just don't go out and replace your memory, that rarely if ever fixes this problem.
Never seen that one but I also would have figured it was a bad stick of ram:-( Jason
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
