Your problem will affect all other SETI users which run stock/standard AstroPulse app
which also run the same antivirus (TrendMicro ?).

So if you are paid customer of TrendMicro - make report to them asking to check the issue with that file, e.g.:

"
I think I found a false-positive given by TrendMicro
Will you check this file to confirm it is virus free or not:
http://boinc2.ssl.berkeley.edu/sah/download_fanout/ap_graphics_6.01_windows_intelx86.exe

I had a look at dskag's host: there's only one WU been processed and it's a high-percentage blanked one, too, so most of the work was done by the CPU (that's why it was so slow).

Looks like it's running Catalyst 11.9 - my HD 4670 host is using Catalyst 12.1. 11.9 falls in between that series of Catalyst 11.3 and 11.11 where CPU usage was abnormally high, I thought. But if you still think it's a good idea, Raistmer, for me to try Catalyst 11.9, I will try to do it in between AP tasks. Will have to hunt down the AGP version, too...Soli Deo Gloria

So you run over AGP, perhaps it's another difference. High blanking means that initial data preparation was done on CPU (where blanking applies). After that stage all work done on GPU too.

It's really hard to judge on only 1 task indeed, especially because your host sometimes produces good results too. Lets gather more statistics. And yes, if you could switch to older CAt driver at least for some time I think it's worth to try.

Most changes in last release were made in FFA part (repetitive pulses search), but overflow in single pulses no way connected to it - that's strange...

I'm looking for the Catalyst 11.9 WinXP AGP drivers. I know AMD keeps them on their server even though they might not show direct links on their public pages any more. But I can't remember the AGP drivers file name - looks like their current AGP release is a 'legacy' Catalyst 12.6. No good for OpenCL on WinXP, anyway.Soli Deo Gloria

I'm looking for the Catalyst 11.9 WinXP AGP drivers. I know AMD keeps them on their server even though they might not show direct links on their public pages any more. But I can't remember the AGP drivers file name - looks like their current AGP release is a 'legacy' Catalyst 12.6. No good for OpenCL on WinXP, anyway.

Here's the url, you'll have to go to an AMD page, probably the AGP Hotfix web page to get it to work:

Do i understand that right? You use an AGP 4xxx Card? I think that i read anywhere that the AGP versions of the 4xxx cards dont run on OpenCL or something (but yes it will report as OpenCL device). But thats a long time ago, dont know where i read that. (wanted to buy an aditional AGP 4xxxx card before put some AGP machines in trash at this point and looked on the web how it run).

Or does anyone here run a AGP 4xxx Card with validated Results to correct that?

I will run some more AP on the 4350 (when i get a new task ^^) because Raistmer wrote 1 tasks is not that representaive. But your right, the usage of cpu was damn high i saw now O.o This card only has 96Gflops what is vverrrryyy low so i dont know how much the GPU or the CPU trotteling eatch other because the CPU is a "greenIT" CPU with the power of i think only a P4 3,6Ghz (but i will look next task with GPUz and Taskmanager how much it needs the components). I just have bad experience with 12.x drivers and cos its my fileserver i dont try to update the catalyst, im aware of a hard to remove Bluescreen on startup again ^^ And dont have any computer left to try it there :/

Yes, it's a HD 4670 with AGP interface. There is no difference to HD 4670 PCIe other than it has a PCIe-to-AGP chip (I think ATI started doing this since the X1950), so it definitely supports OpenCL. The HD 4000 series cards only have 'beta-level' OpenCL support, according to AMD's APP SDK notes - seems to me that's why HD 5000 series and later are much more stable for OpenCL processing.

I have been using this card for a long time, just with increased incidence of invalid results when using the AP r1316 build. I've reverted to r555 and have just completed a task with credit, so it definitely works... just not reliably, apparently.

Another reason why your ATI AP task used so much CPU - aside from high-percentage blanking, you're using the Catalyst 11.9 driver which still suffers from the 100% CPU usage bug with OpenCL applications. I've just confirmed this by installing Catalyst 11.9 (after a DriverSweep) and running the AP bench-test (r1316, unroll 10, ffa_block 4096, ffa_block_fetch 2096):