My compuer is freezing on one of these two WUs - 19746278 or 19737574. It's happened several times today. I'd come into the room, note that the graphics weren't animated, the steps weren't incrementing, and the clock would be stopped. I'd move the mouse (I have it configured to work on the project only when I'm not using the machine), and would get a notice that there was an error and would I like to report to MicroSoft. Next time, I'll get a screenshot.

Bandit's Mom

---

It is possible that there is a background task running(disk defrag, virus check, etc) that is preventing your system from becoming fully idle. This of course would also prevent BOINC from processing any work.

Nope - the only other things I have open are Word (x2), Excel (x2), Reference Manager, and a Mah Jongg game program.

Here's the text of the error message: "rosetta_5.22_windows_intelx86.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

Bandit's Mom

---

I get the following report with the new 5.22:

Result ID 23395831
Name t306__CASP7_JUMPRELAX_SAVE_ALL_OUT_BARCODE_hom001__656_21236_0
Workunit 19711334
Created 8 Jun 2006 22:11:53 UTC
Sent 8 Jun 2006 23:44:52 UTC
Received 9 Jun 2006 11:22:33 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 246538
Report deadline 15 Jun 2006 23:44:52 UTC
CPU time 21089.578125
stderr out <core_client_version>5.3.12.tx36</core_client_version>
<stderr_txt>
# random seed: 1831515
# cpu_run_time_pref: 21600
# DONE :: 1 starting structures built 21 (nstruct) times
# This process generated 21 decoys from 21 attempts


BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...

</stderr_txt>


Validate state Valid
Claimed credit 71.993372528454
Granted credit 71.993372528454
application version 5.22

In other post I have see that someone also reported that Watchdog has shutting down the process.

Regards,
Ricardo

---

I get the following report with the new 5.22:

Result ID 23395831
Name t306__CASP7_JUMPRELAX_SAVE_ALL_OUT_BARCODE_hom001__656_21236_0
Workunit 19711334
Created 8 Jun 2006 22:11:53 UTC
Sent 8 Jun 2006 23:44:52 UTC
Received 9 Jun 2006 11:22:33 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 246538
Report deadline 15 Jun 2006 23:44:52 UTC
CPU time 21089.578125
stderr out <core_client_version>5.3.12.tx36</core_client_version>
<stderr_txt>
# random seed: 1831515
# cpu_run_time_pref: 21600
# DONE :: 1 starting structures built 21 (nstruct) times
# This process generated 21 decoys from 21 attempts


BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...

</stderr_txt>


Validate state Valid
Claimed credit 71.993372528454
Granted credit 71.993372528454
application version 5.22

In other post I have see that someone also reported that Watchdog has shutting down the process.

Regards,
Ricardo

This is a normal shutdown for a successfully completed workunit.

The note regarding the watchdog is just to identify that now that the work unit has finished, the watchdog function is being closed down as well.

---

Regards,
Bob P.

I get the following report with the new 5.22:

Result ID 23395831
Name t306__CASP7_JUMPRELAX_SAVE_ALL_OUT_BARCODE_hom001__656_21236_0
Workunit 19711334
Created 8 Jun 2006 22:11:53 UTC
Sent 8 Jun 2006 23:44:52 UTC
Received 9 Jun 2006 11:22:33 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 246538
Report deadline 15 Jun 2006 23:44:52 UTC
CPU time 21089.578125
stderr out <core_client_version>5.3.12.tx36</core_client_version>
<stderr_txt>
# random seed: 1831515
# cpu_run_time_pref: 21600
# DONE :: 1 starting structures built 21 (nstruct) times
# This process generated 21 decoys from 21 attempts


BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down...

</stderr_txt>


Validate state Valid
Claimed credit 71.993372528454
Granted credit 71.993372528454
application version 5.22

In other post I have see that someone also reported that Watchdog has shutting down the process.

Regards,
Ricardo

This is a normal shutdown for a successfully completed workunit.

The note regarding the watchdog is just to identify that now that the work unit has finished, the watchdog function is being closed down as well.

Noted and thanks Bob for your clarification

Regards
Ricardo

---

I've turned the screensaver off on the Control Panel - is there something I should do in my BOINC preferences? (Color me ignorant, and what I read isn't staying with me at the moment.) You should be able to "see" my computer now, unless there's something else I should do. "... provide a link to the reported results in your Stats list ..." Not sure how to do this.

Bandit's Mom

There was a problem with the screen saver on some Windows systems with version 5.16. This was supposed to be fixed in the new release. Have you tried running BOINC with the screen saver turned off?

In order to assist you you will either have to provide a link to the reported results in your Stats list, or make your computer visible. Currently your computers are hidden so I cannot look up any of your results to see the actual errors.

You can make your computers visible from your preferences without risk to your computer security. If you want to see the kind of information others might see, you can clink on any other user in the forums, and then clink on the link to view their computers.

Of course the system will allow you to see more information on your own systems than it would reveal to others.

---

...You should be able to "see" my computer now, unless there's something else I should do.

They still show "hidden". In your Rosetta preferences, select YES for the question "Should Rosetta@home show your computers on its web site". More details here.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

It's selected as "yes." Maybe it needed time to implement in the system. Maybe you could try again?

Bandit's Mom

They still show "hidden". In your Rosetta preferences, select YES for the question "Should Rosetta@home show your computers on its web site".

---

It's selected as "yes." Maybe it needed time to implement in the system. Maybe you could try again?

Did you hit the "Update preferences" button at the bottom of the screen? I just looked again and it still shows as "hidden".

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

I went back to look and it was saved as "yes," but hit the "Update" button again, just for giggles and grins. Maybe it didn't take the first time around.

Bandit's Mom

Did you hit the "Update preferences" button at the bottom of the screen? I just looked again and it still shows as "hidden".

---

It's not only possible, it's probable that IE was loaded. With the BOINC screensaver off, I'm not certain that I would be able to tell that there was a problem as quickly, but am willing to give it a go.

I'm going to switch my computer back to "hidden."

Thanks for your help.

Bandit's Mom

... but is there any chance you had left your browser loaded when the problem occurred?

My best guess right now is that if you set your screen saver to something other than BOINC or turn it off (from what I read you already did that) the problem may go away. If it does could you please let us know? We are trying to fix that particular issue, and the programmers thought they had it under control. We need to know if they do not.

---

Hello Moderator9

I pulled a client error on Work Unit 19677012 (the result is at https://boinc.bakerlab.org/rosetta/result.php?resultid=23357465), with exit code -1. Client messages for the error began with, "rosetta not responding to screensaver, exiting"

Then again on WU 19684873 (result link https://boinc.bakerlab.org/rosetta/result.php?resultid=23366061). Exit code was again -1, client-side messages once again report, "rosetta notresponding to screensaver, exiting".

The first was a 5.16 client, the second was with a 5.22. I'm not sure the screensaver bug is completely dead yet?

Cheers,
Alan

---

Possible problem with a t299_CASP7 work unit (link to WU). Was a happy camper, then at step 370K+ on Model 6 my CPU dropped from 100% to nothing, and graphics display showed no progress. Didn't write down the stuck step number, sorry.

Suspend on that task released the waiting next, which drove the CPU back to full load. Suspended task #2 and resumed #1, but it still didn't seem to grab any CPU.

For lack of knowing any better (new user), I shutdown BOINC and restarted, which I think I understand to mean that the task resumes at the previous checkpoint (model boundary)? It is now running again.

What is accepted practice if it hangs up again, please? Do I wait for some watchdog abort, or manually abort it? I don't really care about credits, I'll take whatever action provides the best feedback about the failure. Thanks!

---

see above

---

What is accepted practice if it hangs up again, please? Do I wait for some watchdog abort, or manually abort it? I don't really care about credits, I'll take whatever action provides the best feedback about the failure. Thanks!

Wait and don't abort. It will finish after "completion" in maximum an hour. Rosetta waits for the watchdog to shut down. It was something introduced in 5.19 for better debugging but reported over at RALPH and supposedly fixed in 5.22. It is very good that you report this here.
If you happen to observe this again please check whether the graphics show 100% as well or something lower and make a screenshot from the graphics window in "idling" state.

---

The Fatal Winows Error Bug is still with us, I'm afraid. wuid=19791659

Result ID 23483927
Name t309__CASP7_ABRELAX_SAVE_ALL_OUT_nohistag_hom001__661_7645_0
Workunit 19791659
Created 9 Jun 2006 11:23:04 UTC
Sent 9 Jun 2006 12:59:31 UTC
Received 10 Jun 2006 19:23:54 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status -1073741811 (0xc000000d)
Computer ID 212252
Report deadline 16 Jun 2006 12:59:31 UTC
CPU time 28426.171875
stderr out <core_client_version>5.4.9</core_client_version>
<message>
- exit code -1073741811 (0xc000000d)
</message>
<stderr_txt>
# cpu_run_time_pref: 28800
# random seed: 1655106

</stderr_txt>


Validate state Invalid
Claimed credit 109.225790694355
Granted credit 0
application version 5.22

Hi Alan:

Thanks for reporting. There seem to be numerous little issues with the screensaver, and we've been trying to track them down one-by-one over on the test project, ralph. But I haven't seen a lot of problems like the one you describe -- has it happened in previous work units before this double batch? I wonder if something went haywire with the core boinc application -- you may need to restart.

Hello Moderator9

I pulled a client error on Work Unit 19677012 (the result is at https://boinc.bakerlab.org/rosetta/result.php?resultid=23357465), with exit code -1. Client messages for the error began with, "rosetta not responding to screensaver, exiting"

Then again on WU 19684873 (result link https://boinc.bakerlab.org/rosetta/result.php?resultid=23366061). Exit code was again -1, client-side messages once again report, "rosetta notresponding to screensaver, exiting".

The first was a 5.16 client, the second was with a 5.22. I'm not sure the screensaver bug is completely dead yet?

Cheers,
Alan

---

Hi mmciastro... yes, we know its still there. You might be happy to know that the error -1073741811 (0xc000000d) is currently number one on our lists of things to kill. Its been the most common error for a while, but Rom only now has come up with a hypothesis for what the cause might be. He has just put in some extra debugging stuff on ralph to track it down -- maybe that will let us unravel this puzzle!

The Fatal Winows Error Bug is still with us, I'm afraid. wuid=19791659

Result ID 23483927
Name t309__CASP7_ABRELAX_SAVE_ALL_OUT_nohistag_hom001__661_7645_0
Workunit 19791659
Created 9 Jun 2006 11:23:04 UTC
Sent 9 Jun 2006 12:59:31 UTC
Received 10 Jun 2006 19:23:54 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status -1073741811 (0xc000000d)
Computer ID 212252
Report deadline 16 Jun 2006 12:59:31 UTC
CPU time 28426.171875
stderr out <core_client_version>5.4.9</core_client_version>
<message>
- exit code -1073741811 (0xc000000d)
</message>
<stderr_txt>
# cpu_run_time_pref: 28800
# random seed: 1655106

</stderr_txt>


Validate state Invalid
Claimed credit 109.225790694355
Granted credit 0
application version 5.22

---

Hi mmciastro... yes, we know its still there.

It's only a problem for certain video cards, .net, whatever it is. If regular users who get this, turn OFF the screensaver, they'll never see it until it's fixed. I'm in direct communication with Rom on this bug, just FYI. I happen to have a machine, that regularly gets this error (lucky me, and I guess, lucky Rosetta/Rom}.

tony

Hi Alan:

Thanks for reporting. There seem to be numerous little issues with the screensaver, and we've been trying to track them down one-by-one over on the test project, ralph. But I haven't seen a lot of problems like the one you describe -- has it happened in previous work units before this double batch? I wonder if something went haywire with the core boinc application -- you may need to restart.

Rhiju,

Work units before the failures and after were completed based on a look at my results. I may have pulled a boinc restart somewhere in there ...

I'm pitching this as an employee contribution/team-effort project at one of my customer sites, and the three of us who are the test cases have been grabbing our volunteer minutes here and there getting our sample desktops running, to demonstrate safety (at least lack of harm and impact on the "real work") and stability.

When I saw the comments about screen saver issues on the forum and noticed my failures, I may have restarted boinc in a quick-and-dirty quest for a fix.

I set the test machines to not use the screen saver over the weekend, but if there is a better procedure for providing debugging information (i.e., "run the screensaver and do the following if you get another error"), please let me know.

Cheers,
Alan

---