Folding Forum

So does this mean the WU was thrown out and no credit was given?

Finished a second WU and it uploaded to a different server, yay. Meanwhile this one is still stuck and it has currently lost 45% of the points value. Sometimes it connects and starts to upload, but always fails around half a percent. 00:50:15:WU01:FS01:Uploading 24.34MiB to 140.163.4.231 00:50:15:WU...

Started to upload, took 5 minutes to upload 0.56% before it failed. All subsequent attempts to connect have failed. 00:23:31:WARNING:WU01:FS01:Exception: Failed to send results to work server: Failed to connect to 140.163.4.231:80: A connection attempt failed because the connected party did not prop...

Same. Deleted the 21 core and restarted the client, still stuck on updating.

Edit: Updated client to 7.5.1 and it is still stuck on updating the core. Project 14177 (85, 4, 133)

Sorry, this was my mistake! The project 9441 and 9442 were never meant to go live. No problem, stuff happens! That being said, this makes the third time this year that I know of where one, or multiple projects were unintentionally released to general distribution. Perhaps Pande Group needs to add a...

Wow...

We had differences of opinion and we had our agreements, but in the end I could always tell you cared about the Folding@home project and were making a difference in your way, especially through your dedication to these forums. Requiescat in pace, Tim.

Hello everyone, I apologize for the late response. 171.67.108.105 is my WS, which has been given assignemnts by the WS even though it has no assignable jobs. We are currently trying to fix the problem with the AS where it keeps sending jobs to my WS. In the meanwhile, I have reduced the priority of...

No errors after multiple Facore 21 projects, issue looks resolved. Thanks guys for the help figuring this out. :) It's probably something as simple as the order of entries in the PATH environment variable -- and likely influenced by the order of the driver installations. The AMD/NVIDIA drivers were ...

Only been a day, but deleting the igdrcl64.dll seems to have stopped the eventlog errors. The AMD and NVIDIA drivers were the most recently installed drivers on both affected systems. Nothing is connected to the IGP ports so the IGP shouldn't even be active and F@H shouldn't be trying to use it. Bot...

Uninstalled the Intel graphics driver, restarted, resumed F@H and it instantly created a new igdrcl64.dll event.

Went ahead and deleted the dll file, restarted again and seems fine so far. Will check on it later today.

Bruce, looks like both GPUs are using version 18 for core 21. When I installed the Radeon it downloaded a separate copy. That is bizarre, it seems odd F@H would try to access Intel's OpenCL driver. I can confirm that I have the latest Intel HD 4600 (haswell IGP) drivers installed on both of these af...

I wanted to be sure before I posted again as this appears to be a problem with the latest Fahcore 21 build and is not related to GPU driver or GPU vendor. I am seeing this error on two different stock computers. One has a 750 Ti (378.66), the second has an AMD R9 380 (17.2.1) I just installed and im...

So far Prime95 and Memtest are clean, however I found three other instances from last month that involved different program exe's but same event ID + exception code. Oddly there's a dozen for Fahcore21 starting back in Jan, it must've really found the sweet spot. Going to manually tune the RAM timin...

Stock everything, temps are fine. Basic DDR3-1600 kit. Will run some memory stress tests & memtest86, thanks! I presume that was RAM and not VRAM.

Noticed this several times now. I'll see a fault in the event logs for F@H's GPU client, but the F@H log is clean. Faulting application name: FahCore_21.exe, version: 0.0.0.0, time stamp: 0x588257cc Faulting module name: igdrcl64.dll, version: 20.19.15.4531, time stamp: 0x57ed260c Exception code: 0x...