Hi,

We've (the mods at CPDN + BBC/CCE) noticed an increase in the number of reports of buffer overruns in Boinc.EXE in the last month or two.

http://www.climateprediction.net/board/viewtopic.php?t=5926

http://www.climateprediction.net/board/viewtopic.php?t=6216

http://www.climateprediction.net/board/viewtopic.php?t=6185

http://www.climateprediction.net/board/viewtopic.php?t=6021

http://bbc.cpdn.org/forum_thread.php?id=5152

http://bbc.cpdn.org/forum_thread.php?id=3375

One person fixed it by moving the files around on the disk (which might indicate a bad sector). Is it the case that the client_state.xml is modified 800,000 times per day? I seem to recall someone saying something like that.

Someone else reported that the same error occurred even if Boinc was started when in 'suspended' mode.

It particularly seems to be associated with Service installs, although not always.

Is this a problem which other projects have been experiencing too? Does anyone have any ideas of why it's occurring? Is there any way to get a stack-trace within Boinc.exe, and if we can, would it be useful? Is there any way to tell *which* buffer is overflowing? Could this be related to the AOL issue? What questions or advice should we be giving, to help resolve the problem? If it's general it might be related to an MS update.

-Cheers,

Mike

---

Hello,
somebody reported me (as Boinc volunteer helper) this problem. He was attached to Seti and Einstein.
Reinstalling Boinc did not help,
but deinstalling Boinc, removing the Boinc directory and reinstalling solved it.

So I think it has something to do with the files which are created by Boinc during processing.

yoyo

---

Germany biggest distributed computing community Rechenkraft.net

My boinc is down right now because of a buffer over run and I didn't know how to fix it. My Computer is in no way associated with AOL. I'm running XP pro SP 2 with a Pentium 4 2.6 and this is the error message that I get

Microsoft Visual C++ Runtime error

Buffer overrun detected

Program: c:\\Program Files\\Boinc\\boinc.exe

A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated.

I'll have to try deleating the entire boinc directory and then reinstalling and see if that fixes it. I'm attached to Seti and to Climateprediction.

---

Udate I uninstalled boinc and the directory. Then I ran disk defrag. Then I rebooted the computer running chkdisk. Finally I reinstalled boinc and attached back to climate prediciton.net and everything seems to be happy and ducky. It meanse that I lost the project for climate prediction that I was working on but such is life.

---

I've sent an email to Dr. A and Rom about this thread.

I'm not sure what further information they'll need, but a good start is BOINC version, OS, install type and attached projects.

---

Kathryn :o)

My version of Boinc is the most recent download from here. My hard drives file system type is NTFS. But thankfully I have the problem fixed lets just hope this monster isn't a hydra and that it's ugly head doesn't reappear

---

My version of Boinc is the most recent download from here. My hard drives file system type is NTFS. But thankfully I have the problem fixed lets just hope this monster isn't a hydra and that it's ugly head doesn't reappear

Um... so what did you do to fix it?

---

I've put a summary of what I've seen reported so far on the following thread (actually I'd intended to put it on THIS thread, but never mind).
http://boinc.berkeley.edu/dev/forum_thread.php?id=1332&nowrap=true#7286

---

So it seems that big std*.txt files are the root cause for this BOINC bug. The next time I will be asked to help for this problem I will suggest first to remove these files.

yoyo

---

Germany biggest distributed computing community Rechenkraft.net

Just got a response from Dr. A about this.

This problem is in the version of BOINC that we made for BBC,
which is pretty old.
I'll bet the problem disappears if they use 5.8.

---

Kathryn :o)

Thanks everyone, I'll make those two suggestions to the people who've complained about the bug, and report back :-)

-Cheers,

Mike

---