the WU 6122022 Res-ID 7130438 crashed this night and I don\'t know why !
the second (two 5.03-WU\'s at the same time !) 5.03-WU 6122011 is still running fine. two more WU\'s were/are running on my quad-CPU without problems and enough memory (> 3gig; memtest- and prime95-stable !)
in the night - before the short trickles were generated (about 00:15 instead of 02:40) - I used the taskmanager (no other active programs !) to look at the changing memory-using of the 5.03-WU\'s - I saw, that one 5.03-process resets the CPU-time.
in the message-files I don\'t find any advice.

---

The error was 22, which isn\'t one that\'s very helpfull.
If you saw the cpu time being reset, that model may have been looping. There\'s info on looping here.

---

Backups: Here

I saw the cpu time being reset in the taskmanager - not in boinc ! I think, the program tried to restart 4 times (because there are 4 short trickles) and then exited. Perhaps there are more informations in the 5 uploaded zip-files.

---

The time disappearing in the task manager would probably coincide with an \'exit with zero status\' message on the boinc manager log. Often the zero status messages are harmless, in this case I\'d presume they occurred each time a \'model crashed: \' appears in the error log.

Not a JPEG file: starts with 0x01 0xda

Model crashed: 
Not a JPEG file: starts with 0x01 0xda
Not a JPEG file: starts with 0x01 0xda
Not a JPEG file: starts with 0x01 0xda

Model crashed: 

Model crashed: 

Model crashed: 

Model crashed: 

Model crashed: 
Sorry, too many model crashes! :-(

\'\' doesn\'t mean much when trying to work out what happened!

If you happen to have a backup prior to this crash you could see whether the restored model crashes at the same point or continues.

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ