One of my WUs, one of the really long ones, failed with a computational error, and another is having errors, but not auto-failing. I have to manually suspend it in order to let other projects run. Why is only my climateprediction.net not working well? Both WUs have been fine, and only recently have both started giving me problems. I\'m running them on an AMD Athlon X2 6000+ (3.0 x 2), with 2 gigs of RAM and a lot of disc space. Any help or comments would be welcome.

Is the machine overclocked? Running hot?

If you must suspend CPDN to allow other Projects to run, there is a problem with boinc debt. Perhaps you tried CPDN when you joined a year ago but then didn\'t allow work to download? If so, boinc might think it owes CPDN a potload of time.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

OK, it\'s error code is 38...whatever that means. I do not overclock, I have built my own system. I just downloaded the WU about a week ago, it is frozen at 6.6%. I have had some recent system instability, with BOINC\'s visual graphics crashing my computer. Recently this has not happened though. I fear that my northbridge is somehow the source of the problem. It runs at around 45C when under full load from BOINC, which is by no means very hot, but it has crashed around that temp when the visuals for BOINC open, with a unique crash that I have never before seen. (computer 1 year old). I\'m not sure if the length of CPDN\'s WUs is finding even the smallest instability in my system. My BIOS settings are at their defaults, the RAM is underclocked, and nothing else causes disturbances. I\'ll try some more stability tests, but I\'d like to see if I can pinpoint the component causing the problem.

http://i101.photobucket.com/albums/m76/erik212/CPDN_error_38.jpg

^^That\'s a screenshot.

Oh, I don\'t suspend it to make other projects work, its to stop the error, because pressing OK just makes it loop and it keeps coming up.

The usual cause of write failures to pipe_dummy is something else having the file locked. Anti-virus scans are the main culprit and the only known solution is setting up a scan exclusion in your AV program.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

hmm...I restarted and it ran for one more percent before getting the same error. I have no antivirus on my computer, and I haven\'t installed anything new or removed anything. In fact, I turned off Windows Firewall and Installed Battlefield 2, but I get the error even before BF2 was ever run. I\'ll try to see what program is causing the problem. I see what you mean, because when I tried backing the WU up, it said it couldn\'t read the file (permission wise, not data wise).

I can\'t seem to pinpoint the issue. It just seems to pop up some time after the OS boots. Could a registry entry or service cause the problem? I\'ll continue to dig for it. My main project is down because of this...

Bump, please help, I have found no reason for this and even new WUs get the same error, but at seemingly random times after startup.

We don\'t really know what causes the fortran error, none of us moderators have experienced it although we\'ve seen it reported many times.

If you manage to find the cause via experimentation, that would be great.

Do you have anything unusual installed on the machine?

---

I'm a volunteer and my views are my own.
News and Announcements and FAQ

I wonder if the Windows \"Index\" service can cause such a thing too.

If you have that service running (it\'s usually \"on\" if you didn\'t remove it yourself), you could try to exclude the BOINC folder from beeing indexed.

Right-click the BOINC folder in the windows explorer, choose \"Properties\" there and that button for extended properties (I am using a German Win2k, don\'t know the button text for English XP)

There should be one checkbox that allows indexing of this directory. Uncheck that checkbox and confirm (confirm \"including subdirectories\" too).


p.s.: That index service uses resources btw. - without beeing very useful for most users - so if you don\'t search for files containing a certain text too often, you could as well disable that service completely.


One more : HD Defrag while BOINC is running can have not so nice side effects

I wonder if the Windows \"Index\" service can cause such a thing too.

If you have that service running (it\'s usually \"on\" if you didn\'t remove it yourself), you could try to exclude the BOINC folder from beeing indexed.

Right-click the BOINC folder in the windows explorer, choose \"Properties\" there and that button for extended properties (I am using a German Win2k, don\'t know the button text for English XP)

There should be one checkbox that allows indexing of this directory. Uncheck that checkbox and confirm (confirm \"including subdirectories\" too).


p.s.: That index service uses resources btw. - without beeing very useful for most users - so if you don\'t search for files containing a certain text too often, you could as well disable that service completelY.
One more : HD Defrag while BOINC is running can have not so nice side effects

If you are looking for the indexing box in either XP or Vista you will find it by clicking Properties, and then clicking Advanced.

---

I have found that if you bring down BOINC and purge the process in task manager, you can delete the DUMMY file. Once deleted, you can re-start BOINC and it should be okay until the next time.

---