I just noticed last night that both my PC's are getting compute errors with minirosetta, like its bad, real bad, my apologies for all the failed WU's. I usually crunch SETI with no problems and just the other day I decided to crunch Rosetta part time so this all new to me. I've noticed that my Beta's don't fail, but the Mini's fail almost instantly on both PC's. I keep getting an Exit status of -1073741819 (0xc0000005), you can see the full output on Workunit 206160079 if you look under the Task ID 226196786.

So to fix this so far on my Q6600 PC I have:
Updated my bios.
Updated my motherboard drivers in Windows.
Updated my graphics driver.
Updated my DirectX 10.
Made sure graphics are turned off.
Uninstalled and reinstalled BOINC x64 as I am running Vista 64.
Reset the Rosetta project.
Now I am just waiting for memtest86+ to finish, as we speak 40% done, no errors yet.

Then I will try and hopefully crunch a Mini unit successfully. Oh and I do have it set to leave applications in memory when switching, I have 4GB of RAM in my Q6600 PC.

Is anything else I am missing?

Thanks,
E

Me again, memtest passed with no errors, so I fired up BOINC and it downloaded 5 Minirosetta v1.54 work units and they all failed in less then a minute...the same as they did before.

Any ideas?? I don't want to give up on Rosetta as I think it actually makes a difference.

Is anything else I am missing?

Did you try turning off OC?

Different applications react differently on systems. Your system can be fine for SaH or even Memtest ... but not for Rosetta ...

Is anything else I am missing?

Did you try turning off OC?

Different applications react differently on systems. Your system can be fine for SaH or even Memtest ... but not for Rosetta ...

I know this to be a fact as well. I had to much OC and bombed tasks right from the start or they would almost finish and then crash. Einstein had no trouble with my large OC speed but Rosie didn't like it one bit.

Also, ensure the setting of "On multiprocessor systems, use at most ___% of the processors" to 100% in BAM's "AdvancedPreferences|processor usage" tab seems to be a factor.

Hey guys, thanks for help.

I'm not OC'ing my Q6600, everything is running at stock speeds.

But I do have my processor throttled to 75% so that it only uses 3 of the 4 cores for BOINC projects, I will see if changing it to 100% makes a difference, thanks for the tip.

epcorian as you learn more about your outcome, please post to the stickied v1.54 thread. There seems to be some cases where less then 100% has some intermittant problems. Did you configure to use 3CPUs? or a max of 75%? Sounds like the 75%, so did the BOINC Manager actually show 4 tasks in a running status at the same time? And then each of the 4 is suspended briefly to enforce the 75%?

If you could post answers to the above along with what you find when you run at 100% to the other thread, that may help track down the issue.

---

Rosetta Moderator: Mod.Sense

Also, ensure the setting of "On multiprocessor systems, use at most ___% of the processors" to 100% in BAM's "AdvancedPreferences|processor usage" tab seems to be a factor.

Mine is set like this right now: "On multiprocessor systems, use at most 75% of the processors"

Is there a different way of telling it to use just only 3 of 4 cores instead of setting it to 75%?

Regardless, I will change it to use 100% when I get home from work and post back here and in the debug thread.

If it's possible to get working, I would like to only use 3 of 4 cores but I'll worry about that later once we figure out what is going on.

Thanks!

Oh and to answer your question, yes, if I had 4 tasks, 3 would be running and the 4th would be sitting there saying "Waiting to run" or "Ready to start"

I changed it to: "On multiprocessor systems, use at most 100% of the processors" so that it would run completely unthrottled and use all 4 cores. And I let it download minirosetta WU's and it got 5 of them and all failed after 0:33, 1:39, 0:56, 0:38, and last one at 0:51 crashed with a Vista popup saying "minirosetta_1.54_windows_x86_64.exe has stopped working"

I don't know what else to do to get minirosetta working but I have to say that I'm ashamed of looking at my results screen and seeing compute error all over the place! I don't think its fair to this project and all the successful crunchers to keep piling up errors! I seem to be able to crunch Beta WU's okay as long as I don't start messing with settings and starting/stopping the beta crunching so maybe I will just stick with those.

I think Vista 64 is most likely my culprit...

Thanks for the help everyone!

You could save this as cc_config.xml and place in boinc file.

<cc_config>

<options>
<ncpus>3</ncpus>
</options>
</cc_config>

---

I think Vista 64 is most likely my culprit...
Thanks for the help everyone!

I replied to Mod Sense in the other thread about this and hopefully you will get your answer. What I said was that I read somewhere that people with 64 bit OS's had to do something to make the 32 bit workunits work and I was wondering if Rosetta was one of those projects.

---

Thanks guys, I think I've got it working utilizing all 4 cores, but it's still early, I am just crunching my first WU of 8 Mini's...so far it has run 30 minutes without crashing and burning! Much better then the typical 30-60 seconds I was getting before.

My solution, downgrade to the 6.2.19 64-bit of the BOINC client. I'll let you know if I can successfully crunch a mini!

Then I will see if I can restrict to 3 of 4 cores and still successfully crunch.

I think Vista 64 is most likely my culprit...
Thanks for the help everyone!

I replied to Mod Sense in the other thread about this and hopefully you will get your answer. What I said was that I read somewhere that people with 64 bit OS's had to do something to make the 32 bit workunits work and I was wondering if Rosetta was one of those projects.

No, there's nothing you can adjust on the work units. I think what you are thinking of is projects that do not recognize a 64bit OS at all and will not send work.

---

Rosetta Moderator: Mod.Sense

Mine is set like this right now: "On multiprocessor systems, use at most 75% of the processors"

Is there a different way of telling it to use just only 3 of 4 cores instead of setting it to 75%?

Regardless, I will change it to use 100% when I get home from work and post back here and in the debug thread.

If it's possible to get working, I would like to only use 3 of 4 cores but I'll worry about that later once we figure out what is going on.

Thanks!

I run a quad core with Vista 64 and used to have the machine throttled to 50%. It still utilised 4 cores but turned them on and off to run each 50% of the time. It didn't turn any cores off. I checked this with a CPU sidebar gadget.

The <ncpus>3</ncpus> option in cc_config.xml sounds a more likely solution, though I admit I've never used it.

---

Rosetta is one of those projects where the tasks do not seem to take kindly to the use of CPU throttling ... I know when I was using a setting in BOINC to limit to 99% I was having a 40% failure rate.

This is a topic of interest to the testing team, so if you are using CPU throttling, and are having failures, and those failures go away if you turn off the throttle ... well, all I can say is that it worked for me ...

Sid, the ncpus option in the cc_config is intended for test cases where you want to behave as though you have more CPUs then your machine has. For example, allowing a dual core to run 5 tasks at a time. They each just compete for CPU (and memory).

The reccommendation though if you wish to use less then all of the CPUs it to make such a setting in the general preferences on the website, or in the local preferences for each machine.

---

Rosetta Moderator: Mod.Sense

Sid, the ncpus option in the cc_config is intended for test cases where you want to behave as though you have more CPUs then your machine has. For example, allowing a dual core to run 5 tasks at a time. They each just compete for CPU (and memory).

The reccommendation though if you wish to use less then all of the CPUs it to make such a setting in the general preferences on the website, or in the local preferences for each machine.

It also is used to allow the use of CUDA with some versions of BOINC Manager below 6.5.0 for which it is not needed.

So this weekend I installed a fresh copy of XP x64, upgraded it to SP2, installed my x64 version of NOD32 antivirus, told BOINC to use "...use at most 75% of the processors" meaning 3 of 4 cores on my Q6600 and it's crunching Mini's and Beta's without a problem! 1 successful Beta, 5 successful Mini's with 4 more coming down the pipe. So it looks like Mini does not like Vista x64 and on my adventures on google, it turns out that XP x64 is actually based on the Server 2003 code tree while Vista is based on crap. :)

I started running Rosetta this morning on a 64bit Vista machine and all seems to be working well. It's been working well on other projects too. Here is what I'm running:

Core i7 920 CPU
Asus P6T6 WS Revolution motherboard
6Gb DDR3 Triple Channel RAM
Vista Home Premium SP1 64bit

64bit BOINC 6.6.7

As I said, no problems yet and a number of WU's have completed already.

---