Some tasks are seeing this error, fortunately it is fairly uncommon (although when such problems arise, they are often around for a week or two). The Project Team is always working to eliminate such errors, but as you see one can never been entirely successful at such an effort.

BOINC handles many error cases and can clean things up and report the failure back to the project without user intervention. But I am not aware of a way to get BOINC to handle these hard errors on its own.

Does anyone else know of ways to suppress that pop-up error window?

The old freeware version of PTFB might be a decent workaround to get rid of the message box if it does pop up:

http://majorgeeks.com/PTFB_Push_the_Freakin_Button_d4416.html

Does BOINC start a new instance of Rosetta if one crashes or does it need manual intervention?

Some tasks are seeing this error, fortunately it is fairly uncommon (although when such problems arise, they are often around for a week or two). The Project Team is always working to eliminate such errors, but as you see one can never been entirely successful at such an effort.

BOINC handles many error cases and can clean things up and report the failure back to the project without user intervention. But I am not aware of a way to get BOINC to handle these hard errors on its own.

Does anyone else know of ways to suppress that pop-up error window?

Hey Chile Man -

My gosh, it's the wrong time of year to be shutting my systems down - the temperature outside is supposed to drop down to around 31 (F) tonight and with Rosetta being dead in the water I had to light off the fire place just to keep warm ...

OK, it looks like the CPU is definately throttling. I traced back my work completed and the problem seems to have started when I uninstalled the Intel Active Monitor program. It seems the BIOS started making the decision to throttle when I did that, now it's the Intel program doing it, but it appears to have a higher threshold.

I came home yesterday to find the PC turned off. My wife said it was beeping with an error about being "too hot", which was the Intel software. I increased the warning threshold to 85°C in the software, but this morning I found the R@H process stalled again. The temp seems to maxing out around 73°C with R@H. This dumb Pentium D 920 should not be throttling at that low of a temperature. Apparently, I'm going to have to buy an after-market cooler to tame this beast. I swear, Intel never designed this CPU to run under 100% load 24/7. I'm about ready to toss the thing out the window, lol.

The system is adequately cooled IMO. There's a huge 120mm fan in the bottom of the PS, which is just above the CPU. Then I have a 60mm rear exhaust fan and a front 80mm, all of this in a 100% aluminum case with managed cables. I guess I'll have to do some agressive work here to cool this Pentium D!

Thanks to all that replied!

I have a Pentium D 3Gigrunning 24/7 never gets above 35c

Doesn't run Rossetta at the moment because it stalls.

Sure, idle temp is fairly low, my system idles around 40°C. At least now you know why it stalls.

I'm testing a little program I found on the web (since last night) that controls the throttling. I'm not letting the CPU throttle! It doesn't need to throttle until about 80-85°C, and I'm not running that hot. Last I have checked the system it was running 68-72°C under R@H. If this program works, I'll be happy.

It runs at 35c working on other projects, it's not idle, it's at 100%

OK, it looks like the CPU is definately throttling. I traced back my work completed and the problem seems to have started when I uninstalled the Intel Active Monitor program. It seems the BIOS started making the decision to throttle when I did that, now it's the Intel program doing it, but it appears to have a higher threshold.

I came home yesterday to find the PC turned off. My wife said it was beeping with an error about being "too hot", which was the Intel software. I increased the warning threshold to 85°C in the software, but this morning I found the R@H process stalled again. The temp seems to maxing out around 73°C with R@H. This dumb Pentium D 920 should not be throttling at that low of a temperature. Apparently, I'm going to have to buy an after-market cooler to tame this beast. I swear, Intel never designed this CPU to run under 100% load 24/7. I'm about ready to toss the thing out the window, lol.

The system is adequately cooled IMO. There's a huge 120mm fan in the bottom of the PS, which is just above the CPU. Then I have a 60mm rear exhaust fan and a front 80mm, all of this in a 100% aluminum case with managed cables. I guess I'll have to do some agressive work here to cool this Pentium D!

Thanks to all that replied!

I have a Pentium D 3Gigrunning 24/7 never gets above 35c

Doesn't run Rossetta at the moment because it stalls.

Any ideas as to why the Rosetta processes are stalling?

This is a problem in the BOINC API. David Anderson has debugged this problem and written a fix for this problem, which is inlcuded in the BOINC API 5.8.0. This fix needs a recompile of the science application.
This could also happen with BOINC 5.4.x, but mostly seen if CPU throtteling was used (BOINC client 5.6.x/5.7.x and 5.8.x).

Hummm...that's interesting, thanks. I seem to only have this problem on one PC, which is a bit strange. I'm wondering if it may have something to do with the ATI video driver? That's the most unique characteristic on this PC compared to my others.

No.
The problem occurs only one sometimes on some hosts on some different projects. But on some hosts and projects it happens more often. Mostly, if the science app will be to often suspended.
To include the fix of the BOINC API, the science application must be recompiled.

The BOINC client shows two processes are running, but the time is not incrementing and neither core shows a load in task manager. Shutdown the client and restart, it runs fine....for awhile. Today only ONE process was running on a single core.Restarted BOINC, everything is fine, came back 4-5 hours later to find Rosetta "stalled" again.

Screensaver set to blank, no other running processes except for antivirus (SAV 10.0.1). I know a lot about PC's, so there's no viruses nor malware on the system, it's very clean. Temperatures and voltages are fine, the PC is working perfectly.

Any ideas as to why the Rosetta processes are stalling?

This is a problem in the BOINC API. David Anderson has debugged this problem and written a fix for this problem, which is inlcuded in the BOINC API 5.8.0. This fix needs a recompile of the science application.
This could also happen with BOINC 5.4.x, but mostly seen if CPU throtteling was used (BOINC client 5.6.x/5.7.x and 5.8.x).

All -107 exit codes it looks like. This is one of the primary symptom of PCs that are having problems running with BOINC/Rosetta as the screensaver... yet you said you aren't using the screensaver. Do you display the graphics? (if so, it can be prone to the same problems as the screensaver).

Interesting, that host shows significantly more floating point ops per second then integer.
Measured floating point speed 1411.95 million ops/sec
Measured integer speed 1189.46 million ops/sec

Also interesting, when a task completes normally, you are granted roughly double the credit you claim.

Please let us know the result of your tests tonight.