Looks like this one didn't survive a normal File -> Exit of BOINC.

---

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/

My problems didn't start until 5.32. Suddenly, my system goes from almost error free crunching to a variety of errors from read access violations to watch dog shutdowns to solid freezes.

I tried Linux (dual boot) for a while. the first three crunched perfectly. The next thing I know I get a WU halted at 100%, my cpu fan slows to idle and the WU will not upload. I've heard of this happening before.

It is quite unlikely that a hardware failure such as a memory address would go bad just as we upgrade to 5.32 and equally as unlikely that a bad memory addr would cause such a variety of errors. Why would this not happen under linux? I had memory 70% full just to see.

I hope 5.34 goes better.

---

... next thing I know I get a WU halted at 100%, my cpu fan slows to idle and the WU will not upload....

I have had this on both Linux (cli) and Win2k boxes. As you say, only with 5.32

When this has happened to me the result uploaded OK once BOINC has been stopped and restarted. If that did not work, next thing I'd try would be rebooting the OS.

River~~

I don't know if anyone has pointed this out before, but since some of these errors seem to invoke the debugger (most don't, but maybe they should start sending out the .pdb again for users that would like to help debug.

Here
http://boinc.berkeley.edu/app_debug_win.php
is a start of a list Rom Walton created while debugging up to the last stable version od Rosetta@Home (i.e. before the docking)
So maybe some other can look into what's causing the fails on some of them.

---

Team mauisun.org

Hi FluffyChicken, thanks for pointing this out. Actually with the help of Rom Walton, we created a symbol store for Rosetta@Home here and we have added pdb symbols for all the recent R@H updates. The paths information has been defined so that the cilent should be able to download the pdb symbols automatically. This has been working for 5.32. However, I just looked at our symstore and found that the file permissions are not set properly for 5.34 and some newer apps on RALPH. I just corrected the problem and hopefully the pdb symbols will be loaded again if an error occurs. Thanks again for catching it.

I don't know if anyone has pointed this out before, but since some of these errors seem to invoke the debugger (most don't, but maybe they should start sending out the .pdb again for users that would like to help debug.

Here
http://boinc.berkeley.edu/app_debug_win.php
is a start of a list Rom Walton created while debugging up to the last stable version od Rosetta@Home (i.e. before the docking)
So maybe some other can look into what's causing the fails on some of them.

---