FTB client crashes when exiting portals at base.

[TurboLance]

I'm running a small FTB Unleashed server, and the few of us that are playing are having trouble with the FTB client crashing when entering/exiting portals (portals made from portal guns, Nether portal, Mystcraft books and Twilight portal).
It doesn't happen all the time, maybe around 50% of the time. And only been happening the last week.


Pastebin of error log http://pastebin.com/7SVmX013

Server says the following:

Spoiler

2014-02-26 18:20:47 [INFO] [STDERR] java.net.SocketTimeoutException: Read timed
out
2014-02-26 18:20:47 [INFO] [STDERR] at java.net.SocketInputStream.socketRead
0(Native Method)
2014-02-26 18:20:47 [INFO] [STDERR] at java.net.SocketInputStream.read(Unkno
wn Source)
2014-02-26 18:20:47 [INFO] [STDERR] at java.net.SocketInputStream.read(Unkno
wn Source)
2014-02-26 18:20:47 [INFO] [STDERR] at java.io.FilterInputStream.read(Unknow
n Source)
2014-02-26 18:20:47 [INFO] [STDERR] at org.bouncycastle.crypto.io.CipherInpu
tStream.nextChunk(Unknown Source)
2014-02-26 18:20:47 [INFO] [STDERR] at org.bouncycastle.crypto.io.CipherInpu
tStream.read(Unknown Source)
2014-02-26 18:20:47 [INFO] [STDERR] at java.io.FilterInputStream.read(Unknow
n Source)
2014-02-26 18:20:47 [INFO] [STDERR] at net.minecraft.network.packet.Packet.f
unc_73272_a(Packet.java:144)
2014-02-26 18:20:47 [INFO] [STDERR] at net.minecraft.network.TcpConnection.f
unc_74447_i(TcpConnection.java:327)
2014-02-26 18:20:47 [INFO] [STDERR] at net.minecraft.network.TcpConnection.f
unc_74450_c(TcpConnection.java:547)
2014-02-26 18:20:47 [INFO] [STDERR] at net.minecraft.network.TcpReaderThread
.run(SourceFile:94)
2014-02-26 18:20:47 [INFO] [Minecraft-Server] TurboLance lost connection: discon
nect.genericReason
2014-02-26 18:20:47 [INFO] [STDOUT] Unloading Player: TurboLance

Any clues?

 

[TurboLance]

Bump.

It has started happening when we log in to the server too.

Seems like it's only happening when we go through a portal/book etc. going to our main base (where all the machines and everything is),
or logging in when the character is at the base. So there's definitely something there causing it (I would guess).