View Single Post
  #2 (permalink)  
Old October 16, 2009, 05:14 PM
frontier204 frontier204 is offline
Hall Of Fame
F@H
 
Join Date: Nov 2008
Location: Ottawa, ON
Posts: 1,230

My System Specs

Default

Quote:
Originally Posted by Sushi Warrior View Post
[22:58:14] Entering M.D.
[22:58:20] Working on Protein
[22:58:21] Client config found, loading data.
[22:58:21] Starting GUI Server
[22:58:21] mdrun_gpu returned
[22:58:21] NANs detected on GPU
[22:58:21]
[22:58:21] Folding@home Core Shutdown: UNSTABLE_MACHINE
That's the important part... the folding doesn't even get to go to 1% before EUE (early unit end). This can mean a few things, including:
  • Bad driver
  • Unstable overclock
  • Incorrect configuration for GPU client
  • Corrupted F@H core and / or work unit files
  • Bad work unit

I'd try some of the simplest fixes first. Go into the folder where the folding is doing its work (C:\Users\Mike\AppData\Roaming\Folding@home-gpu according to your log). In that folder, delete the "work" folder, the .txt files, queue.dat, and unitinfo.txt and try running F@H again. If that doesn't work, well... I fold ATI and I think you're using nVidia so I'll let someone else chime in.

EDIT: Maybe I'd better explain why I'm asking you to delete stuff... the files I cited are part of the work unit and queue, so it will force your computer to download a new (hopefully not bad) work unit. You may also try deleting the FAHCORE.EXE if you want to force a new core to be installed as well.
__________________
"The computer programmer says they should drive the car around the block and see if the tire fixes itself." [src]

Last edited by frontier204; October 16, 2009 at 05:21 PM.
Reply With Quote