I just had that error... turns out you can't right-click and save as on the link otherwise you get a html page saved. You need to click it, then click view raw where it then downloads. I don't get their logic in how the page is arranged.

I am going to speak anecdotally here for a moment. I will also preface this by stating that I may have an unstable graphics card even though none of the traditional graphics benchmarks or games have any issue running. If you look at my profile you can see that I'll have a few units with errors from GFN-17MEGA, GFN-18 and GFN-19.

Running the OCL app for GFN-21 and GFN-22 causes my system to stutter so badly it becomes unusable. After a while, anywhere from a few minutes to a few hours, a BSOD will happen.
Today I decided to give the CUDA version of GFN-21 a go to see what would happen. As of this post it has been running for 25 minutes without the tiniest indication that anything is even happening as far as system usability and stability are concerned. It's running fantastically. I will, of course, have to see if it returns an error or not in about 60 hours.

This may be a reason for keeping CUDA around, but if the new OCL acts like the current CUDA then I have no objections.

Kieth, if screen lag is indeed a problem with OCL, then yours is the first response that's potentially useful to me. This is the first I've heard of anyone complaining about screen lag with OCL. Screen lag is common with CUDA, which is why we have a block size adjustment which lets you trade off performance for reduced screen lag.

There's no corresponding adjustment for OCL because there's been few if any complaints about it, and I'm not even sure if such an adjustment is possible with OCL. Because of the lack, or at least rarity, of such complaints, I'm wondering if the usability problems you're seeing are related to the other problems you're having with your GPU. It could be that there's an underlying problem causing both symptoms.

Replacing CUDA in favour of OCL (or whatever name you may use for it) seems to be the trend anyway too. POEM e.g. does ist the same way. I find less an less pure CUDA-Tasks (with low CPU-usage) within the world of BOINC.

After all considerations, giving up a core for solving numerous other problems seems very reasonable.

More problems with the combined app, this time around when using Boinc. I found this while using ver 1036, though I've tested 1062 and the issue is there as well (side note, the file transform problem is fixed).

Anyways, here's what happens. At first, it does the crunching as intended. It benchmarks, selects a transform and starts running. But then all of a sudden, performance tanks. Progress bar moves super slowly and GPU usage is minimal. Also, CPU usage goes from "almost 0" to a full core. Looking at the Stderr file:

Command line: projects/www.primegrid.com/geneferocl_combined_1062.exe -boinc -q 1430458^262144+1 --device 0 Priority change succeeded. A benchmark is needed to determine best transform, testing available transform implementations... Testing OCL3 transform... Running on platform 'Intel(R) OpenCL', device 'Intel(R) HD Graphics 530', version 'OpenCL 2.0 ' and driver '20.19.15.4331'. Testing OCL4 transform... Testing OCL5 transform... Benchmarks completed (45.423 seconds). Using OCL4 transform Starting initialization... Initialization complete (1.068 seconds). Testing 1430458^262144+1... Estimated time remaining for 1430458^262144+1 is 3:47:11 Estimated time remaining for 1430458^262144+1 is 830:20:14 Estimated time remaining for 1430458^262144+1 is 830:21:03 Estimated time remaining for 1430458^262144+1 is 830:22:54 Estimated time remaining for 1430458^262144+1 is 830:23:42 Estimated time remaining for 1430458^262144+1 is 830:25:33 Estimated time remaining for 1430458^262144+1 is 830:27:05 ...

It just keeps endlessly writing the time estimate to the file, instead of actually doing computations. Just a few seconds of it happening, and the stderr file was alread 600KB long - it once happened while I was away from the computer for a while, and it reached almost half a GB in size!

The above stderr was retrieved from my HD Graphics 530; still, it also happens with my GTX 970:

Running on platform 'NVIDIA CUDA', device 'GeForce GTX 970', version 'OpenCL 1.2 CUDA' and driver '361.91'. Testing OCL4 transform... Testing OCL5 transform... Benchmarks completed (5.659 seconds). Using OCL4 transform Starting initialization... Initialization complete (1.064 seconds). Testing 1430690^262144+1... Estimated time remaining for 1430690^262144+1 is 0:24:20 Estimated time remaining for 1430690^262144+1 is 485:06:31 Estimated time remaining for 1430690^262144+1 is 485:06:32 Estimated time remaining for 1430690^262144+1 is 485:06:33 Estimated time remaining for 1430690^262144+1 is 485:06:35 ...

Also, they can't be seen due to primegrid's forum posting, but right after each line, there are a bunch of blank spaces, as if someone pressed Tab or the space bar multiple times.


This issue happens randomly - I don't know how to forcefully replicate it. But I know a few things: 1- it doesn't happen with the standalone apps; 2- it can happen at any time. My 970 was at around 50% work done, while my HD 530 was only at around 9% in the latest occurence; 3- when it DOES happen, both instances (my Gtx 970 and my Intel HD 530) are affected at once. I'm currently testing each GPU separately to see if it happens again, will report back at a future time.

EDIT: Happens when running just the Gtx 970, will see if it happens when running the iGPU alone.

EDIT 2: Yup, happens when running the iGPU separately as well. Again, no idea on what causes it. Switching back to standalone apps until fixed.