I first instance of this notice was on 10/31/2017. I noticed the notice and restarted the machine around 23:39. I didn't check the event log at that time so I'm not sure exactly when it started on 10/31/2017, or how many times it had happened. Since that time this 'Task postponed: Suspicious pulse...' appears >25 times in the event log. The machine is running without error otherwise. Has something been updated recently that might be causing this? Any suggestions or questions?

The last time that error came up, I forwarded it to the project admin. None of them knew what it meant, it's an error added by the OpenCL app developers. We're yet to hear back what it means, but like I said last time, if you still see the error, abort the task. Any task that asks you to manually do something to get it running again isn't going to be worth your while.

Edit: although, if they run to a finish fine and validate okay, it's probably more cosmetic than anything else.Jord

Ancient Astronaut Theorists can tell you that I do not help with tech questions via private message. Please use the forums for that.

Your host has an AMD Compute Engine. I found out today that all Compute Engines for the Mac report negative memory, zero memory or extreme amounts of memory (zettabytes). That's been fixed in 7.8.4, which is now out for the Mac. Could you update to that version to see if that also fixes this problem?Jord

Ancient Astronaut Theorists can tell you that I do not help with tech questions via private message. Please use the forums for that.

I will, but I don't know how to do that upgrade. I didn't see a procedure when searched the forums. If you send me link to an upgrade procedure, or respond here with instructions, I'll report the results here.

Please ignore my previous post. I have installed 7.8.4. So far it's working fine. If there are error's I will post them here. If there are no errors in the first 24 hours then post that here also. My apologies for the confusion.

I had to abort one task that was generating an error. Once that was done there have been no other problems. I'll post an update here after it has run without error for 24 hours, or if there is a error I'll report it here when it happens.

No, the 0.5 CPU + {Brand} GPU message in BOINC Manager is what the application asks to be used at maximum of the hardware resources. In reality it's much less than half a CPU that the GPU applications use. But they use the CPU nonetheless, as it's the CPU that does the heavy work of reading, translating, transporting and storing of the data that the GPU does calculations on.

The message you get seems to be benign, and unless it really ends in an error (where the task ends up in the Error section in your task list), it isn't something to worry about. Even if it ends up in the Error section, if it's only one task every several, it isn't something to worry about. Some of us are taking it up with the application developer, but it may well be that the app is doing it right, but the data has a corruption that causes this. As long as not all your tasks start doing this and end in errors, I wouldn't lose much sleep over it. :)Jord

Ancient Astronaut Theorists can tell you that I do not help with tech questions via private message. Please use the forums for that.

It's not BOINC that has the issue, it's the Seti science application. I'm still pretty sure it's a cosmetic issue as well, and that if you just leave them running like that - with their pauses - that they'll finish fine.

Looking at your computers though, you don't seem to have an active Mac. Only ARM devices.Jord

Ancient Astronaut Theorists can tell you that I do not help with tech questions via private message. Please use the forums for that.

Looking at your computers though, you don't seem to have an active Mac. Only ARM devices.

I run two SETI@Home accounts, one with just my Mac and a couple of other machines from time to time, another with five Raspberry Pi 3s (this account). Didn't notice any issues on any of nodes in the RPI cluster though, only on the Mac."I'd love to change the world, but they wouldn't give me the source code" - Unknown

The potential Fix has been sitting at Seti Beta since October 17th, with very few people testing or reporting results. If you'd like to help, add Beta to your projects by adding the url http://setiweb.ssl.berkeley.edu/beta/ to the Add projects window Project URL:, then test the App "8.22 (opencl_ati5_mac)" for about a day and report the results here, https://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=2266
If enough people report success, the New App may be moved to Main.