i don't see any signs of broken OpenCL detection in your BOINC client...i know your startup event log doesn't mention anything about OpenCL, but i believe that's normal - it would probably only mention something about OpenCL in the startup event log if there were actually a problem detecting an OpenCL device. if you scroll a bit more than half-way down
THIS thread, you'll see that i posted my BOINC client's startup event log a few days ago when i was having problems and getting errors w/ the new Separation v1.02 app. notice that its detecting GPU 0 (my HD 4290 IGP) as an OpenCL device, even though its not OpenCL capable...and due to the enumeration mismatches between BOINC and the MW@H application itself, BOINC is also thinks it has to disable GPU 1 (the HD 5870) b/c despite it being the 2nd GPU behind the IGP (GPU 0), it is the
first OpenCL capable GPU in the system. this might not make a whole lot of sense to you, and that's ok b/c you're problem is different than the one i had. i'm just using it as an example of what you'd possibly see in the BOINC startup event log re: OpenCL if the detection was somehow broken.
that being said, i probably won't have more time to do anymore research on it until this evening. in the mean time, read
THIS thread thoroughly...i know that by now its an extremely long and boring thread, but there very well may be advice there that could help you solve your problem.