2016/03/23 14:03:13
un4givn85
bcavnaugh
un4givn85
i think it took me about 10 days to get 3 million, including gaming for a couple hours a couple nights
 
disclaimer: i do not fold at 1601mhz, that is just the max ive achieved for benching, lol


Do you mean on your AMD Cards or your GTX 970 SSC+ Cards?


I do not have any AMD products.
Just my one EVGA GTX 980 SC with a hybrid cooler on it.
2016/04/01 08:28:07
bcavnaugh
Next Testing Two AMD R9 290X Graphics Cards.
Why because I can and they have always beaten out the GTX 780 Cards when it come to Folding.
 
Test will start on 04.01.16 to set status to Zero.

  * Sub Total (Day 01 & 02 are really a half day)
Day 01)  208,363
Day 02)  262,066
Day 03)  565,718  One WU Failed 8 Hours lost.
Day 04)  638,796
Day 05)  516,430  One WU Failed 8 Hours lost.
Day 06)  756,232
Day 07)  469,635  One WU Failed 8 Hours lost.
Day 08)  701,187  One WU Failed 8 Hours lost.
Day 09)  543,698  *4,662,125
So for my AMD Graphics Cards even with all the Failed WU it takes 8 Day on a Low Side and 9 Days on the High Side.
 
Testing back up and running, had some OS Patching issues and now I am back Folding.
2016/04/08 14:18:56
bcavnaugh
BAD_WORK_UNIT
error:FAULTY project:13106 run:2 clone:42 gen:20 core:0x21
error:FAULTY project:13105 run:3 clone:8 gen:69 core:0x21
error:FAULTY project:13105 run:6 clone:18 gen:85 core:0x21
 
Maybe for the AMD GPUs 16.3.2 is not the best driver for Folding.
I will wait for the current tasks to complete and then update to the Hotfix Version 16.4.1.
 
When you remove the 16.3.2 Driver and Software is does not remove the Vulkan Drivers.
You have to do this separately under "Programs and Features" Vulkan
 
Dope Doh! the Driver made no Difference.
error:FAULTY project:13106 run:2 clone:21 gen:61 core:0x21
 
 
I Posted this over on Stanford   Error FAULTY Projects 13105 & 13106 
 
This is what Stanford said:

Re: Error FAULTY Projects 13105 & 13106

by Joe_H » 09 Apr 2016, 10:54All four of the WU's you listed have since been completed successfully by other folders.
2016/04/08 22:44:26
HK-Steve
You are not the only one, Just woke up this morning to find these errors. These are NVidia GPU's, 980ti and 970's
 
*********************** Log Started 2016-04-01T12:38:21Z ***********************
******************************* Date: 2016-04-01 *******************************
00:25:29:WARNING:WU03:FS03:FahCore returned: FAILED_1 (0 = 0x0)


*********************** Log Started 2016-04-01T12:38:21Z ***********************
16:16:26:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
16:16:26:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
16:35:38:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
16:35:38:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
16:16:26:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
16:16:26:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
16:35:38:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
16:35:38:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
17:12:32:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
17:12:32:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
17:48:16:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
17:48:16:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)


2016/04/09 04:48:15
Scarlet-Tech
I had a bad 980ti work unit before I left home. I am down for the week, since I am out of state. I am not going to keep running my system full bore while I am not around to make sure everything is working properly.
2016/04/09 06:19:02
HK-Steve
Be safe my friend..
Fold when you return..and can monitor what is going on.
 
2016/04/09 06:36:42
Zuhl3156
HK-Steve
You are not the only one, Just woke up this morning to find these errors. These are NVidia GPU's, 980ti and 970's
 
*********************** Log Started 2016-04-01T12:38:21Z ***********************
******************************* Date: 2016-04-01 *******************************
00:25:29:WARNING:WU03:FS03:FahCore returned: FAILED_1 (0 = 0x0)


*********************** Log Started 2016-04-01T12:38:21Z ***********************
16:16:26:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
16:16:26:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
16:35:38:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
16:35:38:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
16:16:26:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
16:16:26:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
16:35:38:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
16:35:38:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
17:12:32:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
17:12:32:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)
17:48:16:WARNING:WU01:FS01:FahCore returned an unknown error code which probably indicates that it crashed
17:48:16:WARNING:WU01:FS01:FahCore returned: UNKNOWN_ENUM (127 = 0x7f)




Stanford is getting more proactive with their warning messages. Whenever I get one of those pesky "Bad state detected attempting to resume from a known good point" warnings I also get a comment asking "Is your system overclocked"?
2016/04/09 07:54:48
HK-Steve
No, I have never overclocked any GPU or CPU..
All stock settings and fans controlled with higher speeds than normal.... MSI Afterburner controlled with my own curve for more cooling.
2016/04/09 08:02:39
Zuhl3156
HK-Steve
No, I have never overclocked any GPU or CPU..
All stock settings and fans controlled with higher speeds than normal.... MSI Afterburner controlled with my own curve for more cooling.


Mine wasn't overclocked at the time either. I just noticed the additional question added to the bad state warning. The insinuation that it is never ever Stanford's fault is annoying at best. My video board was running at 70C and I had to limit my temps using MSI Afterburner. I did finish the WU I think but it was drawing 108% Power Limit and the board was running hot because my Maelstrom V2 was getting ready to burst into flames. It did shortly afterwards too.
2016/04/09 09:39:46
bcavnaugh
HK-Steve
No, I have never overclocked any GPU or CPU..
All stock settings and fans controlled with higher speeds than normal.... MSI Afterburner controlled with my own curve for more cooling.


Not sure what Projects you are failing on?
Look for this in your Log Files.
error:FAULTY project:13106 run:2 clone:42 gen:20 core:0x21

Use My Existing Forum Account

Use My Social Media Account