The pop-up shown is of concern to you guys I think - a design error in one of the downloaded tasks???
Scenario:
After some time has passed, and my sytem self-locks (via 10-minute screen saver w/blank screen) - On login or even mouse-movement just prior to screen saver start, I am presented this pop-up:



I.E. I just walked away and came back before the screen saver starts (less than 10 minutes), and saw another pop-up stating the same. These show only for a few seconds then disappear with no event log or BOINC log entries.
My guess - one of the tasks I am running has a design flaw 'incorrectly stopping the runtime' as these seem to occur after system is idle, boinc begins/beginning/running?/, then mouse movement or login stops it.

I am not sure which task is causing this - all show 'Suspended - computer in use' - none are 'waiting' or other status'.
My Task list shows the following tasks(X# = # of instances shown): Rosetta X2, Milkyway X2, World Community X3, climateprediction.net X3. Strange, no Seti shown.

System runs 24/7, and temp-monitoring tools showing load temp when BOINC is running (when set to 'Run Always' to test) are far from max.

I have been having random reboots lately, though I'm thinking they might be defrag utility related as there is one event listed stating 'boot time scan completed' immediately after a blue-screen reported event - so perhaps the defrag util caused these - but these pop-ups are not at the same time, and I have seen them at least 4 times over 3+ days now.

My system: Windows 7 on C:, Intel i7 860 on Intel DP55WB Mb, 8GB DDR3, 12+GB free on D: drive where BOINC is running from (BOINC Disk page reports 'free, available to BOINC 6.15GB'). System is set to 'Run based on preferences'(thus idle time only, all cpus and near 98%cpu I think?), SuspendGPU (since the task / benchmark suggests mine is not fast enough for the tasks to use it - so I set to Suspend GPU), and network activity always available (DSL via T100 ethernet).

---

It's not a BOINC error, it's at minimum a Microsoft one, but because it originates in the D:\Boinc\projects... directory, it's automatically a project error. For you to figure out which one, but speaking from past experience, it's most probably CPDN that's giving that error.

---