Installed the new H50 water cooler but I'm not sure if it's effecting stability. The only thing I've changed recently is the cpu cooler. I did have some disk errors lately that I chkdsk fixed. Do you think this is a disk problem or an OC problem? I was using bittorrent and got a disk full error message so perhaps there wasn't room enough in the Ubuntu partition to write to the disk. Perhaps Linux isn't as good at disk management as W7 is.
 

[04:17:34] Completed 2500 out of 250000 steps  (1%) 
 [04:25:01] mdrun returned 255 
 [04:25:01] Going to send back what have done -- stepsTotalG=250000 
 [04:25:01] Work fraction=1651.6516 steps=250000. 
 [04:25:05] logfile size=15312 infoLength=15312 edr=25 trr=1 
 [04:25:05] logfile size: 15312 info=15312 bed=25 hdr=1 
 [04:25:05] - Writing 15850 bytes of core data to disk... 
 [04:25:05] - Could not write to results file. 
 [04:25:06]  
 [04:25:06] Folding@home Core Shutdown: UNSTABLE_MACHINE 
 [04:25:06] CoreStatus = 7A (122) 
 [04:25:06] Sending work to server 
 [04:25:06] Project: 6900 (Run 14, Clone 18, Gen 22) 
 
 [04:25:06] + Attempting to send results [August 30 04:25:06 UTC] 
 [04:25:06] - Error: Could not read results file work/wuresults_01.dat from disk 
 [04:25:06] - Error: Could not read unit 01 file. Removing from queue. 
 [04:25:06] - Preparing to get new work unit... 
 [04:25:06] Cleaning up work directory 
 [04:25:06] + Attempting to get work packet 
 [04:25:06] Passkey found 
 [04:25:06] - Connecting to assignment server 
 [04:25:06] - Successful: assigned to (171.67.108.22). 
 [04:25:06] + News From Folding@Home: Welcome to Folding@Home 
 [04:25:07] Loaded queue successfully. 
 [04:25:24] + Closed connections 
 [04:25:29]  

I should clarify that I'm wondering if "Could not write to results file." meant that the disk was full and would this cause an Unstable_Machine error?