[Divin12]

https://crash.limetech.org/jqpg5b6hdvmm
Any ideas?
and this: https://crash.limetech.org/6mtqweak3ymh

[DJPlaya]

https://crash.limetech.org/jqpg5b6hdvmm < This is propably related to the last CSGO Update which broke some very basic Stuff

https://crash.limetech.org/6mtqweak3ymh < Ime not sure but i think ive got something similar on WIN. For me it dosent happen that often, but ive got this on TF2/CSGO/Cure

[Divin12]

This: https://crash.limetech.org/6mtqweak3ymh solved, my metamod was old, too old, I just installed last metamod&sourcemod update.
First link is not from my server, maybe we can help my friend with his problems.
He use only basics plugins and extensions...

[DJPlaya]

Originally Posted by Divin12 This: https://crash.limetech.org/6mtqweak3ymh solved, my metamod was old, too old, I just installed last metamod&sourcemod update. First link is not from my server, maybe we can help my friend with his problems. He use only basics plugins and extensions...

Does this happens since the 29.11.17 ? That was the day of the horrible Update, you may need to use -nosse4 in your startup CMD or enable GOTV, depending on what he is running

[Divin12]

We use -nosse4 in statup, i tryed with gotv enabled too.. no succes.
I moved all precaches from configsexecuted to onmapstart...
New crash: https://crash.limetech.org/iyqf2kwrflng
Another one: https://crash.limetech.org/ywl5hkjd4rbj

[DJPlaya]

Originally Posted by Divin12 New crash: https://crash.limetech.org/iyqf2kwrflng Another one: https://crash.limetech.org/ywl5hkjd4rbj

Both Crashes include

>sdkhooks.ext.2.csgo.so!__SourceHook_MFHCls_Spawn::Func
>sourcemod.2.csgo.so!__SourceHook_FHCls_IServerGameDLLGameFramefalse::Func

So i guess something hooking "MFHCls_Spawn" is crashing the Server - IDK what this is, maybe its "Is_Spawn" but thats not a Hook. I would suggest removing parts of your Plugins, you may find the cause then. Or Plugins in general hooking the Player Spawn or Entity Spawn (i couldent think of something else)

[Divin12]

Problem solved, the problem was from wrong SDKHook call.