Out of the last 20 I got 5 errored out at 1300-1450 seconds. (1-111, 2-113, 2-114) The 20 before one errored out (114). This is too many errors to me.

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

I just went through over 700 results done today with not a single error.....anyone else getting errors?

---

Maybe it's specific to my processor or another part of my computer? I haven't done anything but use internet explorer 7. I have Norton's AV on (as always). Not sure what to list except the componets of my pc. Or maybe I'm just darn lucky!

Windows XP Sp2
P4 2.67Ghz
1GB SD DDR Ram
Radeon 9600 (128mb)- video card
WD 120 Gb HDD
Maxtor 200Gb HDD

Boinc 5.10.13
Currently running Rosetta & MilkyWay only.

Norton AntiVirus 2006
IE7

Hope this helps.

Thanks JRenkar for looking.

No prob banditwolf....trying to help you solve your prob here. Have you run any memtests lately? Do you leave app in memory? Is that an HT P4 not being used?

I don't know what to use to run a mem test. Astr._1.13 uses 14-18k of memory when running. I let boinc & mw run how they like. When I see one has froze I close and restart boinc and those run fine. The others either have a pop-up window or just error out with no window. Not sure what 'HT P4' is?

Current bunch only 1 froze so far, 5 have finished.

I don't know what to use to run a mem test. Astr._1.13 uses 14-18k of memory when running. I let boinc & mw run how they like. When I see one has froze I close and restart boinc and those run fine. The others either have a pop-up window or just error out with no window. Not sure what 'HT P4' is?

Current bunch only 1 froze so far, 5 have finished.

Memory usage is not the same as memory quality...bad memory may cause a flaw in one type of application and not another.


Google memory test and you will find a lot of good free tools. HT stands for hyperthreading which a lot of your class computers have. It can be disabled in bios or by the manufacturer. Lets you run 2 units at a time with a typical performance increase in running 2 vs 1.

Do you use the BOINC option of leaving applications in memory?

The memory I am using is 2-512's, one came with it and the other is a PNY brand. (decent brand to me). I will look at doing a memory test. My pc doesn't HT that I know of. I only run one unit at a time. No I don't leave applications in memory when suspended. Usually when I need to suspend I need the perf.

Looking into the memtest and it doesn't seem likely that I have any bad memory. Possibly MW doesn't like the certain ones I have, but they work fine on lots of other applications.

I had one error so far out of 10 completed. (113)

All I can tell you at this point is from almost 4 years experience BOINCing and all the projects in my sig is I had a lot of headaches with frozen and errored out results across most of my projects and applications until I left apps in memory.Since then almost none unless the project or my host has a problem.

With the known bug here of suspending the wu causes a pop-up box error or a not found file means to me that keeping Milkyway in memory may be critical.

---

I shall give it a try when I run more mw wu's.

---

I changed to stay in mem. The first wu still froze. So I had 2 applications of astro_1.13 running. No other probs so far, most of what I got are 104's.

I changed to stay in mem. The first wu still froze. So I had 2 applications of astro_1.13 running. No other probs so far, most of what I got are 104's.

there was a problem with the 104 population file on the server side - it looks like when it crashed last it got corrupted - i fixed the file so that might have been the cause.

I still get the first wu freezeing at 4 secs every time. It does eventually run and complete, usually after the other 19 have run.

I seem to be having a problem and I'm not sure if it's the client or the MilkyWay WUs. Whenever I finish running benchmarks, the tasks from other projects resume but the MilkyWay tasks don't. After the benchmarks I have to exit BOINC and restart it (4.10.30) to get them going again.

@banditwolf-So are you keeping apps in memory? No more errors?

@A/C-Are you keeping apps in memory?

---

@banditwolf-So are you keeping apps in memory? No more errors?

@A/C-Are you keeping apps in memory?

Hi JRenkar. If you mean the setting in the client that says "Leave applications in memory while suspended", no, I don't have that option checked. I don't think it's selected for any of the BOINC projects I'm doing.

I have checked "leave in mem while suspended". This seems to happen with the first wu typically. It's not crashing though, just freezing. I have tried it checked and unchecked today since I've been getting all short wu's and it doesn't seem to make a difference at the moment.

A/C try leaving apps in memory if you want to solve that problem.

A/C try leaving apps in memory if you want to solve that problem.

Thanks for that. I checked the option and after running benchmarks all of the suspended tasks resumed again, including the Milkyway tasks.