Hi @MaSch
An OpenComputers program should never be able to crash your server.
Lets do a quick breakdown.
Here's your stacktrace:
Description: Exception in server tick loop
java.util.ConcurrentModificationException
at java.util.HashMap$HashIterator.nextNode(Unknown Source)
at java.util.HashMap$KeyIterator.next(Unknown Source)
at java.util.AbstractCollection.toArray(Unknown Source)
at com.google.common.collect.ImmutableSet.copyOf(ImmutableSet.java:374)
at elec332.core.grid.internal.GridEventInputHandler.tickEnd(GridEventInputHandler.java:91)
at elec332.core.grid.internal.GridEventHandler.serverTick(GridEventHandler.java:49)
at net.minecraftforge.fml.common.eventhandler.ASMEventHandler_304_GridEventHandler_serverTick_ServerTickEvent.invoke(.dynamic)
at net.minecraftforge.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:90)
at net.minecraftforge.fml.common.eventhandler.EventBus.post(EventBus.java:185)
at net.minecraftforge.fml.common.FMLCommonHandler.onPostServerTick(FMLCommonHandler.java:261)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:657)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:471)
at java.lang.Thread.run(Unknown Source)
You can see there're two lines that don't look like they're not vanilla minecraft or forge related:
at elec332.core.grid.internal.GridEventInputHandler.tickEnd(GridEventInputHandler.java:91)
at elec332.core.grid.internal.GridEventHandler.serverTick(GridEventHandler.java:49)
A quick google reveals that the mod those methods belong to is (suprise suprise) eleccore.
I suggest you go to the github issue tracker and report your findings because this looks pretty much like the exact same thing that's happening to you.
Next up... what is eleccore used for and can we temporarily remove it? Well it looks like eleccore is used by Deep Resonance and that mod has worldgen. So removing it is a no-no. Duh....
So...what can we do?
Since we know that Deep Resonance is using eleccore, you can try to remove all your Deep Resonance machines and see if you're still able to reproduce the isse. Is it gone? Well... this means that you're no longer able to use DeepResonance without crashing your server... but at least you're no longer crashing the server so that's a start. Additionally go and look for the Deep Resonance issue tracker as well and tell them that using that there're some serious issues with the library they're using.
I hope this somehow helps you. Unfortunately there's nothing more I can do. Those are the joys of modded Minecraft
