It seems that a lot of GPU problems revolve around specific versions of drivers. Though AMD has their own support structure, you can often learn from information reported by others who fold.
04:24:48:WU00:FS00:News: Welcome to Folding@Home
04:24:48:WU00:FS00:Assigned to work server 171.67.108.44
04:24:48:WU00:FS00:Requesting new work unit for slot 00: READY gpu:0:"Juniper [Radeon HD 5700 Series]" from 171.67.108.44
04:24:48:WU00:FS00:Connecting to 171.67.108.44:8080
04:24:49:WU00:FS00:Downloading 44.44KiB
04:24:49:WU00:FS00:Download complete
04:24:49:WU00:FS00:Received Unit: id:00 state:DOWNLOAD error:OK project:11293 run:17 clone:91 gen:27 core:0x16 unit:0x000000656652edbc4d94b82c5611a4dc
04:24:49:WU00:FS00:Starting
04:24:49:WU00:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/Sam/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_16.fah/FahCore_16.exe -dir 00 -suffix 01 -version 701 -lifeline 3380 -checkpoint 15 -gpu 0
04:24:49:WU00:FS00:Started FahCore on PID 6392
04:24:49:WU00:FS00:Core PID:4956
04:24:49:WU00:FS00:FahCore 0x16 started
04:24:50:WU00:FS00:FahCore returned: UNKNOWN_ENUM (-1073741515 = 0xc0000135)
04:24:50:WARNING:WU00:FS00:FahCore returned an unknown error code which probably indicates that it crashed
It will get the same error 5 times fail the work unit then start the proccess over again
I'm running win7 fully updated and catalyst v11.5
The SMP core is running great I'm not sure if that's relevant
Could you please post the system portion of the log? Specifically, I'm looking to see if you are running folding as a service which happens to be incompatible with GPU folding. If that is the case, you need to uninstall and reinstall without running it as a service.
The reason running as a service is disallowed is that Microsoft, as a security measure, does not allow services any access to the video subsystem.
Well I decided to read through all the other posts in the forum category just incase my problem was similar and while it wasn't as far as I can tell I did notice that driver updating seemed to be a pretty common solution so I updated my gpu driver and now it seems to be working fine. Catalyst version 11.5 is apparently not friendly with F@h but 12.8 is. Thanks anyway to P5-133XL
Just in case anyone is curious I'll go ahead and post the config portion of the log
Another possibility: A fully updated version of WindowsXP doesn't necessarily include the FAH prerequisite .net framework 2.0. If you don't have it, you'll probably need to explicitly install and update .net framework 3.5. (I spent a long time trying to find a stand-alone net framework 2.0. It turns out that it's included in 3.5 but Microsoft doesn't clearly spell that out if you try looking for .net framework 2.0.) Neither version 1.1 or version 4.0 meet the requirements.