I run DF on multi CPU boxes when I get the chance, and am also seeing the same errors.
They need a lot of nursing to keep running.
I have just checked a quad Xeon and 2 of the instances of DF have died.
One instance had this error at the bottom of the log
FATAL ERROR: [023.024] {trajtools.c, line 2507} RLEUnPack failed, size=3, should=400*400 - likely this is caused by overclocked or faulty RAM chips, please test your RAM
The other instance had this error
FATAL ERROR: CoreLib [002.005] {ncbifile.c, line 715} File write error
This is a brand new dell server with 4 2meg Xeons with 2mb cache on each CPU.
I doubt very much if it has bad ram, it is ECC so it would self repair any errors.
It also has lots of Disc space left.
I have also checked a few older dual P3 servers and a high percentage of them have broken instances of DF.
They have the same 2 errors as posted above.
A couple of them had no error in the log but refused to start until I deleted filelist.txt
Fortunately for me the corporate boxes I run this client on only contribute about 20% of my output.
I usually check them once a week and restart all the stalled instances.