Thanks to everybody who gave me help and advice.
After the usual cycle of dramas you get when bringing an old machine that's been off for a while up from cold, the Q9550 + 2 x GTX750's is now quite stable, and while running 2 units per card, is getting through a normal unit in ~20 mins and, 30 to 40 mins for a guppi. I'm happy with that.
All crunching is being done on the GPU's

Mike wrote

Check for a file called mb_cmdline_win_x86_SSE3_OpenCL_NV_SoG.txt in the projects folder.
Add the following.

This worked wonders for the GTX750's, chopped nearly 15% off the single unit crunching time. Could you please give me some settings for the 1070Ti ?

Raistmer wrote

he issue you encountered on 750Ti is:
ERROR: OpenCL kernel/call 'clGetEventProfilingInfo' call failed (-7) in file ..\..\..\src\GPU_lock.cpp near line 546.

-7 is CL_PROFILING_INFO_NOT_AVAILABLE

It's NV OpenCL Runtime issue. Maybe can be cured by driver change.
As workaround try to update to r3584 (your build is r3557). Newer builds account for such Runtime failures and treat this error as non-important just omitting tuning.

I upgraded to r3584 and the 2nd last WinXP driver, I now get tasks "wating to run" but not "postponed". Which I think is more a BOINC scheduling issue than anything else. It was the "Postponed" message that threw me..

I upgraded to r3584 and the 2nd last WinXP driver, I now get tasks "wating to run" but not "postponed". Which I think is more a BOINC scheduling issue than anything else. It was the "Postponed" message that threw me..

. . If you are getting that "waiting to run" status a lot then you might try reducing the value of -sbs. Maybe 768 or even 512 would work better for you.

In the past they were strongly linked with the PC's stress detection system - the higher your personal stress level the more probable one would experience a BSOD :-(Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

I upgraded to r3584 and the 2nd last WinXP driver, I now get tasks "wating to run" but not "postponed". Which I think is more a BOINC scheduling issue than anything else. It was the "Postponed" message that threw me..

. . If you are getting that "waiting to run" status a lot then you might try reducing the value of -sbs. Maybe 768 or even 512 would work better for you.

Stephen

:)

I tried that, and whatever part of the system that was just managing to keep itself together..... broke completely :(

All I get now when I try to run SoG, is half a dozen or so units going round in a continuous, Run -> Waiting to run -> Postponed -> Run -> n loop.

It's only "normal" units that do this, guppi's crunch quite happily

I tried going back to 41zi, but some of the "normal" units coming through must be unlabelled vlars because they were taking nearly 2 hours to crunch.

Is there any way to modify the app_info so that files with the suffix .vlar get crunched by SoG and those units without a suffix use x41z ?

Is there any way to make this thing behave ? Or do I just put this box back to sleep ?

All I get now when I try to run SoG, is half a dozen or so units going round in a continuous, Run -> Waiting to run -> Postponed -> Run -> n loop.

Is that your Quad 2 doing that? From what I see it is.

My AMD 4200 (w/750Ti) use to do it too with SoG tasks. I cured it by changing to Linux.

The best I could figure with it was the slow CPU casing it. In the sense that IF the GPU tasks were assigned to the CPU, it would be over the 10 day limit, causing the Arecibo tasks to only run for a very short time before switching tasks, the BLC tasks ran fine. I set it to 10s check points to get through them. I don't believe I ever found a cure for it. Thinking maybe a smaller cache might work, don't think I tried that.

I know the it sounds strange that the CPU time would be considered in the GPU equation, but it was the best thing I could think of. I know it started with a changing Lunatics and BOINC versions (upgraded both at the same time), and believe it was because it ran benchmarks to come up with something new. I reverted back to previous versions and that did not cure it. I thought at the time maybe manually entering a flop value may help, but didn't try it.

It's been over a year now, that's the best I can recall from that ordeal ...

I tried that, and whatever part of the system that was just managing to keep itself together..... broke completely :(

All I get now when I try to run SoG, is half a dozen or so units going round in a continuous, Run -> Waiting to run -> Postponed -> Run -> n loop.

It's only "normal" units that do this, guppi's crunch quite happily

I tried going back to 41zi, but some of the "normal" units coming through must be unlabelled vlars because they were taking nearly 2 hours to crunch.

Is there any way to modify the app_info so that files with the suffix .vlar get crunched by SoG and those units without a suffix use x41z ?

Is there any way to make this thing behave ? Or do I just put this box back to sleep ?

T.A.

. . OK I am confused ... I thought that x41z was a CUDA variant. Maybe I am missing something. But I would try to get one or the other working properly rather than mix things up. SoG works pretty well if you get it setup right. Maybe something went wrong when you tried to setup r3584. Not seeing what is setup and seeing r3557 on your result STDERR section I am guessing maybe reinstall Lunatics Beta6 and see if you can get things working properly again. Just run SSE3 for the CPU in the Core2 and AVX for the CPU in the i7. The use SoG for the GPUs and concentrate on getting that back to working AOK. Oh, and make sure you have at least one CPU core free for each GPU, so set the Core 2 Quad Boinc manager to only use 50 or 25 % of CPU cores. I had my Core2 Duo with a GTX1050ti putting up a 13K RAC and I was crunching on one CPU core on that machine (but it does have 6GB Ram). So I know that that series of CPUs can work AOK with SoG on a GPU.

. . Some Normal WUs are what I call Quite Low AR units (QLARs) which have AR values close to but not low enough to be classified as VLAR. (Which is below 0.12 I believe). These QLARs are often below 0.2 and they will run very slowly compared to other normal tasks but SoG can process even Arecibo tasks classified as .VLAR if you wanted. SoG is probably the best thing for crunching GBT work as you have noted but should be AOK for all Arecibo tasks as well. When in doubt take it back to the setup where you know it was working AOK then try to move forward from there.

. . Also I notice that even though you are running doubles your still have -sbs set to 1024. If you look at your STDERR you sill see that it is setting the buffer size to 511MB anyway. So I would suggest you stick to -sbs 512 if you really want to run doubles. But that's up to you.

I have tried various problem solvings, but my computer with 780ti's can only get 8.00 units and I wanted 8.22.
Another issue on my other computer with 2 1080 ti's keeps running only one gpu for SETI, in Primegrid it uses both. What can I do?
Any help would be welcome.

I have tried various problem solvings, but my computer with 780ti's can only get 8.00 units and I wanted 8.22.

The first one (8.00) you have used the Lunatics Installer, the second one (8.22) is running stock.

The one running stock will perform the best, as you have selected the wrong application to run using the Lunatics Installer. Running the CUDA32 application will result in the poorest possible performance from your hardware.
If you were to install the SoG application it would be running what is essentially (other than some very minor differences), the stock application.Grant
Darwin NT

Thank you Grant very much. If you do not mind would you check if I did it right? There were so many choices. I see significant improvement in the speed already.
On my other computer: Could you tell me why am I getting only the one 1080ti card running in SETI( I have two installed) I tried a copy and paste directions, but must have done it wrong. This computer is getting the 8.22 ocl units fine.

...
On my other computer: Could you tell me why am I getting only the one 1080ti card running in SETI( I have two installed) I tried a copy and paste directions, but must have done it wrong. This computer is getting the 8.22 ocl units fine.

Hey folks. Just replaced an AMD 280X with an RX Vega 56. I pretty well had my config files optimized for the 280X, but I'm not so sure about any changes needed for the newer Vega cards. Am I good to go with the old card's config file for Vega, or are there any suggestions as to modifications I should make?