Dedicated Server crashing randomy?? - Help

So, Recently my server has been getting this weird error which is preventing the server from auto-rebooting (because the server doesnt crash, but rather halts). Leading up to the crash, there is literally NO Errors in console. No Lua errors, Nothing. Someone could be killing players, someone could be spawning a prop, its so random! Here is the error: [url]https://gyazo.com/3115509b31af328d601715fe4d1d34d2[/url] The server is on Windows server 2012 R2, with 32 GB ram. It is running on Core 2. Addons: [url]https://gyazo.com/c1e8a1290741eb26b4d5fce0c243a21c[/url] Gamemode: DarkRP 2.7.0 Server CFG: [url]http://pastebin.com/9nuQsJbG[/url] UPDATED INFORMATION: Okay I will try to investigate the models... However i have come across something interesting. I opened my ulx logs to find: [CODE] L 06/11/2016 - 18:08:56: "Ultimate Assassin<342><STEAM_0:1:70644957><>" STEAM USERID validated L 06/11/2016 - 18:08:56: Engine error: Host_Error: Failed to allocate 524288 bytes of memory in CNetworkStringTableContainer::WriteBaselines[/CODE] Another Log: [CODE] L 06/10/2016 - 23:12:27: "CaptainChickenQC<165><STEAM_0:0:77860234><>" STEAM USERID validated L 06/10/2016 - 23:12:27: Engine error: Host_Error: Failed to allocate 524288 bytes of memory in CNetworkStringTableContainer::WriteBaselines[/CODE] And yet another log leading to a crash: [CODE] L 06/09/2016 - 16:19:16: "SaveFerris_<286><STEAM_0:1:32947819><>" STEAM USERID validated L 06/09/2016 - 16:19:16: Engine error: Host_Error: Failed to allocate 524288 bytes of memory in CNetworkStringTableContainer::WriteBaselines[/CODE] If you notice, it happens once a user is validated. Not sure if this helps at all. After this error occurs the server creates a popup with the same error message, and simply haults.

Hi, Windows is instable for servers. What is the processor you have?

Intel Xeon E3 1270v3

Try to modify this in your server.cfg: net_maxfilesize 128 sv_minrate 1000 sv_maxrate 30000 decalfrequency 10 sv_maxupdaterate 66 sv_minupdaterate 33 PS: Memory error, how many GB of RAM do you have? What is your start script ?

[QUOTE=lucas2107;50424998]Try to modify this in your server.cfg: net_maxfilesize 128 sv_minrate 1000 sv_maxrate 30000 decalfrequency 10 sv_maxupdaterate 66 sv_minupdaterate 33 PS: Memory error, how many GB of RAM do you have? What is your start script ?[/QUOTE] 32 GB ram Startup: -game garrysmod -console -tickrate 33 +host_workshop_collection XXXXXXXX -authkey XXXXXXXXXXXXXXXXX +rcon_password "blah" +maxplayers 75

I cry for help people :c

If you're running a lot of playermodels off the workshop, try removing all of them for a reset and using only default models and see if it crashes. If that doesn't work, you can remove addons one by one. I had this issue way back then it turned out to be several playermodels that were rigged very strangely or poorly. Removing them fixed the issue!

I believe I have seen this through some searching a while back having a error simpler to that. Just use [URL="https://www.google.com/"]google[/URL]. Have you mounted anything lately?

Okay I will try to investigate the models... However i have come across something interesting. I opened my ulx logs to find: [CODE] L 06/11/2016 - 18:08:56: "Ultimate Assassin<342><STEAM_0:1:70644957><>" STEAM USERID validated L 06/11/2016 - 18:08:56: Engine error: Host_Error: Failed to allocate 524288 bytes of memory in CNetworkStringTableContainer::WriteBaselines[/CODE] Another Log: [CODE] L 06/10/2016 - 23:12:27: "CaptainChickenQC<165><STEAM_0:0:77860234><>" STEAM USERID validated L 06/10/2016 - 23:12:27: Engine error: Host_Error: Failed to allocate 524288 bytes of memory in CNetworkStringTableContainer::WriteBaselines[/CODE] And yet another log leading to a crash: [CODE] L 06/09/2016 - 16:19:16: "SaveFerris_<286><STEAM_0:1:32947819><>" STEAM USERID validated L 06/09/2016 - 16:19:16: Engine error: Host_Error: Failed to allocate 524288 bytes of memory in CNetworkStringTableContainer::WriteBaselines[/CODE] If you notice, it happens once a user is validated. Not sure if this helps at all. After this error occurs the server creates a popup with the same error message, and simply haults.