But it wasn't doing anything else that day.

---

I have occasionally had work units that clock up the elapsed time while the cpu time stays stationary. The only way round it was to reboot the computer which got the work unit past the block and it finished normally.

---

It seemed like my wingman successfully completed the task in spite of getting the same bunch of errors I got : e.g.

sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
etc.

---

XP Pro, Pentium D 3.20MHz, Rosetta and GPUGRID.

While the Rosetta chaos below unfolds, GPUGRID merrily rolls along.

Getting lots 'n' lots of these:



My results can be seen here.

I migrated to BOINC 6.10.17. No change. I detached/attached Rosetta. The first two WUs failed within a minute; computation error. Two more WUs are running right now and are at 15%, but I know they aren't gunna complete.

I've no idea what else to try.

---

XP Pro, Pentium D 3.20MHz, Rosetta and GPUGRID.

While the Rosetta chaos below unfolds, GPUGRID merrily rolls along.

Getting lots 'n' lots of these:



My results can be seen here.

I migrated to BOINC 6.10.17. No change. I detached/attached Rosetta. The first two WUs failed within a minute; computation error. Two more WUs are running right now and are at 15%, but I know they aren't gunna complete.

I've no idea what else to try.

Well - gave up on Rosetta and attached to Einstein. Guess what? Immediate computation errors! I attached to Climate Prediction and that is running fine.

What is it about Rosetta and Einstein on my Pentium D that gives these errors? I have three other PCs happily running Rosetta...

---

What is it about Rosetta and Einstein on my Pentium D that gives these errors? I have three other PCs happily running Rosetta...

Pentium D, is it? How old is that machine?

What is it about Rosetta and Einstein on my Pentium D that gives these errors? I have three other PCs happily running Rosetta...

Pentium D, is it? How old is that machine?

3-1/4 years. It's a Dell Dimension 9100. It's been running BOINC 24/7 since new.

Last june, a month before the warrantee expired, it died. Dell fitted a refurbished MB and PS.

For a year it's been running with 4 gigs of Crucial Ballistix RAM.

Tom

---

3-1/4 years. It's a Dell Dimension 9100....Last june, it died. Dell fitted a refurbished MB and PS.

There's your problem. The capacitors on the motherboard are old and the CPU is generating errors under heavy power load (computation). Time to throw away the system. Get a 2nd opinion if you want, but 'fraid that's what's going on.

I had a system just like this (custom-built). Runs great for normal tasks, but it fails under heavy CPU load. I guess you could try under-clocking the system, but I never found a reason to work at it that hard. Dell's are notorious for expiring with weird symptoms.

if possible, just undervolting might fix it (possibly only temporarily but maybe not) - the power consumption increases with the square of the voltage so a small reduction can make a big difference. If you can't undervolt in the BIOS then you might be able to use RMClock...

3-1/4 years. It's a Dell Dimension 9100....Last june, it died. Dell fitted a refurbished MB and PS.

There's your problem. The capacitors on the motherboard are old and the CPU is generating errors under heavy power load (computation). Time to throw away the system. Get a 2nd opinion if you want, but 'fraid that's what's going on.

I had a system just like this (custom-built). Runs great for normal tasks, but it fails under heavy CPU load. I guess you could try under-clocking the system, but I never found a reason to work at it that hard. Dell's are notorious for expiring with weird symptoms.

---

3-1/4 years. It's a Dell Dimension 9100....Last june, it died. Dell fitted a refurbished MB and PS.

There's your problem. The capacitors on the motherboard are old and the CPU is generating errors under heavy power load (computation). Time to throw away the system. Get a 2nd opinion if you want, but 'fraid that's what's going on.

Well, not wishing to throw it away without trying something, I focused on the RAM. I removed three 1 gig sticks and ran Rosetta with 1 gig for two days without a hiccough. Then I added a second stick and ran for two days; no problems. Then I removed the two sticks and inserted the other two of four; four days sweetness and light. Then I bit the bullet and took it to 4 gigs. All is well!

Funny...

Tom

---

This is no ploblem, just wondering if there are any tasks still running under this app?

---

Have a crunching good day!!

This is no ploblem, just wondering if there are any tasks still running under this app?

Every few months there is, yes. That's why I've left the sticky on it.

---

Rosetta Moderator: Mod.Sense

Thanks I cant remember the last time I had a 5.98 task. I will look out for a 5.98 task.

---

Have a crunching good day!!

On the subject of Rosetta Beta 5.98 I've had two WU error this weekend.

rossmann3x3_k006_008_18101_1902_0 & rossmann3x3_k006_007_18101_1248_0

<core_client_version>6.10.18</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# cpu_run_time_pref: 10800
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
sin_cos_range ERROR: -1.#IND000 is outside of [-1,+1] sin and cos value legal range
# random seed: 1135220
ERROR:: Exit from: .make_pdb.cc line: 244

</stderr_txt>
]]>

1
2
3

Error, Error and Error.
Fortunately, these WUs took only zero seconds of my precious CPU-time :)