First thing to check is if the module is over on resources. When you break the magic 16k limit, crashes happen. The server has been over before, so it's worth checking. I don't know the exact tech behind it, but the DM Client is known to trigger it if you're right on the edge. Probably something along the lines of it waiting to lazy load some of the blueprints that couldn't be spawned without a DM around to do so.
Easy way to check if you're in the ballpark is to load the module in the toolset. Doing so creates a folder called "temp0" in your modules folder with all the mod's files unpacked. If Windows says that folder's file count is flirting with 16,000, you have a problem and are going to have to do some purging.
