Rosetta Randomly Stops

[cx323]

I was wondering why i wasn't poducing as much as usual today so i looked in the taskmanager and saw that 1 thread of rosetta was using 50% of the cpu and the other was using 0%. I restarted boinc and it worked fine for an hour and then it quit again. Does anyone know what might be causing this?

[[XC] DragonOrta]

have you given D2OL WatchDog a try with this yet? I'll try to find the lines that you add to it for you.

.:EDIT:. I found it!

D2OL Xtreme Watch Dog should still work to manage this app, just add the lines

rosetta_4.81_windows_intelx86=IDLE
Boincmgr=IDLE

to the settings file under processes, and if you aren't running D2OL anymore, you can take out the lines
dockwin.exe
gridwin.exe
d2ol.exe

[k0nsl]

This is just a guess based on personal experiance thus so far, so take it not as gospel. I have noticed that when my system is overclocked too much rosetta will become very sensitive and sometimes it stops producing, other times it does produce but the outcome is not valid (it calculates but the WU fails).

-k0nsl

[cx323]

have you given D2OL WatchDog a try with this yet? I'll try to find the lines that you add to it for you.

.:EDIT:. I found it!

D2OL Xtreme Watch Dog should still work to manage this app, just add the lines

rosetta_4.81_windows_intelx86=IDLE
Boincmgr=IDLE

to the settings file under processes, and if you aren't running D2OL anymore, you can take out the lines
dockwin.exe
gridwin.exe
d2ol.exe


thanks for the help. i'll let you know if it works

[Acrazar]

yes be very carefull in stability testing, CPU to high seems to cause the process to quit (internal check maybe) but mem over causes failed WU more than anything else, which concidering how much more scrutiny the R@H WU get and how much longer they take than D2OL candies you cant be as reckless.

In D2OL i could clock stuff up and watch for how many cand i report and how many i get credit for and if it was unstable lower the OC, but in R@H you spend a crap load more time on a WU and waisting those points is not worth it. Test in superpi or prime first as they are alot quicker to point out errors than checking WU results

[STEvil]

just like when 1 copy of prime95 dies and the other keeps going, probably the cpu.

[Rodzilla]

Sound like you don't have your options in R@H setup right. Login at R@H and change your option "Do work while computer is in use?" to YES. Also make sure the "Leave applications in memory while preempted?" is set to YES.

I bet this will solve your problem.