I'm using BOINC on Windows XP Prof and Windows 7 Ultimate. Once I noticed some programs are being closed without any reason. Then NOD32 self-protection system alert BOINC.EXE tried to terminate it.

My configuration allow BOINC to operate only when system is in idle. Looks like when I use my computer, BOINC call TerminateProcess() on each child process but for some reason specify wrong process IDs. So instead of killing things like SETI*.exe it kills innocent FAR, LigthAlloy and so on.

What should I do?

// Sorry for my English =_=

Which BOINC version are you using?

---

7.0.25 and then - 7.0.28.

OK, thank you Linda. I have forwarded your thread to the developers.

In the mean time, you may want to turn Leave Applications In Memory on.

---

Thank you!

I hate to pile on, but this explains a lot of what I have seen over the years. Currently I am running BOINC 7.0.38 x64 (non-service mode, since I run GPU projects) on Win7 64-bit. My PC (E8400 CPU on a P45 motherboard) runs 24/7 and is set to never sleep, except for the monitor which turns off after 20 minutes. When I copy a large number of files from one drive to another and wake the monitor up after that time, the copy will be interrupted. But when I uninstall BOINC, the problem goes away and the copy proceeds to its finish.

I have another program called Minute Time (http://www.pc-tools.net/win32/) that gives an alarm after a set time. For times less than the monitor sleep time of 20 minutes, it runs normally. But when I wake the monitor up for times longer than that, I find that the timer has stopped. I have had other problems playing videos over the LAN that freeze up over the years, but it is hard to say whether that is the same problem or not. But a couple of years ago I had to uninstall BOINC entirely to get them to play properly, and even reported that on this forum. (By the way, I always have Leave Applications in Memory enabled).

I hope this gets sorted out, as I can't allow BOINC to do this to my main PC, though I do run BOINC on dedicated PCs (with only Folding@home running otherwise) with no problems.