My Garry's Mod Server Crashed! Here's How to Fix It

Server crashes in Garry's Mod are fairly common due to the massive variety of community-created scripts and addons. The same flexibility that makes GMod fun to customize also makes it prone to conflicts and abuse-related crashes.

The good news? Most crashes are easy to identify and fix—especially when using tools like Physgun Utils, which are included in every Physgun GMod Server by default.

💡 Pro Tip: Hosting with Physgun gives you advanced crash diagnosis tools and real-time protections out of the box.

📁 How to Find Your Crash Logs

Physgun Utils automatically generates crash logs and attempts to diagnose the issue so you don’t have to dig through cryptic files manually.

Head to the Physgun Gamepanel
Navigate to Your Server → File Manager
Open the directory:
/home/container/physgun/crashes/

Inside, you’ll find log files for any crashes Physgun Utils has caught and analyzed.

🟡 If you're unsure what your crash log means, create a support ticket or ask for help in our Discord server.

🔁 Crash Type: Infinite Loop Detected

An "Infinite Loop Detected" error means a script is hanging the server in an endless loop. Physgun Utils monitors this and will auto-shutdown the server to prevent lockups. You can configure this behavior with the physgun.json file.



To adjust your Max Loop Time:

Go to Physgun Gamepanel
Navigate to Your Server → File Manager
Open /home/container/physgun.json
Locate MaxLoopTime and increase it to 60 or 90 if your server runs many intensive addons.



Infinite loops are typically caused by poorly optimized scripts or conflicting addons. Consider auditing recent changes before adjusting this setting.

🧱 Crash Type: Physics Crash (Props or Entity Collisions)

Physics crashes are often triggered by players abusing props that cause infinite collisions or heavy strain on the physics engine. Even with protections in place, some newer crash methods can slip through.

You’ll know it’s a physics crash if your crash log contains:

vphysics_srv.so

This means the crash originated in the physics engine:

/proc/1/fd/4(+0x2f4f9)[0xf79674f9]
...
/home/container/bin/vphysics_srv.so(+0x121857)[0xf2f19857]

🟠 Physics-based crashes are most commonly linked to malicious player behavior or poor prop cleanup. Always run a prop protection addon.

🔒 Recommended Fixes:

Use a Prop Protection addon from GModStore or the Steam Workshop.
Make sure to limit prop count, disable collisions on certain models, and prevent prop pushing.
Consider sandbox restrictions like anti-noclip abuse and collision group overrides.

Regularly auditing your server’s spawnlists, entity limits, and player permissions will go a long way in preventing future crashes.

✅ Additional Crash Prevention Tips

🌐 Use a Modern Game Panel

Running outdated game panels or hosting tools can limit crash visibility and recovery options. Hosting with Physgun gives you access to:
Realtime crash reporting in our Audit Logs
DDoS Protection
Performance analytics
Auto-backups

🔄 Revert Recent Changes

If your server started crashing after recent updates or script installations, try reverting those changes temporarily to isolate the issue.

📦 Keep Addons Up to Date

Outdated or poorly coded addons are a leading cause of server instability. Be sure to:
Remove legacy or deprecated addons
Watch for conflicts (e.g., multiple HUDs or admin systems)
Prioritize script quality over quantity

🛠 Still Need Help?

Don’t panic! Crash recovery is part of the game. You can:
Create a ticket
Ask in our Discord
Read more on Physgun Utilities

With the right tools and awareness, you'll be back online in no time.

Updated on: 19/05/2025