All 3 my machines went down at block 2060 so it looks as if there are still some problems with grant-block processing.
As I mentioned before, once the problem is solved that you can load the blockchain while mining, this will prove the client is stable enough to run without crashing.
Okay, that sounds like stability issue 1 . . . it's weird that you'd be seeing problems on all your machines, when many others don't have any stability problem . . . I wonder what might be common to all three machines.
I'm assuming these aren't hard machine crashes, as you know which block you're going down on. It would be helpful to get the tail end of the debug.log file after a crash . . it will probably have crashed somewhere in the middle of the grant allocation code, and then there will be some superfluous network activity . . . just before the network activity is where the interesting stuff is.
You assume righ about it not being hard machine crashes. The program looks fine but the only way to tell it's not working is by opening the debug window and looking at the block number. My 6-core and 4-core both got stuck on a block again tonight.
When I close the program, I have to go into the windows task manager to kill the memorycoin.exe*32 process manually or I can't start the client again.
I will E-mail you the tail ends of the debug.log files but I don't think you will find anything interesting there. All I could see were some connection timeouts.
AFTER I killed the memorycoin process manually in the task manager, these lines were added to the debug.log on both machines:
net thread interrupt
dumpaddr thread stop
opencon thread interrupt
addcon thread interrupt
On my 2-core celeron machine the program crashed due to a runtime error. I will include that debug.log too.