I am seeing the above quite often. The error text goes on to suggest that if it happens often you should reset the project - which I have done, but that makes no difference to the error.

Any ideas?

Running 4.09 intel on Windows XP SP1

I have this problem, too. What I can add is that it seems related to the event of system hybernation. In other words, the message appears every time I restart (after hybernation) the laptop I run BOINC onto.

System is windows 2k pro SP4 on an Armada M700

---

Arielk,
I don't know about the reported problem, although I'm sure I've seen it mentioned before.
Perhaps a search of the forums for "zero error" will give you some answers.

However, you have a worse problem: your computer is seriously under powered!
You would barely be able to finish a wu in the one year time limit even if you let
it run continuously. Which you aren't doing.

CP is a port of a massive program from a 64 bit super computer, not a simple list checking
program like SETI.

See the minimum specs at:
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/tech_faq_boinc.php

Les

Morning (for such it is). I switched my machine off last night with 95% of the WU processed. I switched on this morning to find this error message, and a subsequent message stating that the result was restarting. What steps (if any) can I take to avoid repeating this waste of time and processing capacity?

Cheers,

Moose.

---

> Morning (for such it is). I switched my machine off last night with 95% of the
> WU processed. I switched on this morning to find this error message, and a
> subsequent message stating that the result was restarting. What steps (if any)
> can I take to avoid repeating this waste of time and processing capacity?
>
> Cheers,
>
> Moose.
>
What version of BOINC are you running? Did you suspend and exit BOINC before shutting down? If 4.13 and Yes for your answers...then I've run out of ideas. I had one do this early on when BOINC first started...but no troubles since.

Morning, geophi.

> What version of BOINC are you running? Did you suspend and exit BOINC before
> shutting down? If 4.13 and Yes for your answers...then I've run out of ideas.
> I had one do this early on when BOINC first started...but no troubles since.
>

Yes, I'm running 4.13; but no, I didn't (and never do) suspend and exit before shutting down. The only unusual aspect about last night is that while browsing, I opened a page which prompted Norton to flash up a series of warnings about viruses whereupon I updated and ran an Ad-Aware scan, as well as checking with Spybot, SpywareBlaster and running a full Norton scan. Don't imagine any of these activities would have affected BOINC, though.

Cheers,

Moose.

---

Commiserations if you have lost 95% of a WU.

A backup can help reduce any such losses. If you have one, just copy the backup back to the BOINC folder.

---

Visit BOINC WIKI for help

And join BOINC Synergy for all the news in one place.

Afternoon, crandles.

> Commiserations if you have lost 95% of a WU.
>
> A backup can help reduce any such losses. If you have one, just copy the
> backup back to the BOINC folder.
>

Thanks for the tip. I’ve just searched the site for information as to how to accomplish that. I’ll attempt it this evening, after work. Not knowing why it happened still rankles, though.

Cheers,

Moose.

---

> Morning, geophi.
>
> Yes, I'm running 4.13; but no, I didn't (and never do) suspend and exit before
> shutting down. The only unusual aspect about last night is that while
> browsing, I opened a page which prompted Norton to flash up a series of
> warnings about viruses whereupon I updated and ran an Ad-Aware scan, as well
> as checking with Spybot, SpywareBlaster and running a full Norton scan. Don't
> imagine any of these activities would have affected BOINC, though.
>
>
Early in BOINCing, there were a lot of problems that people thought were related to improper exiting of BOINC. It has been supposed that 4.13 may have helped that situation. However, to be on the safe side, I suspend and exit BOINC before shutting down. A couple power failures have occurred where I couldn't, to no ill effect, but for me better safe than sorry when I have the choice.

General FYI:

I had another one of these pesky errors on a Linux box yesterday. (P4 3.0, 1 Meg dual channel RAM, SuSE Linux 9.0, boinc 4.13) In my experience, it occurs after the second Model of a pair starts and shortly after upload of the five summary files completes. In this case, after TS 58. Not observed with the first of a pair (I can't imagine what difference it makes). Fortunately, restart is automatic and I haven't lose a WU because of it (or because of the "no heartbeat" error).

It seems there is more to the problem than restart after shut-down. (My Linux boxes are rarely shut down -- only when a new kernal is downloaded, and I don't recall seeing the problem then. -- The WinXP box is shut down about once a month, after a pair of Models are uploaded, to go through the defrag/reboot exercise to convince Windoze to behave itself.)

Any other circumstances where this error is experienced?

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

I've seen the same message when I push my computer alot. some other program taking all of the CPU-power and a lot of disk-activity at the same time. Every project that is currently in memory exits and then restarts as they should upon switching only losing the work done since last checkpoint. Doesn't seem too do any real damage...

---

> I have this problem, too. What I can add is that it seems related to the event
> of system hybernation. In other words, the message appears every time I
> restart (after hybernation) the laptop I run BOINC onto.
>
> System is windows 2k pro SP4 on an Armada M700
>
I have similar issues related to recovering from (I believe) power outages
if the battery back up runs off the end and has
to do a shut down. Dell 330 with Win 2K Pro.

I am not sure if the APC is allowing enough time for CP and BOINC
to get closed out.
Unfortunatley I am not here when it happens and I have not been able
to trap the error cause.
Any ideas on helping the CP get closed in time or lengthening the
grace period of the APC is most welcome.

George

---