I shut down my overclocking program and am running a plain system now. I have other projects running, but why would they interfere with this task? They have their own cores. Right now Rosie is using 2 and the other projects are using the other 2 cores on my cpu.

It is weird that on the ones I bombed that my wingman can run them. One wingman has a Intel Core I3 and I have the Intel Core2 series. He runs Win7 and I run XP.
So why does it bomb on my system, but yet he runs it ok?

I shut down my overclocking program and am running a plain system now. I have other projects running, but why would they interfere with this task? They have their own cores. Right now Rosie is using 2 and the other projects are using the other 2 cores on my cpu.

It is weird that on the ones I bombed that my wingman can run them. One wingman has a Intel Core I3 and I have the Intel Core2 series. He runs Win7 and I run XP.
So why does it bomb on my system, but yet he runs it ok?

Hi Greg

What graphics driver version are you running?

---

I shut down my overclocking program and am running a plain system now. I have other projects running, but why would they interfere with this task? They have their own cores. Right now Rosie is using 2 and the other projects are using the other 2 cores on my cpu.

It is weird that on the ones I bombed that my wingman can run them. One wingman has a Intel Core I3 and I have the Intel Core2 series. He runs Win7 and I run XP.
So why does it bomb on my system, but yet he runs it ok?

Hi Greg

What graphics driver version are you running?

Just the onboard Intel G35 chipset which is up to date.
How would graphics have anything to do with a work unit crashing while crunching on a CPU? I do not have screen saver enabled on my system. And some of these crashes happened while the system was not in use and I was asleep.

I shut down my overclocking program and am running a plain system now. I have other projects running, but why would they interfere with this task? They have their own cores. Right now Rosie is using 2 and the other projects are using the other 2 cores on my cpu.

It is weird that on the ones I bombed that my wingman can run them. One wingman has a Intel Core I3 and I have the Intel Core2 series. He runs Win7 and I run XP.
So why does it bomb on my system, but yet he runs it ok?

Hi Greg

What graphics driver version are you running?

Just the onboard Intel G35 chipset which is up to date.
How would graphics have anything to do with a work unit crashing while crunching on a CPU? I do not have screen saver enabled on my system. And some of these crashes happened while the system was not in use and I was asleep.

The GPU driver version seems to affect whether Rosetta is able to complete tasks successfully: https://boinc.bakerlab.org/rosetta/forum_thread.php?id=5914

---

I shut down my overclocking program and am running a plain system now. I have other projects running, but why would they interfere with this task? They have their own cores. Right now Rosie is using 2 and the other projects are using the other 2 cores on my cpu.

It is weird that on the ones I bombed that my wingman can run them. One wingman has a Intel Core I3 and I have the Intel Core2 series. He runs Win7 and I run XP.
So why does it bomb on my system, but yet he runs it ok?

Hi Greg

What graphics driver version are you running?

Just the onboard Intel G35 chipset which is up to date.
How would graphics have anything to do with a work unit crashing while crunching on a CPU? I do not have screen saver enabled on my system. And some of these crashes happened while the system was not in use and I was asleep.

The GPU driver version seems to affect whether Rosetta is able to complete tasks successfully: https://boinc.bakerlab.org/rosetta/forum_thread.php?id=5914

Not using GPU. Only standard on board video driver and quad core cpu.

I shut down my overclocking program and am running a plain system now. I have other projects running, but why would they interfere with this task? They have their own cores. Right now Rosie is using 2 and the other projects are using the other 2 cores on my cpu.

It is weird that on the ones I bombed that my wingman can run them. One wingman has a Intel Core I3 and I have the Intel Core2 series. He runs Win7 and I run XP.
So why does it bomb on my system, but yet he runs it ok?

Hi Greg

What graphics driver version are you running?

Just the onboard Intel G35 chipset which is up to date.
How would graphics have anything to do with a work unit crashing while crunching on a CPU? I do not have screen saver enabled on my system. And some of these crashes happened while the system was not in use and I was asleep.

The GPU driver version seems to affect whether Rosetta is able to complete tasks successfully: https://boinc.bakerlab.org/rosetta/forum_thread.php?id=5914

Not using GPU. Only standard on board video driver and quad core cpu.

From haivng skim-read that thread a few times I don't think it matters whether you're using the GPU (on other BOINC projects) or not - it sounds like there's a relationship between the video driver, BOINC and Rosetta, although I've only seen mention of Nvidia and AMD gpus.

I don't seem to be having problems on this machine and have BOINC set to 'Suspend GPU' so you could give that a go...

---

I shut down my overclocking program and am running a plain system now. I have other projects running, but why would they interfere with this task? They have their own cores. Right now Rosie is using 2 and the other projects are using the other 2 cores on my cpu.

It is weird that on the ones I bombed that my wingman can run them. One wingman has a Intel Core I3 and I have the Intel Core2 series. He runs Win7 and I run XP.
So why does it bomb on my system, but yet he runs it ok?

Hi Greg

What graphics driver version are you running?

Just the onboard Intel G35 chipset which is up to date.
How would graphics have anything to do with a work unit crashing while crunching on a CPU? I do not have screen saver enabled on my system. And some of these crashes happened while the system was not in use and I was asleep.

The GPU driver version seems to affect whether Rosetta is able to complete tasks successfully: https://boinc.bakerlab.org/rosetta/forum_thread.php?id=5914

Not using GPU. Only standard on board video driver and quad core cpu.

From haivng skim-read that thread a few times I don't think it matters whether you're using the GPU (on other BOINC projects) or not - it sounds like there's a relationship between the video driver, BOINC and Rosetta, although I've only seen mention of Nvidia and AMD gpus.

I don't seem to be having problems on this machine and have BOINC set to 'Suspend GPU' so you could give that a go...

Anything to do with GPU is shut off.
Maybe the new version of Rosie will help with this problem.

I shut down my overclocking program and am running a plain system now. I have other projects running, but why would they interfere with this task? They have their own cores. Right now Rosie is using 2 and the other projects are using the other 2 cores on my cpu.

It is weird that on the ones I bombed that my wingman can run them. One wingman has a Intel Core I3 and I have the Intel Core2 series. He runs Win7 and I run XP.
So why does it bomb on my system, but yet he runs it ok?

Hi Greg

What graphics driver version are you running?

Just the onboard Intel G35 chipset which is up to date.
How would graphics have anything to do with a work unit crashing while crunching on a CPU? I do not have screen saver enabled on my system. And some of these crashes happened while the system was not in use and I was asleep.

The GPU driver version seems to affect whether Rosetta is able to complete tasks successfully: https://boinc.bakerlab.org/rosetta/forum_thread.php?id=5914

Not using GPU. Only standard on board video driver and quad core cpu.

From haivng skim-read that thread a few times I don't think it matters whether you're using the GPU (on other BOINC projects) or not - it sounds like there's a relationship between the video driver, BOINC and Rosetta, although I've only seen mention of Nvidia and AMD gpus.

I don't seem to be having problems on this machine and have BOINC set to 'Suspend GPU' so you could give that a go...

Anything to do with GPU is shut off.
Maybe the new version of Rosie will help with this problem.

Caught Roco while he was reading the 3.24 thread

My understanding is that there is an edge case on some of the runs with the very new hybridize protocol (which are mainly being sent out as CASP9 and rb_ runs) which result in numerical instability and range errors in calculations for a substantial fraction of workunits for particular protein systems. The crashes were happening somewhat randomly, so it makes sense that the next person on the same workunit could complete it fine.

The issue should hopefully be fixed in the new version of Rosetta@home we are currently testing on Ralph@home.