What GPU and Os are you using ? Any overclocked version ? Can you share the first part of the log file with with configuration ? Just remove your password or passkeys if visible.
As for checking the projects: this needs a helping hand of a mod to check if done by others ...
Unfortunately the BAD_WORK_UNIT characterization does not guarantee that the WU was corrupt when it was downloaded. Things can happen to them after they're downloaded. Two somethat common reports: (1) An AV program decides something looks like a virus and "protects" your system by corrupting some of FAH's data. (2) Dust or overclocking or fan limitations push the temperatures in a system too close to unstable (or a voltage glitch or ??) and a hardware error occurs. Though it may not crash the OS, corrupt data may be introduced in the calculations which are detected by FAH's quality assurance software.
Failures of two WUs that did not fail on other hardware is not definitive proof of anything, but I'd take it as a strong indication that something in your system is too close to instability.
03:15:35:WU02:FS00:Running FahCore: "C:\Program Files (x86)\FAHClient/FAHCoreWrapper.exe" C:/Users/admin/AppData/Roaming/FAHClient/cores/www.stanford.edu/~pande/Win32/AMD64/ATI/R600/Core_17.fah/FahCore_17.exe -dir 02 -suffix 01 -version 703 -lifeline 4744 -checkpoint 15 -gpu 1 -gpu-vendor ati
03:15:35:WU02:FS00:Started FahCore on PID 4392
03:15:35:WU02:FS00:Core PID:2236
03:15:35:WU02:FS00:FahCore 0x17 started
03:15:35:WU02:FS00:0x17:*********************** Log Started 2013-11-19T03:15:35Z ***********************
03:15:35:WU02:FS00:0x17:Project: 7811 (Run 0, Clone 524, Gen 491)
03:15:35:WU02:FS00:0x17:Unit: 0x000002180a3b1e8651db4ad9849b66d4
03:15:35:WU02:FS00:0x17:CPU: 0x00000000000000000000000000000000
03:15:35:WU02:FS00:0x17:Machine: 0
03:15:35:WU02:FS00:0x17:Reading tar file state.xml
03:15:35:WU02:FS00:0x17:Reading tar file system.xml
03:15:36:WU02:FS00:0x17:Reading tar file integrator.xml
03:15:36:WU02:FS00:0x17:Reading tar file core.xml
03:15:36:WU02:FS00:0x17:Digital signatures verified
03:15:41:WU01:FS00:Upload 7.59%
03:15:47:WU01:FS00:Upload 15.18%
03:15:53:WU01:FS00:Upload 22.77%
03:15:59:WU01:FS00:Upload 29.28%
03:16:01:WU02:FS00:0x17:Completed 0 out of 2000000 steps (0%)
03:16:05:WU01:FS00:Upload 36.87%
03:16:11:WU01:FS00:Upload 44.46%
03:16:17:WU01:FS00:Upload 52.05%
03:16:23:WU01:FS00:Upload 59.64%
03:16:29:WU01:FS00:Upload 67.24%
03:16:35:WU01:FS00:Upload 74.83%
03:16:41:WU01:FS00:Upload 82.42%
03:16:42:WU00:FS01:0x17:Completed 840000 out of 2000000 steps (42%)
03:16:47:WU01:FS00:Upload 88.92%
03:16:53:WU01:FS00:Upload 96.52%
03:17:00:WU01:FS00:Upload complete
03:17:00:WU01:FS00:Server responded WORK_ACK (400)
03:17:00:WU01:FS00:Final credit estimate, 13907.00 points
03:17:00:WU01:FS00:Cleaning up
03:17:46:WU02:FS00:0x17:Completed 20000 out of 2000000 steps (1%)
03:19:00:WU00:FS01:0x17:Completed 860000 out of 2000000 steps (43%)
03:19:25:WU02:FS00:0x17:Completed 40000 out of 2000000 steps (2%)
03:21:10:WU00:FS01:0x17:Completed 880000 out of 2000000 steps (44%)
03:21:11:WU02:FS00:0x17:Completed 60000 out of 2000000 steps (3%)
03:22:50:WU02:FS00:0x17:Completed 80000 out of 2000000 steps (4%)
03:23:19:WU00:FS01:0x17:Completed 900000 out of 2000000 steps (45%)
03:24:29:WU02:FS00:0x17:Completed 100000 out of 2000000 steps (5%)
03:25:38:WU00:FS01:0x17:Completed 920000 out of 2000000 steps (46%)
03:26:14:WU02:FS00:0x17:Completed 120000 out of 2000000 steps (6%)
03:27:47:WU00:FS01:0x17:Completed 940000 out of 2000000 steps (47%)
03:27:53:WU02:FS00:0x17:Completed 140000 out of 2000000 steps (7%)
03:29:39:WU02:FS00:0x17:Completed 160000 out of 2000000 steps (8%)
03:30:06:WU00:FS01:0x17:Completed 960000 out of 2000000 steps (48%)
03:31:18:WU02:FS00:0x17:Completed 180000 out of 2000000 steps (9%)
03:32:15:WU00:FS01:0x17:Completed 980000 out of 2000000 steps (49%)
03:32:57:WU02:FS00:0x17:Completed 200000 out of 2000000 steps (10%)
03:33:11:WU02:FS00:0x17:Bad State detected... attempting to resume from last good checkpoint
03:34:01:WU02:FS00:0x17:Completed 160000 out of 2000000 steps (8%)
03:34:25:WU00:FS01:0x17:Completed 1000000 out of 2000000 steps (50%)
03:35:39:WU02:FS00:0x17:Completed 180000 out of 2000000 steps (9%)
03:36:43:WU00:FS01:0x17:Completed 1020000 out of 2000000 steps (51%)
03:37:18:WU02:FS00:0x17:Completed 200000 out of 2000000 steps (10%)
03:37:33:WU02:FS00:0x17:Bad State detected... attempting to resume from last good checkpoint
03:38:22:WU02:FS00:0x17:Completed 160000 out of 2000000 steps (8%)
03:38:53:WU00:FS01:0x17:Completed 1040000 out of 2000000 steps (52%)
03:40:01:WU02:FS00:0x17:Completed 180000 out of 2000000 steps (9%)
03:41:12:WU00:FS01:0x17:Completed 1060000 out of 2000000 steps (53%)
03:41:40:WU02:FS00:0x17:Completed 200000 out of 2000000 steps (10%)
03:41:54:WU02:FS00:0x17:Bad State detected... attempting to resume from last good checkpoint
03:41:54:WU02:FS00:0x17:Max number of retries reached. Aborting.
03:41:54:WU02:FS00:0x17:ERROR:exception: Max Retries Reached
03:41:54:WU02:FS00:0x17:Saving result file logfile_01.txt
03:41:54:WU02:FS00:0x17:Saving result file badStateCheckpoint_18467
03:41:54:WU02:FS00:0x17:Saving result file badStateCheckpoint_41
03:41:54:WU02:FS00:0x17:Saving result file badStateCheckpoint_6334
03:41:55:WU02:FS00:0x17:Saving result file badStateForceGroup0_18467Core.xml
03:41:55:WU02:FS00:0x17:Saving result file badStateForceGroup0_18467Ref.xml
03:41:56:WU02:FS00:0x17:Saving result file badStateForceGroup0_41Core.xml
03:41:57:WU02:FS00:0x17:Saving result file badStateForceGroup0_41Ref.xml
03:41:58:WU02:FS00:0x17:Saving result file badStateForceGroup0_6334Core.xml
03:41:59:WU02:FS00:0x17:Saving result file badStateForceGroup0_6334Ref.xml
03:41:59:WU02:FS00:0x17:Saving result file badStateForceGroup1_18467Core.xml
03:42:00:WU02:FS00:0x17:Saving result file badStateForceGroup1_18467Ref.xml
03:42:01:WU02:FS00:0x17:Saving result file badStateForceGroup1_41Core.xml
03:42:01:WU02:FS00:0x17:Saving result file badStateForceGroup1_41Ref.xml
03:42:02:WU02:FS00:0x17:Saving result file badStateForceGroup1_6334Core.xml
03:42:03:WU02:FS00:0x17:Saving result file badStateForceGroup1_6334Ref.xml
03:42:03:WU02:FS00:0x17:Saving result file badStateForceGroup2_18467Core.xml
03:42:04:WU02:FS00:0x17:Saving result file badStateForceGroup2_18467Ref.xml
03:42:04:WU02:FS00:0x17:Saving result file badStateForceGroup2_41Core.xml
03:42:05:WU02:FS00:0x17:Saving result file badStateForceGroup2_41Ref.xml
03:42:05:WU02:FS00:0x17:Saving result file badStateForceGroup2_6334Core.xml
03:42:06:WU02:FS00:0x17:Saving result file badStateForceGroup2_6334Ref.xml
03:42:07:WU02:FS00:0x17:Saving result file log.txt
03:42:07:WU02:FS00:0x17:Folding@home Core Shutdown: BAD_WORK_UNIT
03:42:07:WARNING:WU02:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
03:42:07:WU02:FS00:Sending unit results: id:02 state:SEND error:FAULTY project:7811 run:0 clone:524 gen:491 core:0x17 unit:0x000002180a3b1e8651db4ad9849b66d4
03:42:07:WU02:FS00:Uploading 28.24MiB to 171.64.65.98
03:42:07:WU02:FS00:Connecting to 171.64.65.98:8080
03:42:07:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
03:42:08:WU01:FS00:News: Welcome to Folding@Home
03:42:08:WU01:FS00:Assigned to work server 171.64.65.98
03:42:08:WU01:FS00:Requesting new work unit for slot 00: READY gpu:1:Tahiti [Radeon HD 7900 Series] from 171.64.65.98
03:42:08:WU01:FS00:Connecting to 171.64.65.98:8080
03:42:09:WU01:FS00:Downloading 2.09MiB
03:42:13:WU01:FS00:Download complete
03:42:13:WU01:FS00:Received Unit: id:01 state:DOWNLOAD error:NO_ERROR project:7810 run:0 clone:153 gen:437 core:0x17 unit:0x000001d00a3b1e8651d3475d01d47255
It's not unusual for a core 17 work unit to fail if the GPU is overclocked. If that's the case try returning the memory clock back to stock to see if that helps. The memory clock speed has very little effect on folding performance and reducing it can result in fewer failures.
Currently your latest work unit has failed for a number of folders but that's not necessarily an indication of a bad work unit for core 17. I have seen this happen numerous times, especially with Run 0, but eventually someone does complete the work successfully.
i think its safe to say that the 7810 WU is stil available and therefor not faulty.
My new compu is doing mainly 7810 at the time and some 7811.
I'll monitor the log file more closely for e while cause i think there where no problems with
the 9800 WU's on my side the past months.
Clocking i did not do on purpose ( folding is the only game the pc plays and i know overclocking to be of no use)but i am a little in doubt about the catalys control center ??
Should it continue i'll try using one gpu to see.
Hans wrote:...Clocking i did not do on purpose ( folding is the only game the pc plays and i know overclocking to be of no use)but i am a little in doubt about the catalys control center ??...
Generally speaking, overclocking your GPU to a folding stable setting would increase your PPD. However, the increase would vary on the amount of OC and the Project. For F@H, overclocking the Shaders is more useful than overclocking the memory. Please note that overclocking would require you to monitor your GPU for instabilities for future projects since they may be more computationally intensive and thus, could push your once stable OC into the unstable zone. For a (mostly) hassle free option, use the vendor stock settings.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time
