Charity Engine / Boinc Manager applications quitting

rwh202 ID: 2552 Posts: 8
07 Aug 2015 07:44 AM


I've just started running CharityEngine again after a long leave of absence but have a problem where I'll often return to my PC and find the application closed. This has happened multiple times with both the Charity Engine app and also when I changed over to the latest BOINC client.

To try and troubleshoot further, I installed it on a second computer (a stock Lenovo desktop) and have experienced the same behaviour.

A few examples are taken from the logs:

04-Aug-2015 01:40:01 [Charity Engine] Starting task wu_1438429502_333711_1 using ce11 version 101 (idle) in slot 8

04-Aug-2015 01:40:01 [Charity Engine] Starting task wu_1438431302_10430_2 using ce10 version 107 (mt) in slot 9

04-Aug-2015 09:49:07 [---] Starting BOINC client version 7.0.76 for windows_x86_64


06-Aug-2015 08:27:48 [Charity Engine] Starting task wu_1438671514_425388_0

06-Aug-2015 08:27:48 [Charity Engine] Starting task wu_1438671902_332990_0

06-Aug-2015 08:27:48 [Charity Engine] Starting task wu_1438671902_333116_0

06-Aug-2015 08:27:48 [Charity Engine] Starting task wu_1438671902_315385_1

06-Aug-2015 09:14:30 [---] Starting BOINC client version 7.4.42 for windows_x86_64


07-Aug-2015 01:20:03 [Charity Engine] Starting task wu_1438671514_584412_0

07-Aug-2015 08:10:26 [---] Starting BOINC client version 7.4.42 for windows_x86_64

In all the cases, the last entry is that a task is being started and then processing stops and then nothing until I relaunch BOINC manager.

There are no error message, nor anything I can find in Event Viewer. Both PCs are set to maximum performance and to never sleep.

Does anyone have any idea what is going on and how to prevent it?



Laurens ID: 636475 Posts: 8
08 Aug 2015 06:37 PM

This is interesting, because I've experienced the same thing when I leave my computer idle for a long time. Only it's not just BOINC that's no longer running when I get back, it's almost all background processes. Things like f.lux, Hamachi, Rivatuner and Steam are all no longer running when I come back to my computer after being away for 24-48 hours. This is on Windows 7.

I also have Charity Engine running on another desktop that I got up and running solely for this purpose. It has Windows 8.1 and is on 24/7. It has hardly any other background processes running, there's Malwarebytes and that's it. On this computer I never find that Charity Engine stopped for seemingly no reason.

I've never looked into it because I'm rarely away from my computer for more than a day but it's still strange. Are other background processes affected for you as well? Could it be that there's a Windows setting that kills programs if the computer is idle for too long? That's what seems to be happening for me.

rwh202 ID: 2552 Posts: 8
09 Aug 2015 09:27 AM

Thanks, some interesting ideas there. I've since installed on a third system and again, it just quit after a period of inactivity. I've not noticed whether any other processes have quit - these are quite clean systems - nothing installed but windows, drivers, chrome, folding (inactive) and now boinc. I might uninstall folding, but it would be embarrassing if that was killing off BOINC!

However, I've now been using the first system - installing some ETL tools and databases etc for a work project and Charity Engine has kept on running throughout (3 days so far). Maybe you're right and 'inactive' processes are getting purged by Windows?

Laurens ID: 636475 Posts: 8
09 Aug 2015 10:52 AM

Any chance it's OS dependent? What version of Windows are you running?

rwh202 ID: 2552 Posts: 8
09 Aug 2015 01:44 PM

WIndows 7 x64 - a mix of Professional and Home Premium.

I've downloaded the windows debug tools and am now monitoring BOINC.exe for silent process exit using gflags - hopefully that'll show something.

rwh202 ID: 2552 Posts: 8
10 Aug 2015 07:06 AM

OK - we have a winner:

"The process 'C:\Program Files\BOINC\boinc.exe' was terminated by the process 'C:\ProgramData\BOINC\projects\\wrapper_26011_windows_intelx86.exe' with termination code 0. The creation time for the exiting process was 0x01d0d2931852ba91."

I don't know whether the wrapper is crashing and taking down BOINC or if it explicitly closing it though.

Rytis Slatkevičius ID: 195 Posts: 56
12 Aug 2015 07:51 AM


we are trying to track down the exact cause of the issue. We do run multiple applications though and that makes it more complicated.

Your log excerpts show various applications starting; do you know if it is always wrapper_26011_windows_intelx86.exe terminating the client, or are there also other applications, such as wrapper_26014_windows_x86_64.exe and possibly others?

Also, does the client exit immediately after starting the app, or after some runtime?

Your help is very appreciated.

rwh202 ID: 2552 Posts: 8
12 Aug 2015 09:01 AM


wrapper_26011_windows_intelx86.exe is the only one I have caught so far but I'll set up monitoring on the other systems to try and check. Although the last entry in the logs is normally 'starting task...', it's not always and I seem to recall that all the tasks were someway in when I restarted BOINC suggesting that processing had been running before it quit.

Thanks for looking into it,