I figured I'd put our 'idle' E5-2620's to work...
Installed a service-only and was running great.

A few weeks ago, I opted to change the data directory from C:\ProgramData\BOINC to D:\ProgramData\BOINC.
Uninstalled BOINC, rebooted, did a ROBOCOPY, reinstalled and reoboted...

I've done this successfully on 10 other servers, but BOINC consistently pukes on this server. Since it's a non-comissioned server, I was able to do a nuke 'n pave on it. Even after that, I still cannot get BOINC to load.
After the N'nP, I renamed the BOINC data folder so I could get a clean install.

Still crashing on startup.

Now, I'm still installing OS patches to the vanilla install, but that (shouldn't) have caused BOINC to crash identically as it did previously.

Now, prior to the N'nP, I gave .\boinc_master Admin privs, and it the service would start, but some project's tasks would error out w/ 'Computational error' (or something to that effect).

I have not given the account admin access after reinstalling.

Also, I've run memchecker on it and all RAM is peechy-keen.

I've got a stderrdae.txt file with data in it, but to be honest, I have no idea how to attach it.

Any thoughts?

Stupid. Stupid.... STUPID!

This was the first server I migrated the BOINC data directory from.

When I did it, I didn't copy over the permissions properly.

Looked at another server, and found the issue.

.\boinc_admins - Full Control
.\boinc_users - Read & Execute
.\boinc_projects - Special permissions (Traverse folder / execute file) ONLY

Changed permissions, re-enabled the service and started it.
VIOLA!

Just an FYI, but correct options for ROBOCOPY should be:

robocopy C:\ProgramData\BOINC D:\ProgramData\BOINC /MOVE /E /COPYALL

I neglected to use the /COPYALL option... Oops.