[EvilPriest]

function: CBaseEntity::SUB_CallUseToggle
049a9a2e 03c1 add eax,ecx
049a9a30 8b0d9c74a004 mov ecx,[04a0749c] ds:04a0749c=061a0020
049a9a36 8d0440 lea eax,[eax+eax*2] ds:00000000=????????
049a9a39 8d4c8108 lea ecx,[ecx+eax*4+0x8] ds:00a7d5d3=00000000
049a9a3d b867666666 mov eax,0x66666667
049a9a42 f7ea imul edx
049a9a44 c1fa03 sar edx,0x3
049a9a47 8bc2 mov eax,edx
049a9a49 c1e81f shr eax,0x1f
049a9a4c 03d0 add edx,eax
FAULT ->049a9a4e 0fbf01 movsx eax,word ptr [ecx] ds:065ee72c=????
049a9a51 2bc2 sub eax,edx
049a9a53 3d08f8ffff cmp eax,0xfffff808
049a9a58 7d0b jge CBaseEntity::SUB_CallUseToggle+0x12e05 (049b5265)
049a9a5a b808f8ffff mov eax,0xfffff808
049a9a5f 5f pop edi
049a9a60 668901 mov [ecx],ax ds:065ee72c=????
049a9a63 5e pop esi
049a9a64 c3 ret
049a9a65 3df8070000 cmp eax,0x7f8
049a9a6a 7e50 jle CBaseEntity::SUB_CallUseToggle+0x12e5c (049b52bc)
049a9a6c b8f8070000 mov eax,0x7f8

This is the error I get when my CS server crashes.

Does anyone know what it is or how to fix it? I would like to know what exactly this is and why it happens.

Thanks

EP

[yakkob]

Do you have EAX enabled?

If so, disable it.

It just seems as though there are a lot of eax entries in there my friend.
Let me know how you go on.

[EvilPriest]

that is kinda what i fugiured, buuuuut. The other entries what are they?

I will look to see it it is enabled. It is a dedicated server, so the sound isnt used.

Thanks.

[ThC 129]

the other entries are procedure calls pointing to memory locations or something of that sort. The numbers are in hexadecimal that is why they have letters and numbers. Judging by the dump your getting it is due to the soundcard trying to write to a memory location that is already in use, or trying to use EAX when its not able to thus crashing.

[CUViper]

This doesn't necessarily have anything to do with sound guys - what you are looking at is a bit of x86 machine code (assembly). "eax" is a 32-bit register on the processor, and has NOTHING to do with the sound card. Registers are where the processor stores bits of data right before performing an operation on them.

There's really not a whole lot you can do to troubleshoot this, without having access to the source, and even then it would be hard since I'm pretty sure CS wasn't written in assembly. But your best bet for resolving this would be to send it along to the developers...

[EvilPriest]

An answer that makes sense. Thanks bro.

EP

[Brian Frank]

And even if it was done during assembly, are you l33t enough to change the code yerself? Probably not...I know I'll never be l33t on the software side.