Closed Occasional beam-up lag getting me killed.

So, this has only happened to me once before... but this time I had the foresight to take screenshots, then quit and grab the log. The issue is this:

When I go to beam up from a planet (neither time was I experiencing unusual lag or in combat, I was just done exploring), The beam-up animation plays, but the game just sits there, continuing to operate the planet I was on. My character is "gone", thus I cannot move, attack, or heal myself. This goes on for quite literally several minutes. Both times it was long enough for a monster to spawn, walk on-screen, and start pummeling the spot I beamed up from... from which I take damage:

log file: http://pastebin.com/exgzvFMQ
DxDiag: http://pastebin.com/Ms1AKYqj

Windows XP, SP3
AMD Athlon 64 X2 6000+ @~3.1Ghz
Nvidia GeForce 7950GT 512MB
4GB RAM @800Mhz (physical, limited by 32-bit OS)
80GB, 7200RPM SATA1 HDD

Now, this might just come down to my old, decrepit, slow computer (it was fast when I built it in 2007, but it's suffered some downgrades, heat damage and obsolescence since then)... but most of the time, the game runs fine...ish. Y'know, for a beta. lag spikes generally only last a maximum of a few seconds. This feels like a different animal to me.

Oh, also... in the log I'm seeing the usual torch asset problem for which I've downloaded a new packed.pak file... 3 or 4 times now. Doesn't seem to fix the asset problem (though it did fix my crash to desktop issue), that's just always in my log files now. The only unusual thing I spotted was

Code:

[02:11:44.854] Info: UniverseServer: Loading ship world received from client <User: Yarrow Lockewood>
[02:11:44.877] Warn: Recovering SimpleDatabase at device: <unnamed temp file>
[02:11:44.904] Warn: Recovery finished

I assume that call for the ship world happens when I beam up... and it looks to my untrained eye like a corrupted cache file that needed to be replaced from backup. No idea what the fix for that would be, since it appears to clear and rebuild the cache automatically when such an error happens. Prevention of such errors is far beyond my scope of knowledge. Any chance it's just my crappy old hard drive screwing up?

Seriously crappy. The WD Raptor I built the system with died a few years ago. I cooked it with my ignorance. Plenty of heat dissipation on my CPU and GPU, but I ignored my HDD rack.

Code:

Drive Controller:                          Serial ATA 1.5Gb/s
Drive Model:                                  Seagate ST380013AS
Drive Revision:                             8.12
Drive Capacity:                              76,293 MBytes (80 GB)
Cache Buffer Size:                          8192 KBytes

 

Try moving your .shipworld out of the player folder and letting a new one be created to see if that helps at all. I see those database recovery warnings everywhere though; I believe they are just informing you that the game was able to successfully recover a "dirty" save. They don;t seem to interfere with normal gameplay though, so I wouldn't worry too much about them. See if using a new ship helps.